yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] peikojose:
Hi, I tried 06/24 and 06/26 and they didnt work with the latest ezios build! FYI [MENTION=2095315]ezio84[/MENTION]

I need youtube adway :(
[Android Builders Collective] diegocr:
If have multiple users only first user can access to navigation and advanced menu, other users can't modify hardware buttons :crying:
[Android Builders Collective] diegocr:
Now we have a post for chagallwifi SlimLP :good:

http://xdaforums.com/galaxy-tab-s/development/rom-ezio84-slimlp-t3146025

Thanks [MENTION=4222965]deadman96385[/MENTION]
[Android Builders Collective] Yank555:
Would be cool to have a logcat of the moment when playing music via bt generates a reboot...

I'd consider the 3rd and 4th as potential candidate from a quick look, would need to check if the 3rd has a memleak potential... which could explain why it only work for so long before crashing, but seeing a logcat certainly would help a lot not only to pinpoint the commit, but also to fix it ;)

Whoever has this, please grab us a logcat ;)

JP.
[Android Builders Collective] ezio84:
I removed the stock browser also for that reason, some websites aren't loaded well by it. Its development seems stopped.

I like the actual Chrome.

I also reverted the 4th commit but I'm quite sure it was not involved in the problem, instead it should give a better compatibility with some car audio system.

Afaik Garry built it from slim source, so it should be updated at yesterday.

Xposed devs are updating the app to the new ART stuff just these days, so wait for a new beta by them. On my side, I'll stick with the actual ART commits because they seem working like a charm [emoji14]

Yes it's a know issue, slim devs are aware of it. I hope it will be fixed soon ;)
[Android Builders Collective] Mikulec:
I downloaded it 16 minutes before your post and also saw a 0 downloads.
[Android Builders Collective] :
On a PC??? I got Steam to refund mine. Not touching that thing ever again. Back to TW3 it is.
[Android Builders Collective] peikojose:
Hey, about xposed so you use a line called art everything or something like that in build.prop?
[Android Builders Collective] ifwillems:
If a have time this afternoon or evening I will produce a logcat. Need to first reinstall a 0624 or 0627 version; then read up on how to take a logcat (in the car!). Have never taken a logcat.

By the way: now using the 0628 version from [MENTION=2640853]Garrykd[/MENTION], and no issues any longer with streaming music. Great!
[Android Builders Collective] Yank555:
Oh yes ... hmm ... best would be while connected to a PC, cause using an app will make you lose the logcat due to the reboot.

JP.
[Android Builders Collective] ifwillems:
[MENTION=4911350]RobbieL811[/MENTION], [MENTION=2640853]Garrykd[/MENTION], [MENTION=2033478]Yank555[/MENTION] and [MENTION=2095315]ezio84[/MENTION], for at least two weeks now something else is broken on all your ROMs: Trusted Face stops working after a while. When I go into settings and try to improve Trusted Face, the camera function doesn't execute. So that's the reason why Trusted Face doesn't work. After a reboot everything is fine, for a while, then it is broken again.

By the way: the vast majority of functionality in your ROMs works great ! Thank you.

---------- Post added at 07:43 AM ---------- Previous post was at 07:41 AM ----------

No worries, I'll figure it out.
[Android Builders Collective] theesotericone:
PS4. I was reading up on the PC issues. Honestly, your not missing much. It's a good game but not game of the year material. :cool:

TW3 was about as good as I've seen in a while. Though in a few months Fallout 4 should be something special.
[Android Builders Collective] ifwillems:
Here is a logcat. Hopefully it is useful.
[Android Builders Collective] angelcalibur:
New build 20150628 :

With stock (CM) kernel build with Uber Toolchain:

SlimLP-5.1.1-20150628-OPTIMIZED-jflte.zip

With Alucard kernel (with last source, compile by me) :

SlimLP-5.1.1-20150628-OPTIMIZED-ALU-jflte.zip

Changelog (thx to [MENTION=1228651]fusionjack[/MENTION]) :

Rom: Android 5.1.1 release 5

It is not completely r5 since some repos like frameworks/base and cm telephony are not yet updated to r5.

Kernel: Linux 3.4.108

Toolchain: Use an optimized Uber toolchain for cortex-a15 cpu variant

For builders who compile bacon, you don't need to do anything. For other devices which use gcc 4.9, you need to read this commit message.

DevelopmentSettings: Add toggle for captive portal check

Settings: Fix system icon size in draggable sorted list view (NavBar, SlimPie, GlobalMenu, etc)

InCallUI: Fix possible FC

