yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Yank555:
I'd cleanflash tbh ;)

And no Slim stuff in atm. We're at early bringup...

JP.
[Nexus 5 Original Android Development] Yank555:
None, it's a bringup, so that means it stock Android in Slim repos, the base to start working on Slim6.

It actually only has the bootanimation, I think that's the only change. But it's not AOSP based, it's CAF based, hence it took a tad longer than AOSP based ROMs.

JP.
[Nexus 5 Original Android Development] ddarshan:
Thanks, I will wait for the fully featured Slim 6.
[Nexus 5 Original Android Development] preusstang:
So Slim is CAF based now? Is LP as well? Also, do we need to install the CAF version of TRWP? Thanks.
[Nexus 5 Original Android Development] teemo:
Does that mean that non-CAF devices are a no-go? Out in the dark. Forgotten. :banghead:
[Nexus 5 Original Android Development] Yank555:
Nope, only that there is a common base for all devices, hence Nexus devices aren't up much sooner than other devices as the base needs to be ready, but still enjoy the best possible support due to AOSP device tree / kernel availability, hence when they're up they should be more or less hassle-free (basic stuff all working).

5.1.x and onwards is single source based for all devices (caf). so 5.0.x was the last version to have caf / non-caf branches.

Device tree and kernel are AOSP based and (will) stay as close to AOSP as possible.

As for TWRP, nothing special needed, I still run an older TWRP just fine.

What does caf TWRP have that non-caf hasn't ? Didn't even know of the caf version's existance tbh ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] dokie80:
Cleaned flash, boot, reboot to recovery, restore back to 5.1 :D

Everything is too big! . I'll wait for the clothed version.. Sorry for not testing it out longer :(
[Nexus 5 Original Android Development] Chitown021:
Holy crap, an MM alpha build?! I'll give it a go very soon!
[Nexus 5 Original Android Development] Yank555:
That is default HH dpi lol

But I hate it, too :D

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] dokie80:
Yeah. Got used with custom dpi. Dunno if this is bad or not. Lol.

Still using slimLP boot animation, No mm boot animation? At glance, I don't see many difference on UI compare with lollipop. Not really exciting :D
[Nexus 5 Original Android Development] VictorLapin:
And if you look further, you will miss many SlimLP features as well :D
[Nexus 5 Original Android Development] dokie80:
No doubt! Darn. What have I got into... Somebody should start slim rehab for this.
[Nexus 5 Original Android Development] Yank555:
I think animation is not definitive ;)

MM isn't a visual revolution lile LP was.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] Yank555:
DM Build Update

Nothing major, just a repo sync to 0.12.

This is a DM build, so 100% pure SlimLP sources.

Download Link : Slim-hammerhead-5.1.1.beta.0.12-DM-20151112-2054.zip

JP.

PS: Personal build update probably coming tomorrow, too late tonight to merge the additional stuff and finish all devices.
[Nexus 5 Original Android Development] TJKV:
Hey yank, I have a question about the 6.0 bring up process. So I'm only familiar with how things were done with Kitkat and earlier on Slim. Back then the AOSP codebase for Nexus devices was pretty much as stable as one can get on AOSP. The slim devs just added additional enhancements to the build process, and then some extra code to various repos to support more devices, then slim features etc. But the base code, and thus core functionality, was assumed to be as good as Stock for Nexus, with the additions just enhancing it further. (Discounting the occasional AOSP bug, Stock OS bug, device tree/kernel bug due to code added or removed by DM etc)

Now with a new process of using additional caf code even for the Nexus, how much additional work is needed to ensure the code quality remains as good as (or close to) Stock or AOSP quality for the Nexus devices? Put another way, will there be an initial period of uncertainty where some core functionality may be buggy or broken even on Nexus devices, unlike earlier?
[Nexus 5 Original Android Development] Yank555:
I would say you have more or less explained the process, and its inherent additional work / risk. I wouldn't say there is more effort than there was before for Slim as a whole, only that Nexus devices tag along non Nexus devices on the ROM side. The device/kernel/vendor repos work is certainly way less effort on Nexus than other devices and as such more or less similar to what is was before, too. Only bringup on Nexus will not really be sooner than other devices (due to ROM needing to be ready) would be the major drawback I can see so far compared to the pure AOSP base.

Basically the idea is to only have to handle one code base for all devices, which is less effort to maintain as certain enhancements were "hard" to port / keep at the same level between AOSP and CAF bases.

