yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] myepicyear:
Anyone who ever needs the 4.2(.1) binaries quickly, ready to extract in your working directory, I have them in a compressed folder on my Google Drive. They are exactly what The Muppets have on their Github for 4.2.1, and they work on both CM10.1 and AOSP.

https://docs.google.com/file/d/0B5iM2XyfUuFRVEUyRGhHT3AwNW8/edit

You can obviously get them elsewhere, but getting them from The Muppets (I feel ridiculous saying that, lol) requires downloading from all six vendors separately. Just sharing if anyone wants it, especially for people new to this stuff. For some first-timers, pulling the right binaries together can be the most confusing part.

I've used these for CM10.1 and AOSP since the very end of December.
[Samsung Galaxy Nexus] something15525:
Are these the ones extracted from the leaked sprint tar? If not I think I already have them, but thanks.
[Samsung Galaxy Nexus] myepicyear:
No, I've not gotten to those yet. These are what have been used on CM10.1 and most people's AOSP ROMs. The structure of the directories may vary slightly for people's custom AOSP ROMs, but the same basic parts are used. This is the exact configuration for CyanogenMod builds though. Not sure how they'll handle the new Sprint binaries.

Sorry I couldn't be of more help. :( I predict that many of the binaries in Sprint's official are the same, maybe with revised naming or structure. I could be wrong. The current ones seem to just work so well, but idk..
[Samsung Galaxy Nexus] something15525:
Hey, you're fine lol. I was just wondering if these new binaries are any better. The binaries you linked to are exactly what i'm using in my AOSP ROM as well, and they work super smoothly, so I don't see a reason to move from them. And you were helpful, so no worries. :D
[Samsung Galaxy Nexus] something15525:
Alright, here come some more questions guys, let's see if you can figure this out.

I'm trying to set default ringtones on my ROM, yet for some reason they aren't getting applied. Here's the file:

https://github.com/SomethingJelly/android_vendor_sjelly/blob/sj4.2.1/config/common.mk

Here's the weird thing...this code here:

# Default ringtones
PRODUCT_PROPERTY_OVERRIDES += \
ro.config.ringtone=Girtab.ogg \
ro.config.notification_sound=Proxima.ogg \
ro.config.alarm_alert=Cesium.ogg

Should set the ringtones, but if I look at the build.prop for a assembled build of toroplus, i see this:

ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg

Seems to not be overriding. The thing is...this code in my common.mk:

# Set MOD and ROM versions
PRODUCT_PROPERTY_OVERRIDES += \
ro.modversion=SomethingJelly-$(BUILD_VERSION) \
ro.romversion=$(BUILD_VERSION)

Which is right above the config lines, works fine. You can see if you look at these lines in my build.prop:

ro.modversion=SomethingJelly-0.7.0
ro.romversion=0.7.0

Here's the whole build.prop

http://pastebin.com/8MFhw3Uh

One more thing. I'm overriding the default apn-config in this file here:

https://github.com/SomethingJelly/android_vendor_sjelly/blob/sj4.2.1/config/cdma.mk

But the line in that file is giving me an error that that line is being ignored during build...

I've commented out the line in my full_toroplus.mk as well here:

https://github.com/SomethingJelly/android_device_samsung_toroplus/blob/sj4.2.1/full_toroplus.mk

Let me know what you find guys, and thanks!
[Samsung Galaxy Nexus] DonDizzurp:
subscribed.
[Samsung Galaxy Nexus] jaizero:
When cherry picking, where is the "platform directory" that I should be cd'ing into to do this -

"git remote add cm git://git hub.com/CyanogenMod/android.git - which adds cyanogenmod as a remote site for you to cherry pick code from"

So confused lol:confused::confused:

Thanks!
[Samsung Galaxy Nexus] ÜBER™:
The platform dir is the folder you made for your source. That make sense?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dreamsforgotten:
The folder your source is in once in platform you'll see vendor device frameworks etc etc

best to be fresh
[Samsung Galaxy Nexus] something15525:
So I fixed the previous issues, now I'm running into another one. Trying to build for the Nexus 10 and am getting this:

