Post Reply Subscribe to Thread Email Thread

CM12 based on 5.0.2 (Lollipop) OTA

31st March 2015, 05:26 AM |#3551  
Member
Thanks Meter: 26
 
88 posts
Join Date:Joined: Oct 2013
More
I'm on the last non-39a CM12 build and I have to open disable service to check/uncheck systemupdateservice after every reboot.
31st March 2015, 11:43 AM |#3552  
steveo17's Avatar
Senior Member
Flag South Amboy
Thanks Meter: 155
 
732 posts
Join Date:Joined: Sep 2010
Donate to Me
Quote:
Originally Posted by Nafon

I'm on the last non-39a CM12 build and I have to open disable service to check/uncheck systemupdateservice after every reboot.

Update to the latest play services

Sent from my LG-VS980 using Tapatalk
31st March 2015, 02:02 PM |#3553  
xI mEzMeRiZe Ix's Avatar
Senior Member
Flag Maryland
Thanks Meter: 207
 
967 posts
Join Date:Joined: Jun 2011
More
Quote:
Originally Posted by steveo17

Update to the latest play services

Sent from my LG-VS980 using Tapatalk

How exactly? I'm on Google Play services 7.0.99 (1809214-438), which according to APK Mirror, is the latest version, and I still have the wakelock issue.
31st March 2015, 11:44 PM |#3554  
Senior Member
Flag Chesapeake, VA
Thanks Meter: 263
 
562 posts
Join Date:Joined: Aug 2011
More
So, I'm still having issues building successfully... Really not sure what I screwed up where. I'm thinking that I might need to dump my CCACHE, and see how it goes.

Anyway, since I can't seem to find a 'pure' vendor tree from say AOSP or the like. I decided to compare the /vendor/ directories between the stock rom and the CM builds (JPC's not mine). And there are a number of vendor files misising:


