• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [DEV] WIP CM9 (Camera) [updated 2/23/2013]

Can you use the GPS in something else? If so, maybe you can download Scout or something like it and use that instead? I use foursquare all the time.
 
Question: Is the encryption option for CM9 fully functional?

I have tried it twice and both time the phone was idle for 2 hours. Nothing happened and I was able to exit that function by back spacing
 
Confirming gps bug. Whenever I try to use maps, navigation, or waze, the app just crashes or freezes or hangs, never get anywhere. Worked at the very start, but not anymore.

EDIT: After reflashing this rom, it seems that hapticUI for the softkeys stops working after navigation/maps/waze fails to open. rebooting doesn't fix haptic or gps bug

EDITED EDIT: HapticUI seems to work after reboot now, but always stops after trying to open google maps navigation. unable to use any kind of directions app, it seems. used in poynt, and it successful found my location.
 
Question: Is the encryption option for CM9 fully functional?

I have tried it twice and both time the phone was idle for 2 hours. Nothing happened and I was able to exit that function by back spacing

I will have to get back to you on that. I didn't set it up and I don't know what it needs to work.

Confirming gps bug. Whenever I try to use maps, navigation, or waze, the app just crashes or freezes or hangs, never get anywhere. Worked at the very start, but not anymore.

EDIT: After reflashing this rom, it seems that hapticUI for the softkeys stops working after navigation/maps/waze fails to open. rebooting doesn't fix haptic or gps bug

EDITED EDIT: HapticUI seems to work after reboot now, but always stops after trying to open google maps navigation. unable to use any kind of directions app, it seems. used in poynt, and it successful found my location.

There is a lot of changes in the system. I am trying to get the system to boot after I pulled in the changes that adamto pushed upline. I wonder if it's one of the changes that I put on top of it or something that wasn't pushed up with the rest of the stuff.
 
Flash player doesn't seem to work either. Downloaded from the thread on page 2, and no flash content comes up. could be my phone, but I'm not sure.
 
Adamto, this is probably asking for a lot but have you ever considered porting a 3.x kernel to the triumph?

I'm not sure what the value of a 3.x kernel would be.

Anyway, with all the closed stuff we rely on I think I would put this task in the "technically possible, but extremely unrealistic" category.
 
GPS update: the navigation app will now open, but it is stuck on "getting driving directions" even though, in the background, it is displaying my current position.
 
adamto, have you been able to build a ROM that boots with a repo sync?
I've tried to in another folder that I have the CM9 repo pulled to and it won't build boot either.

The only thing I have done to it is removed the libcamera2 from being built.
 
adamto, have you been able to build a ROM that boots with a repo sync?
I've tried to in another folder that I have the CM9 repo pulled to and it won't build boot either.

The only thing I have done to it is removed the libcamera2 from being built.

I haven't sync'd in a while let me check...
 
I haven't sync'd in a while let me check...

It looks like it's coming up ok, I'll try a clean just to be sure. I pushed a couple device_motorola_triumph changes I had been sitting on: don't build libcamera2 and fix the rmt_storage issue which you had commented out. I put those in master because it looked like the ics branch is unused, hope that is ok.
 
It looks like it's coming up ok, I'll try a clean just to be sure.

Nope, not working after clean. I'm getting a bunch of these:

Code:
03-12 23:55:40.914 I/dun_service(  137): The value returned from dun_getusbmodemstate_fromsys is 2

Then a bunch of these:

Code:
03-12 23:57:15.904 I/Netd    (  661): Netd 1.0 starting

With the other error interspersed.
 
I might have figured it out.
I looked at the log for the device project and it was old. Even after a repo sync. I did a update to the device project
Code:
 git remote update
and was able to pull the updated code. I'm building now, let y'all know.

Didn't work. Now I'm working through the projects and checking out some older commits so I can get this thing to boot
 
I might have figured it out.
I looked at the log for the device project and it was old. Even after a repo sync. I did a update to the device project
Code:
 git remote update
and was able to pull the updated code. I'm building now, let y'all know.

Didn't work. Now I'm working through the projects and checking out some older commits so I can get this thing to boot

I didn't really understand the implications of your 3/3 changes to init.triumph.rc, but if one of those mounts failed would it cause this?
 
I didn't really understand the implications of your 3/3 changes to init.triumph.rc, but if one of those mounts failed would it cause this?

It could have, but I removed it and tried it without the extra partitions and it still doesn't boot.
The idea behind it was to use unused space and basically free up /system as it gets pretty full with the ROM.
 
It could have, but I removed it and tried it without the extra partitions and it still doesn't boot.
The idea behind it was to use unused space and basically free up /system as it gets pretty full with the ROM.