build/core/tasks/vendor_module_check.mk:48: *** Error: Product "sjelly_manta" cannot have overlay in vendor tree: vendor/sjelly/overlay/common. Stop.

Is this something in my vendor files restricting me from using a common overlay? Here's the github repo for it:

https://github.com/SomethingJelly/proprietary_vendor_samsung
[Samsung Galaxy Nexus] dreamsforgotten:
Possibly stricter build rules/flags, it's probably another commit. I'd start looking in your make files in device compared to that github.

best to be fresh
[Samsung Galaxy Nexus] something15525:
Yeah I found the issue a bit ago in the device.mk. It was restricting vendor files. Thanks for the input! :victory:
[Samsung Galaxy Nexus] IT_Blackbelt:
So I have never had to merge a android update into my rom, now that they have 4.2.1 r1.2 out, how would I merge that into the rom without screwing things up?
[Samsung Galaxy Nexus] something15525:
I was also wondering what the easiest way to do this is. Maybe a rebase?
[Samsung Galaxy Nexus] IT_Blackbelt:
I doubt that, a rebase would mean you have to move all your current changes into the rebase. The guy im working with on our rom knows how and has done it but hes sick as **** so I was just wanting to help move things along. He said its pretty easy to mess things up so im stuck till he either feels better or someone else who knows feels like giving a walk through.
[Samsung Galaxy Nexus] rascarlo:
git remote add aosp GIT_REPO

git fetch aosp

git merge aosp jb-mr1-release
[Samsung Galaxy Nexus] IT_Blackbelt:
I was able to do this without any conflicts, and I assume a repo sync will get the rest of the repos?

Edit to answer my own question, yes :p
[Samsung Galaxy Nexus] dreamsforgotten:
I could be wrong I'm rusty but your making a new branch to sync newest source, then merging your previous branch over this new stock release thus you create and mod the same branch leaving your previous one in tact. Rascarlo?

best to be fresh
[Samsung Galaxy Nexus] IT_Blackbelt:
We didnt create a new branch, we updated our git repos with the commands Rascarlo provided above and updated the manifest to pull ref tags 4.2.1_r1.2 and repo synced, all seemed to update after that.
[Samsung Galaxy Nexus] kai4000:
I'm trying to disable the back button (All Settings) in the top left corner of the settings app in the aosp source code for branch 4.1.2_r1, could anyone please point me in the right direction please. It would be much appreciated.
[Samsung Galaxy Nexus] mani1999:
AW: Developers Support Thread

Could someone pls make this kind of thread for the Galaxy S2?

Please....;)
[Samsung Galaxy Nexus] dreamsforgotten:
Technically, this thread is for any phone. Go ahead and shoot your question.

best to be fresh
[Samsung Galaxy Nexus] mani1999:
AW: Developers Support Thread

What files do I have to replace or add in android.policy.jar to get this mod on my rom:

http://xdaforums.com/showthread.php?t=2109284

Thanks in advanced....
[Samsung Galaxy Nexus] dreamsforgotten:
That would take me a little time to figure out but the dev specifically asks in his thread you ask him permission to use the mod. I'm willing to bet that dev would share his work if you pm him. So pm the dev and get back to me if you need me to decompile it.

best to be fresh
[Samsung Galaxy Nexus] mani1999:
AW: Developers Support Thread

I'm just using it in my private rom...

....but anyway I sendt him a pm asking how to install manually and that I'm just using it on my private rom.

I'm waiting for his response since yesterday....
[Samsung Galaxy Nexus] dreamsforgotten:
I figured it was just for you if he doesn't reply to you I will dig in but that's going to be a lot of work being I have no clue what he edited. I printed the policy.jar once it was 700 pages in ics. In source decompiled it's bigger.

best to be fresh
[Samsung Galaxy Nexus] mani1999:
AW: Developers Support Thread

