Holy mother of... that $18,000 rig is over the top overkill lol. Geez must be nice to have .. If I ever win the lotto I would buy one for each of the developers here in the Triumph Forums
The Following 2 Users Say Thank You to MediocreBadGuy For This Useful Post:
That is a leaked touchwiz ICS ROM for the ATT Galaxy Note. Doesn't come with any source code, and we share share no hardware with the Note, so it does us no good.
The Following User Says Thank You to NateMckn For This Useful Post:
hey, I know we have a snapdragon proccessor, a guy has recently output a set of open source drivers called freedreno. I thought this might help out, or at least be worth a shot if someone can compile the driver. It looks like only 2-d acceleration is working right now, but it might be interesting to see if it even works for the triumph.
Is there another development thread for this phone? Is anyone actually even developing? Ever since Isaac and Tickerguy left, the community has been slowly dying. I think it's time for me to switch to the Galaxy Nexus.
__________________
Stand in the ashes of a trillion dead souls, and ask the ghosts if honor matters. The silence is your answer.
-Javik
The Following 2 Users Say Thank You to tusing For This Useful Post:
Is there another development thread for this phone? Is anyone actually even developing? Ever since Isaac and Tickerguy left, the community has been slowly dying. I think it's time for me to switch to the Galaxy Nexus.
Well actually, the reason they were booming in development on this phone was because everything / every fix / every new rom for this phone was new, now that we dont have many fixes to uncover, developers are figuring out ways to make it faster/better now which takes more time (pretty sure) to do so thats why it seems sort of slow, most roms are near completion as well. Bug fixes take a lot of time too, so try being a little more patient with them
The Following User Says Thank You to enzilla For This Useful Post:
"Xperia arc, Xperia PLAY, Xperia neo, Xperia mini, Xperia mini pro, Xperia pro, Xperia active and Sony Ericsson Live with Walkman will receive their scoop starting from the end of May/early June*."
From what I understand, the Xperia PLAY uses our SOC, so porting it may work. Though I'm sure it would need alot of elbow grease.
Well actually, the reason they were booming in development on this phone was because everything / every fix / every new rom for this phone was new, now that we dont have many fixes to uncover, developers are figuring out ways to make it faster/better now which takes more time (pretty sure) to do so thats why it seems sort of slow, most roms are near completion as well. Bug fixes take a lot of time too, so try being a little more patient with them
I think the derth of development has more to do with T-Mobile coming out with an affordable roaming pre paid plan than anything else. VM lost a lot of it's value prop when that came out. Why get a Triumph and only get Sprint coverage when you can get a Nexus (or any GSM phone you want) and roam?
The Following User Says Thank You to lanceg For This Useful Post:
as you might not know
but "tj_style is on his way to fix cm9 camera problem"
so we can hope for a fix soon..
he is currently busy with other devices but will provide a full rom when he is done, currently he is working on cam fix only
Sort of... It looks like tj_style has the camera preview working with camera fx and other 3rd party camera apps. However, when the image is taken and saved it becomes distorted. This is certainly progress though!
The Following User Says Thank You to PieFromTheSky For This Useful Post:
as you might not know
but "tj_style is on his way to fix cm9 camera problem"
so we can hope for a fix soon..
he is currently busy with other devices but will provide a full rom when he is done, currently he is working on cam fix only
This is good to hear. Tj_style is a genius. And once he fixes camera, we need to get him to fix hdmi.
I am sure he could do it in like an hour. He fixed it for the andro-id rom which is GB based. ICS already has support for it so it would be easier.
One step at a time though
The Following User Says Thank You to wsimon For This Useful Post:
both latest cm7 & 9 are using .35 vm 3g split based kernel, that can also boot miui ports
but a lot of custom kernel stuff is missing, so if you guys can update then we could get a good .35 custom kernel
for updating first you have to update bootloader like in the case with samsung phones by flashing a base kernel rom http://forum.xda-developers.com/showthread.php?t=1437512
kernel source is same for fih_fb0 only radio is different for cdma users & some touchscreen model difference
The Following 2 Users Say Thank You to nitindeck For This Useful Post:
Why don't you do it since it's so easy?! Mantera already said that ideos x6 variant 2.6.35 kenel was giving us random reboots, which are hard to fix since their random and unpridictable. Since you believe it is so easy, patch the kernel to 2.6.35 then we'll follow your example and patch to 2.6.35.14.
Our greatest devs Isaac and TG left us, the original life of the Triumph, and we are scraping by with the devs we have now. The devs we have left don't have the experience like Tj_style, Isaac, or TG; so stop talking crap unless your able to help the cause instead of unmotivating the cause. We are trying to get farther, even though it's a slow pace, we are gonna reach the finish line somehow; but the devs of the Triumph don't need small people who can't do it themself nagging them. This is why devs leave community, because of the trolls and the negative people...
__________________
I Don't ASK You For Cash, So Atleast Hit My Thanks Button Everytime You See A Good Post... ~~~~ \/My Wish List\/
~Faster Internet~
~55$ dollar plan~ ~64GB SD Card~
Last edited by Austrie; April 25th, 2012 at 01:55 AM.
The Following 4 Users Say Thank You to Austrie For This Useful Post:
Why don't you do it since it's so easy?! Mantera already said that ideos x6 variant 2.6.35 kenel was giving us random reboots, which are hard to fix since their random and unpridictable. Since you believe it is so easy, patch the kernel to 2.6.35 then we'll follow your example and patch to 2.6.35.14.
Our greatest devs Isaac and TG left us, the original life of the Triumph, and we are scraping by with the devs we have now. The devs we have left don't have the experience like Tj_style, Isaac, or TG; so stop talking crap unless your able to help the cause instead of unmotivating the cause. We are trying to get farther, even though it's a slow pace, we are gonna reach the finish line somehow; but the devs of the Triumph don't need small people who can't do it themself nagging them. This is why devs leave community, because of the trolls and the negative people...
calm down bro.. i wasn't into hurt or have some negative feeling for devs,
i don't know about the reboots prob. on truimph by new kernel, but yes i have successfully ported miui gb. to new kernel without any bugs (i'll be posting it tomorrow)
i don't know about kernel modding atm but m learning slowly..
calm down bro.. i wasn't into hurt or have some negative feeling for devs,
i don't know about the reboots prob. on truimph by new kernel, but yes i have successfully ported miui gb. to new kernel without any bugs (i'll be posting it tomorrow)
i don't know about kernel modding atm but m learning slowly..
For what phone did u port miui gb with new kernel ?
For what phone did u port miui gb with new kernel ?
i used miui ideos x5 as base
there are not enough roms available for .35 because of the lack of custom kernel, now people have atleast an option if they want to update
both latest cm7 & 9 are using .35 vm 3g split based kernel, that can also boot miui ports
but a lot of custom kernel stuff is missing, so if you guys can update then we could get a good .35 custom kernel
for updating first you have to update bootloader like in the case with samsung phones by flashing a base kernel rom [ROM] Stock 2.3.5 from Taiwan Sharp SH8188U - xda-developers
kernel source is same for fih_fb0 only radio is different for cdma users & some touchscreen model difference
Also, maybe try adding these libs to the proprietary? MAybe taking them from froyo.
\system/lib/liboemcamera.so \obj/lib/liboemcamera.so \system/lib/libmmipl.so \system/lib/libmmjpeg.so \obj/lib/libmmjpeg.so \obj/lib/libmikecamera.so \system/lib/libmikecamera.so \obj/lib/libcamera_client.so \system/lib/libcamera_client.so \obj/lib/libcameraservice.so \system/lib/libcameraservice.so \obj/lib/hw/camera.thunderc.so \system/lib/hw/camera.thunderc.so
/hw/camera.thunderc.so & \system/lib/hw/camera.thunderc.so are not part of our libs for the camera. The usb won't make a difference for the camera unless you are talking the camera stub. While I am working on CM7 g60 I am also trying some more stuff on the camera. So far I am 0/2 on builds.
Currently trying another build with some more edits. I really need to get some more ram and another CPU so I can crank on the build, it's taking about an hour on my machine for CM9 and about 30 mins for CM7. I don't expect to solve the camera issue but it can't hurt to keep trying
Also, maybe try adding these libs to the proprietary? MAybe taking them from froyo.
\system/lib/liboemcamera.so \obj/lib/liboemcamera.so \system/lib/libmmipl.so \system/lib/libmmjpeg.so \obj/lib/libmmjpeg.so \obj/lib/libmikecamera.so \system/lib/libmikecamera.so \obj/lib/libcamera_client.so \system/lib/libcamera_client.so \obj/lib/libcameraservice.so \system/lib/libcameraservice.so \obj/lib/hw/camera.thunderc.so \system/lib/hw/camera.thunderc.so
Isaac had it set to false in the beginning. Then I vaguely remember seeing someplace in one of the repos that call for it to be set to false but I don't remember exactly where though.
As for the libs, we either have most of them in the vendor repo already or they are built during the build; except for \obj/lib/hw/camera.thunderc.so \system/lib/hw/camera.thunderc.so which are specifically built for that particular board. Ours would be something like camera.msm7x30.so, etc. which our repo is already set to build.
Edit: If you want to change it to try and try a build, go ahead. The worst that could happen is you get an error during the build or it doesn't make a difference.
Here is my current logcat from ICS with my applied changes. If anyone wants to chime in.
V/CameraHolder( 1236): open camera 0
E/CameraService( 123): Camera HAL module not loaded
E/CameraHolder( 1236): fail to connect Camera
E/CameraHolder( 1236): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 1236): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 1236): at android.hardware.Camera.<init>(Camera.java:320)
E/CameraHolder( 1236): at android.hardware.Camera.open(Camera.java:280)
E/CameraHolder( 1236): at com.android.camera.CameraHolder.open(CameraHolder. java:131)
E/CameraHolder( 1236): at com.android.camera.Util.openCamera(Util.java:267)
E/CameraHolder( 1236): at com.android.camera.Camera$4.run(Camera.java:1121)
E/CameraHolder( 1236): at java.lang.Thread.run(Thread.java:856)
Device(s): OV- MIUIgb with Suave HD theme, MT- AOKP with my own theme
Carrier: Not Provided
Thanks: 102
Thanked 507 Times in 185 Posts
Quote:
Originally Posted by g60madman
Here is my current logcat from ICS with my applied changes. If anyone wants to chime in.
V/CameraHolder( 1236): open camera 0
E/CameraService( 123): Camera HAL module not loaded
E/CameraHolder( 1236): fail to connect Camera
E/CameraHolder( 1236): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 1236): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 1236): at android.hardware.Camera.<init>(Camera.java:320)
E/CameraHolder( 1236): at android.hardware.Camera.open(Camera.java:280)
E/CameraHolder( 1236): at com.android.camera.CameraHolder.open(CameraHolder. java:131)
E/CameraHolder( 1236): at com.android.camera.Util.openCamera(Util.java:267)
E/CameraHolder( 1236): at com.android.camera.Camera$4.run(Camera.java:1121)
E/CameraHolder( 1236): at java.lang.Thread.run(Thread.java:856)
You know, it's funny. I'm building a ROM from source right now and it stopped at this part:
Unfortunately, I do not have the time to try and merge his developments into your source; however, out of almost all things I have researched, this seems to be most promising in relation to the Triumph. The camera for the Venus2 seems to be the same as ours except for the facts that it has dual LED flashes and no front facing camera. Maybe you have the time to check it out and pass on your thoughts. Until then, I'll try to find time to work it in myself and let you know hoe it goes.
Unfortunately, I do not have the time to try and merge his developments into your source; however, out of almost all things I have researched, this seems to be most promising in relation to the Triumph. The camera for the Venus2 seems to be the same as ours except for the facts that it has dual LED flashes and no front facing camera. Maybe you have the time to check it out and pass on your thoughts. Until then, I'll try to find time to work it in myself and let you know hoe it goes.
I don't have a lot of extra time either atm. But we'll see. thanks.
I don't know if this would be possible to port, but its awesome And thanks devs for all the work you've done to make this phone what it should have been out of the box
Device(s): OV- MIUIgb with Suave HD theme, MT- AOKP with my own theme
Carrier: Not Provided
Thanks: 102
Thanked 507 Times in 185 Posts
Hey mantera, do you have your own hardware/qcom/gps?
Mine isn't want to compile it..
Code:
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_ni.h:55: warning: 'loc_eng_ni_callback' initialized and declared 'extern'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_ni.h:55: error: 'rpc_loc_event_mask_type' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_ni.h:56: error: expected primary-expression before 'const'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_ni.h:57: error: initializer expression list treated as compound expression
In file included from hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.h:50,
from hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:62:
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:34: warning: 'loc_eng_callback_log_header' initialized and declared 'extern'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:34: error: 'rpc_loc_client_handle_type' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:35: error: 'rpc_loc_event_mask_type' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:36: error: expected primary-expression before 'const'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:37: error: initializer expression list treated as compound expression
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:40: warning: 'loc_eng_callback_log' initialized and declared 'extern'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:40: error: 'rpc_loc_event_mask_type' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:41: error: expected primary-expression before 'const'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:42: error: initializer expression list treated as compound expression
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:44: warning: 'loc_get_event_name' initialized and declared 'extern'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng_log.h:44: error: 'rpc_loc_event_mask_type' was not declared in this scope
In file included from hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:62:
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.h:82: error: 'rpc_loc_client_handle_type' does not name a type
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.h:99: error: 'rpc_loc_event_mask_type' does not name a type
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.h:108: error: 'rpc_loc_server_connection_handle' does not name a type
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:97: error: 'rpc_loc_client_handle_type' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:98: error: 'rpc_loc_event_mask_type' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:99: error: expected primary-expression before 'const'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:99: error: initializer expression list treated as compound expression
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp: In function 'int loc_eng_init(GpsCallbacks*)':
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:266: error: 'struct loc_eng_data_s_type' has no member named 'loc_event'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:291: error: 'rpc_loc_event_mask_type' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:291: error: expected ';' before 'event'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:299: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:299: error: 'event' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:299: error: 'loc_open' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:300: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:307: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp: In function 'int loc_eng_deinit()':
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:345: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:345: error: 'loc_close' cannot be used as a function
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp: In function 'int loc_eng_start()':
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:441: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:441: error: 'loc_start_fix' cannot be used as a function
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp: In function 'int loc_eng_stop()':
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:504: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:504: error: 'loc_stop_fix' cannot be used as a function
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp: In function 'int loc_eng_set_position_mode(GpsPositionMode, GpsPositionRecurrence, uint32_t, uint32_t, uint32_t)':
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:574: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:597: error: 'struct rpc_loc_fix_criteria_s_type' has no member named 'valid_mask'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:599: error: 'struct rpc_loc_fix_criteria_s_type' has no member named 'min_interval'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:603: error: 'struct rpc_loc_fix_criteria_s_type' has no member named 'min_interval'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:604: error: 'struct rpc_loc_fix_criteria_s_type' has no member named 'valid_mask'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:609: error: 'struct rpc_loc_fix_criteria_s_type' has no member named 'min_interval'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:612: error: 'struct rpc_loc_fix_criteria_s_type' has no member named 'preferred_accuracy'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:613: error: 'struct rpc_loc_fix_criteria_s_type' has no member named 'valid_mask'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:616: error: 'struct rpc_loc_fix_criteria_s_type' has no member named 'preferred_response_time'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:617: error: 'struct rpc_loc_fix_criteria_s_type' has no member named 'valid_mask'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:630: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:634: error: 'loc_eng_ioctl' cannot be used as a function
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp: In function 'int loc_eng_inject_time(GpsUtcTime, int64_t, int)':
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:676: error: 'struct rpc_loc_assist_data_time_s_type' has no member named 'time_utc'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:677: error: 'struct rpc_loc_assist_data_time_s_type' has no member named 'time_utc'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:678: error: 'struct rpc_loc_assist_data_time_s_type' has no member named 'uncertainty'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:681: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:685: error: 'loc_eng_ioctl' cannot be used as a function
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp: In function 'int loc_eng_inject_location(double, double, float)':
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:725: error: 'struct rpc_loc_assist_data_pos_s_type' has no member named 'valid_mask'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:744: error: 'struct loc_eng_data_s_type' has no member named 'client_handle'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:748: error: 'loc_eng_ioctl' cannot be used as a function
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp: At global scope:
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:973: error: redefinition of 'int32 loc_event_cb'
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:97: error: 'int32 loc_event_cb' previously defined here
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:973: error: 'rpc_loc_client_handle_type' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:974: error: 'rpc_loc_event_mask_type' was not declared in this scope
hardware/qcom/gps/loc_api/libloc_api_50001/loc_eng.cpp:975: error: expected primary-expression before 'const'
make: *** [out/target/product/triumph/obj/SHARED_LIBRARIES/gps.triumph_intermediates/loc_eng.o] Error 1
15Likes
~Faster Internet~
MT Dev's
