yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Tylog:
Kernel + Rom Build, Gapps stay when you dirty flash.

Edit. Stupid Tapatalk, i see it was a old question.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] pkelly517:
When you track, changes happen automagically by the maintainer.

If you fork, then someone on slim had to keep an eye or on the code to see if anything is happening.

Why duplicate effort (mostly)?
[Nexus 5 Original Android Development] DroidIt!:
Hey all, just a quick general question. We're having a discussion in Robbie's thread. I seem to remember one of the team saying that if you have heads up and quick reply (in messaging settings) enabled at the same time that they can cause conflicts with each other. Any ody know if that's true or found that to be true...or anybody remember what the official statement on that was? Can't remember what the official word on that was :)
[Nexus 5 Original Android Development] AGiLiT:
Looking to see if anyone can confirm this behavior or if it's just happening to me (wouldn't be the first time :silly: )

Using the Peek paid app, if I have a PIN or pattern lock screen set, when a notification comes, I pick up the phone and it blows past the Peek display screen and just wakes the phone. In other words, I never see the notification. The test notification function in the app works fine, and if I have a slide lock on, it works fine.

I have multiROM and have tested this with Stock and PA with the same setup ( Franco.kernel, Dalvik, some Xposed modules.) They both work as expected. I've tried it with Xposed off; same effect. I've tried a clean flash of the ROM (Stable 7.0) and a clean install of Peek. I've tried a variety of settings but can't figure out what might be causing this.

Thanks for listening.
[Nexus 5 Original Android Development] Grondinm:
either way it causes work for slim team. When CM changes something slim team has to react to fix the rest of the system.

The other way around(forking) sure someone has to keep on top of changes but it can be done on there own time and not cause breakage in the mean time...
[Nexus 5 Original Android Development] pseudoheld:
lol [MENTION=992878]hooliganx[/MENTION] that is maybe my strangest post to ever get a "thanks" :D

---------- Post added at 10:39 PM ---------- Previous post was at 10:36 PM ----------

awesome new update for multirom manager is out.

icons for all roms included...except slim...how dare he?? /jk

made a small request to add the slim icon aswell

http://xdaforums.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011/page166

btw if you never tried multirom do it! its great. lets me try out all kind of strange roms but always keep slimkat as my main system^^
[Nexus 5 Original Android Development] chikimonke:
Off Topic sorta, but here's SlimKat getting some recognition as an officially supported ROM for the OPO. http://youtu.be/VwVww_Ci2u4?t=2m50s
[Nexus 5 Original Android Development] Toledo_JAB:
[MENTION=5737873]mrj0087[/MENTION]
[MENTION=992878]hooliganx[/MENTION]

I was going to clean this little "chat" you (and others) had but decided to just leave the posts for everyone else to see some good examples of how NOT to act while on XDA.

This thread has been cleaned many times and yet the locals still reply inappropriately.

Don't get me wrong the question violates the very first XDA rule in the list. "SEARCH BEFORE POSTING" (don't believe me? LOOK FOR YOURSELF)

However, like my late Grandmother would say ,"If you don't have anything nice to say, then don't say anything at ALL" is the golden rule for all XDA members.

I would like to ask everyone to remember we are an International web forum with over 5.7 million users.

Not all of them are at the same knowledge level, age level, maturity level and probably even sea levels :p .

I would bet that, for the majority of members, English is not their first language.

That being said we need to post on the side of caution when replying to others, you may not get their meaning.

If you feel the need to "chat" like that then use the PM system and keep it private.

I do not want to temporarily close this thread or worse take actions on specific members, but that could happen.

IF you do not want to help a new member, that may not be familiar with the proper rules and ETHICS of XDA, then just pass the post over and ignore it.

I would like to thank the couple voices that helped in the issue. (I even hit the button)

If anyone has any comments or questions about this post, PLEASE PM ME!

DO NOT QUOTE ME AND REPLY!

If you like the post hit the button

If not USE A PM.