SystemUI: Visualizer changes/improvements

Frameworks: Fixes and improvements

Chromium: Disable SSLv3

DHCP: Another dhcp fix

Visualizer: Add visualizer to lock screen

SecuritySettings: Allow lock screen visualizer to be disabled

DevelopmentSettings: Chamber of Secrets

See FAQ how to enable or use it. This is a dangerous feature, read carefully.

SlimShortcut: Add more actions and clean up

LayersBackup: Update URL

FFMPEG: Latest update from CM
[Android Builders Collective] amphi66:
[MENTION=2095315]ezio84[/MENTION]: Possible issue with 0628 build: no camera shutter sound, although activated in Sounds-Advanced.

Thank you, -Larry
[Android Builders Collective] AquilaDroid:
I have shutter sound on that build. What camera are you using? (I'm on Google camera 2.5.052)
[Android Builders Collective] ezio84:
Sorry, missed this post!

Slim gapps by dankoman (I prefer the "mini" package).

Yes! You can remove it if that's incompatible with xposed. Then just wipe caches and reboot again.

It works here (with playstore Google camera) ;)

---------- Post added at 08:10 PM ---------- Previous post was at 08:08 PM ----------

Ye I faced the same with a lot of builds, also no slim. But I haven't tried with stock aosp, does it work here?
[Android Builders Collective] amphi66:
Same camera here.. .. .. Hmmmmmm?? Another setting elsewhere?

Edit: After reboot it is back (?) -- sort of a muffled bell now versus the previous "click".

---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------

After reboot it is back (?) -- sort of a muffled bell now versus the previous "click".
[Android Builders Collective] Yank555:
About the BT commits, I've spent last night on the global Headsup switch, haven't looked into the details, will not get to it before tomorrow evening (it's 8am now here)...

JP.
[Android Builders Collective] hooliganx:
Oi! [MENTION=2095315]ezio84[/MENTION] [emoji112][emoji4] ... just a comments...

about camera... flash... this things...

yesterday I used a flashlight in home, and, when pressed power button, light turn off. buuut, when I turn on screen, flashlight don't work anymore and camera too.

after restart, working. made a clean flash 3 days ago, not the last build. [emoji15]

working for you?

and yesterday I miss one good feature.. [emoji4]

a quick reminder in statusbar [emoji6] any plans for this, or not?

thanks for your work and attention man

[emoji1][emoji111]

n5slim.ezio84.jun.24layeredslim.gapps.jun.20

elementalx.4.02rd.2.26v4a.2.3.4twrp2.8.7.1

-------------------------------------------------------
[Android Builders Collective] ezio84:
Flashlight and camera services are kinda crappy, sometimes they behave in a strange way like that. It happened on my side too :D

I used to enable the status bar reminder (i don't remember if it's made by Juba or Kufi), but nowadays with the Keep reminder is less usefull i think.
[Android Builders Collective] Yank555:
I had that very same thing reported on flounder, so it seem to be a generic thing, I expect it's linked to the torch service, if this works correctly on stock Nexus ROMs (which I haven't tested).

JP.
[Android Builders Collective] india86:
This is a known issue in Lollipop and happens on Stock ROM as well...few links fyr

https://code.google.com/p/android/issues/detail?id=173537

http://www.androidpolice.com/2014/1...s-the-camera-and-flashlight-until-you-reboot/
[Android Builders Collective] Yank555:
Thanx for that, that means also, it's not linked to the systemwide torch service....

JP.
[Android Builders Collective] india86:
Went through some threads in XDA as per that prolong use of torch will heat up the sensor and then the sensor\device starts malfunctioning.

http://xdaforums.com/google-nexus-5/help/lollipop-torch-issue-t2942902/page2

I also faced this issue some time back then I stopped using tourch for long time ;)
[Android Builders Collective] dankoman:
now it's even better - snooze button in FAB style :D (also fixed the color - now it's material teal instead of that sea-green shade or whatever)

by the way it's merged into slim source now.
[Android Builders Collective] ezio84:
Thanks again mate :D

Also thanks to [MENTION=2033478]Yank555[/MENTION] and [MENTION=5790246]VictorLapin[/MENTION] for all the heads up improvements!
[Android Builders Collective] amphi66:
[MENTION=4375260]diegocr[/MENTION]: You sent me a PM re: SlimLP for picassowifi, but have your PM receipt turned off so you were not able to receive my reply. I am unable to compile, but very willing to test and can give you a more robust answer if your PM is on.

.

