Database Develop

[Discussion]Building CM10 for p990

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.

Camera Problem With CM10.1 AND LiquidSmooth S3 i9305 (with the latest versions)

I have downloaded and flashed the latest versions of both CM10.1 AND LiquidSmooth. The rom is smoothand fast and as far as I have used it, only encountered little bugs here and there that I don't really care about. However the Camera still doesn't function for me. I know this was fixed in like the second release of cm10.1 but for me the camera still isn't working with the latest release. it gives me the error message 'cant connect to camera' I live in Singapore and thus my phone is from singtel. maybe its different for phones in Sg? and I would be more than happy to give a logcat if someone told me how to thank you so muchhh ) Finally I can get rid of touchwiz

Sv: Camera Problem With CM10.1 AND LiquidSmooth S3 i9305 (with the latest versions)
ebenezer57 said:
I have downloaded and flashed the latest versions of both CM10.1 AND LiquidSmooth. The rom is smoothand fast and as far as I have used it, only encountered little bugs here and there that I don't really care about. However the Camera still doesn't function for me. I know this was fixed in like the second release of cm10.1 but for me the camera still isn't working with the latest release. it gives me the error message 'cant connect to camera' I live in Singapore and thus my phone is from singtel. maybe its different for phones in Sg? and I would be more than happy to give a logcat if someone told me how to thank you so muchhh ) Finally I can get rid of touchwiz
Click to expand...
Click to collapse
Can you even start the camera? What do you do when you get the error?
Sent from my GT-I9305 using xda app-developers app