[MENTION=4568724]fronti90[/MENTION] I am sorry for the off-topic rant in your thread. :(

If you ever need the thread cleaned just send me a PM.

Toledo_JAB

XDA Moderator
[Nexus 5 Original Android Development] pkelly517:
It's caused work for the Slim team today. But, how many times can you think of an upstream change breaking every build?

Maybe Slim forks the ffmpeg code now. Maybe they see what Kondik's doing. Maybe it's worth keeping.

I think it's a knee jerk reaction to immediately fork because of a failure.

Just out of curiosity, is it only the kk4.4, or is the kk4.4-caf repo also affected?

Anyhow, I'm sure there is no wrong answer. And I expect that the Slim team will choose the answer that provides the most benefit going forward.
[Nexus 5 Original Android Development] Garrykd:
...locals....he he

:p:p
[Nexus 5 Original Android Development] ralpheboyo:
All I can say is that this ffmpeg code has caused me nothing but grief the whole day... Look forward to slims approach...

Seriously, have you checked slim FAQ:

http://www.slimroms.net/index.php/faq

Slim&Dankoman GAPPS/TRDS

http://xdaforums.com/showthread.php?p=53632481

SlimRBrew + Ex Kernel
[Nexus 5 Original Android Development] RobbieL811:
Cool video.
[Nexus 5 Original Android Development] pkelly517:
I bet it's nothing compared to the caf/non-caf debate from last summer/fall :)

Which, by the way, caused a whole lot of ROMs to fork the kernel code.

It also brought the (now) age old question: Is this ROM AOSP or caf?
[Nexus 5 Original Android Development] Tylog:
Aosp

Edit. I write it in the Header now.

Edit 2 : done

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Grondinm:
Just different mindset i guess...in my mind forking gives you more peace of mind that only you can break your build not something someone else decided to do. Either way slim team will choose what they want to do and it will just work...and i think both kk and kk caf are affected but can't confirm as i don't build with caf
[Nexus 5 Original Android Development] edrickmph:
How long will this take? I already thought yesterday that i almost bricked my N5. Its almost half an hour but still im stuck with the slimkat logo.
[Nexus 5 Original Android Development] fruitsalt:
This is the process i always follow:

Download latest ROM + Gapps ( make sure to use SlimGapps) + SuperSu + Kernel ( if i want to use a different kernel)

reboot into recovery

wipe system

wipe cache

Flash ROM

Flash Gapps

Flash Kernel -> only if you want to flash a custom kernel

Flash SuperSU

Reboot

Once the system reboots, I dont set it up as i use two step verification so I just setup Wifi and skip google account.

Turn on Developer mode--> Switch to ART, reboot... take about 10-15 mins tops..

After which i download and install all the apps from playstore and set them up

I know people do app backups and rom backups, Ive had issues with restoring from backup So I always just set it up as New every time. Takes all of 30 mins from start to end.
[Nexus 5 Original Android Development] edrickmph:
Thank you for the info. Ill try this if i have more free time. Any difference you can see between ART and the old dalvik? Is it worth the switch?
[Nexus 5 Original Android Development] fruitsalt:
I havent done a scientific test so this could just be all in my head but ive noticed better app & system performance, and better battery life. I think you can stick to dalvik for now as art is still experimental. I just like to tinker and dont mind restoring my system multiple times a day.

& I missed flashing kernel in my post above. Flash kernel before you flash SuperSu, thats if you flash a custom kernel.

I am waiting to get my hands on another nexus 5 so I can actually compare them running side by side.

Do note that not all apps are compatible with ART so some apps will act up at certain times.
[Nexus 5 Original Android Development] edrickmph:
Thanks for the caution. ART is relatively new so i think many apps are not yet compatible. Maybe ill have this done next year to start a new year.
[Nexus 5 Original Android Development] dark_ente:
For now all the apps I'm using are updated to be ART compatible.
[Nexus 5 Original Android Development] jrn2k:
On the latest Franco the stock root app is working for me :thumbup:
[Nexus 5 Original Android Development] handsomejesus:
How can I change the temperature from Fahrenheit to Celsius on the lock screen weather notification?
[Nexus 5 Original Android Development] Jubakuba:
Another few things added to custom toggles...

Long-press to add long-press actions even if no click action is present.

Meaning you can click to cycle apps/tasks. Long-click to launch.

Match-state to toggles with multiple short-click actions...if you treat it like an actual toggle this allows the NEXT task to launch.

Your current displayed task will display the "state" that you're now in (as all real "toggles" function). This is, of course, optional.

Fixed the remaining buggies (one major) in the last few days as well.

And...quick record toggle.

All of Juba's old features are joining the party, lol :fingers-crossed:.

https://www.youtube.com/watch?v=MBVW7HWaco8
[Nexus 5 Original Android Development] ianlunatech:
Pull down on lockscreen widget - there's a setting icon that pops up
[Nexus 5 Original Android Development] handsomejesus:
Oh ****, im blind. Thanks.
[Nexus 5 Original Android Development] bartolinio:
you have cool pictures in the gallery, the intriguing :p
[Nexus 5 Original Android Development] kevtrysmoddin:
Is the chamber of secrets in v1.9?
[Nexus 5 Original Android Development] kevtrysmoddin:
Will it be in any future releases would you say?
[Nexus 5 Original Android Development] DroidIt!:
It's a secret. :p No sir, not in there. :)

from my N5
[Nexus 5 Original Android Development] Jubakuba:
Yes, it was actually meant to be merged for 1.9.

Forgotten...brought up that it was forgotten...

And I said "no worries, compliments custom toggles well anyway."

So it might be merged alongside that.
[Nexus 5 Original Android Development] kevtrysmoddin:
Ah I Read that post to my bad might be a sign in getting old lol
[Nexus 5 Original Android Development] Jubakuba:
Naw, that was a private conversation with the team. You're not getting old, just crazy :p jkjkjk.
[Nexus 5 Original Android Development] dankoman:
still looks like iOS maps :p
[Nexus 5 Original Android Development] RobbieL811:
Whoa whoa whoa! Speak for yourself! I was never a noob! I came out of the whom kicking a$$!!! Lol. Definitely j/k!
[Nexus 5 Original Android Development] tigerxchaos:
Hey guys. I have an ongoing problem with DTMF (touch tones) in multiple versions of SlimKat on my Nexus 5 on T-Mobile.

When dialing in to any sort of auto-attendant on a phone call, most of the time they will not recognize touch tones sent from my keypad.

The tones are playing loud and clear when I press the buttons, but aren't heard on the other end.

I've only gotten this to work a couple of times since starting to use SlimKat on the N5.

A Google search hasn't yielded much except that other people over on the Galaxy S3 and S4 forums reported the same issue months ago, but didn't seem to get any resolution from it. http://forum.slimroms.net/topic/778-rom-442-slimkat-i9300-stable-weeklies/page-9

I'm on build 6.6 5728. I'll try updating to build 7 tonight but it sounds like this may still be a problem, especially since I've encountered the issue despite a recent clean wipe/reinstall.

Any help would be appreciated as my phone use is crippled with how common auto-attendants are these days.

Thanks everyone.
[Nexus 5 Original Android Development] DrunkFuX666:
Guys every time I try to turn on a portable hotspot, it says error. Anyone have the same problem or know the solution...?

Sent from my Nexus 5
[Nexus 5 Original Android Development] chikimonke:
What carrier and APN are you using? I believe it's a known issue on T-Mo that if you use the IPv6 APN, hotspot does not work. Standard LTE APN works not problem.
[Nexus 5 Original Android Development] Tylog:
Ok guys, weekly 7.2 on the way

Builds are up in the next hours. Check the Download page.

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/611-weekly

It's summer, holiday time and a lot of us are on vacation.

Weekly 7.2

Features:

InCallUI: fix blue call button background on some devices

SlimIRC update

Slimrecents: background color && transparency

frameworks/base updates aosp caf

frameworks/av updates aosp caf

display-caf-new updates

display-caf-new updates

external_chromium_org_third_party_openssl updates

more translations

Devices:

htc_msm8660 Kernel updates

clock-8x60 : Remove MDP clock freqs not used in original panel driver

pyramid updates

Fix USB tether, Increase volume level

oppo_msm8974-common updates

msm8974: Move loc_api files here , msm8974-common: Increase volume for voice paths

kernel exynos5410 updates

Revert "Revert "[media] fimc: Move camera file paths to sane location""

d2lte updates

The in-call volume is rather too low. This is applicable for across all cM based Roms. A little boost will go a long way to correct this. Credit XDA user kaos420, More of the Kernel Tweaking to improve Network and Performance.

jflte updates

Update to stable/cm-11.0 kernel for now..

i9500 updates

Remove deprecated defines,Move camera ID file to sane location,Set correct pixel format for recovery,enable eject sdcard, i9500: Add audio.r_submix.default for casting

p51xx/p31xx updates

Add audio.r_submix.default for casting

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Circaflex:
There is a folder you need to delete search this thread for hotspot and you'll find it
[Nexus 5 Original Android Development] DrunkFuX666:
Yea I'm in tMo but I'm not being able to use it with any APN... Keep getting the error...

Sent from my Nexus 5
[Nexus 5 Original Android Development] chikimonke:
Ah yes, that's right, here's one post telling you the folder http://goo.gl/mBORtQ
[Nexus 5 Original Android Development] Flamehell:
Tnx mate!!!!!:good::good:
[Nexus 5 Original Android Development] aow1980:
New build version and it won't build. I think the slim team is messing with us.
[Nexus 5 Original Android Development] nooktablet:
how do I check if it's building or not?
[Nexus 5 Original Android Development] aow1980:
A few of us who do personal builds have a problem with it stopping the build due to errors.
[Nexus 5 Original Android Development] akaHardison:
Got a problem long time ago.RIght now it still very inconvenience for me.When I first time open the dialer and want to open the keyboard.When I touch the keyboard button.it just show nothing.I need to go back again than open it again.It is very inconvenience.Is there someone knows why?I have already clean the data and cache.
[Nexus 5 Original Android Development] hooliganx:
increase

settings / developer options / animator scale

reboot and test

n5sk7.0.Robbie-08.08gapps.199art

Uber4.9.2-08.11twrp2.7.1.0rd2.08

----------------------------------------------------------------------------

have doubts about Slim? click here:

http://slimroms.net/index.php/faq
[Nexus 5 Original Android Development] JaylanPHNX:
Exactly, you can't have animator scale set to zero.

From my Tab Pro 8.4
[Nexus 5 Original Android Development] Schnadam:
Is there a particular video setting to use to send MMS to other people... Tried multiple setting... Says file size is too big... Turned on the 30,sec MMS setting as well. Any help would be appreciated.. Using stable 7.0
[Nexus 5 Original Android Development] htpc_punk_monkey:
You better rephrase that Hooligan, a certain Mr# may misunderstand and get his feelers hurt. ;)
[Nexus 5 Original Android Development] chikimonke:
Not necessary, it's over and done with, let's move on please.
[Nexus 5 Original Android Development] theesotericone:
Give me a few and I'll repo sync and see what happens on my end. How far into the build is it failing?
[Nexus 5 Original Android Development] Andromendous:
Im getting the errors also, I dunno how far, ill try to post a screenie in a sec
[Nexus 5 Original Android Development] aow1980:
A few post back someone posted the error message. I can't remember it off the top of my head. It has to do with ffmpeg.

Just cleaned the cache and did another sync. See how far this one goes.

this is the error i get

In member function 'android::sp<android::MetaData> android::FFmpegExtractor::setAudioFormat(AVStream*)':

external/stagefright-plugins/libstagefright/FFmpegExtractor/FFmpegExtractor.cpp:498:24: error: 'kKeySampleBits' was not declared in this scope

make: *** [/home/aow1980/Slim/out/target/product/hammerhead/obj/SHARED_LIBRARIES/libFFmpegExtractor_intermediates/FFmpegExtractor.o] Error 1

make: *** Waiting for unfinished jobs....

make: *** wait: No child processes. Stop.
[Nexus 5 Original Android Development] efan3719:
How are you trying to send the video? From Hangouts if I click the attach button and select rake video I can record a video and then attach it without issue.
[Nexus 5 Original Android Development] pkelly517:
repo sync && make clean

Then build away. I'll be damned if I know which commit fixes the ffmpeg issue we were seeing earlier, but it's all gone.

I guess the key was to have Jenkins start building. Sneaky little butler.

edit: Seems the make clean just moved the error to much later in the build. Still got problems with ffmpeg. And it happened right after I called Jenkins sneaky...

Coincidence? :)
[Nexus 5 Original Android Development] theesotericone:
Yep. I always make clean then repo sync and it's been building fine for the past 15 minutes or so. That said I have a spinning hardrive so my builds tend to take about three hours. Guess I know what I'm doing after dinner.:cool:
[Nexus 5 Original Android Development] aow1980:
I'm still getting the same error. I'll keep trying till I figure this out
[Nexus 5 Original Android Development] Garrykd:
You need to revert a commit to get it to build. The team is aware of the problem and it should be addressed soon.....Jenkins will be upset otherwise;):D
[Nexus 5 Original Android Development] aow1980:
I just shut the system down for awhile. Will work on it more tomorrow.
[Nexus 5 Original Android Development] pkelly517:
I figured as much. No 7.2 for the masses tonight.