Well two things I allready know I have to change: circleunlockripplerenderer.smali and jniripplerenderer.smali (I think it's called like that).
[Samsung Galaxy Nexus] dreamsforgotten:
Well there you go you have an idea of what needs to be done. Have you ever used apktool? If not Google it and get the one for what ever operating system your using and we'll go from there.
[Samsung Galaxy Nexus] mani1999:
AW: Developers Support Thread

But why do I need apktool for this? I do the compiling and decompiling with dsixda kitchen....
[Samsung Galaxy Nexus] dreamsforgotten:
that'll work it uses apktool decompile the policy classes.dex and compare to his modded one. I use beyond compare but diffmerge is free it highlights the parts of code that are different. Let me know where you need help with it.

best to be fresh
[Samsung Galaxy Nexus] mani1999:
AW: Developers Support Thread

What's the difference between Winmerge and Diffmerge?
[Samsung Galaxy Nexus] ÜBER™:
Im not sure but id go with Diffmerge.. its pretty straightforward i have some experience with it.
[Samsung Galaxy Nexus] artvandelay440:
Any linux heads might be able to help with this. My hard drive died, and I'm setting up ant for compiling again. I continually get this error when trying to compile my themes.

line 66 of build XML is this:

I'm thinking it can't properly run prepare-resources, but i've made sure its permissions are set (chmod 755) and the script is fairly straightforward. Here's the bash for prepare-resources:

Any thoughts? Using Mint 14.
[Samsung Galaxy Nexus] cj360:
Hello, trying to figure out what changes my device needs for 4.2.1. Currently stuck figuring this out:

target Jar: mms-common (/home/andrew/jellybam/out/target/common/obj/JAVA_LIBRARIES/mms-common_intermediates/javalib.jar)
'/home/andrew/jellybam/out/target/common/obj/JAVA_LIBRARIES/mms-common_intermediates/classes.dex' as 'classes.dex'...
Aidl Preprocess: /home/andrew/jellybam/out/target/common/obj/framework.aidl
Docs droiddoc: /home/andrew/jellybam/out/target/common/docs/doc-comment-check
frameworks/base/core/java/android/view/WindowManager.java:808: error 103: Unknown tag: @{hide}
DroidDoc took 112 sec. to write docs to /home/andrew/jellybam/out/target/common/docs/doc-comment-check
make: *** [/home/andrew/jellybam/out/target/common/docs/doc-comment-check-timestamp] Error 45
[Samsung Galaxy Nexus] MBQ_:
Silly question,

I'm currently repo syncing 4.2.1_r1.2 and making a ROM for the Toroplus. I noticed Googles source has releases 4.2.1_r1.2 for the Toroplus, does that mean I don't have to make any Java edits to get the radios to work this time?

Thank you.
[Samsung Galaxy Nexus] something15525:
Yeah...I'm pretty sure they didn't fix that stuff...maybe take a look at the commits in between android-4.2.1_r1 and r1.2? When I updated my repos there were no new commits in frameworks_base, frameworks_native, or the toroplus repo, which is where the edits were made. When I created my repositories it was from android-4.2.1_r1, so in between there and now (r1.2) there haven't been any changes.

Hope this makes sense!
[Samsung Galaxy Nexus] MBQ_:
It does. :)

Okay, so where can I find the files and/or binaries (took a break from doing this stuff and forgot the terms) that will allow the radios to work on the Toroplus? I'm really really new with Java and don't feel like getting upset over trying to edit this stuff with a high risk of continuously screwing things up
[Samsung Galaxy Nexus] something15525:
Here are the commits i used on my repos for the RIL fix. dream's tutorial works too but this one is a little cleaner. ;)

Missing symbol for toroplus ril lib

Fix toroplus lte lib with proper use of cflags (1 of 2)

Fix toroplus lte lib with proper use of cflags (2 of 2)

Take a look at my commit history on these repos as well, as you need to cherry pick the "Missing symbol for toroplus ril lib" first before picking the other ones. Let me know if you need some help.
[Samsung Galaxy Nexus] MBQ_:
I do. It would really really help.

