yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] galets:
init.d disabled?

I'm looking at 4/15 version, and it's excellent, except for some reason init.d is disabled:

root@d2vzw:/ # tail -n 5 /init.cm.rc
# sysinit (/system/etc/init.d)
service sysinit /system/bin/sysinit
user root
oneshot
disabled

Naturally, none of the scripts in /etc/init.d are executing. Can this thing be fixed? I rely on SSH access in my phone, and don't want to screw around looking for hacks to get around init.d issue
[Verizon Samsung Galaxy S III] amf66:
Possible bluetooth fix has just been merged. Poor invisiblek. Just read the commit notes. http://review.cyanogenmod.org/#/c/95422/
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
04/15 build: anyone have MMS issues? I can't seem to send one. Have not tried receiving an MMS yet. Just using the default Messenger app.
[Verizon Samsung Galaxy S III] amf66:
Use Textra. It's been fixed, but there haven't been any new builds with the fix. I would build d2vzw for you guys, but I don't have enough hard drive space for two builds at once. :(
[Verizon Samsung Galaxy S III] galets:
since you are building already, could you pretty please also reenable init.d?
[Verizon Samsung Galaxy S III] amf66:
Like I said, I don't have enough space to build for d2vzw. Try https://play.google.com/store/apps/details?id=com.broodplank.initdtoggler&hl=en for init.d.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Textra not working either (MMS). Oh well. It's Ok. SMS is good enough, for now.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Edit: misread the post
[Verizon Samsung Galaxy S III] timedroid:
Oops, posted this in the wrong thread first.

I think I found the problem with the camera

objdump -CT camera.vendor.msm8960.so | grep -i 'vtable for android::SortedVector'

00031398 w DO .data.rel.ro	0000002c vtable for android::SortedVector<android::key_value_pair_t<android::String8, android::String8> >

objdump -CT libutils.so | grep 'vtable for android::SortedVector'

000155a8 w DO .data.rel.ro	0000006c vtable for android::SortedVector<android::BlobCache::CacheEntry>

00015728 w DO .data.rel.ro	0000006c vtable for android::SortedVector<android::key_value_pair_t<int, android::ProcessCallStack::ThreadInfo> >

The vtable of SortedVector is exactly 64 byte bigger in our build of Android. Which happens to be exactly how much is added when NEEDS_VECTORIMPL_SYMBOLS is defined.

So I think we just need to remove that line from device/samsung/msm8960-common/BoardConfigCommon.mk

I'll test this tomorrow and submit a patch (if no one else gets to it first).

Not sure why it worked sometimes. My guess is some other library was being loaded that used android::SortedVector<android::key_value_pair_t<android::String8, android::String8> > and exported it as a dynamic symbol. So the dynamic linker used that instead of camera.vendor.msm8960.so's.
[Verizon Samsung Galaxy S III] Master Cylinder:
Ask for donations to get you a $50 1 TB drive! :silly: (Assuming you have a desktop, though.)

By the way, I've never gotten 4/15 to boot. Tried ever which way.
[Verizon Samsung Galaxy S III] RustyMongoose:
I lost root access after flashing this. I think it may have been my failure to use Twrp. Otherwise everything is running fine. Any recommendations on how to restore it?

I tried updating SU binaries but it fails. Do i have to try to use ODIN to get it back? Thanks for the great ROM.
[Verizon Samsung Galaxy S III] amf66:
Have you turned on root in developer options?
[Verizon Samsung Galaxy S III] RustyMongoose:
I had no idea this was a thing in the new version of android. It looks like that did it. Thanks a bunch!
[Verizon Samsung Galaxy S III] amf66:
Let me know how it works out.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Don't you have to use the SuperSU zip to install SuperSU & after it should update fine.

---------- Post added at 11:35 PM ---------- Previous post was at 11:32 PM ----------