I was also happier with the CAF / non-CAF segmentation we had until 5.0.x being on the Nexus side of things myself ... but I have to agree this way just makes for a lot less fuss to maintain and that's a non marginal benefit.

So far 5.1.x hasn't proven to have been any less than prior versions, so I tend to accept (even as an AOSP-lover :D) that the benefit is bigger than the drawbacks.

Esp. that I tend to keep my daily on the previous version until all "my" mininal enhancement requirements are met anyway ;)

JP.
[Nexus 5 Original Android Development] TJKV:
Okay so to be clear, the only drawback would be the longer time to get builds out (which is no problem personally, I'm trying out stock MM at the moment). More importantly, the "caffing" of the codebase doesn't affect the quality of the Nexus builds negatively, correct? That is what I meant to ask :p

I haven't dived into caf's codebase, neither have I used a device that used caf branches (slim or cm or any other) earlier. Hence am not aware of the quality of caf's code. So you could say that I was asking you if their code is as high quality as AOSP and slim's earlier non-caf branches :)
[Nexus 5 Original Android Development] pGuerrerox:
I want to know if this ROM have one feature:

when locked using a pin, does the numbers come out on random positions?

Thats like the best security feature EVER, I am still using SLIM 4.4.4 just for that feature...

thanks
[Nexus 5 Original Android Development] Yank555:
Yep, that's a option in security settings you can enable/disable at will.

JP.
[Nexus 5 Original Android Development] Yank555:
Let me put it this way, using a (partly) different code base than AOSP can be better or worse than using AOSP, anything is possible since it's different...

To judge the "quality of caf code", use any SlimLP 5.1.x build as benchmark, 5.1.x has already been this way since day 1, this isn't new to Slim6 ;)

JP.
[Nexus 5 Original Android Development] pGuerrerox:
Awsome!

Thanks for the reply and info!
[Nexus 5 Original Android Development] TJKV:
Ah okay, so nothing clear cut. Well alright then, looking forward to using Slim6 whenever it may be :)
[Nexus 5 Original Android Development] Yank555:
Slim6 Bringup - Second public alpha

Repo sync'ed yesterday, Security patch level at 11/2015, (for builders) compiles as is on clean repo sync.

You'll still get a TimeService FC on boot, and dialer settings will FC.

If you see anything else not working, please let me know here, if possible post a log and how to reproduce.

Note : I'm using [MENTION=1277872]dankoman[/MENTION] 's 1113 gapps.

Slim-hammerhead-6.0.alpha.0.1-UNOFFICIAL-20151115-1647.zip

JP.
[Nexus 5 Original Android Development] ddarshan:
Does this release has any customizations/features or still stock??
[Nexus 5 Original Android Development] Yank555:
Still stock, focus is on device bringup for now, features will be added later, shouldn't be too long I suppose.

JP.
[Nexus 5 Original Android Development] acultr:
multirom support?
[Nexus 5 Original Android Development] Yank555:
Stock kernel should, yes.

But feedback welcome ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] acultr:
I wanted to secondary Rom
[Nexus 5 Original Android Development] Yank555:
No idea, never uses multi-rom, all I know is kexec is needed in kernel, that's in...

Anyone else can help ??

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] Spectrum75:
For Multirom i think you need this. ;)

( For Secondary installation, as Primary there is no problem )
[Nexus 5 Original Android Development] Yank555:
This won't go into Slim I suppose ... so best would be to remove the post install verification from the update_script manually if you want to use the ROM as a second ROM.

JP.
[Nexus 5 Original Android Development] Yank555:
Slim6 Bringup - alpha Update

Dialer FC is fixed.

You'll still get a TimeService FC on boot.

If you see anything else not working, please let me know here, if possible post a log and how to reproduce.

Note : I'm using [MENTION=1277872]dankoman[/MENTION] 's 1113 gapps.

Slim-hammerhead-6.0.alpha.0.1-UNOFFICIAL-20151116-2150.zip

JP.
[Nexus 5 Original Android Development] pkelly517:
JP,

Could I create the same build with a repo sync and brunch? In other words, are all the commits merged?
[Nexus 5 Original Android Development] Yank555:
Almost, you'd only be missing one, the dialer settings FC fix :

https://review.slimroms.org/11498

JP.

PS: I last sync'ed on saturday I think.
[Nexus 5 Original Android Development] Garrykd:
Since you asked....:D

