Yes I did.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [DEV] CM7 Building & Development
- Thread starter g60madman
- Start date
-
- Tags
- motorola triumph
Yes I did.
G
g60madman
Guest
What version of Andro-ID did you use?
Andro-id is based off of the sharp rom, it uses the sharp launcher. The rc2, I believe, was modded to use the kernel from the other X6 gingerbread versions, while rc3 used the newer 2.6.35.7 kernel. I read that it took him a while to get a working recovery because of the new kernel.
It was rc2
dsmryder
Android Expert
I have some information on adding apps and setting up the edify script.
I'm going to test the wildcard process to see if I can just modify the triumph.mk and the triumph_edify_generator.py to accept this method. That way the repo can be set up to have a "app-d" and "app-s" so we can just vomit up what ever apps into those folders and they end up into the /data and /system folders.
HTML:
https://groups.google.com/forum/#!msg/android-building/sPH5l0cV6lQ/TbQyx222L0UJ
HTML:
http://forum.xda-developers.com/showthread.php?p=25721281#post25721281I'm going to test the wildcard process to see if I can just modify the triumph.mk and the triumph_edify_generator.py to accept this method. That way the repo can be set up to have a "app-d" and "app-s" so we can just vomit up what ever apps into those folders and they end up into the /data and /system folders.
G
g60madman
Guest
Updated git hub with version r0.5 run a repo sync
G
g60madman
Guest
Just and FYI on removing commits here is the commands I ran to roll back the camera
The HEAD~4 says to remove the last 4 commits and opens gedit (or what ever editor your using with git) with all commits made.
Basically you delete a line that starts with "pick" and it will delete all the commits in the code. Then save and close gedit and the commit and the code will be removed.
My best guess is the problem we are having is the Camcorder Focus is causing the camera to lock up when switching back and forth. At this point it's trial and error but hopefully this helps in explaining how to remove commits from a repo.
Code:
[B]g60madman@mtdev[/B]:$ git clone git@github.com:g60madman/android_packages_apps_Camera.git
Initialized empty Git repository in /media/android/g60madman/android_packages_apps_Camera/.git/
remote: Counting objects: 16543, done.
remote: Compressing objects: 100% (4168/4168), done.
remote: Total 16543 (delta 8452), reused 16192 (delta 8160)
Receiving objects: 100% (16543/16543), 4.54 MiB | 387 KiB/s, done.
Resolving deltas: 100% (8452/8452), done.
[B]g60madman@mtdev[/B]:$ cd android_packages_apps_Camera/
[B]g60madman@mtdev[/B]:/android_packages_apps_Camera$ git rebase -i HEAD~4The HEAD~4 says to remove the last 4 commits and opens gedit (or what ever editor your using with git) with all commits made.
Code:
pick 6526c3c Commit interim changes - Triumph options
pick 374600a Camera Scene Mode NPE Fix
pick 0f20602 Czech: fixed missing string for timer shutter
pick c9c77fa Fix up touch to focus code via overlays
pick 9af9ee8 Fix skewed camera preview when launched from lockscreen
pick a251b60 Pass the camera ID when getting JPEG quality values
pick 3c82fd6 Camera: update Simplified Chinese translations
pick 340f3fd Update Japanese translation.
pick d2e3023 elGR-Reworked translation/Added missing strings
pick 384f180 Camcorder: Focus once before recording
pick 0db56c9 Camera: Support OMAP4-specific features
pick 77dc249 Delete icon texture's after draw
pick f2b0c25 Add support for wide-screen resolution photo on SGS2
pick 18f382f VideoCamera: Return from onResume sooner to reduce the application launch time
pick 2df22d5 Check for null before storing the jpeg data.
pick cb2e2f8 Camcorder: Send initial focus after starting preview
pick 27f34f8 es_ES: Add missing translations
pick 32b9ee5 Fix touch to focus detection
pick 68803c3 Traditional Chinese: Update translations
pick 8a7d929 Updated Swedish translations
pick d3952ce Camera: Don't delay call too changeHeadUpDisplayState
pick 5d7c8b8 Camera: Updated Hungarian Translation
pick ea6c82e camera: Updated Italian translations
pick 2da496e Camera: update Simplified Chinese translations
pick 2da6f8c es_ES: Add missing translations
pick 9a420be Update Japanese translation.
pick 1da1802 Update hungarian translation
pick 37dcf22 Camera: Remove duplicate hungarian translation that breaks build.
pick 041b695 Camera: OMAP4: Add a default sane SEI encoding
pick 986d75b Camera: Use extensions other than jpg if necessary
pick 0d3d713 Camera: Autofocus camcorder only if needed
pick 579281b Added option to use either removable SD card or internal memory
pick 2e9693d es_ES: Final translations
pick df511cf Update hungarian translation
pick ffbecd5 Camera: Support TTF/TTEC with recent qcom cameras
pick 3b67e7b Update Russian translation - Camera
pick 94103d4 Czech: added missing strings
pick dc0a787 french: updated translation
pick 4d9a322 Camera: tr: CM Turkish Translations
pick c6a7869 Add support for EXIF datetime on Qualcomm libcameras
pick 5726db2 Turn the focus rectangle green when focused. Credit: dsmryder
# Rebase 608923f..5726db2 onto 608923f
#
# Commands:
# p, pick = use commit
# r, reword = use commit, but edit the commit message
# e, edit = use commit, but stop for amending
# s, squash = use commit, but meld into previous commit
# f, fixup = like "squash", but discard this commit's log message
#
# If you remove a line here THAT COMMIT WILL BE LOST.
# However, if you remove everything, the rebase will be aborted.
#Basically you delete a line that starts with "pick" and it will delete all the commits in the code. Then save and close gedit and the commit and the code will be removed.
My best guess is the problem we are having is the Camcorder Focus is causing the camera to lock up when switching back and forth. At this point it's trial and error but hopefully this helps in explaining how to remove commits from a repo.
G
g60madman
Guest
No it would show you pushed on my github which it doesn't.
I don't recommend that you do a git rebase and remove commits that you have already pushed up to github. You will mess up anyone who has pulled down your previous commits already.
Do a git revert instead which will revert the changes and still keep the commit in the history. So the command would be:
#git revert <hash of the commit>
Where <hash of the commit> is the hash for the commit. So if the hash is 65fe521, the command would be
#git revert 65fe521
You can either get the hash from doing a git log and viewing the log or if you already pushed the commit to github, you can look at the commit hash in your repo on github.
G
g60madman
Guest
Thanks mantera for the clarification. Still learning the whole github ways :thumbup:
G
g60madman
Guest
Updated github to r0.6
G
g60madman
Guest
Updated github to r0.7
dsmryder
Android Expert
A little sad when the last two "DEV' thread posts are to say the ROM is updated.
dsmryder
Android Expert
I'll tell you the truth,I have like a months experience. And i just hosed my working directory. The way I try to work it is by logic and reading. Some stuff isn't that hard to figure out, just cryptic.
Oh, on topic. I'm going to add the sound scripts when I redo my github and working directory.
dsmryder
Android Expert
I MAY have found where the code change should go for the screen logic. In Cyanogen's github page there is a mention of the lockscreen awareness. I think the code should be expanded to check the state, then if the phone isn't locked, hold off the lock. I don't know how to do it, but I know someone around here does
G
g60madman
Guest
I MAY have found where the code change should go for the screen logic. In Cyanogen's github page there is a mention of the lockscreen awareness. I think the code should be expanded to check the state, then if the phone isn't locked, hold off the lock. I don't know how to do it, but I know someone around here does
I did a meld on CM9, CM7, and google AOSP Gingerbread. All the code is exactly the same on the lock screen while in call. So it's designed right, I guess I am missing something on the lock screen incall thing. I myself have not seen any problems, as long as I can get to my contacts while on a call the world is good. Can you maybe explain exactly what everyone wants? Even looking at the bug posted it doesn't make sense
0000015: Phone should not lock or have display turn off when in a call - MantisBT
The phone is supposed to lock when on a call, and when you pull it from your face the proximity sensor should turn back on the screen so you can use the phone. As soon as you hang up the phone should lock. Did I miss something
b_randon14
Android Expert
It's not like that on the stock FroYo ROMS, or any Android phone I have used. After the call, the screen comes on, but it does not show the lockscreen. I guess CM7/gingerbread is supposed to be like that so it's not a bug then, but on my brothers CM9 captivate, his does not show the lock screen after the call is ended. And yeah your right he lock screen never shows while in call, but when the call ends it shows it. I suppose that is just the way Gingerbread is designed, but I think it should not show the lock screen. I am going to check and see if my wife's Venture does this running stock 2.3.5 gingerbread.
dsmryder
Android Expert
I did a meld on CM9, CM7, and google AOSP Gingerbread. All the code is exactly the same on the lock screen while in call. So it's designed right, I guess I am missing something on the lock screen incall thing. I myself have not seen any problems, as long as I can get to my contacts while on a call the world is good. Can you maybe explain exactly what everyone wants? Even looking at the bug posted it doesn't make sense
0000015: Phone should not lock or have display turn off when in a call - MantisBT
The phone is supposed to lock when on a call, and when you pull it from your face the proximity sensor should turn back on the screen so you can use the phone. As soon as you hang up the phone should lock. Did I miss something
Like b_random said, the screen locks while in a call. If you were doing somehing when a call came in, and you talked too long, the screen would lock and you would need to unlock it to go back to what you were doing. It wasn't like that on stock. Not a huge deal. A current work a round is to have the lock screen delay cranked up. I have mine set to 5 minutes.
I'm going to see if I can figure out the lock delay default setting in the repo and that will give an apeariance of what we're looking for. Either way, not a big deal.
G
g60madman
Guest
My guess is Google added this into the code to secure the phone more. If the phone is unlocked after you hang up some could access your data. If you have a password set I am not sure it if can bypass it on froyo but I wonder if that's why it's been enabled?
Although I'm not a developer, I've found a bug with CM7 on this device that may be very important to developers. When running CM7-g60style, has anyone else noticed that ddms is borked and will not detect this device? (DDMS is part of the Android SDK) You can view my bug here.
UPDATE: Please mark this bug as invalid. But it sure does not detect the phone out-fo-the-box! I'll include precise instructions in the next FAQ update.
UPDATE: Please mark this bug as invalid. But it sure does not detect the phone out-fo-the-box! I'll include precise instructions in the next FAQ update.