Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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.
Adamto, this is probably asking for a lot but have you ever considered porting a 3.x kernel to the triumph?
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...
It looks like it's coming up ok, I'll try a clean just to be sure.
03-12 23:55:40.914 I/dun_service( 137): The value returned from dun_getusbmodemstate_fromsys is 2
03-12 23:57:15.904 I/Netd ( 661): Netd 1.0 starting
git remote update
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 projectand was able to pull the updated code. I'm building now, let y'all know.Code:git remote update
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?
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.
git checkout 329c082966f0298d1d92374eb74047b932415a84
git checkout ics
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:
but now you are in a 'detached head state', so you don't really want to do anything other than:Code:git checkout 329c082966f0298d1d92374eb74047b932415a84
or whatever your branch is when you're done.Code:git checkout ics
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.
Yeah right!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....Yeah right!
EDIT: Testing out the new script.
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"?