Anybody have the volume working right or know how to correct it? The ring volume and noti volume always stayed linked, you can't separate the two. It actually lets you change the rockers in the drop down menu to two separate levels, but it doesn't do anything, the volumes are still linked. Thanks
[Verizon Samsung Galaxy S III] amf66:
Read my answer.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Yeah, but you still need to install using the zip, no? Lol. I auto turn on dev options, been doing it forever. No worries, great job by you.
[Verizon Samsung Galaxy S III] yorkwar:
This thread

"http://www.xda-developers.com/psa-google-play-services-wakelock-affects-many-5-x-roms/"

says there's a wakelock bug in google play service, which may affect the CM ROM. Is this work-arounded in 4-15 build?

Actually, I'm wondering, if I do not even install Gapps, will I encounter the wakelock problem?
[Verizon Samsung Galaxy S III] amf66:
No, just enable root in dev options. No need to flash.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
What is the last 5.1 build that the default MMS worked?
[Verizon Samsung Galaxy S III] DubleJayJ:
I'm on 4/11 and it works fine for me
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
On the 04/11 build as well with pa-micro 5.1 GApps. My MMS is still broken. Hmm. :confused:
[Verizon Samsung Galaxy S III] amf66:
It will be fixed in the next build. If I can ever afford some more hard drive space I'll build it myself. Not sure what's up with invisiblek.
[Verizon Samsung Galaxy S III] Lrr_r:
Does invisiblek use any out of tree patches? I've tried building 4/19 myself but there was no signal and the network type was stuck at 'Unknown'. The 4/15 from here is fine though.
[Verizon Samsung Galaxy S III] SubwayJrd:
That's why I've avoided building so far. I'm sure he does have some patches he's repopicking, or separate branches that override the main CM 12.1 branches for our d2vzw to work.

I'm happy to spin builds for people too (I've got plenty of hard drive), but I don't want to be handing out broken stuff to people.
[Verizon Samsung Galaxy S III] mastamoon:
I don't think he is cherry picking anything thats not on gerrit, and if he is it wouldn't be something that show stopping. He's not the type to keep stuff off gerrit. I can ask him though.
[Verizon Samsung Galaxy S III] timedroid:
I built 4/19 (synced around 11am EDT) and am getting signal.. No out of tree patches except the one I did trying to get the camera working (I think it fixed one problem but the camera now usually stops working after using it once).

What are you using for blobs? TheMuppets/proprietary_vendor_samsung is working for me.

EDIT: BTW, I uploaded my build to https://mega.co.nz/#!UddTEITI!nfe5E9ZhtRS_cmyga8EESl-Ab23GmZPAE9Z_iZfwqwA if anyone wants to try it. Don't know if there's a better place to upload files.
[Verizon Samsung Galaxy S III] yorkwar:
I'm not sure if it's the appropriate thread.

Anyone know how to change the font of the built-in SMS? I do not want to change the system font, but only the font of the SMS.
[Verizon Samsung Galaxy S III] amf66:
Which patches are you trying? I have been using 92964 and 92969 for the past few weeks and they most of worked. Until now. All my builds after 4/17/15 have a broken camera like you describe.
[Verizon Samsung Galaxy S III] Lrr_r:
Thanks for that link. I used extract-files.sh to get them from the 4/15 build but apparently the script hasn't been fixed after splitting d2lte back into individual devices and it failed to extract lib*ril.so
[Verizon Samsung Galaxy S III] mastamoon:
Builds should be live again tomorrow... build was failing.

---------- Post added at 10:43 AM ---------- Previous post was at 10:09 AM ----------

OK, so you guys building your own, data really isnt an issue, it was something on your end? Just want to make sure.
[Verizon Samsung Galaxy S III] Lrr_r:
Yep, I've just rebuilt a fresh checkout with all the blobs in place and I have data. The only thing lacking in that department now (same as with 4/15) is an ability to switch to 'GSM (auto)' (Global = 'LTE/CDMA/GSM (auto)' is not the same). CM 10.1 used to do it just fine.