Thanks for the update.
[Nexus 5 Original Android Development] Schnadam:
Hangouts won't even let me attach a video... Just says take pic and attach pic... And location.
[Nexus 5 Original Android Development] Garrykd:
...and it's fixed.:D
[Nexus 5 Original Android Development] efan3719:
i would try a clean flash of Slim and see if you can do it. That definitely isn't right.
[Nexus 5 Original Android Development] Schnadam:
Is the default SMS app the "MMS" app... Or hangouts? Can't remember if I downloaded it or if it was baked into the rom
[Nexus 5 Original Android Development] theesotericone:
Damn you people and your fast builds. Mine finally errorred out after 30 minutes. lol
[Nexus 5 Original Android Development] efan3719:
I think MMS is. Hangouts is in Gapps I believe.
[Nexus 5 Original Android Development] Schnadam:
Okay I have both... Just can't figure this out
[Nexus 5 Original Android Development] efan3719:
Try a clean flash to rule out any changes you may have made.
[Nexus 5 Original Android Development] Andromendous:
Hangouts is what replaced google talk, a few months ago it was updated with a feature that allows you to use it as your default text app also. The mms app is just the aosp sms app. If you dont use hangouts, then i see no point in using it. Unless you just like the look and feel... The choice is yours my friend
[Nexus 5 Original Android Development] Jonnyredcorn:
There has been waayyy too many posts since Stable 7.0 was released for me to go through and see if these bugs has been posted...but I'll just give a quick run-down of what I've noticed so far.