Thank you, --Larry
[Android Builders Collective] Real_Justus:
Hey Yank,

I hope you spend your holiday in a relaxing way - but glad to see you back anyway ?

I just flashed your latest build and I am having trouble with Hangouts. When I try to open a thread Hangouts FCs...

I installed Hangouts via the PlayStore (not with GApps). Anyone else having the same problems?

Best regards
[Android Builders Collective] Yank555:
Yeah was nice, and too short, as always :D

Hangouts works fine on my end (shamu), also installed from PlayStore. Which device do you have ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] geiswiz:
I'm not sure if this is a problem, but I noticed that after a while the minimum CPU frequency goes from 300000 to 960000. It starts out at 300000 at boot, but goes up to 960000 after like 50 or so hours uptime. I'm running Ezio's 6/24 build, but noticed it on his last build too. Is this normal?
[Android Builders Collective] randman2011:
I don't know if this is the same problem and I'm not on the same ROM as you, but I have had some problems with Hangouts as well. A specific message will cause the FC in a specific conversation. Now that we've sent some messages back and forth I can view the conversation on my phone again but if I scroll up to the problem message I get the FC again. That is a Hangouts issue, so I'd send some test messages from a computer to and then try the app again.
[Android Builders Collective] teemo:
Unfortunately this affect rtl languages as well. I have at least one such user (arabic).

Does anyone know if this is a priority of SlimRoms?

Here's the logcat with the crash .
[Android Builders Collective] Real_Justus:
I am on Shamu...

I will try this. But it is not a certain thread causing the FC. Just as soon I open a Thread, Hangouts closes.

Have a nice day.
[Android Builders Collective] Real_Justus:
EDIT: I redownloaded the ROM and reflashed. Now everything runs like a charme!

Thank you!
[Android Builders Collective] Yank555:
Hangouts fixed ? Or was it sth else ?

I've retested, works fine on my end, I have the latest installed (no PlayStore update available for me).

JP.
[Android Builders Collective] Real_Justus:
Right... I thought my answer was added to my previous post.

It is a bit strange. The checksum of both zips are OK... But to reflash the first downloaded file did not do the trick.

Anyway; thank you for your support.
[Android Builders Collective] peikojose:
Hey [MENTION=2095315]ezio84[/MENTION] tried to edit the build.prop in your build to delete the "art everything" line and I didn't find it,are you sure it is there?

Latest xposed alpha for 5.1 don't work yet!
[Android Builders Collective] 22sl22:
It's under the 'additional build properties'

Look one line up from build display ID. Just so you know, there is a reason why it's there, here is a short summary by [MENTION=1050103]sykopompos[/MENTION] :good:
[Android Builders Collective] Laggalot:
Look at the bottom of the screen and notice the softkeys not beeing centered... This is driving me nuts xD

Is this just my layers or ROM?
[Android Builders Collective] mslatter:
D850 update.

Lots of merges for the LG G3 from arcardinal deserved a new build:

RRO layers

SuperSU not included (flash instead)

Add alternate WebView provider package

Accidental Wake up OFF by default

Flip to Mute

Latest Kernel, G3 and D850 commits

1. Full Wipe (am told dirty flash works)

2. Flash Rom

