*Update 3/6/12*: I probably should have done this awhile ago, but I just wanted to clarify that this was a one-off release. It will not be updated since Nightlies/Weeklies are up and running again. In fact, they will have everything this ROM has plus more!
In trying to build CM7 (w/ FP) from source, acerbix, crnkoj, and I unwittingly built CM7.2 . You can follow along with our adventures here. We found that using the FP branches of the Atrix-Dev-Team's github repos with the new upstream CyanogenMod changes no longer produced a fully working FP build. After merging and copying the necessary code in frameworks/base from the ADT's repo on top of the newer CM7 stuff, it gave us a working 7.2 build.
I thought others may want to try out an updated CM7. This was my first attempt at compiling from source, so there may be bugs. A few changes I've noticed:
- "Holo" lockscreen
- T9 dialer
- Corrected calendar lockscreen widget
- More detailed battery stats (I think).
There are more if you feel like looking through the CM commits since the last official weekly/nightly release.
I'm not a developer. I will not be offering any kind of support beyond the possible update when worthwhile upstream changes are made. However, feel free to ask and answer questions here. I'm sure the other community members will be willing to help one another out.
Please keep in mind that this is a kang and in no way related to the official CM7 build, so please do not use those threads to post issues if you decide to try this.
Here are all of the sources I used:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android
https://github.com/ghost-og/android_frameworks_base
Here's the download link:
https://rapidshare.com/files/2700446381/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Sorry for using RapidShare. Multiupload was having issues when I tried uploading this there. I'll try to change it later.
*edit* Dropbox mirror. Be gentle:
http://dl.dropbox.com/u/11998742/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Link not working for me mate...
Sent from my MB860 using XDA App
Thanks for this. How recent is this? Does it encompass all of these changes: https://cm-nightlies.appspot.com/?device=olympus
Nice work,ghost_og.
I've used CM7.2 before on my Defy and Milestone 2. Many improvements over previous CM7. I'm waiting for multiupload link. Thanks for your hard work.
guidoido004 said:
Link not working for me mate...
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmm, worked for me. It redirected at first, but then it should give you a 30-sec wait window. Sorry for the crappy hosting.
NguyenHuu said:
Thanks for this. How recent is this? Does it encompass all of these changes: https://cm-nightlies.appspot.com/?device=olympus
Click to expand...
Click to collapse
I built it 1/16/12, so I think the French translations were the last thing I caught. Sorry for the extra work, but checkout the main CM repo and checkout the commit history.
ghost_og said:
Hmm, worked for me. It redirected at first, but then it should give you a 30-sec wait window. Sorry for the crappy hosting.
I built it 1/16/12, so I think the French translations were the last thing I caught. Sorry for the extra work, but checkout the main CM repo and checkout the commit history.
Click to expand...
Click to collapse
Thanks, will test it out, been looking for some updates to CM7.
The only nightly update you doesnt have is the ones specific for atrix....
You also could add tweaks and mods on it ^^
Flashing now, lets see how much good is it. Hehehe
Sent from my MB860 using XDA App
ghost_og said:
In trying to build CM7 (w/ FP) from source, acerbix, crnkoj, and I unwittingly built CM7.2 . You can follow along with our adventures here. We found that using the FP branches of the Atrix-Dev-Team's github repos with the new upstream CyanogenMod changes no longer produced a fully working FP build. After merging and copying the necessary code in frameworks/base from the ADT's repo on top of the newer CM7 stuff, it gave us a working 7.2 build.
I thought others may want to try out an updated CM7. This was my first attempt at compiling from source, so there may be bugs. A few changes I've noticed:
- "Holo" lockscreen
- T9 dialer
- Corrected calendar lockscreen widget
- More detailed battery stats (I think).
There are more if you feel like looking through the CM commits since the last official weekly/nightly release.
I'm not a developer. I will not be offering any kind of support beyond the possible update when worthwhile upstream changes are made. However, feel free to ask and answer questions here. I'm sure the other community members will be willing to help one another out.
Please keep in mind that this is a kang and in no way related to the official CM7 build, so please do not use those threads to post issues if you decide to try this.
Here are all of the sources I used:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android
https://github.com/ghost-og/android_frameworks_base
Here's the download link:
https://rapidshare.com/files/2700446381/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Sorry for using RapidShare. Multiupload was having issues when I tried uploading this there. I'll try to change it later.
Click to expand...
Click to collapse
I think all of the fingerprint changes have been committed today, so you should get them if you pull the source to make your own build. No more splicing files necessary!
EDIT: Oops, I was wrong. Fingerprint branch was updated, but still need to merge those files into the base CM build.
the T9 dialer is great. Looking forward to more updates as more changes are comitted. Good work.
Let me mirror this up for you mate. Give me a while to upload it on my crappy connection.
kennethpenn said:
Let me mirror this up for you mate. Give me a while to upload it on my crappy connection.
Click to expand...
Click to collapse
Thank you! I appreciate it. Hehe, rapidshare...
ghost_og said:
Thank you! I appreciate it. Hehe, rapidshare...
Click to expand...
Click to collapse
http://bandbinnovations.com/xda/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Have fun!
ghost_og said:
In trying to build CM7 (w/ FP) from source, acerbix, crnkoj, and I unwittingly built CM7.2 . You can follow along with our adventures here. We found that using the FP branches of the Atrix-Dev-Team's github repos with the new upstream CyanogenMod changes no longer produced a fully working FP build. After merging and copying the necessary code in frameworks/base from the ADT's repo on top of the newer CM7 stuff, it gave us a working 7.2 build.
Click to expand...
Click to collapse
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
turl1 said:
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
Click to expand...
Click to collapse
Great news! I was debating whether or not to post this. I didn't want to step on any toes. Thanks for the hard work; I just synced and started a new build.
is it possible to flash this right over neutrino rom or is it best to full wipe?
Sent from my MB860 using XDA App
If coming from a cm7 based rom then just wipe /cache and dalvik. Been working for me switching between different versions.
Sent from my MB860 using XDA App
turl1 said:
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=xHhUmRE2YOo
Can faux kernel be used with this rom?
Nipit said:
Can faux kernel be used with this rom?
Click to expand...
Click to collapse
Yes. The latest open beta runs very well for me.
turl1 said:
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
Click to expand...
Click to collapse
Wow great news!! Will the Weekly #5 be based on CM7.2?
Related
Highly experimental stuff:
Release candidates and nightly builds available via Rom-Manager.
Description:
CyanogenMod has nightly builds for Legend since Sept. 30 2010 as it's become an officially supported device. I will provide experimental builds (for public beta testing) here from time to time. No files available for the moment.
Please adhere to a few rules when discussing builds in here.
Read and search before you post.
Do not request help. This is the development board.
Requests for builds, features, fixes or apps to include will be ignored.
Do not report broken or not installable apps from the Market (we can't fix them).
Do not expect bugs to be fixed.
Credits:
Thanks go out to the whole CM team for their great work!
Beer / Coffee:
Additional stuff:
Some people experience GPS issues. To help us debug, flash that verbose module and get a full log via adb:
gps-test.zip (gps.legend.so)
EDIT.
Got it.
differences beetween azure and dark azure?
screenshots will be appreciated
thanks for your work
It will be same as Azure 1.0 , but with a Dark Theme , and some bug fixes.
This, Ali Ba, is a really neat idea.
rajasyaitan said:
What is this exactly? An Azure mod?
Click to expand...
Click to collapse
Lostpassword said:
differences beetween azure and dark azure?
Click to expand...
Click to collapse
dhanu007 said:
It will be same as Azure 1.0 , but with a Dark Theme , and some bug changes.
Click to expand...
Click to collapse
You really did not read the first post. Not even the second sentence.
dhanu007 said:
...and some bug changes.
Click to expand...
Click to collapse
As a software developer I like that wording - much more accurate than "bug fixes"
Need idea love having Android in black...
TCarlsen said:
Need idea love having Android in black...
Click to expand...
Click to collapse
Bloody hell, who wrote this was a mod? Does anyone of you even understand what "nightly build" means?
What is this board here? Kindergarten?
You made my day, thank you!
Message removed
So what is a nighty build then ? I know m a Noob
dhanu007 said:
So what is a nighty build then ? I know m a Noob
Click to expand...
Click to collapse
"Nightly builds are daily compiled builds from the source, therefore have the latest features & tweaks, but will are mostly likely to break due being fresh, not fully tested code. "
Great idea, but dangerous! Like, I almost choked on my coffee while starting to laugh over the comments in this thread!!
<irony>But finally we can have a black themed ROM ! * </irony> lol This thread made my day, seriously!
Edit: Don't want to spam the thread with useless comments, sorry bout that, but this was too hilarious!!
Good start.
No, but seriously, dont let the kids make you nervous.
Carry on with the good work.
Poor Ali Ba, wrestling with incompetent fools. But we were all there. I'm still there. But at least I understood what he mean by nightly builds I suppose...
Thanks, ali ba. Would you consider automating the builds, or do the patches you apply to CM for Legend support break frequently?
I've always been curious of why you haven't submitted your patches upstream to CM, but that's for another discussion.
Ah, nightly builds I love em!
I work in a game studio, nightly builds cause me nothing but pain as an animator ;D
pfak said:
Thanks, ali ba. Would you consider automating the builds, or do the patches you apply to CM for Legend support break frequently?
Click to expand...
Click to collapse
Nope, no automated builds planned. Thus inverted commas in "nightly" builds.
pfak said:
I've always been curious of why you haven't submitted your patches upstream to CM, but that's for another discussion.
Click to expand...
Click to collapse
I submitted all that were useful enough and not breaking anything else.
The most critical one being the lights patch because CM code is still written as if every device had a trackball RGB light. Will most likely never submit that one.
09/07 online.
To keep them separate from the main thread, post 'em in here
Awesome Rusty, realle needed this thread.. You guys should team up, so it would be clear who is building these kangs. Maybe you could be listed in 1st post, and you could specify the small differences you have. I guess you all put something of your own into the kangs..
Really appreciate your work guys, gives a good hunch about what the future of Android 2.3.4 holds..
ionhide said:
I guess you all put something of your own into the kangs.
Click to expand...
Click to collapse
Not me as it happens
I just build what's been committed, anything from me would be identical to a nightly if the buildbot had run at the time.
I'd suggest to put a sort of scheme in the KANG posts. Something Like
Builder:
Date:
Base nightly:
Last merged commit included:
Cherry picks/custom changes:
So it would look like for example:
Builder: aMpeX
Date: 10/06/2011 11:08 CET
Base nightly: 42
Last merged commit included: Update prebuilt kernel and modules (android_device_lge_p990)
Cherry picks/custom changes: ADW.Launcher: Screen Transitions, Backup Categories
That way, the KANGs would be much more organized and would help to keep the Thread clean.
aMpeX said:
I'd suggest to put a sort of scheme in the KANG posts. Something Like
Builder:
Date:
Base nightly:
Last merged commit included:
Cherry picks/custom changes:
So it would look like for example:
Builder: aMpeX
Date: 10/06/2011 11:08 CET
Base nightly: 42
Last merged commit included: Update prebuilt kernel and modules (android_device_lge_p990)
Cherry picks/custom changes: ADW.Launcher: Screen Transitions, Backup Categories
That way, the KANGs would be much more organized and would help to keep the Thread clean.
Click to expand...
Click to collapse
+1 on this
Most of that is superfluous really.
Builder & date are kinda obvious from the post, and base nightly isn't really relevant when you include the last commit.
All you really need is a link, last commit and an MD5# to keep folks happy. Could always make a uniform template to cover that stuff though
All right, good plan
Builder: destilant
Date: 09/06/2011 - 21:44 CET
Base nightly: #41
Last merged commit included: V8: Stop generating v8.log in build root directory
Cherry picks/custom changes: none
Download
Rusty! said:
Most of that is superfluous really.
Builder & date are kinda obvious from the post, and base nightly isn't really relevant when you include the last commit.
All you really need is a link, last commit and an MD5# to keep folks happy. Could always make a uniform template to cover that stuff though
Click to expand...
Click to collapse
I've seen numerous "what are your cherry picks?" "which commits are included?" "will this print 100$ notes?" questions in the main CM7 Thread so I still think the template is a good idea
Oh yeah it's not a bad idea at all, just thought some tweaking might be in order. Of course you'd mention any cherry-picks, not sure how I forgot that one
Sorry for my noob question and sorry if it's the wrong place to ask: what exactly is a CM7 KANG build?
It's a build of CyanogenMod compiled by users, not the buildbot.
Rusty! said:
It's a build of CyanogenMod compiled by users, not the buildbot.
Click to expand...
Click to collapse
You should put this in the op
Sent from my Optimus 2X using XDA Premium App
New commits posted after #42, anyone up for making updated KANG? :-D
http://cm-nightlies.appspot.com/?device=p990
Sent from my Optimus 2X using XDA App
ionhide said:
New commits posted after #42, anyone up for making updated KANG? :-D
Click to expand...
Click to collapse
+1...
ionhide said:
New commits posted after #42, anyone up for making updated KANG? :-D
http://cm-nightlies.appspot.com/?device=p990
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
I would have done it, but have repo sync problem, due to internet
Fetching projects: 1% (3/259) android.git.kernel.org[0: 2001:6b0:e:4017:1972:112:1::]: errno=No route to host
android.git.kernel.org[0: 2001:500:60:10:1972:112:1::]: errno=No route to host
android.git.kernel.org[0: 2001:6b0:e:4017:1972:112:1::]: errno=No route to host
android.git.kernel.org[0: 2001:500:60:10:1972:112:1::]: errno=No route to host
Click to expand...
Click to collapse
Great that you made a kang thread!
Sent from my Optimus 2X using XDA Premium App
bhanvadia said:
I would have done it, but have repo sync problem, due to internet
Click to expand...
Click to collapse
Yep, getting the same issue here aswell..
Worked all right for me this morning when I updated my CWM thread.
Any of the kangs the notification lights that was shown on youtube?
I tried cherry-picking, but the notification light doesnt seem to be working.
Hi,
This thread is to discuss building CM9 build from source for Atrix. In order to do that, you will need to overlay Atrix specific stuff over the vanilla CM9 code.
There are two overlays possible:
- The official Atrix-dev team repositories
- The official Photon-dev team Atrix repositories
There is more (visible) activity on the photon team than the Atrix team right now so personally I am using the Photon team's Atrix repositories. In order to use the Photon repo you might have to edit olympus-vendor-blobs.mk in vendor/motorola/olympus. It has a few sunfire dependencies that will need to be changed to olympus. I submitted a pull request to the photon dev team, so those changed might be merged in sometime soon
Attaching two scripts that you can use in android/system to overlay vanilla CM9 code for Atrix: one for the Atrix-dev-team overlay, and another for the Photon-dev-team. Both build cleanly without issues as of this time.
I built the kangs but havent tested yet. Will test when I get home and back up my CM7
I used the build instructions here and made minor changes: http://forum.xda-developers.com/showpost.php?p=21077425&postcount=1
t.s.eliot said:
Strike one on a CM9 attempt.
I didn't get the changes quite right in LockPatternKeyguardView.java.
"frameworks/base/policy/src/com/android/internal/policy/impl/LockPatternKeyguardView.java:452: updateScreen(com.android.internal.policy.impl.LockPatternKeyguardView.Mode,boolean) in com.android.internal.policy.impl.LockPatternKeyguardView cannot be applied to (com.android.internal.policy.impl.LockPatternKeyguardView.Mode)
updateScreen(mMode);
^
frameworks/base/policy/src/com/android/internal/policy/impl/LockPatternKeyguardView.java:1029: cannot find symbol
make: *** [out/target/common/obj/APPS/Settings_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
symbol : variable mLockscreenDisableOnSecurity
location: class com.android.internal.policy.impl.LockPatternKeyguardView
if (mLockscreenDisableOnSecurity && isSecure() && (usingLockPattern || usingLockFinger) || (simState == IccCard.State.PIN_REQUIRED)) {
"
Click to expand...
Click to collapse
Copying over from the CM7 source build thread...
Fingerprint needs to be properly ported. Building on cm7 code just gives you a jumbled mess.
I know its a little more setup but you really need proper cm9 source to build correctly. You can overlay the fingerprint code in the device tree and still keep the latest cm9 sync.
Its actually pretty easy to set up.
Repo init cm9githubyatayata... -b ics
Repo sync -j1 (yes j1 cm9 github is taxed)
Pull the vendor and device
Edit cm vendor setup
Build
Sent from my MB855 using XDA App
acerbix said:
Copying over from the CM7 source build thread...
Click to expand...
Click to collapse
I got past that initial problem by just copying the entire source file rather than trying to do the edits.
Currently stuck applying the group of changes from the "packages/apps/Settings" tree. The "SecuritySettings.java" file seems to have a lot of additional stuff for the face unlock, so it is really hard to tell where the FP stuff goes.
No luck so far with the line by line changes. Next attempt will be to try just replacing the files.
CM9 will build with no issue without the FP unlock. Just need to add the "device/motorola/olympus" directory and the olympus proprietaries. The Atrix Dev Team keeps these on their github under the ICS branch.
---------- Post added at 07:28 AM ---------- Previous post was at 07:22 AM ----------
jokersax11 said:
Fingerprint needs to be properly ported. Building on cm7 code just gives you a jumbled mess.
I know its a little more setup but you really need proper cm9 source to build correctly. You can overlay the fingerprint code in the device tree and still keep the latest cm9 sync.
Its actually pretty easy to set up.
Repo init cm9githubyatayata... -b ics
Repo sync -j1 (yes j1 cm9 github is taxed)
Pull the vendor and device
Edit cm vendor setup
Build
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
(I have to preface all of my comments with the observation that I really don't know what I"m doing.)
It seems like we have proper source for building the basic CM9 on the Atrix. There isn't a camera yet, but the Atrix Dev Team's ICS branch seems to have the right files for /device/vendor/motorola/olympus and vendor/motorola/olympus directories. Basic version builds with no issue.
Trying to merge the FP unlock code into the Atrix stuff seems much more challenging. I don't think that replacing the changed files will work, since the Security Settings seem to have some dramatic changes made for the Face Unlock.
(On a side note, two factor biometric authentication would be really cool if it ever gets working....)
When I say proper source I mean your source base. Overlaying ics vendor and device on gingerbread source is not going to make cm9, but cm7 breaks and partially checkouts a few ics branches. If you start with current up to date cm9 source from cyanogenmod then modify you have a better chance.
As far as porting fp use a diff viewer and a syntax highlighting editor. Ideally you should separate then fp class and point to it by adding to the include.
t.s.eliot said:
I got past that initial problem by just copying the entire source file rather than trying to do the edits.
Currently stuck applying the group of changes from the "packages/apps/Settings" tree. The "SecuritySettings.java" file seems to have a lot of additional stuff for the face unlock, so it is really hard to tell where the FP stuff goes.
No luck so far with the line by line changes. Next attempt will be to try just replacing the files.
CM9 will build with no issue without the FP unlock. Just need to add the "device/motorola/olympus" directory and the olympus proprietaries. The Atrix Dev Team keeps these on their github under the ICS branch.
---------- Post added at 07:28 AM ---------- Previous post was at 07:22 AM ----------
(I have to preface all of my comments with the observation that I really don't know what I"m doing.)
It seems like we have proper source for building the basic CM9 on the Atrix. There isn't a camera yet, but the Atrix Dev Team's ICS branch seems to have the right files for /device/vendor/motorola/olympus and vendor/motorola/olympus directories. Basic version builds with no issue.
Trying to merge the FP unlock code into the Atrix stuff seems much more challenging. I don't think that replacing the changed files will work, since the Security Settings seem to have some dramatic changes made for the Face Unlock.
(On a side note, two factor biometric authentication would be really cool if it ever gets working....)
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
ive managed to get cm9 to build several times, even before we started on the cm7+fp, and the older builds worked well with a few of o2x libs (i can put a link with the ones i used as a flashable zip here), the only things not working were obviously camera, and hw acceleration (although maps, gallery and games/benches worked, but slower than on cm7), after that ive tried to build it again with cm9 + atrix dev team cm9/ics sources, which built nice, but on bootup i get a permanent com.android.phone stopped, so one would have to edit some (probably ril related) files or use the ones from photon cm9. As was said already, the cm7 fp code needs a rewrite for cm9, overlaying cm7 over cm9 will just break stuff. additionally there is updated cm9 code from atrix dev team but, since there are no useful proprietary binaries, there is no real need to update the sources
jokersax11 said:
Fingerprint needs to be properly ported. Building on cm7 code just gives you a jumbled mess.
I know its a little more setup but you really need proper cm9 source to build correctly. You can overlay the fingerprint code in the device tree and still keep the latest cm9 sync.
Its actually pretty easy to set up.
Repo init cm9githubyatayata... -b ics
Repo sync -j1 (yes j1 cm9 github is taxed)
Pull the vendor and device
Edit cm vendor setup
Build
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I'll start porting sometime later this evening after work.
crnkoj said:
ive managed to get cm9 to build several times, even before we started on the cm7+fp, and the older builds worked well with a few of o2x libs (i can put a link with the ones i used as a flashable zip here), the only things not working were obviously camera, and hw acceleration (although maps, gallery and games/benches worked, but slower than on cm7), after that ive tried to build it again with cm9 + atrix dev team cm9/ics sources, which built nice, but on bootup i get a permanent com.android.phone stopped, so one would have to edit some (probably ril related) files or use the ones from photon cm9. As was said already, the cm7 fp code needs a rewrite for cm9, overlaying cm7 over cm9 will just break stuff. additionally there is updated cm9 code from atrix dev team but, since there are no useful proprietary binaries, there is no real need to update the sources
Click to expand...
Click to collapse
Hope we dont need to rewrite the entire FP code - just port it/find the right hooks into app/settings and frameworks/base. Will look at CM9 code later this evening. Will be slow since this is my first time w CM9.
acerbix said:
Hope we dont need to rewrite the entire FP code - just port it/find the right hooks into app/settings and frameworks/base. Will look at CM9 code later this evening. Will be slow since this is my first time w CM9.
Click to expand...
Click to collapse
very nice,
one thing, it seems you know how to go around this stuff and i am very new to this..., so i was wondering if you would have some advice what to read/learn to be able to edit/fix this (c++/java programming?), as like this i cant or dont know how to do code tweaking, if i get a hang of it i would gladly work on it than.
second to that the good thing is fp is actually working in cm9 (the navigation), so the drivers for it work, we jsut in fact need to implement the app as we had to in the cm7 kangs now.
crnkoj said:
very nice,
one thing, it seems you know how to go around this stuff and i am very new to this..., so i was wondering if you would have some advice what to read/learn to be able to edit/fix this (c++/java programming?), as like this i cant or dont know how to do code tweaking, if i get a hang of it i would gladly work on it than.
second to that the good thing is fp is actually working in cm9 (the navigation), so the drivers for it work, we jsut in fact need to implement the app as we had to in the cm7 kangs now.
Click to expand...
Click to collapse
Sure - Sent you a PM on this.
t.s.eliot said:
I got past that initial problem by just copying the entire source file rather than trying to do the edits.
Currently stuck applying the group of changes from the "packages/apps/Settings" tree. The "SecuritySettings.java" file seems to have a lot of additional stuff for the face unlock, so it is really hard to tell where the FP stuff goes.
No luck so far with the line by line changes. Next attempt will be to try just replacing the files.
CM9 will build with no issue without the FP unlock. Just need to add the "device/motorola/olympus" directory and the olympus proprietaries. The Atrix Dev Team keeps these on their github under the ICS branch.
---------- Post added at 07:28 AM ---------- Previous post was at 07:22 AM ----------
(I have to preface all of my comments with the observation that I really don't know what I"m doing.)
It seems like we have proper source for building the basic CM9 on the Atrix. There isn't a camera yet, but the Atrix Dev Team's ICS branch seems to have the right files for /device/vendor/motorola/olympus and vendor/motorola/olympus directories. Basic version builds with no issue.
Trying to merge the FP unlock code into the Atrix stuff seems much more challenging. I don't think that replacing the changed files will work, since the Security Settings seem to have some dramatic changes made for the Face Unlock.
(On a side note, two factor biometric authentication would be really cool if it ever gets working....)
Click to expand...
Click to collapse
Where did you found FP sensor unlock code?
As far as i know, the finger print sensor unlock code is closed source!
(creating+managing fingers activities and the unlock screen activity!)
Sent from my MB860 using XDA App
Paschalis said:
Where did you found FP sensor unlock code?
As far as i know, the finger print sensor unlock code is closed source!
(creating+managing fingers activities and the unlock screen activity!)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Checkout the Atrix-Dev-Team github. As far as I know t0dbld wrote all new code for it from the ground up. Which is why it has the added navigation features and multiple finger support.
Learning programming for hacking fun
crnkoj said:
very nice,
one thing, it seems you know how to go around this stuff and i am very new to this..., so i was wondering if you would have some advice what to read/learn to be able to edit/fix this (c++/java programming?), as like this i cant or dont know how to do code tweaking, if i get a hang of it i would gladly work on it than.
second to that the good thing is fp is actually working in cm9 (the navigation), so the drivers for it work, we jsut in fact need to implement the app as we had to in the cm7 kangs now.
Click to expand...
Click to collapse
Well - there were several other PM'd requests for this info - so I thought I'd post the info here.
Disclaimer: I am not a comp-sci grad, just a geek If you have easier ways to learn C or Java please post here.
I am guessing you already know your way around linux, shell prompt/scripting etc. Next thing to learn would be C. I'd say C is easier to learn than C++ since there is a lot less to it (no classes and OO) and most of the native code is in C. If you know C, learning C++ or java is no problem
I learnt both C and java while I was hacking - that gave me the incentive to learn I tried reading books and found them to be either very boring (lots of unnecessary stuff) or confusing.
The books that I used most was K&R C - http://www.amazon.com/Programming-Language-2nd-Brian-Kernighan/dp/0131103628 - Supposed to be a beginner's book but can be confusing. I mostly used it as a reference once I learnt C.
This book helped a lot as well: http://www.amazon.com/Data-Structures-Using-Aaron-Tenenbaum/dp/0131997467
The way I learnt C was mostly by asking around, trial and error
An online tutorial: http://crasseux.com/books/ctutorial/
And also: http://www.cprogramming.com/
I never did really learn Java - I hack around, mostly get things wrong, and sometimes get things right
A good Java tutorial - http://docs.oracle.com/javase/tutorial/
My advice, for what its worth - learn C first. That gives you a strong basis for learning other languages. I haven't really spent much time learning Java or C# but have written working programs/tools in both languages
Finally - Google is your friend when you are stuck - which you will be
Best of luck - I will be happy to help as you learn.
Paschalis said:
Where did you found FP sensor unlock code?
As far as i know, the finger print sensor unlock code is closed source!
(creating+managing fingers activities and the unlock screen activity!)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
The Atrix-Dev team did the work - you can use their weekly build or if you want to build your own, Read this post, and this thread:
http://forum.xda-developers.com/showpost.php?p=21436681&postcount=59
Sorry to say - both kangs failed when loaded on my atrix - they boot up fine, but com.android.phone crashes. must be something to do with the RIL. Will resync /rebuild/retry and see if I have better luck this time
acerbix said:
Sorry to say - both kangs failed when loaded on my atrix - they boot up fine, but com.android.phone crashes. must be something to do with the RIL. Will resync /rebuild/retry and see if I have better luck this time
Click to expand...
Click to collapse
That wont help. It's like this since a week or so. It seems the cm team has updated something that messes with film and is not compatible with the atrix dev team sources anymore. I did a logcat of it but didn't get far.
acerbix said:
The Atrix-Dev team did the work - you can use their weekly build or if you want to build your own, Read this post, and this thread:
http://forum.xda-developers.com/showpost.php?p=21436681&postcount=59
Click to expand...
Click to collapse
I compiled also CM7.1, with ALL fingerprint branches 1-2 weeks ago..
I used fp branches of atrix-dev-team: settings app, and framework base, and all their work in the top of pure CM7.1 source code, but the build result didnt include a fingerprint unlocker..
I will try acerbix's framework base to see..
Btw acerbix, what are the differences of your framework base, and framework base of the atrix-dev-team fingerprint branch?
Paschalis said:
I compiled also CM7.1, with ALL fingerprint branches 1-2 weeks ago..
I used fp branches of atrix-dev-team: settings app, and framework base, and all their work in the top of pure CM7.1 source code, but the build result didnt include a fingerprint unlocker..
I will try acerbix's framework base to see..
Btw acerbix, what are the differences of your framework base, and framework base of the atrix-dev-team fingerprint branch?
Click to expand...
Click to collapse
The Atrix-Dev-Teams's frameworks/base had deprecated files that haven't been updated since December. We found that some of the non-atrix related upstream code from CM had changed, so this was causing issues with FP unlocker. Instead of using the FP branch files, we ended up manually merging or copying the updated Atrix-Dev-Team stuff on top of the vanilla CM7.2 source for frameworks/base. The atrix related stuff is exactly the same, it's just the underyling CM7 code that is different from what is on the dev team's github. Checkout the CM7 build thread for more details and workarounds.
ghost_og said:
The Atrix-Dev-Teams's frameworks/base had deprecated files that haven't been updated since December. We found that some of the non-atrix related upstream code from CM had changed, so this was causing issues with FP unlocker. Instead of using the FP branch files, we ended up manually merging or copying the updated Atrix-Dev-Team stuff on top of the vanilla CM7.2 source for frameworks/base. The atrix related stuff is exactly the same, it's just the underyling CM7 code that is different from what is on the dev team's github. Checkout the CM7 build thread for more details and workarounds.
Click to expand...
Click to collapse
Ghost_og is correct. We built this on CM7.2 codebase by maually merging the Atrix-dev team's changes to the CM7.2 files. Without the merge, CM7.2 the Atrix-dev-team overlays will not compile.
Paschalis said:
I compiled also CM7.1, with ALL fingerprint branches 1-2 weeks ago..
I used fp branches of atrix-dev-team: settings app, and framework base, and all their work in the top of pure CM7.1 source code, but the build result didnt include a fingerprint unlocker..
I will try acerbix's framework base to see..
Btw acerbix, what are the differences of your framework base, and framework base of the atrix-dev-team fingerprint branch?
Click to expand...
Click to collapse
If you want to compile 7.1, you dont need my framework/base. Use it only if you are pulling CM7.2 code and overlaying Atrix-dev changes on it.
Here is my build of lollipop for the T800. it's useable in so far as being able to see what it's like.
It has been posted in here because it is not ready for prime time and I figured others might want to have a look. It has bugs and doesn't fully work so might not be suitable for daily use, but you decide
How to Install
Download zip to phone
Reboot to recovery
Flash CM12 zip
Flash gapps
Reboot
The first reboot may take a while so be patient.
Known Issues
Some slight graphical issues
Camera gives an error after each picture, just reopen to use use again.
Hardware keys aren't disabled if you use on-screen keys (but they are dimmed)
Video/Movies/Youtube won't play
Download Link
lonespeaker version (10th Dec) -- https://mega.co.nz/#!4ckg0BwB!AhpucIfXJ6P-Y1z7mxQgKkWzHVg4dEhkwiVEUvM3gyA
barracuda7 version -- http://forum.xda-developers.com/showpost.php?p=57300243&postcount=22
You can use any gapps but I use these ones -- https://s.basketbuild.com/gapps
Source Code
My CM12 Repo -- https://github.com/lonespeaker?tab=repositories
CyanogenMod -- https://github.com/CyanogenMod
Thanks and Credits
Thanks to @crpalmer (https://github.com/crpalmer) for the picassowifi files without whom this would not be possible.
Thanks to @Barracuda77777 (https://github.com/barracuda7), @eousphoros (https://github.com/eousphoros) for providing help and fixes here and on github.
// end
Changelog
Thanks to @Barracuda77777 - Post #22 contains an alternative version that he is working on.
http://forum.xda-developers.com/showpost.php?p=57300243&postcount=22
10th Dec
Camera is now working! But.... there is an error after you take a picture, so you need to reopen the camera app to take another picture, but at least you can take a picture!
Updated to CM12 sources 10th Dec 15:00 GMT.
7th Dec
Recents button now works. If you enable onscreen buttons, then the hardware buttons still work, albeit with the backlight on them turned off.
The sdcard seems to work, I had to reformat mine to get it recognised.
Wifi is now working thanks to barracuda7
Hoping T700/8.4 is not far behind. Can't test, but great job anyways. [emoji2]
Awesome job buddy!
hhairplane said:
Hoping T700/8.4 is not far behind. Can't test, but great job anyways. [emoji2]
Click to expand...
Click to collapse
T700 got it first check original development. Great work lone speaker on getting lollipop to the t800.
Looking forward to it !!! Great job !
Having more of a nightmare trying to work out how to use git and github to put my changes up there lol
My work is based off @crpalmer excellent work and with some not too big changes but I'd like to fork his work and then push my changes to keep his credits, but I'm having a nightmare
lonespeaker said:
Having more of a nightmare trying to work out how to use git and github to put my changes up there lol
My work is based off @crpalmer excellent work and with some not too big changes but I'd like to fork his work and then push my changes to keep his credits, but I'm having a nightmare
Click to expand...
Click to collapse
I fixed WIFI, Uploading now
Barracuda77777 said:
I fixed WIFI, Uploading now
Click to expand...
Click to collapse
excellent, how did you do it?
This is looking great! Awesome work. I realise its a very early build but hows the speed of it?
lonespeaker said:
excellent, how did you do it?
Click to expand...
Click to collapse
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Barracuda77777 said:
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Click to expand...
Click to collapse
I've been playing with ones from various places and no luck so Im so glad you figured it out. I will fork to my git and then try and work out how to add my own fixes to that fork and maybe be able to contribute this time lol
lonespeaker said:
I've been playing with ones from various places and no luck so Im so glad you figured it out. I will fork to my git and then try and work out how to add my own fixes to that fork and maybe be able to contribute this time lol
Click to expand...
Click to collapse
do you mind if I post my rom in this thread?
Barracuda77777 said:
do you mind if I post my rom in this thread?
Click to expand...
Click to collapse
No not at all, go for it
i
lonespeaker said:
No not at all, go for it
Click to expand...
Click to collapse
thank you
here is the build with WIFI working:
cm-12-20141206-UNOFFICIAL-chagallwifi.zip
here is the link to the vendor files
Also, like lonespeaker, l have borrowed heavily from @crpalmer to get this rom up and going, please thank him and also if you wish to donate to him that would be great, without him there would have been no LP rom yet
Barracuda77777 said:
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Click to expand...
Click to collapse
Always the blobs. Some day maybe we will get source for some of this stuff.
Would a build be possible for 805 as well?
Which gapps should I use...can you point me to it? Thanks
naomile said:
Which gapps should I use...can you point me to it? Thanks
Click to expand...
Click to collapse
Im pretty sure you need to use the lollipop gapps since cm12 is lollipop. http://highonandroid.com/android-apps/download-android-5-0-lollipop-gapps/
This is very promising . fun to give it a go. Thankyou for you hard work guys. As said in the OP not ready for daily driver yet. One thing I noticed as I could at the moment its all about smoothing out the bugs. The recents apps button doesn't work. (Although I did select in options to double press home button to bring up recent apps to get around it. On screen buttons disabled
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 3.18.100 and the current version upstream is 3.18.124 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/marlin
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
3.18.88 has been merged in.
3.18.89 has been merged in.
3.18.90 has been merged in.
3.18.91 has been merged in (conflict notes).
Hi Nathan, thanks for the code - built the kernel and flashed (wasn't easy at first). All working well, will use it at a later stage when I build the ROM. BTW, I am running the factory image. Credit also to Anykernel for the zip file
GeyerA said:
Hi Nathan, thanks for the code - built the kernel and flashed (wasn't easy at first). All working well, will use it at a later stage when I build the ROM. BTW, I am running the factory image. Credit also to Anykernel for the zip file
Click to expand...
Click to collapse
Not a Dev, but totally would like to give this a try if you have a zip. On the factory image + twrp 3.2.1
Sent from my [device_name] using XDA-Developers Legacy app
Hi, No problem. There you go... Just flash in TWRP and feedback if all went ok
3.18.92 has been merged in.
Hi, thanks for the code, compiled it against linaro 6.4 (built the cross-compiler following your thread). Tested for one day. All smooth. Sharing the job for those who might be interested. BTW, flashed it directly from fastboot....
Code:
fastboot flash kernel Image.lz4-dtb
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
GeyerA said:
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
Click to expand...
Click to collapse
No worries lol, gives it some life :silly:
Sent from my Pixel 2 XL using XDA Labs
GeyerA said:
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
Click to expand...
Click to collapse
Running this now, so far so good! Thanks!
Definitely interested in wire guard, but currently use WindScribe and am not sure how to properly configure it.
Will try and Frankenstein a config file together tonight and report back [emoji106]
Thanks again
Sent from my [device_name] using XDA-Developers Legacy app
Hi, question. Added DSPManager to my ROM and see that it always gets killed. Can you support the idea to build the kernel with
Code:
CONFIG_SECURITY_SELINUX=n
. Will this get me the kernel permissive and any disadvantages with this? I also see that Viper4android needs a permissive kernel.
3.18.93 has been merged in.
Somebody willing to do a build of the update to flash with fastboot?
I would if I could (still learning how to build myself)
Thnx in advance.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Somebody willing to do a build of the update to flash with fastboot?
I would if I could
Thnx in advance.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Was just going to ask if someone could point me to a good resource on how to do so. Will post anything I manage to do [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
jimbub said:
Was just going to ask if someone could point me to a good resource on how to do so. Will post anything I manage to do [emoji106]
Click to expand...
Click to collapse
Hi,
I used this for the most part: https://forum.xda-developers.com/yureka/help/guide-compiling-64-bit-android-kernel-t3352728
And this:
https://forum.xda-developers.com/an...-how-to-compile-android-kernel-t3627297/page1
Was very helpful and am building right now
Credits to those guys offcourse.
Sent from my Google Pixel using XDA Labs
Sgace said:
Hi,
I used this for the most part: https://forum.xda-developers.com/yureka/help/guide-compiling-64-bit-android-kernel-t3352728
And this:
https://forum.xda-developers.com/an...-how-to-compile-android-kernel-t3627297/page1
Was very helpful and am building right now
Credits to those guys offcourse.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
If it's ok, here is my personal first ever self built kernel from source. It's 3.18.93 and flashable in fastboot (unzip the zip and then: fastboot flash kernel Image.lz4-dtb)
Offcourse thnx to @nathanchance for the source and all the work!
Cheers
Sgace said:
If it's ok, here is my personal first ever self built kernel from source. It's 3.18.93 and flashable in fastboot (unzip the zip and then: fastboot flash kernel Image.lz4-dtb)
Offcourse thnx to @nathanchance for the source and all the work!
Cheers
Click to expand...
Click to collapse
Thanks for doing this, very much appreciate it! For some reason though, this prevented my phone from booting. Ended up restoring my boot partition and things are well now!