Would you mind 'holding my hand' and giving the exact step-by-step instructions or commands I need to enter in order to get this working correctly? Thank you so much
[Samsung Galaxy Nexus] something15525:
No prob. So where exactly is your source right now? Did you just clone from android-4.2.1_r1.2 and thats it so far?
[Samsung Galaxy Nexus] MBQ_:
Yes. I'm currently repo syncing android 4.2.1_r1.2

I'm also headed to bed, I'll check back as soon as I'm up. Thanks again bro
[Samsung Galaxy Nexus] something15525:
Yeah, no prob man. Let me know how it goes.
[Samsung Galaxy Nexus] MBQ_:
I'll let you know if it syncs successfully soon

And do I just have to cherry-pick the code from those links you posted? Or is there more work to get these radios working?
[Samsung Galaxy Nexus] something15525:
Well I'm assuming you're going to make your own git/github repo from what you get from Google's source. So cherry-pick those commits, and this one too, since Google magically forgot to fix this:

https://github.com/SomethingJelly/android_device_samsung_toroplus/commit/cef6b098638c6aa13c4a15896eace0fa50ba56cb

There's a couple more things too...

I put this into a common overlay for all the devices I build for, since it's missing from each one, but if you're just building from toroplus for now, you can just put it in the device-specific overlay:

https://github.com/SomethingJelly/android_device_samsung_toroplus/commit/d84a1e0cb1fddb90576cfd7df33e9a8b2c70906e

There's some stuff to fix with the vendor files too if you're using the one's dreams provided. Let me know
[Samsung Galaxy Nexus] MBQ_:
Man, was Google/sprint trying to punish toroplus Devs? Ahaha. I'll do this when I get home today, thanks man.. I appreciate your help
[Samsung Galaxy Nexus] dreamsforgotten:
I was under the impression if you used the binaries released with the new ota there is no need to mod the source for the ril

best to be fresh
[Samsung Galaxy Nexus] MBQ_:
Is it because they officially released android 4.2.1 for the toroplus?
[Samsung Galaxy Nexus] dreamsforgotten:
I'm guessing if you remove the binaries from this tar http://www.sxtpdevelopers.com/showthread.php?t=107, you shouldn't need to do the edits to source for the ril to function. I don't have toroplus anymore to test this so let everyone know.
[Samsung Galaxy Nexus] MBQ_:
How would I go about removing the binaries?

Hahaha, I feel like such a 'noob' :(
[Samsung Galaxy Nexus] maddoggin:
yes this is true. from 4.1 to 4.2 the telephony files were moved from frameworks/base to frameworks/opt/telephony. this is the reason why we needed the fix for data. the old binaries from 4.1 pointed to frameworks/base but with the new binaries they have been updated to point to the right direction wich is frameworks/opt/telephony. ypu can grab the new binaries from any new rom im sure has been updated with new binaries by now. im sure there is a deodex version of stock 4.2.1 sprint ota update somewhere or you can just use my vendor for toroplus which i have updated with new binaries already HERE.
[Samsung Galaxy Nexus] MBQ_:
Yes!!!! THANK YOU.

:good: :good:
[Samsung Galaxy Nexus] something15525:
Wow well color me impressed, I didn't know that. I'll have to update my binaries today. Sorry for the misinformation, wasn't my intention.

Guess we both something today. Lol
[Samsung Galaxy Nexus] dreamsforgotten:
Don't feel bad you were helping!

best to be fresh
[Samsung Galaxy Nexus] mani1999:
AW: Developers Support Thread

YEAHH now the ink color changer app opens normaly....

....but ink effect still doesn't work, just ripple effect (even tough I ticked Ink effect)

Please help me....
[Samsung Galaxy Nexus] IT_Blackbelt:
I can confirm this, removed rushdogs fix, make clobbered, rebuilt and everythings working!
[Samsung Galaxy Nexus] MBQ_:
noob question 2:

How do I properly cherry-pick a code from Cyanogenmod? I did it before, but cant remember how, and.. would it work if im using androids google source?

i.e: adding CM feature to stock rooted OTA 4.2.1_r1.2 build
[Samsung Galaxy Nexus] maddoggin:
Need to learn how to use git! Learn how to create branches and add remotes. First thing you need to do is add the cyanogenmod remote. For instance if you want to add something in frameworks base. CD frameworks/base. Git remote add cm (cyanogenmod/frameworks/base remote URL) then git fetch cm then git cherry-pick (commit id). Or add the remote by CD (work tree) run git init. Then git remote add cm git:github cyanogenmod/github.com (something like that you can find the URL in cm wiki) now you can cherry pick directly from cyanogenmod gerrit code. It's not easy to explain sorry. Takes some getting used to and takes learning git

And yes it will work with android source. Or any source since cm builds off android
[Samsung Galaxy Nexus] MBQ_:
Awesome, thanks dude. :)