3. Flash Gapps (I used Slim's 6/29 gapps from their XDA thread: http://tinyurl.com/pncj8jk )

4. Flash SuperSu

https://www.androidfilehost.com/?fid=24052804347767854

MD5: 018d45c3abfe2759d5294a2ef4941e94

Rebooted with power button twice, and wifi held fine. Rebooted with Quick Boot app, and had to enter wifi password. Related? Will have to test some more.

Changelog is all new merges since last build from this link:

https://review.slimroms.eu/#/q/status:merged

Huge thanks to the following for making all this possible:

Slim Team - for a great ROM

arcardinal - Slim device maintainer

ezio84 - RRO fixes (Layers rock)

X-san - commits help / time saving script!
[Android Builders Collective] 22sl22:
Probably layers related, try another layer otherwise it could be DPI or rom related.

Try another layers navbar (Be sure to clear the old one and any other conflicting ones) and its also worth checking if they are made for your device (Nexus 5 is XXHDPI). If that fails try reverting to stock and if it happens on stock too, go to dev options-show layout bounds to make sure everything is set in the right place for the navbar (see screenshot )
[Android Builders Collective] peikojose:
I removed these lines just for trying, flashed latest xposes zip, and got stuck in boot animation. So anyway it doesn't work.
[Android Builders Collective] rpr69:
Same experience here. Clean flash of latest Ezio, removed the two oat lines in build.prop, installed latest Exposed, boot loop.
[Android Builders Collective] kantjer:
Guys,

Need some help, I'm trying to add Westwood tcp congestion control to the Slimsaber stock kernel.

tcp_westwood.c is already present in the source, also is westwood included in Kconfig and the Makefile and I have activated westwood in the deconfig (CONFIG_TCP_CONG_WESTWOOD=y) but it still doesn't show as available.

Any tips what I'm missing.
[Android Builders Collective] Thecrazyskull:
Show me your kernel source
[Android Builders Collective] kantjer:
https://github.com/SlimSaber/kernel_oneplus_msm8974

the only thing not yet on the git is the deconfig (CONFIG_TCP_CONG_WESTWOOD=y) change
[Android Builders Collective] DroidIt!:
You show me your kernel source, I'll show you mine [emoji15] [emoji14]
[Android Builders Collective] kantjer:
You first [emoji13]
[Android Builders Collective] ezio84:
Quite busy these days so a fast heads up :angel:

About xposed: if you get a bootloop also after removing the dalvik lines in the build.prop (dalvik.vm.image-dex2oat-filter=everything and dalvik.vm.dex2oat-filter=everything), perhaps it's still not compatible with some ART commits i added to the rom.
[Android Builders Collective] JaylanPHNX:
Did you guys clear dalvik cache in recovery and reboot so it rebuilds cache before trying Xposed? Otherwise, you still had the cache that was built based on those lines.

From my SlimTab Pro 8.4
[Android Builders Collective] mslatter:
Noob question for building. Is there a list somewhere, or how do I go about finding how to enable / disable certain things in my build process, so the settings I want are already done after first boot. For example, if I want 24 hour clock (which we had but it went away), where do I find the setting/s to enable that during the build process. Hiding the battery, turning touch tone sounds off, turning lock screen off....that type of thing...

Any help / advice would be appreciated! Cheers, and happy 4th to all the Americans =)
[Android Builders Collective] rpr69:
This is exactly what I did:

- flashed clean latest ezio build in Multi-Rom (no kernel, no gapps, nothing except the ROM file)

- booted into ROM, installed TiBu, restored ROM Toolbox, edited build.prop and removed the two lines with 'oat' in them

- rebooted into ROM again to make sure it worked

- rebooted to recovery, installed latest 06/29 V65 Xposed by romracer, wiped dalvik and cache, rebooted

- boot loop
[Android Builders Collective] Yank555:
ROM Update

Tiny update again, includes :

- Global SlimHeadsup 3-way switch (Yank555.lu)

- Reverted the 4 suspicious bluetooth commits (for now, will dig deeper as I find time)

The bluetooth commits are in Slim base and reverting them fixes a hotreboot after listening to music for a longer period via BT connection.

As usual, ROM download links can be found in my OP in the Builders Collective, post 14.

JP.

PS: shamu is up, hammerhead uploading on both servers, flounder compiling, flo to be compiled.
[Android Builders Collective] luisangel89:
Thank you very much for the update. Everything is great but there's a small glitch with the Slim Launcher. I'm not sure if its already been addressed. Its the only thing keeping me away and staying with Nova. Its this gray bar in the bottom that shows up every time I press and hold the screen and then press the home button. Another thing is that even when i set the home screen to the middle when I press the home button it take me to the left screen.

Again thanks a lot guys! ;)
[Android Builders Collective] Yank555:
Can't comment as I use No a myself all the time...

Is this device specific or happening accross the devices ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] luisangel89:
I'm on hammerhead but other than the launcher, your build is great! Thank you!
[Android Builders Collective] cimdrap:
I'm on Ezio 28/06 and i suffering a great rilj Wakelock
[Android Builders Collective] DroidIt!:
Great what? Is it affecting battery? It is normal for you phone to acquire wakelocks, even if it looks like it might be large numbers of them. That's not necessarily abnormal behavior. Unless you see it affecting battery, I wouldn't worry about it. If it is affecting battery, can you see what service it belongs too? If so you could try greenifying it of freezing it with something like Titanium if it'd be safe to do so. ;)
[Android Builders Collective] cimdrap:
Yes it drains too much battery with 3.200 Wakelocks. I get 7 hours of battery. I read it could be modem related, i'm on the last one.
[Android Builders Collective] DroidIt!:
3,200 in my experience actually isn't very bad. I've seen some services with 40,000 plus. So like I said, if it's a system service it's tied to you could try an app called Servicely to see if you can isolate it and kill just that wakelock. I would be careful. If that wakelock is attached to a key service, freezing or restricting it may cause funky behavior on you phone. The safest way to do it is probably to try greenifying whatever it is that that wakelock is attached to. If that doesn't help then I would try the servicely route personally. ;)
[Android Builders Collective] 7sen:
Anyone get lucky with running xposed 01/July. With ezio building!
[Android Builders Collective] BrencelJ:
Sadly ezio build has a bit more of ART so it doesn't work YET.