Both stock and OpenCamera seem to be able to shoot photos with flash and videos.

Got a GPS fix.

Encryption works.

In-call volume doesn't seem to take: it starts out at maximum each time regardless of the slider position. If during the call I change it to max and then back, it decreases but the next call is loud again.

BTW, I've had two random reboots in two days while on 4/15.
[Verizon Samsung Galaxy S III] Master Cylinder:
I'm gonna try yours to see if I can get it to boot, then we'll see what it looks like!:good:
[Verizon Samsung Galaxy S III] mastamoon:
Do you want "GSM (auto)" because your not using the phone on VZW? If so you'll likely need the GSM ril blobs.. maybe the switch would work then. I have them here http://mastamoon.truelinux.net/other/d2gsm_rilblobs.zip if you want to give them a shot. Just flash in recovery.

---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------

Also, invisiblek has a build running now.. should be done within the near future. EDIT: Its done!

He also said he turned off the dex-preopt stuff.. so builds will be smaller again. Savings wasnt worth it.
[Verizon Samsung Galaxy S III] Lrr_r:
I'm not but I'm on a CDMA network. However I want an option of forcing GSM as well.

That looks like it would remove the CDMA support.
[Verizon Samsung Galaxy S III] mastamoon:
Are you switching sims between a GSM and CDMA carrier or something? If so, you probably would have to flash back and forth between GSM and CDMA ril blobs. d2lte and had gsm ril blobs "built in" so thats probably why it worked. If you build for d2vzw right now, your only gonna get CDMA.
[Verizon Samsung Galaxy S III] Lrr_r:
The CDMA info is programmed into NVRAM and I have a GSM SIM inserted. Rebooting is a bit too drastic. Too bad this got broken...
[Verizon Samsung Galaxy S III] Lrr_r:
d2lte and what? =) Also not sure what "built in" means here.

Are you saying that neither of blobs available for the current baseband can switch the mode on the fly or that the maintainers chose to not support this and putting the blobs back could be possible?

What about older modems? As I'm not on VZW, I may not care about most of the differences between their versions. Unless the older ones just aren't expected to work with 12.1...
[Verizon Samsung Galaxy S III] mastamoon:
d2lte was basically a global build for multiple carriers. It had a setup where depending on your carrier it would know to load either the cdma blobs or gsm blobs. It sounds like you will need to do this manually now. If you want it to be automagic, I guess you have to go back to CM11.

I just know from people using my cm12 builds that wanted to use it on a GSM carrier, they would have to load those GSM blobs to get it to work.
[Verizon Samsung Galaxy S III] Lrr_r:
My successful use of live switching was on 10.1.3 before the unified build was even introduced. So I figure the contemporary Samsung ROMs carried a blob that supported switching back then. So either they changed their ways or I have no idea where those blobs actually come from.
[Verizon Samsung Galaxy S III] mastamoon:
I dont know if its the blob per'se, but the way the RIL can talk to the blob. I believe QCRIL really flipped most of these phones for a loop. Phones that didnt get the magic touch from the guys who really know their **** when pulling all this CAF code in.

Have you tried CM11 to see if it helps you out?
[Verizon Samsung Galaxy S III] Lrr_r:
Thanks for explaining.

Installing 11 has never seemed worth the trouble and especially now that it's obsolete. So unless you're suggesting I flash it just to test the switching, I'll pass on that. =)

Unrelatedly, I've found that muting the microphone in a Skype video call doesn't seem to work (running my own build from today).
[Verizon Samsung Galaxy S III] Master Cylinder:
You'll be glad to know that you're build seems solid. Can't find anything wrong with it. Stock camera will take all the shots I asked of it but video is a no go.