Code:
Only in Stock_system/vendor/firmware: widevine.b00
Only in Stock_system/vendor/firmware: widevine.b01
Only in Stock_system/vendor/firmware: widevine.b02
Only in Stock_system/vendor/firmware: widevine.b03
Only in Stock_system/vendor/firmware: widevine.mdt
Only in Stock_system/vendor/lib/hw: activity_recognition.msm8974.so
Only in Stock_system/vendor/lib: libalarmservice_jni.so
Only in Stock_system/vendor/lib: libbtnv.so
Only in Stock_system/vendor/lib: libchromaflash.so
Only in Stock_system/vendor/lib: libcneconn.so
Only in Stock_system/vendor/lib: libcne.so
Only in Stock_system/vendor/lib: libdisp-aba.so
Only in Stock_system/vendor/lib: libdpencalib.so
Only in Stock_system/vendor/lib: lib-dplmedia.so
Only in Stock_system/vendor/lib: libdpmframework.so
Only in Stock_system/vendor/lib: libdpmnsrm.so
Only in Stock_system/vendor/lib: libdsucsd.so
Only in Stock_system/vendor/lib: libepdsp_SDserver.so
Only in Stock_system/vendor/lib: libHevcSwDecoder.so
Only in Stock_system/vendor/lib: lib-imscamera.so
Only in Stock_system/vendor/lib: lib-imsdpl.so
Only in Stock_system/vendor/lib: lib-imsqimf.so
Only in Stock_system/vendor/lib: lib-imsrcscmclient.so
Only in Stock_system/vendor/lib: lib-ims-rcscmjni.so
Only in Stock_system/vendor/lib: lib-imsrcscmservice.so
Only in Stock_system/vendor/lib: lib-imsrcscm.so
Only in Stock_system/vendor/lib: lib-imsrcs.so
Only in Stock_system/vendor/lib: lib-imsSDP.so
Only in Stock_system/vendor/lib: lib-imss.so
Only in Stock_system/vendor/lib: lib-imsvt.so
Only in Stock_system/vendor/lib: lib-imsxml.so
Only in Stock_system/vendor/lib: liblocationservice.so
Only in Stock_system/vendor/lib: libloc_ext.so
Only in Stock_system/vendor/lib: liblowi_client.so
Only in Stock_system/vendor/lib: libmasc.so
Only in Stock_system/vendor/lib: libmmcamera_chromaflash_lib.so
Only in Stock_system/vendor/lib: libmmcamera_ubifocus_lib.so
Only in Stock_system/vendor/lib: libmm-hdcpmgr.so
Only in Stock_system/vendor/lib: liboemcrypto.so
Only in Stock_system/vendor/lib: libppl.so
Only in Stock_system/vendor/lib: libqmi_client_helper.so
Only in Stock_system/vendor/lib: lib-rcsimssjni.so
Only in Stock_system/vendor/lib: lib-rcsjni.so
Only in Stock_system/vendor/lib: librmp.so
Only in Stock_system/vendor/lib: lib-rtpcommon.so
Only in Stock_system/vendor/lib: lib-rtpcore.so
Only in Stock_system/vendor/lib: lib-rtpdaemoninterface.so
Only in Stock_system/vendor/lib: lib-rtpsl.so
Only in Stock_system/vendor/lib: libscale.so
Only in Stock_system/vendor/lib: libscve.so
Only in Stock_system/vendor/lib: libscve_stub.so
Only in Stock_system/vendor/lib: lib-sec-disp.so
Only in Stock_system/vendor/lib: libSecureUILib.so
Only in Stock_system/vendor/lib: libsecureui.so
Only in Stock_system/vendor/lib: libsecureuisvc_jni.so
Only in Stock_system/vendor/lib: libsecureui_svcsock.so
Only in Stock_system/vendor/lib: libsensor_test.so
Only in Stock_system/vendor/lib: libsensor_thresh.so
Only in Stock_system/vendor/lib: libStDrvInt.so
Only in Stock_system/vendor/lib: libSubSystemShutdown.so
Only in Stock_system/vendor/lib: libTimeService.so
Only in Stock_system/vendor/lib: libubifocus.so
Only in Stock_system/vendor/lib: libusutils.so
Only in Stock_system/vendor/lib: libvcel.so
Only in Stock_system/vendor/lib: libvendorconn.so
Only in Stock_system/vendor/lib: libVenusMbiConv.so
Only in Stock_system/vendor/lib: libwifiscanner.so
Only in Stock_system/vendor/lib: libwqe.so
Only in Stock_system/vendor/lib: libxtadapter.so
Only in Stock_system/vendor/lib: libxt_native.so
Only in Stock_system/vendor/lib: libxtwifi_ulp_adaptor.so
Only in Stock_system/vendor/lib: libxtwifi_zpp_adaptor.so
Binary files Stock_system/vendor/lib/mediadrm/libdrmclearkeyplugin.so and /CM_System/vendor/lib/mediadrm/libdrmclearkeyplugin.so differ
Only in Stock_system/vendor/lib/mediadrm: libwvdrmengine.so
Only in Stock_system/vendor/lib: soundfx
Only in Stock_system/vendor: media
Only in Stock_system/vendor: overlay
Only in Stock_system/vendor: pittpatt
Only in Stock_system/vendor: etc


Only in /CM_System/vendor/lib: libbt-vendor.so
Only in /CM_System/vendor/firmware: BCM4335B0_002.001.006.0191.0201_ORC.hcd
Only in /CM_System/vendor/firmware: bcm4335_prepatch.hcd



I'm thinking the 3 files that are only in the CM tree probably aren't needed anymore.

In the stock tree there are quite a few files, most of them I'm unsure what they might actually do.


Probably unimportant:
/vender/pittpatt/ can probably be ignored, it's a pattern recognition thing. Apparently helps search the web for images.
/vendor/overlay/ is full of replacement APKs, probably largely unimportant.
The widevine files are just links to the same filenames in /persist-lg/firmware but apparently it's for some proprietary DRM stuff.
/vendor/etc/ only contains an audio_effects.conf and charger images in a directory... meh.


Possibly important:
Only in Stock_system/vendor/lib: libxtadapter.so
Only in Stock_system/vendor/lib: libxt_native.so
Only in Stock_system/vendor/lib: libxtwifi_ulp_adaptor.so
Only in Stock_system/vendor/lib: libxtwifi_zpp_adaptor.so

service xtwifi_inet /system/bin/xtwifi-inet-agent
class late_start
user gps
group inet gps
disabled