Im going to update all my Ubuntu stuff, make clean (build errored out, my friend pointed me in the right direction and gave me a different libsecril-client.so to use), then going to use CCACHE to speed up my builds. The first step is ensuring it boots, and has data working. Hahah

Im super thankful for those who helped me, and those who helped others. Thank you.
[Samsung Galaxy Nexus] something15525:
Let me know if you need anything else dude. :D
[Samsung Galaxy Nexus] IT_Blackbelt:
What is the best way to go about fixing merge conflicts?
[Samsung Galaxy Nexus] MBQ_:
4.2.2 added to the source tree guys!! :)
[Samsung Galaxy Nexus] something15525:
Just manually go through the files, look for the <<<<<<<<<<HEAD marker and anything between that and >>>>>>>>>>>>>'commit msg here' is the conflict. Fix the issues and you're good! Let me know if this makes sense.

Totally going to update my ROM tonight with this! EXCITED!!! Lol
[Samsung Galaxy Nexus] IT_Blackbelt:
I was pretty sure someone...maybe not in this thread mentioned a tool or something, if I find it again ill update :p, Ive got all the merges pushed to our git minus the 3 repos that had conflicts.
[Samsung Galaxy Nexus] IT_Blackbelt:
Im not so sure 4.2.2 is 100% ready...
[Samsung Galaxy Nexus] maddoggin:
I think your right? When sync 4.2.2 not all the files are there. Don't think they have pushed everything to github yet
[Samsung Galaxy Nexus] IT_Blackbelt:
I updated my manifest to match the 4.2.2 manifest, and I noticed it was missing some of the hardware repos, repo synced, and now builds wont even start, blah
[Samsung Galaxy Nexus] MBQ_:
2 questions

When do you think 4.2.2 will be ready to sync?

Do I have to re-download the entire repository?

Thanks guys. :)

Good news, just compiled a source CM build, and I think(**) itll actually boot this time, I diffed my build, and the 021113 build of CM, and Im only missing a few libs, but no apps are missing this time!!! Off to go see if it boots. :)
[Samsung Galaxy Nexus] something15525:
Well that's disappointing...D:. I noticed that the android-4.2.2_r1 tag was missing from all the device trees, and thought there just weren't any updates for them. Guess the update isn't fully pushed out yet. That's kind of weird that they only pushed some of it out...
[Samsung Galaxy Nexus] MBQ_:
I finally did it. :)

View attachment 1725934
[Samsung Galaxy Nexus] something15525:
YAYY!!!! :D
[Samsung Galaxy Nexus] MBQ_:
Thinking about making my own CM nightly ROMs, I actually edited the strings.xml of the settings.apk to better explain the performance settings. Re-compiling a build as we speak and am crossing my fingers that it'll work and look as it should.

Thank you all for your help.
[Samsung Galaxy Nexus] Kurre:
I haven't really followed this thread and this might be mentioned, but I fix merge conflicts with kdiff3 and git's mergetool. It makes it easier and faster if you have many files with conflicts.

First install kdiff3 (of needed):

sudo apt-get install kdiff3

Then you can use it with git like this:

git mergetool -t kdiff3

-t will choose your tool in case you have multiple options available and haven't set kdiff3 as a default option.

Then just browse through delta parts with ctrl+up/down and make your choice with ctrl+1/2/3 or just use your mouse. You can also input your own text if needed.