However, "A Better Camera" works perfectly in every respect! [emoji106]
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Just installed 4/21 & some issues are gone, like the ringer & noti volumes can be linked or not now, but the lockscreen autorotates though it's turned off in settings. This lockscreen issue was present in 4/6, fixed in 4/15, and now back in 4/21. Any ideas?
[Verizon Samsung Galaxy S III] galets:
and init.d is also not fixed
[Verizon Samsung Galaxy S III] bamaredwingsfan:
My picture gallery is just loaded with blank images, is there any way to purge the blanks so I don't have to roll through so many pictures to find what I'm looking for?
[Verizon Samsung Galaxy S III] Droidriven:
Use a file manager or go through the gallery itself and long press the first blank one, then go through the list and select all the other ones, after getting them all selected you can delete them all together. You must have accidentally deleted their thumbnails.

Tapped under ice from my Ice Cold lollipopped S3
[Verizon Samsung Galaxy S III] amf66:
Updated OP to reflect 4/21/15 build.

Guys, there have been some big camera changes today. I'm not sure if they made it into invisiblek's 4/21 build but you'll like them if they are. They've almost completely fixed the camera on my end.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 04/21

GApp: PA-Micro

My MMS is now working! :good::highfive: Just wanted to report that for anyone else that had this issue.

Edit: Spoke too soon. Now it's not working. :(
[Verizon Samsung Galaxy S III] fluffman86:
Running InvisibleK's latest 4/21 with the 4/21 GApps from the OP, totally fresh install, and have no mobile data. Cellular phone calls work fine, as does WiFi.

Was on InvisibleK's ML1 modem, and just upgraded to the NE1 Modem. Same results. Any ideas? Should I roll back to the previous build?

Edit: Nevermind. LTE started working after another reboot. Not sure why.

Now I need to work on the camera. That's been giving me issues for a while. Replaced the physical camera once, maybe the connection's loose. I'm getting nothing despite others saying it works.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Yeah, I'm noticing this too. When I'm home, I'm on Wi-Fi, no worries, but once I'm out on data, calls come in fine, but data is a no go. A reboot fixes the issue. Weird.
[Verizon Samsung Galaxy S III] Master Cylinder:
I've seen it a lot myself. I pull the battery after every flash and I don't see that any more.
[Verizon Samsung Galaxy S III] DubleJayJ:
Phone won't get passed the boot screen. I've rebooted plenty of times before, haven't installed any new apps or updated and now it just won't boot. I just wiped system and reflashed 4/10 and now I'm waiting to see if it boots. If nothing happens, I'll backup data and completely wipe then reflash 4/10 and see if that boots. Anyone got any suggestions? I really don't want to ODIN back to stock, even as a last resort.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I see a new 4/22 build is up, what new toys or repaired toys do we have here? ?
[Verizon Samsung Galaxy S III] jackyalice:
maybe it's android 5.1.1

but I cannot boot in after flashed it.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Same here, wouldn't boot. I noticed no cm guy startup animation & then phone looped on starting apps. Also, app count went from 180 to 148 which seems odd too.
[Verizon Samsung Galaxy S III] DubleJayJ:
What was the latest working nightly for you guys? 4/10 puts itself into a bootloop after restoring all my apps, 4/21 still hasn't booted and I'm getting pretty concerned
[Verizon Samsung Galaxy S III] stevet86:
I clean flashed 4/21 yesterday, used the op gapps and restored from titanium without a problem. I tried 4/22 and it didn't display the cm boot screen.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I've tried 4/6 4/15 4/21 & 4/22, only 4/22 gave me issues & wouldn't boot. All the others booted without a hitch and just a few errors once rom is in use.

---------- Post added at 07:24 AM ---------- Previous post was at 07:22 AM ----------