service xtwifi_client /system/bin/xtwifi-client
class late_start
user gps
group net_admin wifi inet gps
disabled

Only in Stock_system/vendor/lib: liblowi_client.so

From stock's init.galbi2_core.rc:
service lowi-server /system/bin/lowi-server
class late_start
user gps
group gps net_admin wifi inet
disabled


The one that seems really important to me though... is this one
Only in Stock_system/vendor/lib: liblocationservice.so

From the same .rc file I was linking before we have:
#Create directories for QuIPS
mkdir /data/misc/quipc 0770 gps system

#Create directories for Location services
mkdir /data/misc/location 0770 gps gps
mkdir /data/misc/location/mq 0770 gps gps
mkdir /data/misc/location/xtwifi 0770 gps gps

and

service location_mq /system/bin/location-mq
class late_start
user gps
group gps


from init.qcom.rc
service loc_launcher /system/bin/loc_launcher
#loc_launcher will start as root and set its uid to gps
class late_start
group gps inet net_raw qcom_diag net_admin wifi

I'm thinking that maybe these daemons *might* need to link to these vendor files somehow.. but we're also not building some of these binaries for /system/bin


I'm thinking that maybe these daemons *might* need to link to these vendor files somehow.. but we're also not building some of these binaries for /system/bin

There's a couple more sub directories that didnt compare either it seems. Like /vendor/lib/hw also contains flp.default.so and sensors.msm8974.so in the stock system.

Like I've said before. GPS seems like it's working, it's just not reporting as accurately as it should... which is what I'm trying to trace down right now.

Any ideas?
Like I've said before. GPS seems like it's working, it's just not reporting as accurately as it should... which is what I'm trying to trace down right now.

Any ideas from anyone with a bit more knowledge than me? Perhaps there's a way to trace what's using what vendor files while in stock?
Last edited by Yoinx; Yesterday at 12:43 AM.
Yesterday, 11:21 AM |#3555  
JackpotClavin's Avatar
OP Recognized Developer
New York
Thanks Meter: 3,613
 
1,001 posts
Join Date:Joined: Feb 2011
Donate to Me
Hey, what's wrong with your builds? Not booting or not compiling? Also, you might wanna look into adding the following into the build.prop

persist.gps.qc_nlp_in_use=0
ro.gps.agps_provider=1

Quote:
Originally Posted by Yoinx

Perhaps there's a way to trace what's using what vendor files while in stock

I wrote a blob utility last year to trace which files should be needed to add to a ROM's build to load a daemon in /system/bin or a library in /system/lib or /system/vendor/lib

http://forum.xda-developers.com/show....php?t=2794413

I don't think I'm missing anything for the ROM currently, but if you find a daemon that's needed to fix the GPS, you could run it through the blob utility and it will tell you which libraries to build from source (if they aren't proprietary) or add into the build (if they are proprietary)
The Following 2 Users Say Thank You to JackpotClavin For This Useful Post: [ View ]
Yesterday, 12:41 PM |#3556  
marleyinoc's Avatar
Senior Member
Thanks Meter: 47
 