Video recording is broken (can't connect to camera message) - I've fixed this in my build :D

Sensors are broken so rotation, compass, auto brightness, etc. don't work (maybe blobs?)

I've also got double tap to sleep and slim recents working on my build, but not without some weirdness:p
[Nexus 5 Original Android Development] Yank555:
Yup ;) Thanx for testing AND feedback :D

Can you point me to the fix, will save me time ;)

Rotation ? Oh ... I though that was working fine on HH on my end ?? Need to retest then. On shamu it was a commit in the device repo ... will have a look likely on thursday (tonight some SlimLP stuff to attend to), but indeed device repo for HH isn't completed yet, have been working on shamu yesterday, plan to get back to HH on thursday.

I'll leave those out for the moment, want to focus on device-tree only atm ;)

JP.
[Nexus 5 Original Android Development] Garrykd:
http://review.cyanogenmod.org/#/c/116273/

http://review.cyanogenmod.org/#/c/117694/

http://review.cyanogenmod.org/#/c/118148/

Might be one, two, or all three of those :D I picked all three.

I'll see what I can dig up too (trying different blobs atm)

:D
[Nexus 5 Original Android Development] Yank555:
SlimLP 5.1.1 Testbuild

This test build contains SMS/MMS fixes by [MENTION=3877985]prbassplayer[/MENTION] which should make stock messaging app work correctly.

I'd be very happy if those still running SlimLP could flash this build and report back.

The build is a 1:1 copy of my latest personal build with the SMS/MMS fixes added.

Slim-hammerhead-5.1.1.beta.0.12-DM-DEV-20151117-2033.zip

Thanx, JP.
[Nexus 5 Original Android Development] Garrykd:
Ha! I used your commit from shamu on hammerhead and it worked!!

Sensors now working :D
[Nexus 5 Original Android Development] prbassplayer:
Technically it doesn't contain a single sms/mms change its all telephony related [emoji14]
[Nexus 5 Original Android Development] Yank555:
Seriously ??? Wow, wouldn't have tried that ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] lightingcloud:
sorry, I'm seeing this just now... tomorrow night I'll have some time, but it's not like I'm having problems with SMS at all and I think no one used MMS in Italy in the last 5 years or so. :P
[Nexus 5 Original Android Development] pGuerrerox:
hey, I downloaded and flashed SlimLP 5.1.1, awsome ROM so far, feels snapy.....

but I have one question, the DPI is set to 400, the thing is that it only affects the google apps,, other apps are not affected, is there an option to make the DPI work on all apps??

thanks!
[Nexus 5 Original Android Development] formicae:
Whatever it was, thank you. I had weird MMS problems where I could send/receive pictures within 10-15 minutes of booting, after which, failure in either direction. Spent ages messing with APN settings, even though I was sure they were fine (they were). Seems to be fixed now, have been sending people pictures of my cat for an hour. :D

ps: he has a lot of thumbs

pps: mutants need love too
[Nexus 5 Original Android Development] t0mas_:
I'm sorry to report this but for me mms still doesn't work. it even got worse with this build, for incoming mms I don't even get a notification/can't receive even in 3rd party apps, which works fine in your previous build
[Nexus 5 Original Android Development] Yank555:
Hmm ... not gonna be easy to catch that one I suppose :silly:

Hard to validate on my end, I don't use MMS much, either it's SMS or email here with my contacts ...

JP.
[Nexus 5 Original Android Development] Yank555:
Can you provide logcats ?

Thx, JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] TJKV:
If you've just done a clean flash, then change the DPI to something else and then change back to 400. That should set right any inconsistencies.
[Nexus 5 Original Android Development] pGuerrerox:
Thanks, i tweak around a bit and did something similar to your recommendation, but there is ones app that doesn't change no matter what.

The app is INGRESS. All the other have adjusted to the DPI but this one doesn't.

No idea what else to do.
[Nexus 5 Original Android Development] t0mas_:
sorry for late reply, but here are the logcats. obviously there was also some derp with my carrier when i tested this (a day before?) yesterday, so discard the part where i was saying it got worse with the patches. the logcats attached are 1 while sending (gets stuck at sending end never sends) and 2 while recieving (fails to dl mms without error msg).

thanks, have a nice day
[Nexus 5 Original Android Development] Yank555:
I can't see any attachments ;)

JP.
[Nexus 5 Original Android Development] Yank555:
Slim6 Bringup - alpha Update - first official DM build

Sensors fixed (rotation, autobrightness...), video encoding fixed (filming works).