PS I see 4/23 is up, anyone try it yet? Results?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
To add: seeing some folks report 4/23 is a no go like 4/22, fyi, guys.
[Verizon Samsung Galaxy S III] JumperPunk:
I also tried 4/22 with no success. Tried 4/23 without any gapps and it doesn't even make it past the kernel splash screen.
[Verizon Samsung Galaxy S III] mastamoon:
OK, somebody is gonnna have to get a logcat from boot or something so we can see whats going on. Or somebody else run a build and see if it boots. That way we know if its something that was merged or one of invisiblek's cherrypicks or something.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
FYI : The nightly roms have all been taken down. Idk for how long or what, but if you have some stable builds saved on your phone or pc, KEEP THEM SAFE. For me, 4/21 last stable build.
[Verizon Samsung Galaxy S III] jbleach:
I was never able to get 4/15 to boot all the way. I had no trouble at all with 4/21 - it booted fine and was is very stable. I downloaded 4/22 yesterday but haven't tried it yet.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
No one I've seen has gotten 4/22 or 4/23 to work. Furthermore, like mentioned in the post before this one, all these builds are down from the server, so keep some copies of 4/21 or later stable builds around for now.

Btw, are you able to get a sys log? You'd have to do it with 4/22 installed though & know that it's a 99% chance it won't boot. Lmk
[Verizon Samsung Galaxy S III] mastamoon:
Somebody will need to grab a log, while on the broken build, via ADB and a PC.

Hopefully somebody here knows how to do that lol. Otherwise googlez is ur frend.
[Verizon Samsung Galaxy S III] JumperPunk:
Sorry, I already deleted the files for the bad ROMs. Also, I'm pretty sure I was unable to use ADB on the 4/22 build. Not sure how to get logs on boot without it.
[Verizon Samsung Galaxy S III] mastamoon:
Almost always it will eventually start working, even on failing boots if you let it sit long enough.. if it never brings adb up.. then thats not gonna be fun to figure out. Basically somebody will have to run some builds while reverting the latest changes to the d2 repos (d2vzw, d2-common, msm8960-common and qcom-common) and see where the derp is. Doesnt sound like its a CM wide issue so it was likely something that was merged over the past 2 days in one of those repos. I was thinking maybe this commit http://review.cyanogenmod.org/#/c/95764/ but it works on other devices so not sure.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I have 4/22 on my phone still, if you wanna try it again and get a sys log. Lmk ?
[Verizon Samsung Galaxy S III] JumperPunk:
EDIT: Just saw [MENTION=5674847]NoCrAppleHere[/MENTION] post.

Got a link I can download it from?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I just told you I did ??? lol. I'll post a link for the download in a sec. ?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I'm sorry, having trouble uploading the damn file. Lol. I don't ever share files, don't need to, so I've been trying to find a site and all to share the zip. Smh.
[Verizon Samsung Galaxy S III] mastamoon:
Use dropbox or mega.
[Verizon Samsung Galaxy S III] Master Cylinder:
Easy instructions here:

http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat

It says free 50GB here: https://mega.co.nz/#

[MENTION=3124924]timedroid[/MENTION] posted his 4/19 which works fine here: http://xdaforums.com/showpost.php?p=60249242&postcount=119

I just deleted 4/22, which wouldn't boot, from my phone and was gonna load 4/21 to see if I could get it to work when I found they were all gone. Anybody got a 4/21 to share?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
https://www.dropbox.com/s/j8n98oftqe71uhx/cm-12.1-20150422-UNOFFICIAL-d2vzw.zip?dl=0

https://www.dropbox.com/s/j8n98oftqe71uhx/cm-12.1-20150422-UNOFFICIAL-d2vzw.zip?dl=0
[Verizon Samsung Galaxy S III] Master Cylinder:
Oh thanks man, but both of those links are for 4/22. Looking for 4/21.

Running 4/10 now but I'll probably up to [MENTION=3124924]timedroid[/MENTION]'s 4/19 if 4/21 doesn't come along...

I've got 4/10 and 4/15 (which never booted for me) if anybody wants them.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Apologizes, misread your post.
[Verizon Samsung Galaxy S III] stevet86:
Hope this works.

4/21