153 posts
Join Date:Joined: Jan 2011
Yesterday I tightened my G2 screws and it went from not working at all (I tried the tape under clip/cover connection suggestion and thought I'd broke the whole thing) to working better than it did when I got it.

Not development related but maybe folks could rule hardware out that way.

I was using an old S3 on wifi for a GPS game and felt it was a little wobbly and that was the top fix for those (not sure it helped as I immediately tried on my G2 and haven't bothered with trying S3 yet).
Yesterday, 03:47 PM |#3557  
Senior Member
Flag Chesapeake, VA
Thanks Meter: 263
 
562 posts
Join Date:Joined: Aug 2011
More
Quote:
Originally Posted by JackpotClavin

Hey, what's wrong with your builds? Not booting or not compiling? Also, you might wanna look into adding the following into the build.prop

persist.gps.qc_nlp_in_use=0
ro.gps.agps_provider=1



I wrote a blob utility last year to trace which files should be needed to add to a ROM's build to load a daemon in /system/bin or a library in /system/lib or /system/vendor/lib

http://forum.xda-developers.com/show....php?t=2794413

I don't think I'm missing anything for the ROM currently, but if you find a daemon that's needed to fix the GPS, you could run it through the blob utility and it will tell you which libraries to build from source (if they aren't proprietary) or add into the build (if they are proprietary)

They aren't booting now, and they're ending up about 20 megs smaller than they should be. I cleaned all of my build and ccache stuff out... No change. I'm thinking something synced that shouldn't have when I pulled the other day... Might have to dig through cm's commits since everything else is still the same now.

I'll have to look at that utility again. Thought last time it just have me the other blobs that file needed... Not the binary that used it.

I know on your build though there is still at least a few selinux issues in dmesg. That's what I was trying to work out first.

Sent from my LG-VS980 using XDA Free mobile app
The Following 2 Users Say Thank You to Yoinx For This Useful Post: [ View ]
Yesterday, 07:14 PM |#3558  
JackpotClavin's Avatar
OP Recognized Developer
New York
Thanks Meter: 3,613
 
1,001 posts
Join Date:Joined: Feb 2011
Donate to Me
Do a diff from your build to mine, perhaps you are using the official CM prop files

Sent from my LG-VS980 using XDA Free mobile app
The Following 3 Users Say Thank You to JackpotClavin For This Useful Post: [ View ]
Yesterday, 07:35 PM |#3559  
Senior Member
Flag Chesapeake, VA
Thanks Meter: 263
 
562 posts
Join Date:Joined: Aug 2011
More
Quote:
Originally Posted by JackpotClavin

Do a diff from your build to mine, perhaps you are using the official CM prop files

Sent from my LG-VS980 using XDA Free mobile app

Yeah, I was planning on doing that when I got a chance . Just been pretty busy the last few days. I've got some time tonight and this weekend, I should be able to get to the bottom of it. Just gets a bit annoying when you think you fix it, wait the 2-3 hours for the build to finish... then figure it out it wasn't.

It could be using their device trees, but I don't think it is. Repo ignores my LGE devices, vendor and kernel as a mismatch.

By the way, please don't feel like I'm bashing your builds or anything with the spitball ideas I'm putting out... Just trying to come up with some reasoning for the wonky GPS. You know way more about this stuff than I do... I'm more of a hobbyist.
The Following 2 Users Say Thank You to Yoinx For This Useful Post: [ View ]
Today, 12:12 AM |#3560  
Senior Member
Flag Chesapeake, VA
Thanks Meter: 263
 
562 posts
Join Date:Joined: Aug 2011
More
Quote:
Originally Posted by JackpotClavin

Hey, what's wrong with your builds? Not booting or not compiling? Also, you might wanna look into adding the following into the build.prop

persist.gps.qc_nlp_in_use=0
ro.gps.agps_provider=1



I wrote a blob utility last year to trace which files should be needed to add to a ROM's build to load a daemon in /system/bin or a library in /system/lib or /system/vendor/lib

http://forum.xda-developers.com/show....php?t=2794413

I don't think I'm missing anything for the ROM currently, but if you find a daemon that's needed to fix the GPS, you could run it through the blob utility and it will tell you which libraries to build from source (if they aren't proprietary) or add into the build (if they are proprietary)

I got my builds working again. Not entirely sure what happened, but it seems like my vendor files weren't getting copied. Which was weird, because I hadn't messed with those previously. But, still getting my no sim indications when I boot up. There wasn't anything else you had to cherry pick to get your RILD working? I saw the commit for the rild symbols crossed out because of the radios, I tried that but can't test until Thursday night.

I'm still getting selinux denials for most of my system services...

<4>[ 534.980117 / 12-31 20:20:47.209] type=1400 audit(4847.209:2073): avc: denied { getattr } for pid=10631 comm="IntentService[M" path="/system/bin/rild" dev="mmcblk0p34" ino=281 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:rild_exec:s0 tclass=file permissive=0


like rild there. I get these for most of my daemons. Its really weird... not sure why selinux is considering them untrusted apps.



Also, I ended up using your utility. I think I got all the files that I'm looking at. Still not sure it will work if SE linux is being stupid about system binaries.
Last edited by Yoinx; Today at 10:30 AM.

Post Reply Subscribe to Thread

Tags
cm11, cm12, kitkat, lollipop, rom
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes