Related
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.
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
--WiFi (Partially: Signal strength indicator broken. Disable avoiding poor networks in advanced menu)
--GPS
--Internal sdcard
Doesn't work:
--Camera
--3G
--Sound
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
==Boot image gzip for flashing with system image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part07.20120724.img.gz
==System image gzip for flashing with boot image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part08.20120724.img.gz
Remember to always do a backup copy of your device images before flashing new ones.
Great work mate! I assume that if we want to test this later on our tablets, we need to be rooted?
suntechnic said:
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
Doesn't work:
--Camera
--WiFi
--3G
--GPS
--sdcard fuse mounting
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
Click to expand...
Click to collapse
Woohoo! Look forward to trying this!
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Great work, thanks! I'm glad that there is work going on!
Great news! As I installed ota3 before rooting my device, I hope that there will be some way to get cwm and root working...
Sent from my GT-I9300 using xda premium
Very happy that you're working on a new ROM for our device!!!
And I really hope that someone finds a way to root OTA3 since I was also too dumb to do that before updating.
Cheers!
Wow!! Keep up the good work!!!
can't wait, great work!
Great!
I thought I will be first
According to full_indigo device ID, it is AOSP, not CM? Wow..
I think together we could at last make 3G work as other hw are relatively easy to fix(may be not true for camera as sources again changed). I familiar with Qualcomm RIL framework and can't wait to see how it works with tablet and more opensource hardware module..
I also had to repack boot image to include configuration changes (init* files).
Click to expand...
Click to collapse
lenovo haven't packed init scripts? Oo how it works then? ;/
PS: hello from Russia
obscure.detour said:
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Click to expand...
Click to collapse
Lenovo released ICS open source code but they forgot to release new kernel sources. This prevents me from building bcmdhd driver instead of bcm4329. It looks like JB is oriented for NL80211 wireless interface and not WEXT.
this isnt for the K1 is it
It's for tpt only
When can we see this in a flashable version? Not to sound pushy, I know we have all see the development slow down.
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
What is TPT
Not to sound stupid but what is TPT? I have a K1 as well and am wondering if this will work?
TPT= ThinkPad Tablet
Lenovo released ICS open source code but they forgot to release new kernel sources
Click to expand...
Click to collapse
yes I also tried to get more info but for now no response. At last they released external folder of their custom build, which also contains alsa-audio, as I seen in cm9 device tree, it should fix audio with ease(maybe after patch as sources again changed in JB).
It looks like JB is oriented for NL80211 wireless interface and not WEXT.
Click to expand...
Click to collapse
but WEXT is there isn't it?
Anyway, congrats on working wifi.
Has anyone else got this up and running? I tried uninstalling CWM and reflashing part 7 and 8 but still no luck.
mr toasty said:
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
Click to expand...
Click to collapse
Some of existing software probably blocks normal startup. It is always advised to clean dalvik-cache and user data (backup first). It's up to you.
Right after Lenovo logo you should see 'Android: Optimizing applications' or something similar.
I am browsing through touchpad development forums and trying to decide which ROM to install. It seems some have working camera while others have Bluetooth, does anyone know of a ROM which has both camera and Bluetooth working?
venkythegeek said:
I am browsing through touchpad development forums and trying to decide which ROM to install. It seems some have working camera while others have Bluetooth, does anyone know of a ROM which has both camera and Bluetooth working?
Click to expand...
Click to collapse
Evervolv 4.3.1
8)
and also i believe cm 10.1 does
Problem with KitKat
Hello ,
I have not had success with version 3 kernel . After installation the system is in a loop trying to make the Cyanogenmod boot without success. Appears at a time, Moboot screen and then the screen goes black ( dimly lit ) ... Then the system reboots .
I used Tailor to create the partitions :
USB ( media) : 1.953 MiB
User ( ext3 ) : 1.758 MiB
Android (system ) : 600 MiB
Android ( cache ) : 200 MiB
Android (date ) : 23,148 GiB
Unused Space : None
I created a folder with name cminstall with the following files (all downloaded through the appropriate links) :
cm - 11-20140110 - UNOFFICIAL - tenderloin.zip
GAPPS - kk - 20131208.zip
moboot_038 - tenderloin.zip
recovery - clockwork - 6.0.4.6 - tenderloin.zip
I reseted the WebOS Touchpad through and hit the volume button until the USB connection symbol appeared. Finally , as with all Novacom drivers installed on your computer I entered the following command in the Windows command prompt :
novacom.exe boot mem :/ / < ACMInstaller5M
The system installation appears to be correct , but the system is in boot loop .
Any help is welcome .
Grateful.
CM10 has a working camera, not yet in CM11.
it's not easy to bring the camera to live on 3.x kernels mostly because of qualcomm's proprietary camera stuff. I'm working on this for about month and still have no success.
Did you try to contact qualcomm? What, if they provide you with the information you need??? That would be wonderful.....
ranjib said:
Did you try to contact qualcomm? What, if they provide you with the information you need??? That would be wonderful.....
Click to expand...
Click to collapse
Forget about getting anything from Qualcomm. Tried once and I was redirected to Code Aurora Forum and then at CAF told me that all they have is pushed to git and there's no chance to get any missing headers from them or any information. So every time I need to figure out everything on my own basing on those pieces posted to CAF.
so is cm9 still the only rom with everything working?
anonxlg said:
so is cm9 still the only rom with everything working?
Click to expand...
Click to collapse
No, the CM10.x and CM11 running 2.6.35 kernel has also a working camera. It's not yet working with 3.4 kernel.
I've created a separate thread for camera driver development for 3.x kernel: http://forum.xda-developers.com/showthread.php?t=2611497
_Dorregaray_ said:
Forget about getting anything from Qualcomm. Tried once and I was redirected to Code Aurora Forum and then at CAF told me that all they have is pushed to git and there's no chance to get any missing headers from them or any information. So every time I need to figure out everything on my own basing on those pieces posted to CAF.
Click to expand...
Click to collapse
Thank you for the answer. It sounds like you're quite angry about that.
If I was native English speaker and also a coding freak I would make another try at Qualcomm. Perhaps someone who reads this and knows a little about hardware programming can ask again?
My programming skills stopped with Sinclair ZX81 programming (more or less successful). Z80 machine language called. It's a long time ago. Sorry, I'd love to help in any way....
_Dorregaray_ said:
No, the CM10.x and CM11 running 2.6.35 kernel has also a working camera. It's not yet working with 3.4 kernel.
I've created a separate thread for camera driver development for 3.x kernel: http://forum.xda-developers.com/showthread.php?t=2611497
Click to expand...
Click to collapse
Possible explanation installation
Possible explanation installation driver development for 3.x kernel
Evervolv nondata rom from 10 feb still has a crashing cam too bad, no skype.
Cm11 on hp touchpad success
i finally got cm 11 on my hp touchpad and the camera works but is very narrow. my head looks long. not evervolv. cyanogenmod. i will be posting video's on my channel soon
camera still doesnt work
MrGHLover said:
i finally got cm 11 on my hp touchpad and the camera works but is very narrow. my head looks long. not evervolv. cyanogenmod. i will be posting video's on my channel soon
Click to expand...
Click to collapse
i have tried the latest milaq evervlov and invisilek builds and my camera still doesnt work with default app
Google Camera App and JCS CM11
venkythegeek said:
i have tried the latest milaq evervlov and invisilek builds and my camera still doesnt work with default app
Click to expand...
Click to collapse
Just installed [4.4.2] [CyanogenMod 11 by Jcsullins] [DM] [04/09/14] and then installed the new Google Camera app. HPTP camera works better than it ever has!
My AOKP build has working camera no problem
Sent from my TouchPad using xda app-developers app
Since Sony has added new v45 Adreno graphics driver in .295,I think it will be good to compile a CM-like kernel and chances are that we can fix the blue flickers in this way.However,when I mananged to get the zImage booting CM properly(no reboot),I found the screen froze at Sony logo.In the logcat I can see the system is waiting for media.audio_policy,and BootAnim,or the whole display system, isn't working.though all the Adreno libs are loaded properly and the screen param is read correctly.
Related logcat:
Code:
E/Adreno-EGLSUB( 237): <CreateImage:1837>: Offset beyond buffer size.
W/Adreno-EGL( 237): <qeglDrvAPI_eglCreateImageKHR:4637>: EGL_BAD_PARAMETER
E/GLConsumer( 237): [BootAnimation] error creating EGLImage: 0x300c
W/GLConsumer( 237): [BootAnimation] updateAndRelease: unable to createImage on display=0x1 slot=0
E/qdhwcomposer( 237): Failed to call ioctl MSMFB_OVERLAY_SET err=Invalid argument
// And there are some "MDP: unknown ioctl (....)" errors in dmesg
Code:
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
W/AudioSystem( 670): AudioPolicyService not published, waiting...
W/libc ( 236): WARNING: generic atexit() called from legacy shared library
I'm using Liquid Smooth 20140223(based on CM).And replaced the following files with stock 295.The other files are untouched.Now logcat shows nearly no error other than the ones mentioned above.
/system/etc/firmware/*
/system/etc/audio_policy.conf
/system/etc/sysmon.cfg
Click to expand...
Click to collapse
And here is how to update the Adreno libs in the system:
1.Delete these files
/system/lib/egl/* (except egl.cfg)
/system/lib/libC2D2.so
/system/lib/libc2d2_a3xx.so
/system/lib/libc2d2_z180.so
/system/lib/libgsl.so
/system/lib/libllvm-a3xx.so
/system/lib/libllvm-arm.so
/system/lib/libOpenCL.so
/system/lib/libOpenVG.so
/system/lib/libsc-a2xx.so
/system/lib/libsc-a3xx.so
Click to expand...
Click to collapse
2.Copy these files from stock 9.2.A.0.295 to the same directory(/system/vendor/lib, /system/lib will not work.)
/system/vendor/lib/egl/*
/system/vendor/lib/libadreno_utils.so
/system/vendor/lib/libC2D2.so
/system/vendor/lib/libc2d2_a3xx.so
/system/vendor/lib/libc2d2_z180.so
/system/vendor/lib/libCB.so
/system/vendor/lib/libgsl.so
/system/vendor/lib/libllvm-a3xx.so
/system/vendor/lib/libllvm-arm.so
/system/vendor/lib/libOpenCL.so
/system/vendor/lib/libOpenVG.so
/system/vendor/lib/libsc-a2xx.so
/system/vendor/lib/libsc-a3xx.so
/system/lib/egl/libGLES_android.so -> /system/lib/egl/
Click to expand...
Click to collapse
3.Boot.You can see all the libs are loaded without any error and driver info is read correctly.
Click to expand...
Click to collapse
And I will attach my kernel config and the full logcat.I didn't save dmesg...sorry...
I'm new to porting Android...Does that mean we need new HALs or something like that?Thanks!
I do not understand in porting Android. Can ask for help in the team FXP?
nnmka said:
I do not understand in porting Android. Can ask for help in the team FXP?
Click to expand...
Click to collapse
They should be already working on this...but any help is welcome
I've already got Kitkat running with 4.3 kernel sources - still no dice with the new Adreno blobs however. See the kernel source https://github.com/chirayudesai/laughing-octo-dangerzone/tree/omni/
As for the audio policy errors - they are what's causing the bootloops - you can fix that by either removing the camera HAL or fully updating it.
tilal6991 said:
I've already got Kitkat running with 4.3 kernel sources - still no dice with the new Adreno blobs however. See the kernel source https://github.com/chirayudesai/laughing-octo-dangerzone/tree/omni/
As for the audio policy errors - they are what's causing the bootloops - you can fix that by either removing the camera HAL or fully updating it.
Click to expand...
Click to collapse
THANKS A LOOOT MAN! :good::laugh:
tilal6991 said:
I've already got Kitkat running with 4.3 kernel sources - still no dice with the new Adreno blobs however. See the kernel source https://github.com/chirayudesai/laughing-octo-dangerzone/tree/omni/
As for the audio policy errors - they are what's causing the bootloops - you can fix that by either removing the camera HAL or fully updating it.
Click to expand...
Click to collapse
I used your source to compile the kernel.When I delete /system/lib/hw/vendor-camera*,booting process moves forward(the screen dims and Xperia logo gets lit,MediaScanner runs.I can even hear SMS notification sound)but there is "InputDispatcher" log spam,indicating that some window isn't responding so further input events are ignored.But after a reboot,there seems to be no problem in the logcat,except for the MSM_FB_OVERLAY/Invaild Argument error.Still nothing displayed on screen.
One weird problem:if I use Adreno libs from CM11,DDMS will grab screenshots correctly.But if stock updated ones are used,DDMS won't grab scrnshot properly.Just some lines on black ground:the attachment shows that.
If I add back the two files from stock 4.3,audio_policy error shows again.Let's see what else should be changed...
Well I've released a new omnirom test build which has everything working (except gps). The props repo is on my github and the patches for device configs are on omnirom gerrit.
Sent from my Xperia T using Tapatalk
tilal6991 said:
Well I've released a new omnirom test build which has everything working (except gps). The props repo is on my github and the patches for device configs are on omnirom gerrit.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
Maybe replacing the whole arch/arm/mach-msm directory with old OmniROM one will do...I fixed GPS on CM by doing so,one and a half month ago.But I'm not sure which file causes this...
It occurred to me that if I leave CM11 unchanged and boot on 4.3 source,there will be "Bad OVInfo" log spam,which is the same as CM booting on previous Omni kernel...I should have tested the source with OmniROM.But why does CM change the ioctl/HALs? Related files in the kernel are the same...
Well I managed to get 4.3 source working on CM/LS/... roms...Just change "struct mdp_overlay_pp_params" definition in include/linux/msm_mdp.h to
struct mdp_overlay_pp_params {
uint32_t config_ops;
struct mdp_csc_cfg csc_cfg;
struct mdp_qseed_cfg qseed_cfg[2];
};
Click to expand...
Click to collapse
Things will be okay...
Now there is the long-lasting problem...ramdom reboots...I noticed there was some Watchdog:Modem Crashed logs in last_kmsg.I tried replacing /system/etc/firmware with stock one,which resulted in a not booting phone.It got stuck after the Recovery amber light with Sony logo still on screen.ADB is not running,or to say the kernel has died - removing battery with USB plugged in doesn't make the phone shut down.Any idea to upgrade the modem software?
Well I don't have enough time to test now...schoolwork is busy...sorry..
It's OK. I'll wait for it still... The CM11 is better than stock then the reboot issue would need kernel updated to help.
Sent from my Xperia V
@OP
New source have arrived:
http://developer.sonymobile.com/dow...es/open-source-archive-for-build-9-2-a-1-199/
Maybe these are somewhat easier to port :victory:
silasje1 said:
@OP
New source have arrived:
http://developer.sonymobile.com/dow...es/open-source-archive-for-build-9-2-a-1-199/
Maybe these are somewhat easier to port :victory:
Click to expand...
Click to collapse
Thanks~After the busy weeks I'll look into it.
Doesnt FXP usually incorporate the new kernels after Sony releases the source blobs?
Im not sure how long It usually takes them though...
Brewski606 said:
Doesnt FXP usually incorporate the new kernels after Sony releases the source blobs?
Im not sure how long It usually takes them though...
Click to expand...
Click to collapse
Yes.They are working on fusion3 and rhine devices now.Our devices are not active
Got a little free time...tried extract-files.sh,and new baseband is working now.Seems more stable than before...but camera & GPS & WiFi is broken.I have added new GPS blobs into proprieatry-files.txt but no use...logcat shows startFix() error...
You can look my omnirom commits - everything is now working.
Sent from my Xperia T using Tapatalk
tilal6991 said:
You can look my omnirom commits - everything is now working.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
OK.I will be watching them.Thkx!
(Is light sensor working? Not until I removed /lib/hw/sensors.msm8960.so and pushed stock sensors.default.so did it start to work...no sure if it was my problem only.
And it seems that the stock lights.default.so can take the place of vendor/lib/hw/lights.qcom.so and lib/hw/vendor-lights.default.so. If that's common,we can remove the unnecessary files...)
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
P880-dev sources
MoltenMotherBoard!
Downloads:
MoltenMotherBoard mirror | AndroidFileHost
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
Device: platform_device_lge_p880 | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20150101
telephony: SignalStrength: hotfix GSM and TD-SCDMA
imgdiff: search the magic number 1f8b0800 starting from the ramdisk page
build: no more needed make 4.X support
p880: lights: disable backlights for notifications and power supply
p880: re-include missing GPS configuration files
AOSP updates
20141204
system/extras: exclude Google SU binaries
p880: include CM SU binaries by default
p880: force-build libemoji module
p880: force-build e2fsck module
hardware/broadcom/wlan: dhd: add missing fini interface command
p880: restore old manual density parameter
p880: restore old WiFi firmwares path
AOSP updates
20141203
init: add a mechanism to extend the property service in device configs
p880: sources up-to-date with CyanogenMod
build: allow build with make 4.1
kernel/lge/x3: corrected patch "disable setting security contexts on rootfs inodes"
build: switch to custom apns-conf.xml
manifest: update to android-4.4.4_r2.0.1
manifest: switch to CyanogenMod kernel (branch cm-12.0)
vendor/mmb: add MMB banner
vendor/mmb: add support for init.d scripts
vendor/mmb: add APNs up-to-date with OMNI
vendor/mmb: add support for ADB over the network
p880: inherit MMB vendor
p880: device_perms: add device perms for LCD density
p880: ril: remove deprecated rmnet scripts
p880: prop: disable LTE (it's not supported on P880)
p880: init: update TCP buffer sizes and thresholds
p880: init: add miscellaneous updates from CM's branch
p880: fstab: usb: detect filesystem instead of hardcoding
p880: ril: add SIM state change string
p880: ril: fix LGE recovery with new TS0710_mux driver
p880: fstab: enable /data encryptionon FOTA partition
p880: init: add TCP delayed and autotuning settings to init
p880: overlay: disable fading marquee
p880: init: enable OTG host
p880: init: small adjustements for optimal effectiveness
p880: init: restructure x3 init to accomodate kernel changes
AOSP updates
20140928
packages/apps/Camera2: fix camcorder access
frameworks/native: miscellaneous OMNI updates
hardware/libhardware: add missing declarations needed by native
manifest: update to android-4.4.4_r2
p880: gps: update GPS configuration to current standards
p880: fstab: update mount options
p880: audio_policy: use only one sampling rate on submix
p880: correct PRODUCT_MODEL string
p880: init.rc: fix DHCP permissions
p880: correct partitions sizes
p880: bluetooth: add BLE flags
p880: selinux: add a sensor and smartdimmer sepolicy
p880: init.rc: adjusted GPS permissions
p880: init.rc: additions for better battery life
p880: relaxed cpu.speeds and cpu.active consumption adjustments
p880: camera: improve AAC audio codec
p880: camera: increase Image encoding quality
p880: camera: add 720p recording in front camera
p880: camera: switch to MP4 instead of 3GP for recordings
p880: camera: add ffmpeg Audio & Video decoders
build: Prevent zip to replace /recovery partition
p880: device cleanup
AOSP updates
20140704:
hardware/broadcom/libbt: bluetooth: add support for board-specific configuration
p880: camera: add HAVE_ISO flag support
frameworks/av: camera: add HAVE_ISO flag support
frameworks/base: backlights: reintroduce button-backlight (and respective inactivity timeout)
kernel: selinux: fix /cache partition mounting (and /cal, /persist-lg, /mpt and /mnt/shell/emulated along with it)
frameworks/native: audio: register Tegra audio devices as service
p880: bluetooth: enable BLE peripheral mode
p880: use P880-dev's RIL
manifest: updates to 4.4.4_r1
AOSP updates
TB-20140527
First build
Issues:
-----
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
XDA:DevDB Information
AOSP KitKat 4.4.X, ROM for the LG Optimus 4X HD
Contributors
MoltenMotherBoard, streambinder
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
Version Information
Status: Stable
Created 2014-06-11
Last Updated 2014-08-27
Hey. I'm the project mantainer.
First of all, it's my first thread here: then, I don't want to be overbearing in offering my work, never.
If I would ever result like that, please tell me.
About the project: my team has always followed AOSP projects, even with ARMv6.
This time I decided to work on it, for this phone, as I need bugfree sources even for it, as for all the others custom ROMs.
The build shared is only the result of the first compilation, quickly tested by me.
I would like to ask you to test and report any bug you experience, so that we can reach as soon as possible a bugfree release.
Obviously, planning to update manifest to 4.4.3.
Very fast ! Tho I have issues with signal, its very low and when you try to download something from browser it crashes. Cant turn off NFC. Gallery not mounted. This ROM is going to be amazing !
ex0rt said:
Cant turn off NFC.
Click to expand...
Click to collapse
Reboot.
Any screenshot?
Thanks
ex0rt said:
Very fast ! Tho I have issues with signal, its very low and when you try to download something from browser it crashes. Cant turn off NFC. Gallery not mounted. This ROM is going to be amazing !
Click to expand...
Click to collapse
Thanks for the report.
For gallery 'not-mounting', what do you mean?
For NFC, as Adam said, you need to reboot.
Everytime you experience an issue and report it, please, add a log.
Gonna work on 4.4.3 this afternoon.
I Think On This Rom Does Not Have Reboot?
Sent from my LG-P880 using Tapatalk
streambinder said:
Thanks for the report.
For gallery 'not-mounting', what do you mean?
For NFC, as Adam said, you need to reboot.
Everytime you experience an issue and report it, please, add a log.
Gonna work on 4.4.3 this afternoon.
Click to expand...
Click to collapse
When I open it, I just couldn't access, it says storage not mounted or something similar. Looking forward for new version
Thanks @streambinder and @Adam77Root
ex0rt said:
When I open it, I just couldn't access, it says storage not mounted or something similar. Looking forward for new version
Thanks @streambinder and @Adam77Root
Click to expand...
Click to collapse
Ok, that should be easy to be fixed, I think, as I have a fix in mind!
Will make a 4.4.3 build and check it.
Would it be possible to upload your sources (I mean those repos you have altered, like frameworks/base, frameworks/av, frameworks/native, hardware/libhardware,...) so others can use it as a base for their project?
and would you mind adding a proper commit history to the p880 device tree?
laufersteppenwolf said:
Would it be possible to upload your sources (I mean those repos you have altered, like frameworks/base, frameworks/av, frameworks/native, hardware/libhardware,...) so others can use it as a base for their project?
and would you mind adding a proper commit history to the p880 device tree?
Click to expand...
Click to collapse
Yep, it would be possible and I'll do it at the same moment I publish a build using different/altered sources.
The build shared is using stock AOSP sources, plus stock P880-Dev device tree and kernel.
Obviously, will need some alterations to make everything working, then, I'll do it, of course!
streambinder said:
The build shared is using stock AOSP sources, plus stock P880-Dev device tree and kernel.
Click to expand...
Click to collapse
That means at least the following stuff doesn't work: camera, audio, sensors, Bluetooth, mobile data. I say at least as these are whose come to my mind right now.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
That means at least the following stuff doesn't work: camera, audio, sensors, Bluetooth, mobile data. I say at least as these are whose come to my mind right now.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
You can add button backlight to the list as well, but BT might even work, at least it did when I ported APSP 4.3
Adam77Root said:
That means at least the following stuff doesn't work: camera, audio, sensors, Bluetooth, mobile data. I say at least as these are whose come to my mind right now.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
laufersteppenwolf said:
You can add button backlight to the list as well, but BT might even work, at least it did when I ported APSP 4.3
Click to expand...
Click to collapse
Didn't test every function: maybe all of them are not properly working, that's why I shared a TB (Test Build).
Obviously, will do everything needed and asked by @laufersteppenwolf for next release.
Thank you for an AOSP taste for our p880! Was about time :b
MidnightDevil said:
Thank you for an AOSP taste for our p880! Was about time :b
Click to expand...
Click to collapse
You have to thank P880-dev, I did nothing but mounted correct sources, the most superficial part the whole job!
streambinder said:
You have to thank P880-dev, I did nothing but mounted correct sources, the most superficial part the whole job!
Click to expand...
Click to collapse
Thank you p880-dev :b
Aka wolf, Tetris, Adam, and all the dev fellows!
And you, 'cause I asked wolf for a aosp release but he's one lazy bum no offense stef
Some bug?
Thanks
Okay, guys. Correctly made a new 4.4.3-code based build: it's useless now to release it, as, as told by @Adam77Root and @laufersteppenwolf, many things aren't correctly working.
Used the same - updated - sources used for the first build, just re-adapted to make them compiling for AOSP.
@laufersteppenwolf: going to upload them, also because need to apply some important patches - as you know, to fix whatever is not working on AOSP.
Atleast thank you for your time for our device! I was looking forward for this. Thanks!
Sent from my LG-P880 using XDA Premium 4 mobile app