https://drive.google.com/uc?export=download&id=0B82qoYmldeJ6TWIyTkFxVW53QUE
[Verizon Samsung Galaxy S III] JumperPunk:
About how long is "long enough"? Are we talking 30-60 seconds, 10 minutes, or 2 hours?
[Verizon Samsung Galaxy S III] mastamoon:
10 mins max.. sometimes there is so much crashy going on that the service doesnt get started for quite a while. Hopefully it comes up at some point to spit out some output.
[Verizon Samsung Galaxy S III] JumperPunk:
Trying the 4/22 build. It's been about 20 minutes and ADB hasn't come up. I'll boot back into recovery do a wipe and install the 4/21 build and give that one a go.
[Verizon Samsung Galaxy S III] mastamoon:
Damn.
[Verizon Samsung Galaxy S III] JumperPunk:
uhh... the 4/21 build just booted. Still hasn't started adb, though. Looks like debugging is turned off by default. [MENTION=6225898]stevet86[/MENTION] was that 4/21 build from [MENTION=2385005]invisblek[/MENTION]?

I got the dates mixed up and was thinking that bad builds from invisiblek were 4/21 and 4/22, not 4/22 and 4/23.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I'm trying to get a copy of the 4/23 build that wasn't booting for anyone either, maybe that'll bring us a syslog?
[Verizon Samsung Galaxy S III] JumperPunk:
Not likely. That one didn't even make it past the kernel splash screen for me.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Mine made it to "starting apps" & then just looped for a loooooong time on that. I dirty flashed it coming from 4/21, could that have assisted me in getting it to get that far at least? Just thinking.
[Verizon Samsung Galaxy S III] amf66:
Anyone got a spare drive they could send me? I'll gladly build but I've run out of space.
[Verizon Samsung Galaxy S III] Master Cylinder:
I swear, if I wasn't down to my last Quatloo I would spend $50 and send you a 1TB from Amazon today! I need one and I can't buy it for myself! (Down to groceries over computer stuff - never thought i'd see the day... As a Thrall, my means have been limited.) On the other hand, I see you have a donate button ... Maybe i can squeeze out 1/40th of a Quatloo to you? Any other takers?

4/21 booted up fine. Lockscreen flipping around on this one. (I don't think [MENTION=3124924]timedroid[/MENTION]'s had this.)

Incidentally, I've noticed that 5 of invisiblek's 9 build folders on his site are empty.
[P3600 General] Piston Broke:
Help my M700 displays the owner id and not the device id when connected to another bluetooth device

any idea on how to swap this so bluetooth displays device id
[P3600 General] NeilM:
From a recent post on 4WM:

By default the Bluetooth name is set to the Owner name. However the Bluetooth name can be set to something else in the registry. In HKEY_CURRENT_USER\Software\Microsoft\Bluetooth\Settings There is a text string "LocalName". Change this to what you want for the Bluetooth name. Soft reset the device (doesn't work without the reset). The name now shows up as the value in this setting.

Hope this helps. You will need a registry editor to make the change.
[XDA Assist] Altaaf663:
Please Is there someone Who have a Custom Rooted ROM For LG D170 With Android 4.4.2.

Please I Really NEED!!! :confused:
[XDA Assist] Heisenberg:
Hi :)

Thanks for writing to us at XDA Assist. I can't find any custom ROMs for your device, but you can root it:

[GUIDE][ROOT] Root your LG L40/L70/L90/G2 mini!
[XDA Assist] Altaaf663:
HELLO!!!:)

Thanks It Was really helpfull :D:D:D. I Tried it and it worked...
[XDA Assist] Heisenberg:
Great news. Thread closed, thanks.
[Moto G Q&A, Help & Troubleshooting] mik0tsi:
I have tried to put cm12 on my phone and it says that recovery is not compatible.

Does it matter that i have 4.4 bootloader on my phone? Is there a way to update the bootloader easily? Thanks! :)