You'll still get a TimeService FC on boot.

If you see anything else not working, please let me know here, if possible post a log and how to reproduce.

Note : I'm using [MENTION=1277872]dankoman[/MENTION] 's 1113 gapps.

Slim-hammerhead-6.0.alpha.0.1-DM-20151119.zip

JP.
[Nexus 5 Original Android Development] amphi66:
Looks good for as far as developed, JP.
[Nexus 5 Original Android Development] TJKV:
Oh yes, Ingress is borked. It used to be fine earlier, but one of Niantic's bigger updates about half a year ago screwed it up.
[Nexus 5 Original Android Development] pGuerrerox:
That sucks, i hate this big interfaces,

I hace also notice that clash of clans is behaving in the same manner as Ingress... I don't want to back to KitKat but next week I will do it to test if it is the games or the rom!
[Nexus 5 Original Android Development] formicae:
Looks like I spoke too soon about that 5.1.1 build fixing my MMS problems. :( Result now is when I click send, nothing happens. Message editing bubble disappears, nothing appears in conversation. If I send using ChompSMS, progress bar zooms left to right at lightning speed as if it's doing something, but nothing gets sent.

It still works for a random time from a fresh boot, can be ten minutes or two hours. Very bizarre.
[Nexus 5 Original Android Development] TJKV:
I don't have any problem on COC, just Ingress.

Either way don't go backwards, go forwards to Marshmallow. I'm currently on Stock MM with 400 DPI, no issues with COC. I doubt Slim6 will have any issues with it either.
[Nexus 5 Original Android Development] Yank555:
Can you post a logcat taken while you try sending and it doesn't work ?

Thanx, JP.
[Nexus 5 Original Android Development] t0mas_:
thats because ia obviulsy forgot to attach them, sorry :angel:

here they are (i hope:P)
[Nexus 5 Original Android Development] formicae:
Sure thing, chief. I've attached two, one using stock, one using ChompSMS. Thanks for taking a look.
[Nexus 5 Original Android Development] amphi66:
Just a thought: have you verified the APN Type listing under APN Settings? I was having MMS issues and it was simply the ORDER of the items. default,fota,mms,supl,hipri workes while default,mms,supl,fota,hipri did not!

Unless, of course, simply retyping them corrected some error in the telephony db ???
[Nexus 5 Original Android Development] formicae:
I've tried, though I haven't tried every permutation. I'm just using 'default,mms' right now anyway, research strongly suggested that anything else is useless these days.

Also how would that explain that MMS works for a while after I boot? Like the carrier finally notices the order of my APN settings and says 'wait a second, you shouldn't be able to do this?' :)
[Nexus 5 Original Android Development] amphi66:
Lots of questions . .. .. . Glad these phones aren't airplanes or we would be ducking a lot!

One other thought: is your active APN the ONLY one in the list? If there are others, delete them then reboot.
[Nexus 5 Original Android Development] formicae:
It isn't anymore, though I went through that one and will be deleting the extra one anyway. Steps I've followed so far, APN-wise:

Clean install, whole pile of APNs.

Delete all but the one I needed.

Delete the one I used, re-add it manually using carrier's instructions.

Add my carrier's separate tethering-specific APN (even though I don't use it)

Same results each time, reboots in between, then cache wipes for good measure when I was getting desperate. I really tried to rule out the APN being the problem.
[Nexus 5 Original Android Development] wangdaning:
Not going on about MM as I have been on LP only for a few months. I flashed the latest, and it is awesome as always. A few things to note:

1. if you are using a kernel that is not slim

2. if you are using xposed for whatever reason

Make sure you nandroid. A restore of boot gets you back, I use EX and have for a while, so like to keep it.

Second, I use xposed for xprivacy and gravity box, I know I know. I have my settings all set up on xprivacy, so privacy guard will take me time to set up. I use gravity box for rotations and lockscreen stuff. Slim has most of what I enjoy, but a few other bits I am used to are not in Slim and I haven't gotten around to building as I have been studying.

Gravity box works with Slim, but be careful, it will initially disable the navbar. You need to get into GB and go to nav settings and enable navigation bar. Second, do not enable anything you cannot do through settings.

ROM is awesome, and even without this I loved it. Thank you [MENTION=2033478]Yank555[/MENTION] for sticking with us on the N5
[Nexus 5 Original Android Development] KingDani1997:
Hey guys,

