yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Delete the CMHW folder in your local path under device/samsung/msm8960-common
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
it added a new line to that terminal output:

============================================
find: ‘../../../hardware/samsung/cmhw’: No such file or directory
find: ‘../../../device/samsung/msm8960-common/cmhw’: No such file or directory
build/core/copy_headers.mk:15: warning: overriding recipe for target '/home/arunscape/slim6/out/target/product/d2att/obj/include/qcom/display/copybit.h'
build/core/copy_headers.mk:15: warning: ignoring old recipe for target '/home/arunscape/slim6/out/target/product/d2att/obj/include/qcom/display/copybit.h'
build/core/copy_headers.mk:15: warning: overriding recipe for target '/home/arunscape/slim6/out/target/product/d2att/obj/include/qcom/display/copybit_priv.h'
build/core/copy_headers.mk:15: warning: ignoring old recipe for target '/home/arunscape/slim6/out/target/product/d2att/obj/include/qcom/display/copybit_priv.h'
build/core/base_rules.mk:157: *** hardware/qcom/power: MODULE.TARGET.SHARED_LIBRARIES.power.msm8960 already defined by device/samsung/msm8960-common/power. Stop.

#### make failed to build some targets (34 seconds) ####
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
After Deleting you're supposed to make clobber and do lunch again, before proceeding to build. Also add hardware/samsung to your local manifest. For your reference, my local manifest is as follows.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Hey Perseus, good to see you! and glad to see somebody's giving Arunscape some assistance, kudos to him for taking a stab at this ROM:good: Keep up the good work guys, of course I'll be available at testing time:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I cleared my working directory, repo synced again (don't worry, it only takes me about 10-15 mins to redownload everything), and copied your local manifest, yet I still get this:

build/core/copy_headers.mk:15: warning: overriding recipe for target '/home/arunscape/slim6/out/target/product/d2att/obj/include/qcom/display/copybit.h'
build/core/copy_headers.mk:15: warning: ignoring old recipe for target '/home/arunscape/slim6/out/target/product/d2att/obj/include/qcom/display/copybit.h'
build/core/copy_headers.mk:15: warning: overriding recipe for target '/home/arunscape/slim6/out/target/product/d2att/obj/include/qcom/display/copybit_priv.h'
build/core/copy_headers.mk:15: warning: ignoring old recipe for target '/home/arunscape/slim6/out/target/product/d2att/obj/include/qcom/display/copybit_priv.h'
build/core/base_rules.mk:157: *** hardware/qcom/power: MODULE.TARGET.SHARED_LIBRARIES.power.msm8960 already defined by device/samsung/msm8960-common/power. Stop.
make: Leaving directory '/home/arunscape/slim6'

#### make failed to build some targets (37 seconds) ####

Update:

I was able to fix this by myself!! I'm learning!! All I had to do was make clobber and then delete device/samsung/msm8960-common/power

I might upload a build today!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
D2 Testing Help Needed

Hey guys, I need some help testing some Audio HAL commits. I need voice calls tested on a CM13 build I will provide, if anyone can help me with this, that would be much appreciated. Please respond to this post, PM me, or email me if you can/are interested in helping me test this. I am posting this with the permission of [MENTION=3639717]Perseus[/MENTION].

Thanks,

javelinanddart
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Please can you replace contents of your local_manifest with the one I posted earlier ?

Also please clone / Fork the mm6 trees off of my git if needed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I did copy your manifest, and what would I be forking from your GitHub?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
The MM6 Branches of all those device trees

msm8960-common, qcom-common and d2-common
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Since Nougat source has been dropped, and Cyanogenmod is already merging it into their cm-14.0 branch

I think I'll try making cm14 builds for the d2att, because I have successfully done cm13 builds in the past, although I will probably have as much success as with attempting to build slim6 lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
New Maintainer!

Hey guys, I'm the new maintainer for D2 for Slim! I'm planning on supporting d2att, d2spr, d2tmo, and d2vzw. Weeklies for everything except d2tmo is up from last week, and this week will include d2tmo (I missed an overlay, silly me).

I don't believe it has the same kernel tweaks that [MENTION=3639717]Perseus[/MENTION] added to his kernel, but I'll see if I can add my own tweaks to this kernel and find anything that makes it perform well and adds cool tweaks and features.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Nice.... And a big thanks to you for your dedicated service to d2 users..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Thanks, but what kind gesture are you referring to? :confused:

Also: new builds should be up tomorrow, with d2tmo support this time, and SamsungDoze from CM should be present (which is some Ambient Display extras). Nothing really exciting device side, I'm afraid, unless you're on d2tmo and have been itching for a slim build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Actually meant to say thanks for your work in here.. It's highly appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
New weeklies are up, d2tmo has support now

Enjoy!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] locprohp:
hey guy

i building slim for cancro

error: http://hastebin.com/cumaduwupu.js

please, help me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
You have cmsdk stuff, and slim doesn't support that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Well now! I sure wish you'd said that the testing you wanted, in that earlier post was for this puppy! I probably would've volunteered my services, have done it before but was also helping out another pretty nice build - Resurrection Remix- but it's all good, welcome to the thread and thanks for volunteering! gonna flash this soon's it downloads and let you know how she drives.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] locprohp:
pls, how to fix ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
In addition to being completely off topic, you're asking me to fix a device I've never worked on, and never looked at the devices trees for. I'm not sure how to help you, and if you're looking for help on cancro, you'd be better off asking someone in the cancro forums
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
It's all good :) I was testing those changed on cm13, but yeah I'd appreciate feedback on how it runs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Injuis:
I've been using this for about a week now and it runs beautifully. Compared to the CM versions of Marshmallow, this one runs the best by far.

I've actually not had many hiccups at all, which for me is unusual as I go crazy on customizations.

The only issue I had is that the bundled root gave me problems with installing systemless Magisk/SuperSU and SafetyNet validation. Oh, and the default hardware buttons were a bit weird but luckily the navigation utility lets you fix that.

Great work, otherwise! Again, this has been the best Marshmallow build for me out of all the others - Highly recommended.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Yeah, I've noticed it runs much smoother than CM does as well.

Not sure about root stuff, I rarely use root unless I'm hotswapping files to avoid rebuilding a whole ROM, and I haven't done that on d2 in a while.

Default hardware buttons has menu mapped as recent apps, which makes it have the 3 buttons Google wants it to have. I made it that way, probably should've put a note about that in the OP, my bad.

Thanks for the review though, glad to hear it runs well!

EDIT: put a note about HW buttons in the FAQ, thanks for reminding me :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] craterface12:
Any issues with overheating on this rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Not that I've noticed, but d2 isn't my daily driver so I'm not entirely sure
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tcaudill01:
Slim is the stuff!!!!! Very smooth and relatively bug free except for the compass bug. Hopefully this will prove easy to squash.

Thanks very much dev's for all your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] craterface12:
I'm definitely going to flash this to my S3 soon. It's not my daily driver either, but I wouldn't mind giving it a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Compass bug? Tell me more.... I haven't heard of this before. What variant are you?

Cool, I think you'll like it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Weird, what app are you using? I just tested it and it seems to work fine for me

The compass in the quick settings panel seems to be inaccurate, but it's not constantly flipping and spinning and neither is the app i just tested and that one is really accurate. I'll clean flash the latest build and see if I can replicate, I have a d2att too

EDIT: ah, my gps was on, that could probably complicate matters in trying to test something. silly me. IDK if I can squash that bug but I can look into it. I'm really busy atm so not sure when it'll get done, and I'll likely forget because i'm kind of spread out: jf, d2, klte, klimtwifi, g3 (soon), and likely another device in the near future too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tcaudill01:
No problem, get to it if and when you can.

Really appreciate you have put so much work into an old phone.

Edit: Looking through CM13 nightlies and the compass issue is coming from them so it may or may not ever be corrected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] craterface12:
Is there any way to change the notification light color, or just disable it completely? Also, is there a double tap status bar to sleep feature? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Yeah, it is an upstream CM bug, and that means it's *that* much more difficult to solve.

I heard it has worked fine in LP, but I cannot confirm, I got my d2 very recently
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
first of all, buttery smooth~ don't know how you guys achieve that in such old device

only one feature that I find missing is the option to enable/disable battery notification light (the previous ROM I used, Oct-M has it)

I disabled the notification light option, but it still blink red light at low battery and persist light when charging.

Thanks for such great ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
I'm not a ROM side dev guy, I don't know how to add features, and I'm not that great at finding them, but I'll see if I can find it in Oct-M sources.

On the note of buttery smooth - best i can explain? magic :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
You could flash it and check :)

There is a way to disable notification light from what [MENTION=7753138]chenyia1[/MENTION] said, but I'm not sure how.

I would assume double tap 2 sleep on the status bar would be there, it's a pretty standard feature, but again, I don't use it so I can't say for sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
yes, you can disable notification light but you cannot change the color. And, no, there is no double tap 2 sleep for status bar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Karbuster:
kernal?

i may have missed the link but does this come with a marshmallow compatible kernal or do i need to find one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
I have problem with voip call just the Google Phone app. I can hear fine, but they cannot hear me on the other side. Wasn't a voip server problem because the call was fine using other phones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
The kernel included will work fine

What app? Hangouts dialer worked fine for me last I checked

EDIT: [MENTION=3044346]arco68[/MENTION] sent me some patches for review related to voip, I'll be taking a look at them soon
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
I use Google Dialer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
Let me try another VOIP app to see what the root of the problem is. Stay tune. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Thanks.

I'm also going to try getting a build going with the VoIP commits from [MENTION=3044346]arco68[/MENTION] (have been busy with other device work) for d2, what variant are you?

I am going to build d2att if I don't find out the variant by the time the mixers are done, I can build another after but it'll take more time

EDIT: starting build of d2att now. Will take a bit, and I'll link when it's done, If you have another variant, let me know and I'll build that for you

EDIT 2: [MENTION=7753138]chenyia1[/MENTION] Here you go, try this build: https://www.androidfilehost.com/?fid=312968873555003148
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
Yep mine is d2att. I will give it a try. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
Clean flash the testing ROM, most up-to-date OpenGapp.

Voip SIP call still doesn't work on Google Dialer app, and this time I can't hardly hear the incoming voice (stuttering). Try CSipSimple (voip SIP softphone app), same problem as before that I can hear the incoming voice but the other side cannot hear me. HOWEVER, when I try Zoiper (another voip SIP softphone app), it works! I guess I found my temporarily solution.

It might be a missing or conflicting component in the ROM that some voip SIP softphone app relies on (e.g. Google Dialer and CSipSimple), while other softphone app have the component build-in the app.

I think it's impossible to troubleshoot at this point without someone w/ extensive knowledge in the voip SIP calling field.

Thanks for the help. I will just use a 3rd party app instead of Google Dialer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Can you link me what app you mean by Google Dialer?

This app works for me: https://play.google.com/store/apps/details?id=com.google.android.apps.hangoutsdialer

Also, does Zoiper work on the weekly build (not my attempt at fixing voip)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
Confirm Zoiper works on weekly build.

This is Google Dialer https://play.google.com/store/apps/details?id=com.google.android.dialer&hl=en
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
that's not a voip app, that's a replacement for the stock dialer app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
It has SIP call function (voip). I've always use it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
What was the issue with SIP? You said in the test build that the other side couldn't hear you, what was the issue before?

Also, do you mind hitting me up on hangouts? It's probably easier to talk there

javelinanddart@gmail.com
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I haven't been here in a while (didn't expect university to be such a big jump from high school)

It's nice to see the progress that has been made. Today I tried flashing the 1.7 weekly and the only thing I've noticed is that when I long press the home button, no recents screen shows up. I did read earlier that maybe it's the menu key by default, so I'll try it right after I flash gapps

Update: yeah menu button brings up recents
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
You can reconfigure the buttons to be as they were previously in button mapping settings. I really like the extra options slim has for button mapping.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
So far i have been unable to get the hotspot to work. It turns on and my tablet connects but no internet. Does it work for others with tmobile?

Edit solved

You can use this command in terminal emulator, pending you are rooted.

Quote:

su

settings put global tether_dun_required 0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Huh, i didn't know this was a bug (I can't test ril) and this fix likely won't make it into weekly because I don't know how to implement it, but thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Just add that line to build prop ;) It might work

?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Holding off on this weekly, since there's no confirmation that that will work before the builds start rolling, but will look into it for next week (if we run mm builds next week)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
I just finished installing slim6 jtetmo 1.8 to a friend's gs4 and the hotspot worked without the mod.

Something different in the d2 1.7 builds. Neither d2tmo or d2att 1.7 weekly worked without setting that global setting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Yeah I've noticed JF works.
[MENTION=5806583]canodroid15[/MENTION] Sent me stuff I'm going to take a look at for tethering before next weekly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=5795145]javelinanddart[/MENTION], if you need anything else you know where to find me ;)

?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Android412:
Just installed 1.9 and its not finding my SIM card. I'm assuming it's because I'm in Canada.

I've had to add D2CAN to the device install list a couple times to get various roms to install, but have never had a problem after install.

EDIT: Nvm, figured out it was my outdated baseband/modem. All good now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
Fyi

I found a bug with the camera flash. It works on auto but the selection is wrong. Off setting gives auto mode, auto setting gives on mode, and on setting crashes and force closes the camera.

Edit: fixed in weekly 1.10 for d2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] super1395:
Extremely Loud Call Volume

Has anyone experienced the issue where the speakerphone is blaring loud during calls? Yes, I've tried turning down the volume with the rockers, but even at the lowest setting it sounds exactly the same as the highest. I've seen about an audio boost for calls option, but I didn't see it in this rom. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
Flashing from stock 4.4.2 NJ1 modem and I get stuck at the GS3 logo with the lil alien and a pulsing blue notification light. Wiped everything but micro SD, flashed 12/09/16, and am installing Nano GApps. Any ideas where I went wrong? Tried searching on this thread but didn't find anything. CM13 works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gadgetguy08:
Yeah, 1.15 bootloops for me as well. Clean flash, only ROM. D2vzw.

1.14 booted OK.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
Same here, downloaded 1.14 and was able to boot. Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
I finally got around to flashing the 1.15 weekly and it stuck at the boot screen before slimrom emblem shows. Glad I backed up 1.14. Used twrp to restore 1.14 backup. Looks like a problem with the kernel. Just a guess. Came here and see others with the same problem. There also seems to be a problem with the slimroms.org website.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JERW28:
I can confirm this. I had the same issue with 1.15, too. I restored an old backup. Glad to know that someone else has this issue and it isn't just my phone. [MENTION=5795145]javelinanddart[/MENTION] I don't know how to provide logs since my phone never booted past the splash screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
I'm not sure, sorry, and I'm really busy with school and finals and stuff like that right now so it won't be fixed soon. At best, somewhere in january. At worst, next summer. We'll have to see. Sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
No worries. 1.14 works great. very few issues and has given new life to d2. I haven't heard my wife say "I hate my phone" since i put this on hers. Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
No problem. I'm a student so I know how hectic this time is :P. Take your time, no rush. As above, nothing wrong with 1.14.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Thanks :)

I've been spending my limited d2 time working on cm 14.1, all but sprint have nightlies (ril needs confirmation especially data, check [MENTION=5806583]canodroid15[/MENTION]'s post history for a test build) so enjoy those if you can live with them (cm has been more laggy then slim for me, YMMV)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
any timetable for slim7 alpha reaching d2att?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Some point within 2017 :P

In all seriousness, after my finals are done, i have an android todo list longer than my device wishlist (and that's saying something!)

I'll be working with [MENTION=5806583]canodroid15[/MENTION] when my finals are done to put together test builds for d2. It shouldn't be overly difficult, but d2 isn't my main device so my time is limited
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chenyia1:
Great! Thank you guys for keeping such an old device up to date. :good: Looking forward to Slim7 in d2att!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
As always I look forward to working with [MENTION=5795145]javelinanddart[/MENTION] on the Slim7 updates & keeping g another great ROM alive for d2 variants. Good luck on your finals brother!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skurys:
Just curious, last edit says builds after 1.14 are hosed. Anyone successfully get 6.0.1.build.2.0 stable to work? How is it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Injuis:
I'm running 2.0 0118 and it runs good. I'm having a hell of a tough time getting SuperSU to install though. Only way so far is to completely wipe in order to update the SuperSU binary. I get stuck at boot, otherwise. LIkewise, suhide doesn't work at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
Slim6 has su built-in. You turn it on and off in the developer options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Injuis:
Yes, I know. I prefer SuperSU though. Also, in some past builds I was able to use suhide as well. With Slim6 as is, you cannot pass safetynet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
I wish i could keep this going, but I don't have a D2 anymore. I'm having enough trouble as is shoring up Cm14.1 which is having a lot of weird wifi issues, and my personal life got a lot more busy. I'm always working with [MENTION=5806583]canodroid15[/MENTION] when i have a chance to test stuff for lineage, and I hear Team Oct-Os has a solid offering for N, i'd suggest you try it out :)

Sorry for the suspense and the drop off guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=5795145]javelinanddart[/MENTION] always glad to help out & everyone needs a break sometimes. Especially one who has as many things going on as you do (not just the #droidthings) You are a beast dude! Appreciate all your hard work & contributions brother!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] newbe1droidx:
I747 d2att, Is the NE4 bootloader and modem good enough for this ROM? Can't find twrp flashable nj1 then nj2. Thanks for the help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javelinanddart:
Should be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] newbe1droidx:
Thanks I try it on the old beast...