I tested Xposed on Garrykd build and it works.

If you need xposed badly than switch build otherwise stick with it :).
[Android Builders Collective] Garrykd:
Well, if you're going to settle, you can settle with me:D

:p:p
[Android Builders Collective] Mikulec:
[MENTION=3392625]cimdrap[/MENTION] I do occasionaly have the rilj wakelock too, but a reboot usually fixes the wakelock.

I tried last two modems but I had similar experience with both of them. So I am not sure if changing the modem will help. Just charge your battery, reboot the phone and no more rilj wakelock.

Just found a screenshot from bbs with the walelock.
[Android Builders Collective] pkelly517:
That's same line I used to propose to my wife!

:highfive:
[Android Builders Collective] Real_Justus:
Hey there,

has somebody tryed the Slim GApps compiled 02. july? I had some serios problems with them... I flashed all versions... But only an oder ZIP fixed the issue.
[Android Builders Collective] fraz14:
No issues with SlimGapps 02.07.
[Android Builders Collective] Yank555:
ROM Update

Tiny update again, includes :

- Global SlimHeadsup 3-way switch - disable per app setting in disabled/forced mode (Yank555.lu)

- Re-added the 4 suspicious bluetooth commits (caused BT audio issues on shamu, as said will dig deeper as I find time)

The bluetooth commits are back in as is, so might be a drawback for Hammerhead but should make BT work again on shamu ... I do hope to get the time to get behind this thing...

3-way switch is brought up to the level that has now been merged.

As usual, ROM download links can be found in my OP in the Builders Collective, post 14.

JP.

PS: builds are up on both servers.
[Android Builders Collective] Silentbob999:
Concerning bluetooth issue / commit.

I will do +1 on the comment of Ezio quoted below.

I don't know if the "bluetooth commits" and those "audio streaming commit " are the same but if they are they it should be call it the audio streaming issue. (it would be less confusing)

3 or 4 times in the last few weeks my sound cut while listening to music and I loose any type of sound until a reboot. (with wire headphones or using speaker)

I keep flashing ezio build each time he release one.

I have no log or anything. It's often while I am in transit. The one time it happen while I was close to a pc the adb driver wasn't cooperating.
[Android Builders Collective] Yank555:
Yep, I do mean those 4, although reverting them all may fix HH reboot, but generates issues on shamu with some car audio.

It's certainly about audio streaming, but from what I gathered (not that I had any such problems myself) it's only when streaming through BT that it happens.

And those commits are BT related, granted streaming audio over BT related ;)

The thing is, we need to fix this properly, it's a commom repo and it should work on all devices rather than what fixes one breaks the other :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] ifwillems:
When I first reported this issue I thought it was Bluetooth related. However I can reproduce it with wired headset. So definitely a streaming audio issue, but most likely not a Bluetooth issue.

So were these commits reverted, or are they still in the latest build? I am currently using a [MENTION=2640853]Garrykd[/MENTION] version from 0629, which has these commits taken out.
[Android Builders Collective] mslatter:
D850 update.

Lots of merges yesterday for the LG G3, so figured would build a new one:

RRO layers

Add alternate WebView provider package

SlimHeadsUp: Add a global 3-way switch

Flip to Mute (enable in call settings)

Accidental Wake up OFF by default

Latest Kernel, G3 and D850 commits

Also, removed the following (install app to replace):

FMRadio / HTMLViewer / wallpapers / Camera2 / Calendar

1. Full Wipe (am told dirty flash works)

2. Flash Rom

3. Flash Gapps (I used Slim's 6/29 gapps from their XDA thread: http://tinyurl.com/pncj8jk )

4. Flash SuperSu

https://www.androidfilehost.com/?fid=24052804347768861

MD5: dc2fc64b53041d4c91e1c3d06661f2a4

Changelog is all new merges since last build from this link:

https://review.slimroms.eu/#/q/status:merged

Huge thanks to the following for making all this possible:

Slim Team - for a great ROM

arcardinal - Slim device maintainer

ezio84 - RRO fixes (Layers rock)

X-san - commits help / time saving script!