Well other than that it's just the camera changes, right?
 
I hope so.

I reverted vendor_motorola_triumph back to https://github.com/MTCM9/android_ve...mmit/329c082966f0298d1d92374eb74047b932415a84 and it's working. I think it's the libcameraservice.so and libcamera_client.so in the copy you modified, those two we should be using the ones that are built.

EDIT: BTW, since I had to figure this out maybe it will be useful for you too. Once you identify the commit you want to go back to in git log, for example the commit above, do:

Code:
git checkout 329c082966f0298d1d92374eb74047b932415a84
but now you are in a 'detached head state', so you don't really want to do anything other than:

Code:
git checkout ics
or whatever your branch is when you're done.

EDIT2 (lol): In most cases when source code (c files, java files) change, I don't think you should have to do a 'make clean'. However, when we are modifying these makefiles or other parts of the build system, android doesn't seem to handle that. But, instead of doing a 'make clean' when modifying makefiles, I think you should still be able to prevent a full rebuild by removing just 3 directories: system, root, and recovery in out/target/product/triumph. That should make sure all the source code is built, but only recopies the built stuff, reducing build time drastically.
 
I reverted vendor_motorola_triumph back to https://github.com/MTCM9/android_ve...mmit/329c082966f0298d1d92374eb74047b932415a84 and it's working. I think it's the libcameraservice.so and libcamera_client.so in the copy you modified, those two we should be using the ones that are built.

EDIT: BTW, since I had to figure this out maybe it will be useful for you too. Once you identify the commit you want to go back to in git log, for example the commit above, do:

Code:
git checkout 329c082966f0298d1d92374eb74047b932415a84
but now you are in a 'detached head state', so you don't really want to do anything other than:

Code:
git checkout ics
or whatever your branch is when you're done.

EDIT2 (lol): In most cases when source code (c files, java files) change, I don't think you should have to do a 'make clean'. However, when we are modifying these makefiles or other parts of the build system, android doesn't seem to handle that. But, instead of doing a 'make clean' when modifying makefiles, I think you should still be able to prevent a full rebuild by removing just 3 directories: system, root, and recovery in out/target/product/triumph. That should make sure all the source code is built, but only recopies the built stuff, reducing build time drastically.

the "not" make clean might help. I made a script to delete the out/ if it finds it. I can modify it to remove the parts you mention.

And on the commit thing, I was doing that and a bunch of other things like upgraded the HDD in the workstation. The weird thing is it would boot from either drive (I imaged the old drive to the new one) So I was confused on what drive I was in at what time.


I need to slow down. Get some rest....:rolleyes: Yeah right!

EDIT: Testing out the new script.
EDIT2: The old, full build
Start: Thu Mar 14 00:58:30 EDT 2013
Finish: Thu Mar 14 01:41:41 EDT 2013~42Minutes
The new, partial build
Start: Fri Mar 15 00:12:23 EDT 2013
Finish: Fri Mar 15 00:18:56 EDT 2013~~6minutes

Didn't work for me, but like I said, I need sleep.
I'll try tomorrow.
And I see what you are talking about with the camera files.
Thankyou
 
the "not" make clean might help. I made a script to delete the out/ if it finds it. I can modify it to remove the parts you mention.

And on the commit thing, I was doing that and a bunch of other things like upgraded the HDD in the workstation. The weird thing is it would boot from either drive (I imaged the old drive to the new one) So I was confused on what drive I was in at what time.


I need to slow down. Get some rest....:rolleyes: Yeah right!

EDIT: Testing out the new script.

I think removing out is the same as make clean. I still don't understand how repo works. The one thing i did learn is 'repo branches', I then manually used git to update and pull each branch listed there to the proper one. I'm staying away from 'repo sync' for now.
 
GPS update: the navigation app will now open, but it is stuck on "getting driving directions" even though, in the background, it is displaying my current position.

How did you get it to work? Were you able to actually get navigation to guide you through a route or was it still stuck on "getting driving directions"?
 
How did you get it to work? Were you able to actually get navigation to guide you through a route or was it still stuck on "getting driving directions"?

I'm not sure how I got it to work. What happened was, The splash screen saying "getting driving directions" never closed, but, in the background behind the splash screen, the map was showing with my correct location. I was unable to do anything else from there, though.
 
Hopefully tonite I'm going to reset the device files and try to bring clarity to what we are using. I'll start small with the known camera files. I think we are using the stock for now? Then I'll move on to media type files and finish with telephony.
 
For whoever has write access to the opening page, wifi tether works perfectly (for me) on the 2/23 rom. Our wifi at work went down briefly. Was pleasantly surprised.
 
Back
Top Bottom