The proximity sensor doesn't seem to recognize when I put my phone to my face during a call or take it away(not so sure about taking it away but putting it up to my face screen stays on).

I get a random reboot now and then when processing a HDR+ photo or Lens Blur photo but I am on Faux's kernel so I suppose that isn't your guys problem.

I'm getting way worse battery drain...again...dunno if it's a kernel thing but I'm comparing two different slim builds with the same faux kernel. Haven't messed around too much yet as I just got a LG G3 which is a nice phone, but I'm going with a Galaxy S5 instead(which I'll probably sell when the Nexus 6 comes out, or something else that this Nexus 5 slimROM community moves too....I seriously LOVE this thread).

Here is a OT story if anyone is interested in how I came about a LG G3.

I had upgraded to a Galaxy S5 back when it first came out because of the camera and the IP67 water proofing was nice, but my Nexus 5 was still new to me and I had just discovered SlimKat and the revamped Google Camera came out and my Nexus 5 out preformed the Galaxy S5 in real world use. I had AT&T's insurance, and I activated my GS5 and played with it a while, but I switched my IMEI in AT&T's system back to my Nexus 5. Well July 31 I dropped my Galaxy S5 in the lake(I was using my Nexus 5 as a phone, but taking pictures and video with my Galaxy S5), and while yes it's water resistant I didn't have a dive suit to dive 40-50ft to grab it. I reported it lost, but since I hadn't been using it as a phone and AT&T's system showed me as using a Nexus 5 Asurion denied my claim. Well I called AT&T and *****ed, and since we have been customers for so long, have AT&T U-Verse and most importantly PAY MY BILL ON TIME, AT&T offered to give me a choice of a new phone for the 2 year contract price WITHOUT renewing my contract! I chose the G3, it's a great phone, lots of cool features that are actually useful especially the knock codes...the camera was soso, I personally think the G2 took better quality photo's and videos, but damn did it focus fast. And yes the screen is AMAZING, however it is also it's bottleneck. It's very hard to see, nearly impossible outside at full brightness, AND some app's I use are not yet compatible with a UHD display, so I would get app's not working properly. So I am going back to the GS5, however I'm gonna sell my AT&T GS5 and get a model that will let me unlock the bootloader...just gotta find out which ones have the right bands for proper LTE and HSPA+ in my area.
[Nexus 5 Original Android Development] DroidIt!:
Well, out of all those issues the only one I've personally experienced is the proximity sensor getting goofy during call with the phone next to my cheekie. Seems if I rotate the phone by one millionth of a degree the screen kicks on.....otherwise, no problemos :)
[Nexus 5 Original Android Development] gamerZ1:
Does Franco Kernel work with this ROM?
[Nexus 5 Original Android Development] akaHardison:
such like cm.cm is based on caf which has more things tweaked

---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------

ok.Problem solved.But why I can't disabled animator?I don't like it
[Nexus 5 Original Android Development] Tylog:
Rom Aosp / Franco Aosp = yes

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Hopper8:
Because of that bug you can't disable them completely. Try 0.25x though, you won't get the dialpad disappearing and you'll still get almost no animation.

Sent from my Nexu5