To keep my Threat "[GUIDE] Bulding CM9 from Sources for O2X (P990)" clean, I decided to open a new Threat in General Section,
lets use this Threat to discuss about compiling CM10 for the O2X.
thorstenhirsch said:
1. Changed "default revision" in manifest.xml to jellybean.
Code:
manifest.xml: <default revision="refs/heads/jellybean"
Click to expand...
Click to collapse
You have to download the jellybean sourcecode,
possibly it`s better to init the sources to a different folder e.g. /CM10/android/system
if you want to keep the CM9 sources, too.
Code:
cd ~/CM10/android/system/
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
you have to create all files for yellybean which are added to local_manifest.xml, or find jellybean branches for those files on github, (I don`t know if there are jellybean branches for our O2X, I didn`t searched for it)
When removing all entries from local_manifest.xml "repo sync" works at least. But well... I think now I've got the same as I had after "repo init [...] -b jellybean". So I still need jellybean-ed repos for /system/device/lge/star-common and p990. Guess I start with the CM9 versions...
That`s exactly what I mean,
without the necessary working jellybean files, it makes no sense to try building CM10 for O2X,
except you are able to create the necessary working jellybean files by yourself,
Stuck with this:
Code:
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: virtual void android::MediaPlayerBase::sendEvent(int, int, int)
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: candidate expects 3 arguments, 4 provided
This is the code line:
Code:
158 virtual status_t getMetadata(const media::Metadata::Filter& ids,
159 Parcel *records) {
160 return INVALID_OPERATION;
161 };
162
163 virtual status_t setLGAudioEffect(int ) { return NO_ERROR; };
164
165 virtual void sendEvent(int msg, int ext1=0, int ext2=0) { if (mNotify) mNotify(mCookie, msg, ext1, ext2); }
Any ideas of how to avoid this?
Hey.
Without some serious modifications or to be more precisely hacks. Like the one introduced in cm9 and more. Like disabling and hacking around the project butter features. Like dealing with the vsync etc.
Anyway. Without these features a cm10 build doesn't make sense at all. Just more hacks and instabilities. It won't run better than the cm9 builds and the biggest improvement is the smoothness. The other stuff isn't worth the update. Without a OEM update to ICS a jb build isn't worth the amount of work. Not even the compile time. Sorry to say that. (And yeah I looked into it and had some progress. However it's not worth the time.)
Sent from my Nexus S using xda app-developers app
Benee said:
Hey.
Without some serious modifications or to be more precisely hacks. Like the one introduced in cm9 and more. Like disabling and hacking around the project butter features. Like dealing with the vsync etc.
Anyway. Without these features a cm10 build doesn't make sense at all. Just more hacks and instabilities. It won't run better than the cm9 builds and the biggest improvement is the smoothness. The other stuff isn't worth the update. Without a OEM update to ICS a jb build isn't worth the amount of work. Not even the compile time. Sorry to say that. (And yeah I looked into it and had some progress. However it's not worth the time.)
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Yeah, i think all we know that. But i'm trying to make it with educational purpouses. I don't want to make a ROM with graphic acceleration and the other stuff that didn't work in cm9, cause it's impossible.
The only one thing i'mt trying is to bake some from sources and make it run on my phone. And maybe make a start point to make my roms for personal use.
If anyone want to help, i would be greatfull. If you don't want to help, it's ok. Probably you have better things to do xD.
Cya
ethansp said:
Stuck with this:
Code:
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: virtual void android::MediaPlayerBase::sendEvent(int, int, int)
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: candidate expects 3 arguments, 4 provided
This is the code line:
Code:
158 virtual status_t getMetadata(const media::Metadata::Filter& ids,
159 Parcel *records) {
160 return INVALID_OPERATION;
161 };
162
163 virtual status_t setLGAudioEffect(int ) { return NO_ERROR; };
164
165 virtual void sendEvent(int msg, int ext1=0, int ext2=0) { if (mNotify) mNotify(mCookie, msg, ext1, ext2); }
Any ideas of how to avoid this?
Click to expand...
Click to collapse
You need to update this file to JB. It's currently based on the ICS MediaPlayerInterface.h and then you need some audio hacks (the shim by arcee).
With the above I was talking about: Without these hacks the build will run worser than a sdk port. Unusable worse. Even with dev spirit it was just a temp flash.
Benee said:
You need to update this file to JB. It's currently based on the ICS MediaPlayerInterface.h and then you need some audio hacks (the shim by arcee).
With the above I was talking about: Without these hacks the build will run worser than a sdk port. Unusable worse. Even with dev spirit it was just a temp flash.
Click to expand...
Click to collapse
Yes, probably you have all the reason about this. But, if i can taking some advantages in the developing of a "experimental" build waiting for some sources from nvidia/LGE an then implement it. I think the work is not going all to trash. Maybe in the future, can we use it, probably not. Ok. But if people want, what is the inconvenience of "loosing" time trying to make it work?
Cya.
Ok, i've do some advances, now logcat is running but stuck on 2nd lg boot logo.
If want to know the changes i have make: https://github.com/ethansp
And the logcat: http://pastebin.com/SZGwM0Xm
The errors i've seen:
Code:
E/libEGL ( 1175): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 1175): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
F/libc ( 1175): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 1192 (SurfaceFlinger)
Code:
D/dalvikvm( 1176): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1176): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
Code:
I/ServiceManager( 1008): service 'media.audio_flinger' died
I/ServiceManager( 1008): service 'media.player' died
I/ServiceManager( 1008): service 'media.camera' died
I/ServiceManager( 1008): service 'media.audio_policy' died
Just a few ideas...
Regarding the EGL errors: probably some of the proprietary vendor files are missing (check /bin, /etc, /lib) or not included correctly.
The audio errors are most likely the result of the changes Google made to the audio system of JB. If these errors are critical to booting try compiling the rom without audio.
Good luck and keep on trying!
Have a nice day!
ethansp said:
Ok, i've do some advances, now logcat is running but stuck on 2nd lg boot logo.
If want to know the changes i have make: https://github.com/ethansp
And the logcat: http://pastebin.com/SZGwM0Xm
The errors i've seen:
Code:
E/libEGL ( 1175): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 1175): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
F/libc ( 1175): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 1192 (SurfaceFlinger)
Click to expand...
Click to collapse
EGL issues are related to the missing egl hacks from arcee (here for ics) (I think you need add even more hacks than in ics due to vsync etc.).
ethansp said:
Code:
D/dalvikvm( 1176): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1176): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
Click to expand...
Click to collapse
This error is related to above error.
ethansp said:
Code:
I/ServiceManager( 1008): service 'media.audio_flinger' died
I/ServiceManager( 1008): service 'media.player' died
I/ServiceManager( 1008): service 'media.camera' died
I/ServiceManager( 1008): service 'media.audio_policy' died
Click to expand...
Click to collapse
Same as above. Your complete egl driver etc is going down.
Raum1807 said:
Just a few ideas...
Regarding the EGL errors: probably some of the proprietary vendor files are missing (check /bin, /etc, /lib) or not included correctly.
The audio errors are most likely the result of the changes Google made to the audio system of JB. If these errors are critical to booting try compiling the rom without audio.
Good luck and keep on trying!
Have a nice day!
Click to expand...
Click to collapse
Getting audio running shouldn't be too difficult. You basically need to add the ics audio shim and make some adjustment to eventual JB changes. It will most likely bug around without working audio (mediaserver is crashing)
EDIT:
Ok. Had a closer look. In CM nearly everything is implemented. Like this for audio and this for egl etc. You just need to update the cam lib, the audio includes and it should boot and work partly.
Benee said:
EGL issues are related to the missing egl hacks from arcee (here for ics) (I think you need add even more hacks than in ics due to vsync etc.).
This error is related to above error.
Same as above. Your complete egl driver etc is going down.
Getting audio running shouldn't be too difficult. You basically need to add the ics audio shim and make some adjustment to eventual JB changes. It will most likely bug around without working audio (mediaserver is crashing)
EDIT:
Ok. Had a closer look. In CM nearly everything is implemented. Like this for audio and this for egl etc. You just need to update the cam lib, the audio includes and it should boot and work partly.
Click to expand...
Click to collapse
Lot of thanks benee for taking some time to watch it.
I have moded the expresions about the storages (changed /mnt/sdcard to /storage/scdcard0 ) and moded de libslights.c in the frameworks. a new logcat and seems very improved. Stays the screen black cause not working properly de egl driver. I'm going to take a look. I think there is a problem with kernel>drivers expresions.
Latest logcat if you want to take a look: http://pastebin.com/L3hjvTEi
ethansp said:
Lot of thanks benee for taking some time to watch it.
I have moded the expresions about the storages (changed /mnt/sdcard to /storage/scdcard0 ) and moded de libslights.c in the frameworks. a new logcat and seems very improved. Stays the screen black cause not working properly de egl driver. I'm going to take a look. I think there is a problem with kernel>drivers expresions.
Latest logcat if you want to take a look: http://pastebin.com/L3hjvTEi
Click to expand...
Click to collapse
I've send you some pull requests. Due to lag of time I havn't compiled them. Hope you can fire up a compile and send me a log and report if you noticed a improvement.
Benee said:
I've send you some pull requests. Due to lag of time I havn't compiled them. Hope you can fire up a compile and send me a log and report if you noticed a improvement.
Click to expand...
Click to collapse
A lot of thanks. i've see it. Doing the compile now. When finish i will post the results.
Hi, no solution. Stills blackscreen, same EGL errors, and i discovered, logcat only work on first boot. if i pull battery off and on, no more logcat until wipes.
I let here the logcat: http://pastebin.com/TH1wCsvV
Thanks for help.
ethansp said:
Hi, no solution. Stills blackscreen, same EGL errors, and i discovered, logcat only work on first boot. if i pull battery off and on, no more logcat until wipes.
I let here the logcat: http://pastebin.com/TH1wCsvV
Thanks for help.
Click to expand...
Click to collapse
Oh sure.. Yeah wait a moment . We need some more ported over changes.
EDIT:
use this this and that instead of the cm ones or cherry-pick the changes.
EDIT2:
Doing some blind RIL changes. Maybe they're working out - currently my girlfriend uses my o2x because her phone got stolen.
EDIT3:
and add frameworks_base. If the phone boots, please send me a adb logcat -b radio. I need the logcat from booting till 30 secs booted up rom. I suggest routing it to a txt file because the log is quite spammy.
EDIT4:
I created a repo for easier syncing: here
Benee said:
Oh sure.. Yeah wait a moment . We need some more ported over changes.
EDIT:
use this this and that instead of the cm ones or cherry-pick the changes.
EDIT2:
Doing some blind RIL changes. Maybe they're working out - currently my girlfriend uses my o2x because her phone got stolen.
EDIT3:
and add frameworks_base. If the phone boots, please send me a adb logcat -b radio. I need the logcat from booting till 30 secs booted up rom. I suggest routing it to a txt file because the log is quite spammy.
Click to expand...
Click to collapse
Ok. I'm at work right now, in 5 hours i go home. Expect results in ~7 hours or tomorrow in morning.
Thanks a lot for all your help.
you're the man benee
Benee said:
Oh sure.. Yeah wait a moment . We need some more ported over changes.
EDIT:
use this this and that instead of the cm ones or cherry-pick the changes.
EDIT2:
Doing some blind RIL changes. Maybe they're working out - currently my girlfriend uses my o2x because her phone got stolen.
EDIT3:
and add frameworks_base. If the phone boots, please send me a adb logcat -b radio. I need the logcat from booting till 30 secs booted up rom. I suggest routing it to a txt file because the log is quite spammy.
EDIT4:
I created a repo for easier syncing: here
Click to expand...
Click to collapse
Ok, phone boots, but the radio logcat only output this:
Code:
D/RILD ( 1011): radio disabled
D/RILB ( 1268): /proc/[email protected] [email protected] loglevel=0 muic_state=1 lpj=9994240 CRC=3010002a8e458d7 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800 androidboot.hardware=p990
D/RILB ( 1268): getLteOnCdmaMode=0 curVal=-1 product_type='' lteOnCdmaProductType=''
I have to say, i didn't understand the "edit 3" add frameworks base, where? I have synced it but have to take out from star.mk cause that files now exist only in frameworks/native.
Edit: forgot to say: FC's com.android.phone repeteavly. Tonyp, how did you that? xD
Edit2: Latest logcat without -b radio trigger: http://pastebin.com/ASUyM0vR
When load this service "884.I/SystemServer( 1270): AssetRedirectionManager Service" (you can find it at end of logcat) the logcat stops, is like usb get disabled. If i reboot, no more logcat output until full wipes.
Edit3: took off phone.apk and FC's media, and voice syntethizer.
Related
An official OTA for GSM Nexus S (GT-i9020T/i9023) is now available:
http://android.clients.google.com/packages/ota/google_crespo/9ZGgDXDi.zip (thanks bl1nkk)
Because an official release is now available, this ROM is now EOL and will receive no further support.
By popular demand, here's a new thread for my port of the Jelly Bean SDK. This is a continuation of DaxMax's thread, so if you want to see previous discussion, look there. (Thanks to DaxMax for putting up with discussion of what is essentially a distant cousin of his original ROM for so long on his thread.)
http://files.mrks.me/update-crespo-JRN83C-preview-2012063001.zip http://goo.gl/40Cxf (thanks to bl1nkk for the hosting)
Code:
MD5: 015e322b048b7e1464a90a87a5a6bcb1
SHA1: 3aca40900b40625505d4b6c0afce93c31e33770d
SHA256: 3b0b76444c307f4ffe685205cb92ad6060d957152dadef72444b3f2407510a34
Service Pack 4 for this ROM: https://docs.google.com/uc?export=download&id=0BwGWbMaI9twWRHFrRUROcDhIeVk http://goo.gl/ZVlQS (many thanks to bl1nkk for hosting) (alternately, check thread for mirrors) (see this post for changelog)
Code:
MD5: ac85b1e309ba3a3f438efe0954c11c32
SHA1: d147f777f8594c5d33dfd480143758107ff1baab
SHA256: 951d39e75e8d4891e18a1da3896567f293074262d8aef3cd0021d4239492cf00
Flash the main ROM zip (update-crespo-JRN83C-preview-2012063001.zip) first, then the service pack.
These are zips which should be flashable from ClockworkMod or other recovery. They contain /system and a boot.img and will not touch your recovery, data, or SD card. I believe you need to do a full wipe if you're flashing over ICS or below.
This ROM is quite stable and almost fully working at this point. Highlights:
Based on the Jelly Bean SDK release (JRN83C), with Google apps and other components from the Nexus 7 factory image (JRN84D). Hardware-related files and kernel from the ICS IMM76D release for Nexus S. (The source for the GPL components (mainly the kernel) is available from http://android.googlesource.com/.) The wifi hack (libhardware_legacy.wifi.so) is posted farther down this thread (including source).
Remarkably smooth. Project Butter really lives up to its name. (I've made one tweak in the init.herring.rc to make the default ICS cpufreq governor more aggressive in upping the clock frequency, in order to simulate the change in governor in the Jelly Bean kernel.)
Wifi, Bluetooth, GPS, GSM all work. NFC should work.
Sound and calls work as of July 9 (SP1).
Video recording works as of July 10 (SP2).
Tethering, including wifi tethering, works as of July 11 (SP3).
Calls via a Bluetooth headset work as of July 11 (SP3).
Google Now/voice search, offline voice text input, voice dialing, and text-to-speech all work as of July 11 (SP4).
Broken:
Voice/video chat in Google Talk Patch available to fix video/voice chat, see this post. (thanks selectormoldy for the crash log leading to fix)
Media scanning (used by Gallery and Music to find files on the SD card, among other things) is broken for some, but not for others. This appears to be triggered by something stored on the SD card/external storage. (thanks spupuz)
High-performance WifiLocks (the wifi driver drops into low-power mode when the screen turns off, even though it shouldn't when a high-perf WifiLock is held).
Sound. Note that means no phone calls of any kind, not even emergency calls, so this isn't ready for serious day-to-day use. This is likely unreasonably difficult to solve given that we have an official OTA coming in 2-3 weeks; look upthread for an account of what's been tried.
Ambient light sensor. It worked in the Galaxy Nexus-based ROM, and I'm not sure why it doesn't work in this one; in any event I'm not planning on putting more time into figuring out why. The light sensor works, but automatic brightness setting does not -- presumably something in the Android framework needs to be changed.
Video recording (as reported by users in this thread).
The Google Now/Google Search app may crash (reported by users in this thread). (This should be fixed in SP3 -- if you're still having problems, please provide a logcat.)
Tethering via wifi.
Phone calls via Bluetooth.
Voice dialing.
Voice search in Google Now. (The app fails to recognize when you stop speaking, so the search is never performed.)
Text-to-speech functionality with Google TTS (Pico TTS works).
Notes:
If the first-run setup keeps crashing on you: from the language selection (first) screen, tap on the four corners of the screen, proceeding clockwise from top left. This will bypass the first-run setup; you can then set up a Google account manually in Settings. (thanks urko95) (If you are still experiencing this with SP4, please report in this thread. A logcat would be helpful.)
Note also that there won't be much in the way of support -- I do have other things that I really should be doing ...
Service Pack 4
Service Pack 4 for the 2012/06/30 SDK JRN83C ROM. This can be flashed on top of the original JRN83C ROM with or without any of the previous service packs applied.
https://docs.google.com/uc?export=download&id=0BwGWbMaI9twWRHFrRUROcDhIeVk http://goo.gl/ZVlQS (many thanks to bl1nkk for hosting) (alternately, check thread for mirrors)
Changes in SP4:
Added the files in /system/usr/srec/en-US from the Nexus 7 JRN84D factory image -- Google Now/voice search, voice dialing, and offline voice dictation input all work.
Added /system/lib/libpatts_engine_jni_api.so from the Nexus 7 JRN84D factory image -- Google TTS now works. (Pico TTS already worked in previous releases.)
Replaced /system/app/SetupWizard.apk with the version from the Galaxy Nexus JRN84D build -- first-run setup should now display properly. (For the curious, I got the apk from Koush's jb-takju.zip and verified that it matched the JRN84D OTA via the SHA1 sums in the OTA update package.)
Added /system/app/{LiveWallpapers,VisualizationWallpapers,HoloSpiralWallpaper}.apk from Nexus S IMM76D to provide some live wallpapers.
Reverted a change in /system/framework/framework-res.apk to the default wallpaper; defaulting to the Nexus live wallpaper hurts performance.
Changes in SP3 (included in SP4):
libhardware_legacy.wifi.so updated to support wifi tethering. (See the linked post for source code.)
Permissions on /system/etc/bluetooth fixed to allow BlueZ to see its config files -- fixes phone calls over a Bluetooth headset, plus lots of other Bluetooth-related functionality.
hwcomposer.s5pc110.so replaced with a build from Jelly Bean-based source -- hopefully fixes hwcomposer bugs people have been experiencing. (See this post for more information.)
Removed /system/app/QuickSearchBox.apk to prevent conflicts with Google Now -- should fix Google Now access for most people. If you're still seeing problems, please provide a full logcat. (thanks afzalarsalan)
Changes in SP2 (included in SP3 and later):
New boot.img with /init.herring.rc edited to fix a thinko which was preventing CPU governor tweak from taking effect -- should result in more smoothness.
/system/build.prop edited to report as a "user" build instead of an "eng" build -- resolves red border flashing on screen. (thanks capez)
/system/etc/media_codecs.xml and /system/etc/media_profiles.xml copied from the Jelly Bean device/samsung/crespo tree -- video recording now works.
/system/lib/libjni_mosaic.so copied from Nexus 7 JRN84D image -- panoramic camera now works.
More changes from Nexus S ICS /system/framework/framework-res.apk integrated -- automatic brightness setting now enabled, tethering menu now enabled (wifi tethering is still broken).
Changes in SP1 (included in SP2 and up):
Jelly Bean audio HAL modules included -- sound now works.
/system/build.prop edited to report as a "user" build instead of an "eng" build -- resolves red border flashing on screen. (thanks capez) I screwed up integrating this fix, so it's not actually part of SP1. Will be in SP2.
/system/bin/make_ext4fs and /system/bin/setup_fs replaced with Nexus 7 JRN84D binaries -- fixes installing apps to SD card. (thanks smojica for reporting)
Removed LegacyCamera app to avoid having two camera apps.
Code:
MD5: ac85b1e309ba3a3f438efe0954c11c32
SHA1: d147f777f8594c5d33dfd480143758107ff1baab
SHA256: 951d39e75e8d4891e18a1da3896567f293074262d8aef3cd0021d4239492cf00
This is safe to flash on top of your ROM, whether or not you have any of the previous service packs installed.
I'll probably continue to distribute updates to this ROM via these service packs, mostly to save everyone bandwidth. (As with MS Windows service packs, they will be cumulative -- e.g. SP5, assuming there is one, will be flashable on top of the base ROM or any of SP1-4.)
FAQ
Frequently Asked Questions:
Did you see that the Jelly Bean source is out?
Yes -- and we're using it to provide audio, among other things. It was faster to use bits and pieces of the source to fix the SDK port than it was to sync and build the whole thing from source -- particularly since Google has not released proprietary blobs matching Jelly Bean for the Nexus S yet.
How do I get root?
The same way you do on a stock ROM -- flash Superuser. (thanks DaxMax)
The first-run setup keeps crashing!
From the language selection (first) screen, tap on the four corners of the screen, proceeding clockwise from top left. This will bypass the first-run setup; you can then set up a Google account manually in Settings. (thanks urko95)
Google Now crashes when I try to use GPS/navigation!
Install Google Maps from Market. (Several of the standard Google apps were not included in the base ROM to save download time.) (thanks legolas93)
My language is something other than US English, and offline speech recognition/voice input doesn't work!
Google's only implemented offline speech recognition for US English at the moment -- all other languages (including other English variants) still rely on Google servers to perform speech recognition.
I can't install the XDA app.
I can't install apps to SD card!
Flash Service Pack 1 or later.
I flashed http://www27.zippyshare.com/v/48676662/file.html, and I still can't install apps to SD card!
Flash Service Pack 1 or later. That zip only includes audio HAL modules and a fix for the red flashes on screen, not the rest of the SP1 bugfixes.
What are those red flashes on screen?
Video recording doesn't work!
Where's the tethering menu?
Flash Service Pack 2 or later.
The bar at the top of the home screen doesn't launch Google Now!
Wifi tethering doesn't work!
My Bluetooth headset/hands-free kit can't be used in phone calls!
Flash Service Pack 3 or later.
Google Now doesn't recognize when I stop talking!
Text-to-speech doesn't work!
Why is "Welcome" in the first-run setup screen so giant?
Flash Service Pack 4 or later.
I flashed 1337kernel, and now XYZ doesn't work!
See this post by Oodie for advice.
XXX/YYY/ZZZ doesn't work!!!!!!
Make sure you've done a full wipe (including data) and flashed the ROM correctly (base ROM, then the latest service pack). Try using the stock kernel included with this ROM; people have reported problems using custom kernels, particularly with sound. If the problem persists, pleave provide a detailed description of the problem and a logcat so that we can help you.
Why not do a full build from source?
This was quicker for me and works quite well. That said, anyone who wants to attempt a build from AOSP and/or CM10 source is welcome to do so, and I'll be happy to answer any questions that may come up in the process.
From the first 30 minutes playing with it.. Google Search / Now takes into account what your saying but doesnt do anything with the data - But doesnt seem to crash with SP1 Also a little big laggy here and there. But pretty much perfect. EXCELLENT ROM Steven676. I have been so excited for this release Thankyou!!
EDIT: Also get a red flash around screen when unlocking phone (still not a huge thing) :]
Looks great, thank you!
So flash the rom, then flash the service pack in op and then service pack in second post?
g1user101 said:
So flash the rom, then flash the service pack in op and then service pack in second post?
Click to expand...
Click to collapse
Both are the same, as I understand
Flashed to SP1 half a day ago and it was rocking! Kudos for this! :good:
I tried flashing GN's JB-SuperSU.zip, it seems to be incompatible (constantly crashing on the permission dialog). Anyone got ideas of how to get root?
nice thread !! i want to try it but i use the Phone calls via Bluetooth on my car radio !! i cant make call when the bluetooth connect on my car radio ?
thanks
thanr said:
Flashed to SP1 half a day ago and it was rocking! Kudos for this! :good:
I tried flashing GN's JB-SuperSU.zip, it seems to be incompatible (constantly crashing on the permission dialog). Anyone got ideas of how to get root?
Click to expand...
Click to collapse
Superuser - Download it and flash it.
DaXmax said:
Superuser - Download it and flash it.
Click to expand...
Click to collapse
Worked
cant bypass the setup screen, tapping 4 corners does nothing? no idea
Bringing over some other tidbits from the other thread about what's broken in SP1:
Automatic brightness setting. I've checked that the ambient light sensor works through another app, so presumably something in the Android framework is missing.
Video recording. Trying to start video recording turns up this set of errors:
Code:
V/videocamera( 2240): startVideoRecording
D/CameraStorage( 2240): External storage state=mounted
V/videocamera( 2240): initializeRecorder
W/StagefrightRecorder( 97): Max file duration is not positive: 0 us. Disabling duration limit.
W/StagefrightRecorder( 97): Target duration (0 us) too short to be respected
V/videocamera( 2240): New video filename: /mnt/sdcard/DCIM/Camera/VID_20120710_025327.mp4.tmp
D/CameraSource( 97): Camera does not support setVideoSize()
E/CameraHardwareSec( 97): Non-metadata buffer mode is not supported!
W/StagefrightRecorder( 97): Failed to create the encoder
D/CameraSource( 97): reset: E
W/CameraService( 97): attempt to use a locked camera from a different process (old pid 97, new pid 2240)
D/CameraSource( 97): reset: X
E/MediaRecorder( 2240): start failed: -2147483648
E/videocamera( 2240): Could not start media recorder.
E/videocamera( 2240): java.lang.RuntimeException: start failed.
E/videocamera( 2240): at android.media.MediaRecorder.start(Native Method)
E/videocamera( 2240): at com.android.camera.VideoCamera.startVideoRecording(VideoCamera.java:1484)
E/videocamera( 2240): at com.android.camera.VideoCamera.onShutterButtonClick(VideoCamera.java:614)
E/videocamera( 2240): at com.android.camera.ShutterButton.performClick(ShutterButton.java:108)
E/videocamera( 2240): at android.view.View$PerformClick.run(View.java:16966)
E/videocamera( 2240): at android.os.Handler.handleCallback(Handler.java:615)
E/videocamera( 2240): at android.os.Handler.dispatchMessage(Handler.java:92)
E/videocamera( 2240): at android.os.Looper.loop(Looper.java:137)
E/videocamera( 2240): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/videocamera( 2240): at java.lang.reflect.Method.invokeNative(Native Method)
E/videocamera( 2240): at java.lang.reflect.Method.invoke(Method.java:511)
E/videocamera( 2240): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/videocamera( 2240): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/videocamera( 2240): at dalvik.system.NativeStart.main(Native Method)
V/videocamera( 2240): Releasing media recorder.
V/videocamera( 2240): Empty video file deleted: /mnt/sdcard/DCIM/Camera/VID_20120710_025327.mp4.tmp
This is suggestive of a problem with the video encoding or camera HAL, but replacing libstagefrighthw.so with one built from the Jelly Bean device/samsung/crespo tree doesn't make a difference, and building camera.herring.so from that tree completely breaks the camera app (segfault in a call to libc from camera.herring.so).
There's a thinko in /init.herring.rc which means the tweak to the ondemand CPU governor isn't actually applied.
Lots of reports of Google Now and/or Google Search crashing. A logcat would be helpful for anyone trying to diagnose the problem.
Other notes:
Any ICS kernel should work with this Jelly Bean ROM. People have reported a variety problems with custom kernels. Please make sure you're using the stock kernel before reporting bugs.
That said, it appears that the official release will use a different wireless driver (the bcmdhd driver which Galaxy Nexus already uses), so ICS kernel releases may need some changing for Jelly Bean.
If you're having problems with Market or something else crashing, please provide a logcat -- otherwise problems are difficult to diagnose. Make sure you've wiped all data if you're flashing over an existing ICS installation.
There will be an SP2 to fix the governor issue, along with any other easy wins that crop up, but I'd gently suggest that most further effort should be devoted to a build from source.
figured it out followed this to get past the setup screen:
http://www.youtube.com/watch?v=L5XjF6sPef4
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
urko95 said:
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
Click to expand...
Click to collapse
urko what u mean all fixed ??
urko95 said:
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
Click to expand...
Click to collapse
Can you explain more?
legolas93 said:
Can you explain more?
Click to expand...
Click to collapse
Sorry, I mean that all fixes are applyed, the fixes that Steve realased!
EDIT: Uploading it right now
Regards,
Urko
why is the "ro.build.type" in sp1 still "eng" in stead of "user"?
Hello steven i flashed this port this morning... working very smooth . One problem i have which I'd like to solve. When trying to restore to 4.0.4 cyber or m6 i got md5 mismatch
.. any way i could restore them ? Thank you
Sent from my Nexus S using xda app-developers app
e way we got a little help from Broadcom.
David has given us all we need to build CM7 ..
Thanks for the information whitexp.
Based on your feedback, we've noted the following issues with the current BCM21553 CM7 port, and will investigate to see if we can help resolve them:
1) Colors are swapped when using software rendering. There are fixes for this, which involve copying libraries from the stock firmware, but they introduce stability issues.
2) libGLES_hgl.so has many shared library dependencies and does not work with the stock surfaceflinger/libui.
I was able to build CM7, with a couple modifications to your device tree, and replicate the color swap issue seen with software rendering.
We're working on a solution to formally release our software, but in the meantime, we have a test patch to fix the color swap issue without using any additional prebuilt libraries.
To try this, please copy the gralloc folder from hardware/libhardware/modules/gralloc (http://madteam.co/forum/go.php?url=aHR0cHM6Ly9naXRodWIuY29tL0N5YW5vZ2VuTW9kL2FuZHJvaWRfaGFyZHdhcmVfbGliaGFyZHdhcmUvdHJlZS9nYi1yZWxlYXNlLTcuMi9tb2R1bGVzL2dyYWxsb2M) to your device tree and apply the attached patch to use the correct fbFormat for the hardware.
You will also need to modify the LOCAL_MODULE in Android.mk with the correct board name.
Thanks,
David
Patch inline:
diff --git a/modules/gralloc/framebuffer.cpp b/modules/gralloc/framebuffer.cpp
index fe57a8a..a46d46e 100644
--- a/modules/gralloc/framebuffer.cpp
+++ b/modules/gralloc/framebuffer.cpp
@@ -355,7 +355,7 @@ int fb_device_open(hw_module_t const* module, const char* name,
if (status >= 0) {
int stride = m->finfo.line_length / (m->info.bits_per_pixel >> 3);
int format = (m->info.bits_per_pixel == 32)
- ? HAL_PIXEL_FORMAT_RGBX_8888
+ ? HAL_PIXEL_FORMAT_BGRA_8888
: HAL_PIXEL_FORMAT_RGB_565;
#ifdef NO_32BPP
format = HAL_PIXEL_FORMAT_RGB_565;
Of course these are only temporary drivers ..
Click to expand...
Click to collapse
LINK FOR ORIGINAL POST: http://madteam.co/forum/general-77/%28dev%27s%29%28broadcom%29-open-dialogue-with-broadcom/60/
This is just a hacked up solution to the blue-red color switch problem that was haunting devs for a very long time...
I'm not sure if we even have a cm7 build that can even boot to that point!
What you highlighted in red is the difference between the 'before' and 'after' code. Basically the only thing changed is the order in which colors are read by the GPU. Before it was reading red-green-blue-(ignores alpha), now it's reading blue-green-red-alpha.
Now that it's reading alpha too I think it might fix some crashes with some games but i'm not sure
Ooops!!! Wrong section i guess
ZakooZ said:
This is just a hacked up solution to the blue-red color switch problem that was haunting devs for a very long time...
I'm not sure if we even have a cm7 build that can even boot to that point!
What you highlighted in red is the difference between the 'before' and 'after' code. Basically the only thing changed is the order in which colors are read by the GPU. Before it was reading red-green-blue-(ignores alpha), now it's reading blue-green-red-alpha.
Now that it's reading alpha too I think it might fix some crashes with some games but i'm not sure
Click to expand...
Click to collapse
Can't find the sense about change the RGBA order :silly:
Now colors not are swapped! Yeeeeaaaahh
Thats one small step for Cm7, One giant leap for Broadcomm.. (yes i am taking the ****)
I have tried to compile AOKP 4.1.2 with this Cherry Pick:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_base refs/changes/85/13285/9 && git cherry-pick FETCH_HEAD
and I get this near the end of the build:
target SharedLib: camera.msm7x30 (out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so)
/home/theapant/aokp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/cameraHAL.o: in function camera_set_preview_window(camera_device*, preview_stream_ops*):frameworks/base/include/ui/cameraHAL.cpp:494: error: undefined reference to 'android:verlay:verlay(void (*)(void*, int), void (*)(void*, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(void*, void*), void*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so] Error 1
make: *** Waiting for unfinished jobs....
I have build aokp before using camcory's prebuilt, and everything works fine but I want to be able to oc and use my own build, with working camera. I tried editing the cameraHAL.cpp, changing void to int, but it doesn't work, it just throws some other related error. I think, I am missing some makefile somewhere, but I'm not certain where. Thanks.
theAPANT said:
I have tried to compile AOKP 4.1.2 with this Cherry Pick:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_base refs/changes/85/13285/9 && git cherry-pick FETCH_HEAD
and I get this near the end of the build:
target SharedLib: camera.msm7x30 (out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so)
/home/theapant/aokp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/cameraHAL.o: in function camera_set_preview_window(camera_device*, preview_stream_ops*):frameworks/base/include/ui/cameraHAL.cpp:494: error: undefined reference to 'android:verlay:verlay(void (*)(void*, int), void (*)(void*, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(void*, void*), void*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so] Error 1
make: *** Waiting for unfinished jobs....
I have build aokp before using camcory's prebuilt, and everything works fine but I want to be able to oc and use my own build, with working camera. I tried editing the cameraHAL.cpp, changing void to int, but it doesn't work, it just throws some other related error. I think, I am missing some makefile somewhere, but I'm not certain where. Thanks.
Click to expand...
Click to collapse
I had this issue camcory never pushed the finished camera sources
Here
https://docs.google.com/file/d/0Bwu6jmegWBFQRXNpRFAwc2dZam8/edit
Also, if RIL (data) doesn't work pull the hardware/ril folder from cm10.
I don't have the sources for aokp atm but I think I had to do a few other things to get everything working but they broke camera
Sent from my Nexus 7 using xda app-developers app
Re awaking this thread, hopefully someone can help. OK i am having allot of problems building /hardware/qcom/display and surfacflinger on 4.2.2 liquidsmooth so far i have just removed the problematic things from the specific Android.mk but I'm stilling having lots of problems. Ill post specific error if that is helpful. What have you done to get it to build, I'm downloading aosp now to see if the loquidsmooth team hasnt pushed files but i doubt it. Thanks
Sent from my Nexus 7 using xda app-developers app
CM10.1 wpa problem
I'm getting this and don't know how to fix it. Hopefully one of you do, I had to try using cm10.1 sources instead of liquidsmooth because they haven't pushed changes yet. Any ideas? Thanks
/home/theapant/cm10.1/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/theapant/cm10.1/out/target/product/ancora_tmo/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/driver_wext.o: in function wpa_driver_wext_ops:driver_wext.c(.data.rel.ro.wpa_driver_wext_ops+0x198): error: undefined reference to 'wpa_driver_signal_poll'
/home/theapant/cm10.1/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/theapant/cm10.1/out/target/product/ancora_tmo/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/driver_wext.o: in function wpa_driver_wext_ops:driver_wext.c(.data.rel.ro.wpa_driver_wext_ops+0x1a0): error: undefined reference to 'wpa_driver_wext_driver_cmd'
collect2: ld returned 1 exit status
make: *** [/home/theapant/cm10.1/out/target/product/ancora_tmo/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant] Error 1
make: *** Waiting for unfinished jobs....
Well I deleted /external/wpa_supplicant_8 and renamed the wpa_supplicant_6 to 8 and compiled and I got it to build.
Package complete: /home/theapant/cm10.1/out/target/product/ancora_tmo/cm-10.1-20130301-UNOFFICIAL-ancora_tmo.zip
md5: e714e16988f891693df172e405be1b54
Unfortunately it doesn't boot (black screen) perhaps an issue with using the prebuilt kernel in device/samsung/ancora_tmo/prebuilt/zImage?
Any ideas anyone? I will add the TARGET_KERNEL_CONFIG := ancora_tmo_defconfig in boardconfig.mk and see if that works. Also hopefully someone could shed some light on the previous error that i didn't actually fix. Thanks
Edit: still no boot when i build the kernel
if i can ever get some time dude ill try and help but look for a cm10.1 release from me in a couple of days. i ahve it built and working just havent had time to do anything with it. been working on getting the team sites looking good
target SharedLib: camera.msm7x30 (out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so)
/home/theapant/aokp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/cameraHAL.o: in function camera_set_preview_window(camera_device*, preview_stream_ops*):device/samsung/ancora_tmo/camerahal/cameraHAL.cpp:494: error: undefined reference to 'android:verlay:verlay(void (*)(void*, int), void (*)(void*, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(void*, void*), void*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so] Error 1
make: *** Waiting for unfinished jobs....
[email protected]:~/aokp$
I'm getting the same error that I got a long time before. I'm using camcory's device github. If i remove the camerahal.cpp from the android.mk it finishes the build fine and I think I have everything else working now. I built it with camcory's prebuilt 3.0.66 kernel, so is that the issue? Any suggestions are welcome. Thanks!
Using that prebuilt explains your kernel version. Comment out the prebuilt references, make a build, replace new zImage and use that as your prebuilt with new build.
jfbs said:
Using that prebuilt explains your kernel version. Comment out the prebuilt references, make a build, replace new zImage and use that as your prebuilt with new build.
Click to expand...
Click to collapse
Thanks I all ready knew why it is kernel version 3.0.66. I could swap out the zimage but i still cant get camerahal.CPP so i need to fix that first. Camcory built slimbean with camera and 3.0 kernel and i would like to do the same with aokp, however i have to take camerahal out of the make file so that the build finishes because of that error above. I have built plenty of kernels and i can just add kernel source and the target_kernel_config := ancora_tmo_defconfig to boardconfig and it would build the kernel that way too however camcorys kernels are much more stable than mine, so.... Any ideas on how i can fix the camerhal thing?
Sent from my Nexus 7 using xda app-developers app
That cherry-pick is for ICS. I believe Jellybean overlays are in frameworks/native and others in frameworks/av. Check arco's jellybean branches.
Edit: review.cyanogenmod.org/#/c/19964 and the fetch link is mid-page.
jfbs said:
That cherry-pick is for ICS. I believe Jellybean overlays are in frameworks/native and others in frameworks/av. Check arco's jellybean branches.
Edit: review.cyanogenmod.org/#/c/19964 and the fetch link is mid-page.
Click to expand...
Click to collapse
Thanks again, I made a really stupid mistake and only had Overlay.h when I also needed Overlay.cpp, your post made me go back and check my sources and I found the problem. Before I was racing around trying to modify camerahal.cpp with no c++ knowledge. I also fixed an issue I was having with turning wifi on in settings and now I think I have a fully working build of AOKP with 3.0 kernel. Once again thanks!!!
Hey guys
First: THIS THREAD IS DEV-ONLY! All not development related posts will be deleted!
Now, working on AOSP last night, i found a derp in the device tree. This derp seems to be present in all device trees i have found for our device. So i thought it would be good to have one thread where such things can have an appropriate place, without making new threads over and over again. Also it is big advantage to have everything bundeled in one thread IMO.
I have registered a channel on freenode called "#p880-dev", so we can discuss everything in there
Feel free to join in
As already mentioned, I found a (most likely) typo in the device tree. Our battery's capacity is 2150mAh, but all device trees got 2050mAh.
See HERE
Now, to make it public, let's call some ppl in here
@Adam77Root, @Demetris, @arararagi, @kholk, @Rudjgaard, @dcos
(no particular order, just ROM devs i found in the section, building from source)
Good catch. Does anyone know what effect this has though?
The kernel directly reports the battery % through /sys/class/power_supply/battery/capacity
http://forum.xda-developers.com/showpost.php?p=46361993&postcount=344
Will push to Omni device tree.
BT tethering is also derped. The needed value in overlay is "bt-pan" instead of "bnep\\d".
Sent from my OmniROM-powered LG Optimus 4X HD
laufersteppenwolf said:
Hey guys
First: THIS THREAD IS DEV-ONLY! All not development related posts will be deleted!
Now, working on AOSP last night, i found a derp in the device tree. This derp seems to be present in all device trees i have found for our device. So i thought it would be good to have one thread where such things can have an appropriate place, without making new threads over and over again. Also it is big advantage to have everything bundeled in one thread IMO.
As already mentioned, I found a (most likely) typo in the device tree. Our battery's capacity is 2150mAh, but all device trees got 2050mAh.
See HERE
Click to expand...
Click to collapse
Thanks for the heads up and let me just say, great idea opening this thread. :good:
arararagi said:
Good catch. Does anyone know what effect this has though?
The kernel directly reports the battery % through /sys/class/power_supply/battery/capacity
Click to expand...
Click to collapse
Well I believe this mostly reflects on battery usage statistics, but maybe I'm wrong.
Reference: https://source.android.com/devices/tech/power.html#
In our kernel source there is a emc bw efficiency name error in
arch/arm/mach-tegra/tegra3_clocks.c line 3141 + 3142
bw = emc_bw_efficiency ?
(bw / emc_bw_efficiency) : bus->max_rate;
In arch/arm/mach-tegra/tegra3_emc.c is looking for u8 tegra_emc_bw_efficiency = 35;
and also same thing in arch/arm/mach-tegra/tegra3_emc.h extern u8 tegra_emc_bw_efficiency;
Demetris said:
In our kernel source there is a emc bw efficiency name error in
arch/arm/mach-tegra/tegra3_clocks.c line 3141 + 3142
bw = emc_bw_efficiency ?
(bw / emc_bw_efficiency) : bus->max_rate;
In arch/arm/mach-tegra/tegra3_emc.c is looking for u8 tegra_emc_bw_efficiency = 35;
and also same thing in arch/arm/mach-tegra/tegra3_emc.h extern u8 tegra_emc_bw_efficiency;
Click to expand...
Click to collapse
I think that's intentional. Maybe an LGE change. In the beginning of the tegra3_clk_shared_bus_update function, the emc_bw_efficiency is defined. It's initialized to tegra_emc_bw_efficiency_boost and is set to tegra_emc_bw_efficiency if the clock name is "3d.emc" and shared bus mode is enabled and set to ceiling mode.
Sometimes my laziness is beyond compare
Never bothered to look good into tegra3_clocks.c
Thanks adam huge derp from me
Could you care have a look into my mount options for a cherry-pick
Here they are:
HTML:
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,noatime,barrier=0,noauto_da_alloc,data=writeback wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 discard,noatime,nosuid,nodev,nomblk_io_submit,noauto_da_alloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 discard,noatime,nosuid,nodev,nomblk_io_submit,noauto_da_alloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/CAL /cal ext4 nosuid,nodev,barrier=1 wait
/dev/block/platform/sdhci-tegra.3/by-name/DRM /persist-lg ext4 nosuid,nodev,barrier=1 wait
/dev/block/platform/sdhci-tegra.3/by-name/MLT /mpt ext4 nosuid,nodev,barrier=1,data=ordered wait
/devices/platform/sdhci-tegra.2/mmc_host/mmc2 /storage/sdcard1 auto defaults voldmanaged=sdcard:auto
/dev/block/platform/sdhci-tegra.2/by-num/p1 /external_sd auto defaults recoveryonly
I find them to perform better than stock ones
Looks good to me.
Something we really lack are full SELinux policies. I'm calling out to you since I have little to no knowledge in this field. We should really fix this before the KitKat release. The audit2allow tool might help analysing the needed rules. What do you say?
Adam77Root said:
Something we really lack are full SELinux policies. I'm calling out to you since I have little to no knowledge in this field. We should really fix this before the KitKat release. The audit2allow tool might help analysing the needed rules. What do you say?
Click to expand...
Click to collapse
Well, I have the same problem as you do.... I have no idea about SELinux
Never been actually working on/with it. Let's hope @Demetris can help us out
Guys, I could use some help on the camera for AOSP... It's driving me crazy Whatever I try, it keeps FC'ing
Here's the logcat
It'd be great for someone having an Idea to "start" from
Thanks in advance
laufersteppenwolf said:
Guys, I could use some help on the camera for AOSP... It's driving me crazy Whatever I try, it keeps FC'ing
Here's the logcat
It'd be great for someone having an Idea to "start" from
Thanks in advance
Click to expand...
Click to collapse
I am not sure if this is it https://github.com/SlimRoms/frameworks_av/commit/3c2c4f8f8a4abdc61aa2321640b0b03a3a2661b7 but whatever it is it should be on frameworks_av .
I would look on the commits and see if there is anything else relevant there.
ezet said:
I am not sure if this is it https://github.com/SlimRoms/frameworks_av/commit/3c2c4f8f8a4abdc61aa2321640b0b03a3a2661b7 but whatever it is it should be on frameworks_av .
I would look on the commits and see if there is anything else relevant there.
Click to expand...
Click to collapse
no, already checked, it's neither frameworks/av, nor hardware/libhardware, nor hardware/libhardware_legacy...
laufersteppenwolf said:
no, already checked, it's neither frameworks/av, nor hardware/libhardware, nor hardware/libhardware_legacy...
Click to expand...
Click to collapse
frameworks/native? and frameworks/av? maybe, take them from cm?
penguin449 said:
frameworks/native? and frameworks/av? maybe, take them from cm?
Click to expand...
Click to collapse
I cannot just take another repo and replace it. But i sure did cherry-pick from it
laufersteppenwolf said:
Guys, I could use some help on the camera for AOSP... It's driving me crazy Whatever I try, it keeps FC'ing
Here's the logcat
It'd be great for someone having an Idea to "start" from
Thanks in advance
Click to expand...
Click to collapse
Little update to the problem: Whatever I do, I can't get around the SIGSEGV... Any ideas?
And the according logcat of course
Hmm ive spent some time investigating, but with a lack of understanding of the android camera implementation, its hard to narrow it down. I did find a post that at least gives us some leads
Have been doing some work on trying to get the camera to work... sadly no good news for now
I have fixed the HAL methods ( new camera HAL had some minor changes ), but still getting the same errors on load:
07-20 00:09:24.500: E/NvOmxCamera(162): createCameraObjects: graph creation failed! [0x80001005]
07-20 00:09:24.500: E/NvOmxCamera(162): createCameraObjects: Fail! [0x80001005]
07-20 00:09:24.500: E/NvOmxCamera(162): NvOmxCamera::createObjects :::: FAIL ::::::::::::::::: [0x80001005]
And on usage of the camera a segfault on PowerOnSensor.
The reason that it segfaults is basically because they forgot to add a check in cameraservice if the HAL module actually returned any working cameras. I have added logging to the cameraservice and manually called get_number_of_cameras on the HAL module.
07-20 00:09:24.500: D/CameraService(162): reported number of cameras: 0
So basically after graph creation fails the entire camera initializations stalls, but libcameraservice is also happy to work with 0 cameras aslong as there is a module ( oops ). Then calling a HAL method on some uninitialized pointer will not do much besides give a nice segfault of course.
Just to be sure the HAL module was working correctly i did call get_camera_info which should return the camera info defined in nvcamera.conf.
07-20 00:09:24.510: D/CameraService(162): camera info for camera 0 = 0 90
The entire graph creation process depends on omx and the graph error (0x80001005) is actually OMX_ErrorBadParameter.
So either our implementation of OpenMax is broken or there are other compatibility issues...
Click to expand...
Click to collapse
http://www.icsforums.com/comment/1315991#comment-1315991
Could there be a problem with the Openmax DL in aosp?
JoinTheRealms said:
Hmm ive spent some time investigating, but with a lack of understanding of the android camera implementation, its hard to narrow it down. I did find a post that at least gives us some leads
http://www.icsforums.com/comment/1315991#comment-1315991
Could there be a problem with the Openmax DL in aosp?
Click to expand...
Click to collapse
I thinks so, too, but I just cannot figure out what exactly the problem is...
Been cherry-picking most frameworks/av commits, but still no success...
Let's start a discussion about the new Android, a.k.a. KitKat. I compiled Omni 4.4 today, there were only a few build errors, those are trivial to fix. First it didn't boot, because now SELinux is set to enforcing mode by default. This can be fixed by modifying 'selinux_is_enforcing()' function in init.c to return always false or by setting 'ro.boot.selinux' property to 'permissive'. I had some errors with SurfaceFlinger (0x3 device version, need to revert only new blobs support.) and with sensors.tegra.so, it's complaining about a missing function.
Adam77Root said:
Let's start a discussion about the new Android, a.k.a. KitKat. I compiled Omni 4.4 today, there were only a few build errors, those are trivial to fix. First it didn't boot, because now SELinux is set to enforcing mode by default. This can be fixed by modifying 'selinux_is_enforcing()' function in init.c to return always false or by setting 'ro.boot.selinux' property to 'permissive'. I had some errors with SurfaceFlinger (0x3 device version, need to revert only new blobs support.) and with sensors.tegra.so, it's complaining about a missing function.
Click to expand...
Click to collapse
You may laugh, but I'm still trying to compile AOSP 4.4 I somehow had a broken source, so even pure AOSP for mako/hammerhead did not compile
But it is now, so would you mind sharing the commits you reverted in order to get SurfaceFlinger working? The same as in 4.3 I suppose, right?
And about SELinux, let's hope for CM to bring a proper SELinux for our device with CM11
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...)