Occasionally I have weird issue that kdiff3 doesn't run after the git command. That causes some problems.. :mad: but I use manually running and closing kdiff3 before using git command as a workaround.

Ps. I'm just a newbie what comes to compiling stuff and using git, so feel free to correct me :D

edit: link for the git mergetool manual page

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] IT_Blackbelt:
So I seen on android police that all 4.2.2 source has been pushed, so if thats the case, I gotta figure out why I cant build it lol fing google
[Samsung Galaxy Nexus] MBQ_:
I can't wait to read the changelog :)
[Samsung Galaxy Nexus] IT_Blackbelt:
Basicly, bluetooth audio stream is supposed to be fixed, the wifi and bluetooth tiles work as toggles by long pressing, and performance fixes.
[Samsung Galaxy Nexus] MBQ_:
That's good enough for me!
[Samsung Galaxy Nexus] IT_Blackbelt:
I can't believe google still hasn't pushed the missing 4.2.2 repos yet, they obviously have them ready since its been pushing out to phone for 2 days....wtf, I wonder if they even realize the device repos and most of the hardware repos aren't updated for us to sync too.
[Samsung Galaxy Nexus] something15525:
Does anyone know what the deal is?
[Samsung Galaxy Nexus] IT_Blackbelt:
I havent found any info on it, so my guess would be no.
[Samsung Galaxy Nexus] something15525:
Yeah, I've been googling for like 3 hours and found nothing except that android police thinks they pushed everything already, which they obviously haven't. I'm a little frustrated. Lol
[Samsung Galaxy Nexus] something15525:
Guess what, I figured it out. All you need to do is look at Google's platform manifest for android-4.2.2_r1, and you'll see they got rid of a bunch of device files and hardware files.

Just diff with your current manifest. Still trying to figure out why they did this, but now we know why this isn't working. Lol
[Samsung Galaxy Nexus] IT_Blackbelt:
Yeah, I brought that up a page or so back, I updated my manifest to match theirs (cuz thats what your supposed to do) and boom build wont even start, hell I cant even run a make clean. The hardware and device files are needed, wish I knew wtf they were thinking, hope they update it soon to include them in 4.2.2

on a side note, on CM's g+ page, the post about 4.2.2 mentions lots of changes to hardware/qcom/display, but....i dont see it on the 4.2.2 manifest or any 4.2.2 tag under that repo, so confused, maybe google completely changed up where **** is and how it works O.O
[Samsung Galaxy Nexus] maddoggin:
I think it's safe to build with the old hardware files bro. Try adding the missing files to the manifest and just add revision="jb-mr1-release" at the end and run sync again. Then Try that. I think you can build with the old files. That's what some have done. They have just merged in the changes that were released.
[Samsung Galaxy Nexus] IT_Blackbelt:
Good idea, Im going to give it like a week or so to see if any changes come down and then ill do that and see how it runs
[Samsung Galaxy Nexus] mani1999:
Hi everybody,

How do I activate on/off toggle for ripple effect in secsettings.apk?

Thanks in advanced....;)
[Samsung Galaxy Nexus] IT_Blackbelt:
JBQ is working on the device and hardware trees and will have the 4.2.2 tagged repos out as soon as he gets them done, good thing is, we now know google KNOW'S about the issue, so Im going to hold off building until then, for anyone wanting to build it now, use maddoggins suggestion for editing the manifest.
[Samsung Galaxy Nexus] maddoggin:
Do you have a link to the convo? Would like to see what he said. Why they were not initially pushed.
[Samsung Galaxy Nexus] IT_Blackbelt:
https://groups.google.com/forum/#!msg/android-building/WY6KRt8v738/Zr21QCOr86YJ

Basicly he said he just didnt have them ready on time...more likely they wanted to be the first to release actual 4.2.2 roms lol
[Samsung Galaxy Nexus] maddoggin:
Lol. Thanks!
[Samsung Galaxy Nexus] mani1999:
Does anyone know of a "Disable Scrolling Cache" tutorial?

I'm on Galaxy S2 XWLSD deodexed....