I have compiled mm aosp r26 and it does boot, but i can't flash it as secondary rom using MultiRom. I am getting this error: "error executing updater binary" while flahing.

So do I have to add/change something to make it Multirom compatible?

Thanks in advance.

(sorry for spamming this thread with Slim unrelated stuff, but people are so friendly here, that i can't resist to ask my questions here :D)
[Nexus 5 Original Android Development] Phazmos:
Post #325
[Nexus 5 Original Android Development] acultr:
I have a other way.

first make a backup your internal rom.

install mm rom to primary.

make a backup.

go to recovery

advanced - multirom-add rom-backup.

so you can add the backup your MM rom to secondary.

restore your original rom was you first backed up. ?
[Nexus 5 Original Android Development] malek_anas_97:
Clean Flashed slim6 yesterday with slim gapps, everything was running smoothly till about 10 minutes ago, it started lagging alot, rebooted my phone and now everything's back to normal :/

Isn't this a bug that was on SlimLP before ?

+

About root, the marshmallow builds don't have root built in (at least i didn't find it when i looked around in usual places) should we flash supersu zip or is there something I'm missing ?

Thanks in advance ☺
[Nexus 5 Original Android Development] Yank555:
Did you run into the lags using stock kernel ?

Am testing a few things atm with the kernel ... don't know about whether it'll avoid that lagging after longer uptime. But since it needs long uptime to validate this, this will take a tad.

As for su, no built in indeed, and I don't think SuperSU will work, as SuperSU needs SELinux stuff, which I don't have the details of nor have had the time to analyse this manually so far.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.

EDIT: Just found what's likely needed for SuperSU support, compiling, but it's midnight, so heading to bed, work tomorrow. Will test the ROM tomorrow morning before going to work and let you know.
[Nexus 5 Original Android Development] Yank555:
Slim6 Bringup - alpha Update - DM build

SuperSU support added ! Please use Chainfire's beta 2.52.

I suppose you'll still get a TimeService FC on boot (didn't check).

If you see anything else not working, please let me know here, if possible post a log and how to reproduce.

Note : I'm using [MENTION=1277872]dankoman[/MENTION] 's 1121 gapps.

Slim-hammerhead-6.0.alpha.0.1-DM-20151123.zip

JP.

PS: Now really time to get some sleep :angel:
[Nexus 5 Original Android Development] Yank555:
Just a quicky ... to anyone having a Chomecast ...

Couly you test casting your screen (not a Chromecast app, but mirroring your screen on your TV) ?

It's been reported to instantly reboot on shamu, and I'd like to know if the issue is shamu specific, device/kernel related, or more generic and rather ROM related.

Thanx, JP.
[Nexus 5 Original Android Development] malek_anas_97:
Installed the latest build and so far everything is fine, the TimeService Force close persists

About root, did you mean the systemless root ? which one you're referring to cuz i want root and I'll flash and test whether it's gonna work or not

+

About my previous post

Yes, everything was stock
[Nexus 5 Original Android Development] Yank555:
Standard SuperSU : https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] SnZ:
[CRASH] SlimRecents (4.4.4)

Hi [MENTION=2033478]Yank555[/MENTION],

I have question related to SlimKat 4.4.4 which I still use as daily rom. Last times I'm getting a lot of "com.android.systemui" crashes after trying to use SlimRecents menu. Can you help me with this? Is there any fix or some commit which i can cherry pick and rebuild ROM?

Crashlog below... :( :fingers-crossed:
[Nexus 5 Original Android Development] Yank555:
Good question, I've only started looking at ROM stuff since SlimLP 5.x, but I haven't run into and issue with SlimRecents yet.

Did this start after a certain build, or after running the same build over longer time ?

Maybe verify if this also happens on a clean system.

JP.
[Nexus 5 Original Android Development] malek_anas_97:
Root Works \*0*/ [MENTION=2033478]Yank555[/MENTION]
[Nexus 5 Original Android Development] SnZ:
This is after latest 4.4.4 official build. Clean system with few apps installed. I found something which may be related to this http://xdaforums.com/showpost.php?p=62292529&postcount=1232 but except that no luck of finding some fixes i can cherry-pick :(
[Nexus 5 Original Android Development] Yank555:
We're on the bringup of 6.0, 5.1.x will get one final (and has been fully usable as daily as is for months), 5.0.x reached final and 4.4.4 as well.

So a fix for 4.4.4 ... very unlikely to put it optimistically ... unfortunately.

JP.