ebenezer57 said:
I have downloaded and flashed the latest versions of both CM10.1 AND LiquidSmooth. The rom is smoothand fast and as far as I have used it, only encountered little bugs here and there that I don't really care about. However the Camera still doesn't function for me. I know this was fixed in like the second release of cm10.1 but for me the camera still isn't working with the latest release. it gives me the error message 'cant connect to camera' I live in Singapore and thus my phone is from singtel. maybe its different for phones in Sg? and I would be more than happy to give a logcat if someone told me how to thank you so muchhh ) Finally I can get rid of touchwiz
Click to expand...
Click to collapse
Reboot your phone (to remove irrelevant data), go onto Mobile Terminal (if you don't have it download it) then login as root 'su', then cd to a new directory (recommend downloads or something) so 'cd /storage/emulated/legacy/Download' and then run 'logcat > cannot_connect_to_camera_logcat.txt', hope screen it (let it run in the background) and try open up the camera app. It will give you the error as usual but then you want to exit out of the camera app, go back into mobile terminal and close the session (the big 'X' in the top right corner).
Then get the file off your device, upload it to http://pastebin.com/ and put a link in the Liquid Smooth thread and the Cyanogenmod thread (although Cyanogenmod doesn't have a maintainer so it is less likely to be fixed there but the fix should work across roms).
Also use the -v long output and tags to make reading logcats much easier and for more relevant information (*W tag for warnings only etc.) so it would be 'logcat *W -v long > ...'

sebbe312 said:
Can you even start the camera? What do you do when you get the error?
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Yeap i can, it goes to the app and gives me the error. i just press home and close it.
I have posted on the LiquidSmooth thread in the development section and attatched the log file as well

Magik_Breezy said:
Reboot your phone (to remove irrelevant data), go onto Mobile Terminal (if you don't have it download it) then login as root 'su', then cd to a new directory (recommend downloads or something) so 'cd /storage/emulated/legacy/Download' and then run 'logcat > cannot_connect_to_camera_logcat.txt', hope screen it (let it run in the background) and try open up the camera app. It will give you the error as usual but then you want to exit out of the camera app, go back into mobile terminal and close the session (the big 'X' in the top right corner).
Then get the file off your device, upload it to http://pastebin.com/ and put a link in the Liquid Smooth thread and the Cyanogenmod thread (although Cyanogenmod doesn't have a maintainer so it is less likely to be fixed there but the fix should work across roms).
Also use the -v long output and tags to make reading logcats much easier and for more relevant information (*W tag for warnings only etc.) so it would be 'logcat *W -v long > ...'
Click to expand...
Click to collapse
Thanks for the instructions! I found this app to do the recording for me though and i have uploaded the logcat with the tag on the liquid smooth thread

-- I've accidentally posted this in the i9300 QA forum so I'm moving it here since it's the same issue --
Hi, I'm trying to setup an AOSP rom for my brother on his i9305 and everything is working great for the latest CM build but the camera app cannot start saying it cannot connect to camera:
02-16 02:37:04.725: E/SecCameraHardware(1951): camFW = GHFJ02
02-16 02:37:04.725: E/SecCameraHardware(1951): FimcV4l2 init: error -1, VIDIOC_S_INPUT
02-16 02:37:04.725: E/SecCameraHardware(1951): initCamera X: error, /dev/video0
02-16 02:37:04.725: V/SecCameraHardware(1951): FimcV4l2 deinit EX
02-16 02:37:04.725: E/SecCameraHardware(1951): createInstance: error, camera cannot be initialiezed
02-16 02:37:04.725: E/SecCameraHardware(1951): Instance is not created
02-16 02:37:04.725: E/CameraWrapper(1951): vendor camera open fail
02-16 02:37:04.725: E/CameraClient(1951): Could not open camera 0: -38
02-16 02:37:04.725: E/CameraClient(1951): initialize: Camera 0: unable to initialize device: Function not implemented (-38)
02-16 02:37:04.725: I/CameraClient(1951): Destroying camera 0
02-16 02:37:04.730: E/CameraHolder(3885): fail to connect Camera
02-16 02:37:04.730: E/CameraHolder(3885): java.lang.RuntimeException: Fail to connect to camera service
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.native_setup(Native Method)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.<init>(Camera.java:340)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.open(Camera.java:302)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraManager.cameraOpen(Camera Manager.java:283)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraHolder.open(CameraHolder. java:210)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.Util.openCamera(Util.java:366)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.PhotoModule$CameraStartUpThread .run(PhotoModule.java:323)
Now, the camera firmware version GHFJ02 is nothing like any I've been able to come across (none start with GH****) and have seen that changing the firmware can help with this problem. Does anyone know if it would be ok for me to install (downgrade as I could figure from the letters - revisions) a differently labeled firmware like for instance GDFE01 which (mostly) works ok with CM? Also, is it possible to backup the current firmware so I can restore it in case of problems? I see a dump firmware option but dont have a clue where this dump ends up being stored.
Also, if someone can give any more info on the above error message and what exactly does it mean? Maybe I can help in fixing the camera interface if it's possible.
Since it's such a crucial part of the phone, either I get it working somehow or he's better of with a rooted stock rom.
Thanks

mm43107 said:
-- I've accidentally posted this in the i9300 QA forum so I'm moving it here since it's the same issue --
Hi, I'm trying to setup an AOSP rom for my brother on his i9305 and everything is working great for the latest CM build but the camera app cannot start saying it cannot connect to camera:
02-16 02:37:04.725: E/SecCameraHardware(1951): camFW = GHFJ02
02-16 02:37:04.725: E/SecCameraHardware(1951): FimcV4l2 init: error -1, VIDIOC_S_INPUT
02-16 02:37:04.725: E/SecCameraHardware(1951): initCamera X: error, /dev/video0
02-16 02:37:04.725: V/SecCameraHardware(1951): FimcV4l2 deinit EX
02-16 02:37:04.725: E/SecCameraHardware(1951): createInstance: error, camera cannot be initialiezed
02-16 02:37:04.725: E/SecCameraHardware(1951): Instance is not created
02-16 02:37:04.725: E/CameraWrapper(1951): vendor camera open fail
02-16 02:37:04.725: E/CameraClient(1951): Could not open camera 0: -38
02-16 02:37:04.725: E/CameraClient(1951): initialize: Camera 0: unable to initialize device: Function not implemented (-38)
02-16 02:37:04.725: I/CameraClient(1951): Destroying camera 0
02-16 02:37:04.730: E/CameraHolder(3885): fail to connect Camera
02-16 02:37:04.730: E/CameraHolder(3885): java.lang.RuntimeException: Fail to connect to camera service
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.native_setup(Native Method)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.<init>(Camera.java:340)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.open(Camera.java:302)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraManager.cameraOpen(Camera Manager.java:283)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraHolder.open(CameraHolder. java:210)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.Util.openCamera(Util.java:366)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.PhotoModule$CameraStartUpThread .run(PhotoModule.java:323)
Now, the camera firmware version GHFJ02 is nothing like any I've been able to come across (none start with GH****) and have seen that changing the firmware can help with this problem. Does anyone know if it would be ok for me to install (downgrade as I could figure from the letters - revisions) a differently labeled firmware like for instance GDFE01 which (mostly) works ok with CM? Also, is it possible to backup the current firmware so I can restore it in case of problems? I see a dump firmware option but dont have a clue where this dump ends up being stored.
Also, if someone can give any more info on the above error message and what exactly does it mean? Maybe I can help in fixing the camera interface if it's possible.
Since it's such a crucial part of the phone, either I get it working somehow or he's better of with a rooted stock rom.
Thanks
Click to expand...
Click to collapse
Are you from sg? cuz I think ppl in sg have this problem. Anyway u should post this on the development thread! ull get a lot more help there. but I think u cant post there yet because u only have 3 posts so just post something 7 more times and come to the development thread in the liquidsmooth thread! ill copy ur message there and ill let u know the response? come on there as soon as u can!

ebenezer57 said:
Are you from sg? cuz I think ppl in sg have this problem. Anyway u should post this on the development thread! ull get a lot more help there. but I think u cant post there yet because u only have 3 posts so just post something 7 more times and come to the development thread in the liquidsmooth thread! ill copy ur message there and ill let u know the response? come on there as soon as u can!
Click to expand...
Click to collapse
Don't bother putting it on the thread. Email logcats directly to [email protected] & [email protected].
Sent from my GT-I9305 using xda premium

Well done just like a turkey with correct gran mah...lolxxx

Magik_Breezy said:
Don't bother putting it on the thread. Email logcats directly to [email protected] & [email protected].
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yeap I sent them a email right after I saw amp's post.

ebenezer57 said:
Are you from sg? cuz I think ppl in sg have this problem. Anyway u should post this on the development thread! ull get a lot more help there. but I think u cant post there yet because u only have 3 posts so just post something 7 more times and come to the development thread in the liquidsmooth thread! ill copy ur message there and ill let u know the response? come on there as soon as u can!
Click to expand...
Click to collapse
I'm from croatia (hr), maybe our operator is shipping phones from sg
I know I'd be better off posting in the dev forum, but have to pass the 10 post min. like you figured...
PS
Whose emails are these ([email protected] & [email protected])? Is there any more info I can send them to help? dmesg log?

ebenezer57 said:
I have downloaded and flashed the latest versions of both CM10.1 AND LiquidSmooth. The rom is smoothand fast and as far as I have used it, only encountered little bugs here and there that I don't really care about. However the Camera still doesn't function for me. I know this was fixed in like the second release of cm10.1 but for me the camera still isn't working with the latest release. it gives me the error message 'cant connect to camera' I live in Singapore and thus my phone is from singtel. maybe its different for phones in Sg? and I would be more than happy to give a logcat if someone told me how to thank you so muchhh ) Finally I can get rid of touchwiz
Click to expand...
Click to collapse
I'm also from SG and using 9305, though i didn't have this camera issue, I noticed that the camera seems stretched in video mode. I also noticed that 4G(singtel) is not as great as the stock rom, I used to have full 4G signal here at home but now I can only get 3G, my visitors who have i9305 also gets good 4G signal here. But I can get good 4G signal from other places. Besides these issues, everything looks great. It's a very good job done by Amplified(Liquid Team) and codeworkx for the CM10.1.

mm43107 said:
I'm from croatia (hr), maybe our operator is shipping phones from sg
I know I'd be better off posting in the dev forum, but have to pass the 10 post min. like you figured...
PS
Whose emails are these ([email protected] & [email protected])? Is there any more info I can send them to help? dmesg log?
Click to expand...
Click to collapse
I believe the Singapore version also uses the same international version i9305

deepsweech said:
I'm also from SG and using 9305, though i didn't have this camera issue, I noticed that the camera seems stretched in video mode. I also noticed that 4G(singtel) is not as great as the stock rom, I used to have full 4G signal here at home but now I can only get 3G, my visitors who have i9305 also gets good 4G signal here. But I can get good 4G signal from other places. Besides these issues, everything looks great. It's a very good job done by Amplified(Liquid Team) and codeworkx for the CM10.1.
Click to expand...
Click to collapse
Your signal has absolutely nothing to do with the ROM unless your ROM flashed your modem too and CM and LS both don't so there should be absolutely no difference unless you have made a standalone decision to flash a different modem. Constructive criticism, sorry if I came across as rude.
Sent from my GT-I9305 using xda premium

mm43107 said:
I'm from croatia (hr), maybe our operator is shipping phones from sg
I know I'd be better off posting in the dev forum, but have to pass the 10 post min. like you figured...
PS
Whose emails are these ([email protected] & [email protected])? Is there any more info I can send them to help? dmesg log?
Click to expand...
Click to collapse
They are part of the team liquid! (developers of the liquidsmooth rom) yeap u can send them any more info that u think would be helpful!

deepsweech said:
I'm also from SG and using 9305, though i didn't have this camera issue, I noticed that the camera seems stretched in video mode. I also noticed that 4G(singtel) is not as great as the stock rom, I used to have full 4G signal here at home but now I can only get 3G, my visitors who have i9305 also gets good 4G signal here. But I can get good 4G signal from other places. Besides these issues, everything looks great. It's a very good job done by Amplified(Liquid Team) and codeworkx for the CM10.1.
Click to expand...
Click to collapse
Ahh... so its just my phone then. damn that sucks. ill try doing a full wipe and reflashing! hopefully that fixes the problem!
Edit: I did a full wipe including system but no luck ):

Magik_Breezy said:
Your signal has absolutely nothing to do with the ROM unless your ROM flashed your modem too and CM and LS both don't so there should be absolutely no difference unless you have made a standalone decision to flash a different modem. Constructive criticism, sorry if I came across as rude.
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
all good bro, im also a noob in this AOSP thing. Ok ill just search for the best modem flash.

You're not the only one.
I'm having the same issue.
if you've found some solution, can you tell me?

Hi, I just got my GT-19305 and rooted as soon as I got it. I get the same error when opening the camera app "can't connect to camera". I have tried Cyanogenmod stable, and some nightlies, CodenameLungo and RipperROM (the camera works on this one).
I have tried searching for an answer for two days now but I cant find anything helpfull.
I got my phone in Norway btw.. (which is where I live)..

Any news ?
Little up ?

[DEV-ONLY] Development related Discussions

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

port HTC one max camera

any developer can port HTC one max camera ?

darkidz555 said:
any developer can port HTC one max camera ?
Click to expand...
Click to collapse
Why? They are esentially the same AFAIK

Because HTC one max can capture picture with with ourself in it like Samsung s4 can use back camera capture picture while using front camera to include us inside
Sent from my HTC One using xda app-developers app

darkidz555 said:
Because HTC one max can capture picture with with ourself in it like Samsung s4 can use back camera capture picture while using front camera to include us inside
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Have you tried simply installing it yet? I'm thinking Sense 5.5 framework is Sense 5.5 framework... If you haven't, here is a flashable of the One Max camera. It may need some libs to go along with it...but try it and let me know. If you get any crashes, get me a log during the crash and if it's missing libs I can pull them too..

homeslice976 said:
Have you tried simply installing it yet? I'm thinking Sense 5.5 framework is Sense 5.5 framework... If you haven't, here is a flashable of the One Max camera. I've renamed the apk to Camera2 so ut won't overwrite the current camera. It may need some libs to go along with it...but try it and let me know. If you get any crashes, get me a log during the crash and if it's missing libs I can pull them too..
Click to expand...
Click to collapse
I`ve just checkt it... I replaced it with the original .apk because the installation is not working this way... so there is no extra camera app in app drawer. Anyway... as I said, I replaced the original file and the camera starts. But there is no difference... means I cant find an option for the portrait/main camera effect. Should there be an extra icon or a option in camera settings?

BanBoo said:
I`ve just checkt it... I replaced it with the original .apk because the installation is not working this way... so there is no extra camera app in app drawer. Anyway... as I said, I replaced the original file and the camera starts. But there is no difference... means I cant find an option for the portrait/main camera effect. Should there be an extra icon or a option in camera settings?
Click to expand...
Click to collapse
i have no idea. I'm not running sense at the moment and I don't have a max. That's the camera apk pulled from a One Max stock/rooted ROM. I would have assumed it would be a camera mode.. if i get a minute to flash a sense rom this afternoon i'll look at it.
Edit: Dual mode didn't show up for me either. After tearing apart out sense 5.5 camera and the one max 5.5 camera, both contain the code for dual camera mode, so it must be getting activated by a flag somewhere else? I'll keep looking.
Edit 2: @BanBoo I managed to get it enabled (screenshot) but the picture doesn't actually take/save, and the second camera preview is black. Still playing
Edit3: Any suggestions from the pros?
Code:
W/CameraDeviceManager( 6014): openCamera(Front)
W/CameraController( 6014): openCamera(Front)
E/QualcommCamera( 255): ERR!! camera is opened and cameraId didn't match! now 0 new 1
E/CameraClient( 255): Could not open camera 1: -1
E/CameraClient( 255): initialize: Camera 1: unable to initialize device: Operation not permitted (-1)
W/CameraBase( 6014): An error occurred while connecting to camera: 1
W/HTCCamera( 6014): onPreviewStarted() - Invalid handle
E/CameraDeviceManager( 6014): openCamera() - Fail to open camera
E/CameraDeviceManager( 6014): java.lang.RuntimeException: Fail to connect to camera service
E/CameraDeviceManager( 6014): at android.hardware.Camera.native_setup(Native Method)
E/CameraDeviceManager( 6014): at android.hardware.Camera.<init>(Camera.java)
E/CameraDeviceManager( 6014): at android.hardware.Camera.open(Camera.java)
E/CameraDeviceManager( 6014): at com.android.camera.CameraController.openCamera(CameraController.java:400)
E/CameraDeviceManager( 6014): at com.android.camera.CameraController.<init>(CameraController.java:229)
E/CameraDeviceManager( 6014): at com.android.camera.component.CameraDeviceManager.openCamera(CameraDeviceManager.java:323)
E/CameraDeviceManager( 6014): at com.android.camera.dualcamera.DualCameraController.openSecondaryCamera(DualCameraController.java:1339)
E/CameraDeviceManager( 6014): at com.android.camera.dualcamera.DualCameraController.startSecondaryPreview(DualCameraController.java:1704)
E/CameraDeviceManager( 6014): at com.android.camera.dualcamera.DualCameraController.onPreviewAdapterCreated(DualCameraController.java:1082)
E/CameraDeviceManager( 6014): at com.android.camera.dualcamera.DualCameraController.handleMessage(DualCameraController.java:724)
E/CameraDeviceManager( 6014): at com.android.camera.component.Component$MessageHandler.handleMessage(Component.java:70)
E/CameraDeviceManager( 6014): at android.os.Handler.dispatchMessage(Handler.java)
E/CameraDeviceManager( 6014): at android.os.Looper.loop(Looper.java)
E/CameraDeviceManager( 6014): at com.android.camera.CameraThread.run(CameraThread.java:2811)
E/DualCameraController( 6014): openSecondaryCamera() - Fail to open camera : Unknown

Maybe the Camera.apk checks your build.prob to see if its a One or a One Max and enable the feature? What if you change your model ID to match the Model ID of the One Max

solracarevir said:
Maybe the Camera.apk checks your build.prob to see if its a One or a One Max and enable the feature? What if you change your model ID to match the Model ID of the One Max
Click to expand...
Click to collapse
Good suggestion but no-go. I'd imagine a check like that would just be to enable the feature,which I managed to do a little differently.. according to the log it looks like it's not identifying the cameras properly once in dual capture mode.. but I don't yet know where/when they're identified
Sent from my HTC6600LVW using Tapatalk 4

How did you get the other options to show up in the camera, or can you link a copy of what you did

[WIP]Make KitKat run on new 4.3 kernel source

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...)