yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] adinkwok:
You didn't even have to ask ;)
[ONE Android Development] Natakranta:
The force is strong with this thread :)

Pleasure to follow up [emoji106]

I'd have to have three lives and six phones to enjoy all the goodies here.

#whiteuimustdie
[ONE Android Development] fusionjack:
i think it has something to do with incompatible package glibc.

this link is the best shot to try...
[ONE Android Development] Mrwargod:
boeffla-kernel-4.1-beta18-SlimVersion is out.

Go get it wile it's hot.

Link is in the OP.
[ONE Android Development] fusionjack:
btw, if someone know the commit to make main settings menu toggle-able, let me know...too lazy now to search for it[emoji14]

i barely able to follow this thread after 1 day of absent...keep up the spirit people! :D
[ONE Android Development] abhibnl:
Well i guess you can remove live wallpapers. I don't think many people use stock live wallpapers anyways.

I didn't notice any difference tbh. I'm only using caf build due to camera libs. They produce some awesome quality pics. Rest, performance and battery is same as per my usage. Infact i used to get better battery at slimsaber, lol!

Sent from OnePlus One
[ONE Android Development] Poesini:
To be honest, battery performance is bad but I think this is due to lack of a good kernel like [MENTION=3685904]ak[/MENTION] because Tyr doesnt boot for me with CAF
[ONE Android Development] pgarza:
what are your the thoughts on dirty flashing boeffla version over the caf version, is it possible ?
[ONE Android Development] kanyazsombor:
It doesn't work on custom roms at all ATM

---------- Post added at 14:58 ---------- Previous post was at 14:56 ----------

Maybe I'm wrong but it is supposed to work only in USA. Isn't it?
[ONE Android Development] abhibnl:
Dirty flash or clean flash?
[ONE Android Development] fusionjack:
builders, the frameworks/base doesn't have the latest two commits:

*Natiq Ahmed - Compilation fixes

*fusionjack - Revert "appops: Reduce lock contention in service"

i forgot to push them last night ;p
[ONE Android Development] fusionjack:
show me the ota_conf file. perhaps it is not configured properly or it isn't included in the slimota.

you can also see logcat what kind of debug messages are printed there.
[ONE Android Development] rituj_b:
Clean flash ak kernel no multi rom
[ONE Android Development] maxim.m:
I have the same results(

Tried to flash stock CAF-buld then AK kernel.:rolleyes::(
[ONE Android Development] -iHackerz-:
Here's my test on heavy battery usage with SlimSaber CAF 03/09 build and AK CAF and Stylo King V1 profile. Around 2-3 hours of gaming, atleast 1 hour of music listening, surfing, copying some files and other random stuff. The result is great!
[ONE Android Development] martinoff:
is weekend coming -> check

is internet alive -> check

has [MENTION=1228651]fusionjack[/MENTION] made his magic on github -> check

is cpu asking for some burning moments -> check

It's PARTY TIME

[YOUTUBE]Hp20JSzfImc[/YOUTUBE]

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

don't forget to flash gapps and supersu alongside the rom

any survivor script for dirty flash won't work with my build

have fun
[ONE Android Development] Ofthecats:
[MENTION=4296062]abhibnl[/MENTION] [MENTION=5284595]YoshiShaPow[/MENTION] [MENTION=3306843]kantjer[/MENTION]

Interested?

http://www.purdue.edu/newsroom/rele...martphone-battery-drain-from-faulty-apps.html

https://github.com/hushnymous
[ONE Android Development] skeetzor:
I am not a dev (or even close) but isn't this basically Greenify?
[ONE Android Development] taufiqs:
From my point of view, similar to greenify.

Maybe better. Because of Intel support? Kind of remind me about Meego LoL raised and left alone until it dies and reborn as Tizen on another company
[ONE Android Development] Ofthecats:
It sounded similar to me too, but I wanted to notify developers
[ONE Android Development] jonny68:
Brilliant ROM the best ive had on my OPO, ill be selling this in a few weeks when i get a Samsung Galaxy S6 Edge plus but whoever buys it ill be highly recommended they keep this ROM on it, no issues at all.
[ONE Android Development] f41lbl0g:
By the looks of it, it is exactly greenify, but supported with research (which may not even make a difference).
[ONE Android Development] abhibnl:
[MENTION=5284595]YoshiShaPow[/MENTION]

Any news on a fixed build bro? Did u find out what's the cause as of now? The build didn't boot for me as well.

Sent from OnePlus One
[ONE Android Development] trotos:
Plus one here. Clean install of latest build. Bootloop. Went back to previous version.
[ONE Android Development] nadiros:
Apparently it boots on ak caf kernel, however I cannot personally confirm this.
[ONE Android Development] Whaaaaa:
The same for me. Clean flash and bootloop.

I'm looking forward to flashing the next build ! :D
[ONE Android Development] adinkwok:
No, the kernel didn't even load according to logs (because there weren't any logs >.<). Kmsg didn't show anything, no adb, no kernel. The commits vivek_neel sent me are already in the source... I've switched back to using Sultans stock kernel until I can get things working again. I'm building another build right now, but I am going to need testers because I'm extremely busy.
[ONE Android Development] Whaaaaa:
I can test !
[ONE Android Development] adinkwok:
III have a build for testers here. I've removed a bunch of previous changes to get builds working now that official patches were pushed. Now that things are close to stock source, this build may possibly boot.

CONFIRMED: BOOTING

SlimSaber-CAF-bacon-5.1.1-20150912.zip

Also, if someone could logcat what is preventing the ota from working that'd be great! (Sept 3rd users only!)

You can do this by:

1. Entering settings -> SlimOTA

2. Plugging device into computer and starting logcat (guide for that is here)

3. Pressing all the different options one at a time in the menu

4. Stop and upload logcat :)

[MENTION=1228651]fusionjack[/MENTION] here is my ota_conf (placed in rootdir of the source)

#

# ota_lollipop.xml

#

# <?xml version="1.0" encoding="UTF-8"?> <SlimOTA xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ota.xsd">

# <Stable>

# <A0001>

# <Filename>SlimSaber-bacon-5.1.1-20150817</Filename> <RomUrl

# id="rom" title="Rom" description="Download SlimSaber builds">https://www.androidfilehost.com/?w=files&flid=34505</RomUrl>

# <ChangelogUrl

# id="changelog" title="Changelog" description="Download SlimSaber

# changelogs">https://www.androidfilehost.com/?w=files&flid=36856</ChangelogUrl> <GappsUrl

# id="gapps" title="Gapps" description="Download latest

# SlimGapps">https://www.androidfilehost.com/?w=files&flid=32587</GappsUrl> <SlimSaberCustomUrl

# id="xda_custom" title="SlimSaber Custom builds" description="Visit the SlimSaber custom builds and mods thread on

# XDA">http://xdaforums.com/oneplus-one/development/custom-slimsaber-builds-mods-t3175742</SlimSaberCustomUrl>

# <SlimSaberUrl

# id="xda" title="SlimSaber" description="Visit the SlimSaber thread on

# XDA">http://xdaforums.com/oneplus-one/development/rom-slimsaber-bacon-t2858033</SlimSaberUrl> </A0001> </Stable> </SlimOTA>

#

ota_url=drdevs.com/devs/paradox/slimsaber/rom/.ota_lollipop.xml

release_type=Stable

device_name=ro.product.device

#

# VERSION

#

# Example: Parse the 20150817 from the version name

#

# Version name: SlimSaber-bacon-5.1.1-20150817 Version delimiter: - Version position: 3 (zero based) Version format: yyyyMMdd

#

# Note : * Version name must contain a parseable date * Version name must match with the Filename in the OTA XML file in order to compare the date

#

version_name=ro.modversion

version_delimiter=-

version_position=3

version_format=yyyyMMdd
[ONE Android Development] dwaipayanray95:
BOOTED!
[ONE Android Development] Vivek_Neel:
That moment when the ROM boots :angel:
[ONE Android Development] nadiros:
Confirmed, on a clean flash with Gapps and SuperSU only. Thanks Yoshi. So is this good to go with as far as the latest build? Or just a test and I should restore my backup?
[ONE Android Development] adinkwok:
Latest everything :)
[ONE Android Development] Whaaaaa:
Dirty flash ok ! Thanks !
[ONE Android Development] KenjiHannya:
[MENTION=5284595]YoshiShaPow[/MENTION] r18?
[ONE Android Development] Ofthecats:
I think it's like Greenify but automatic
[ONE Android Development] adinkwok:
I think it's only to 5.1.1r16
[ONE Android Development] chikimonke:
Correct, today's build running well with [MENTION=3685904]ak[/MENTION] v017 btw.
[ONE Android Development] nadiros:
Thanks again Yoshi[emoji41]

The latest CAF build is running smooth as silk.

BTW, a beautiful day here in Vancouver eh!
[ONE Android Development] adinkwok:
Cheers to a not as beautiful week coming ahead :silly::crying:!

Thanks to all the brave testers who had to go through bootloops in the past couple of days! Hopefully it was worthwhile!
[ONE Android Development] kantjer:
Try version_position=4

#whiteuimustdie
[ONE Android Development] just4u32:
Thanks for that.

I'm having just a single issue.

When turning Bluetooth on, it says "turning Bluetooth on" then after 2-3 seconds it turns it back off.

Had that on previous builds as well. Any ideas?
[ONE Android Development] Wicked4u:
Where is the BATTERY tile? Why did you remove it? Or what happpened??

Slimsaber OTA is not functional. I did a full wipe of all my internal memory, pushed the zip files thru adb, still dare I say it's a crappy build. Sorry, m8, but one cannot be worse after an update??? Or shall I call it downgrade??

Talking about the twelfth build. Dayum!! :(
[ONE Android Development] SuRPasser:
here it is, i hope ive done well)

View attachment adb.rar
[ONE Android Development] kantjer:
If you paid any attention you would have known that there also isn't a battery tile in SlimSaber, and the non working OTA is been discussed more than once over the last few pages and the dev is aware of it :rolleyes:
[ONE Android Development] rezor92:
Hello everybody,

I want to build incrementals. I have managed to get it working but I have one problem. When I try to flash the incremental update I get the an error message like "package expects build fingerprint XXXXX this device uses YYYYY".

Hope someone can help me :)

Best regards
[ONE Android Development] kantjer:
Did you use an updater script made for an other device?

#whiteuimustdie
[ONE Android Development] rezor92:
Hi kantjer,

thanks for replying. No I dont use an updater script mad for another device, what I do is:

1. build my rom via "breakfast device" & "make -jX bacon"

2. after this I use ota_from_target_files to generate the incremental ota

Hope this helps cause I have no clue where this problem comes from.
[ONE Android Development] pu3cyg:
if yiu feel it's crappy then don't use it, and ask for refund at the customer service counter.
[ONE Android Development] kantjer:
I never tried it and have no idea how that's suppose to work.

Perhaps the ROM needs additional commits to make this work.
[ONE Android Development] rezor92:
Argh! No one knows :D but thanks for trying to help.
[ONE Android Development] kantjer:
I made my first CAF build and OTA is working with "version_position=4" in the ota_conf.

Test by setting the build in the future <Filename>SlimSaber-CAF-bacon-5.1.1-20150914</Filename>
[ONE Android Development] beany>:
SlimmerSaber

I have just built and uploaded a minimal version of SlimSaber. If anyone would like to try it out, please let me know what you think. ROM : md5
[ONE Android Development] srvoleti:
A new rom from my favourite beany!
[ONE Android Development] fusionjack:
your version_position is wrong. it should be 4 because you have additionally CAF in the file name.

edit: kantjer has already answered it :)
[ONE Android Development] Genericxx:
After being on CAF for some weeks (both builds by [MENTION=5284595]YoshiShaPow[/MENTION] and [MENTION=4800121]Sultanxda[/MENTION]) gave my bacon a clean flash today with the non-caf from [MENTION=3306843]kantjer[/MENTION]. Since i dunno if it is all about placebo i just wanna hear about you opinions guys: What are the pros and cons in terms of caf for your personal preference?

It feels like caf builds are slightly snappier. Also the oxygen-os camera hal produces awesome photos with Snapdragon Camera, especially portraits taken in dark surroundings with flash (guess chroma-flash works although not mentioned). On the other side CameraNext 50mp or Clear Image won't work currently, due to HAL limitations. HDR Shots seem far superior to me too in comparism to CameraNext. But as said: May be placebo. Since i mostly drive with ak kernels (0.17 on caf and 307 on non-caf) because i'm addicted to smartmax, i cannot tell much about the stock kernel behaviour. Overall it feels like CAF gives a much more fluid experience with slightly better battery life and remarkable better photo shots, the downside is that non-caf builds give me some feeling of beeing half-baked. But this could be placebo too ;)
[ONE Android Development] hewhomustnotbenamed:
was looking forward to a ROM exactly like that :good:Always used to delete these very apps manually after every flash..

with a focus on stability this ROM would soon be my favourite :)

would request you to replace the built in audio fx with latest maxxaudio here http://xdaforums.com/showpost.php?p=62589035&postcount=795

thread http://xdaforums.com/oneplus-one/themes-apps/app-05q-maxxaudio-lib-t3026967

thanks

can any one of the members please let me know if viper4android causes any extra battery drain?

and how do you like maxxaudio vs viper4android

many thanks
[ONE Android Development] nadiros:
[MENTION=5284595]YoshiShaPow[/MENTION]

I got my first random reboot with the latest CAF build.

Here's a bug report.

*Edit - OK busted, I am using xposed. I hope no one's choked I posted a report anyways [emoji52]
[ONE Android Development] kantjer:
I made my first CAF build earlier today. Rom feels smooth. It's too early to tell what the difference with stock build is exactly. I'm now running it with AK Kernel zzmoove relaxed profile.

#whiteuimustdie
[ONE Android Development] Ofthecats:
Anyone having issues waking the screen? I've had two reboots on render and on ak, where screen doesn't wake. I do not have "prevent accidental wake" enabled
[ONE Android Development] dead0:
no issues so far with either kernel on latest caf build
[ONE Android Development] kalapapa:
It could be firmware issues. Try flashing firmware files through fastboot and see if it fixes the issue
[ONE Android Development] gordon.shameway:
I really second that! Such a disresptful post.

#whiteuimustdie
[ONE Android Development] Ofthecats:
It's odd because everything was awesome before 0912.

I will keep everyone informed with relevant info
[ONE Android Development] SuRPasser:
Guys, I'm currently using 03/09 with well known build.prop tweaks. No problems so far, everything is smooth and stable. Haven't tried ak kernel. Are there any profits of jumping to ak caf?
[ONE Android Development] kalapapa:
The same benefits you get from flashing any custom kernel: custom settings for your usage
[ONE Android Development] adinkwok:
Does OTA work now..?!

SlimSaber-CAF-bacon-5.1.1-20150913.zip

Changelog:

Project name: proprietary_vendor_oneplus

*Sultanxda - bacon: Don't ship modem and mba images

Project name: android_kernel_oneplus_msm8974

*Junjie Wu - cpufreq: interactive: Do not reschedule timer if policy->max changes

*Hanumath Prasad - cpufreq: interactive:call __cpufreq_driver_target() for cur frequency

*Minsung Kim - cpufreq: interactive: don't skip waking up speedchange_task if target_freq > policy->cur

*Ruchi Kandoi - cpufreq: interactive: prevents the frequency to directly raise above the hispeed_freq from a lower frequency.

*Junjie Wu - cpufreq: Protect against hotplug in cpufreq_register_driver()

*Sultanxda - Revert "power: Import charger and fuelgauge drivers from cm-12.1"

*YoshiShaPow - defconfig: update

*Pranav Vashi - msm: use of swp{b} is deprecated for ARMv6+

*Evisceration - dts: fix incorrect frequency

*flar2 - Update ARM topology and add cpu_power driver

*Mauro Andreolini - block, bfq: add Early Queue Merge (EQM) to BFQ-v7r8 for 3.4.0

*Paolo Valente - block: introduce the BFQ-v7r8 I/O sched for 3.4

*Arianna Avanzini - block: cgroups, kconfig, build bits for BFQ-v7r8-3.4

*Zachariah - Revert "msm: clock-krait-8974: Limit CPU max freq to 1958MHz"

*Zachariah - Revert "msm: clock-krait-8974: Make CPU underclock optional via cmdline"

*Ezekeel - Added optimized ARM RWSEM algorithm.

*Peter Zijlstra - sched/fair: Optimize find_busiest_queue()

*Srivatsa Vaddagiri - sched: Fix inaccurate accounting for real-time task

*Peter Zijlstra - sched: Micro-optimize the smart wake-affine logic

*Michael Wang - sched: Implement smarter wake-affine logic

*Henrik Rydberg - Input: Send events one packet at a time

*andip71 - leds: Boeffla touchkey control driver version 1.1.0

*myfluxi - arm/dt: msm8974: Lower GPU voltage constraints

*Eric Dumazet - softirq: reduce latencies

*Fengguang Wu - readahead: make context readahead more conservative

*Jiri Kosina - ./Makefile: tell gcc optimizer to never introduce new data races

*Andi Kleen - Disable -fconserve-stack on ARM v2

*flar2 - Add /dev/frandom support

*flar2 - adjust Makefiles

*Davidlohr Bueso - lib/int_sqrt.c: optimize square root algorithm

*Eakkasit L - Readahead: Optimize divide/multiply by power of 2 using L/R shift

*Joe Swantek - power: catch wake-up requests in suspend_again

*Joe Swantek - msm: lpm-levels: add suspend_again handler

*Joe Swantek - power: quickwakeup: initial driver

Project name: android_packages_apps_Mms-caf

*Adnan Begovic - Mms: For any working message, also use default sms sub for mms.

Project name: android_packages_apps_SnapdragonCamera

*Sultanxda - SnapdragonCamera: Fix reversed video flash-mode icons

Project name: android_device_oppo_msm8974-common

*Sultanxda - Revert "msm8974: Disable fluence"

*YoshiShaPow - msm8974: use BFQ

*Sultanxda - msm8974: Add symlinks for modem and mba images
[ONE Android Development] chikimonke:
I get told it can't check for update. I imagine you were asking if the 9-12 build saw the 9-13 build? Or do you want us to check once we're on the 9-13 build?

Edit: Also, why is this build so much smaller? Is it the removal of the firmware stuff in the changelog? If so, does that mean since flashing previous builds I'm no longer on the 5-15 firmware?
[ONE Android Development] kantjer:
Check ota on the 9/13 build.

#whiteuimustdie
[ONE Android Development] adinkwok:
Check if you're on the 9-12 build for the 9-13 update. As for size, I honestly have no clue. I just synced sources, switched kernels to mine, and that was it!

---------- Post added at 11:13 PM ---------- Previous post was at 11:11 PM ----------

Just realized, OTA probably isnt working on the 9/12 build because that build doesn't have the ota_conf change! I guess we will have to wait for future updates after the 9/13 build :( my bad guys
[ONE Android Development] chikimonke:
Well now you 2 are telling me conflicting things [emoji15] I'm on the 9-12 build and could not check for the 9-13 build. Heading to bed now, so don't have time for flashing the 9-13 build until the morning. Need to be sure my alarm works. And the size difference seems like it would be the removal of embedded firmware that is mentioned at the top of your changelog.
[ONE Android Development] kantjer:
Not after [MENTION=5284595]YoshiShaPow[/MENTION] post edit.

You can check using the 9/13 build and get a no update message. That's a good thing.
[ONE Android Development] adinkwok:
My post after what you quoted explains.

TL;DR [MENTION=3306843]kantjer[/MENTION] is right, OTA should be working from now on after flashing the 9/13 build.

Edit: got ninja'd by [MENTION=3306843]kantjer[/MENTION] >.>
[ONE Android Development] kanyazsombor:
Can you explain what does "your kernel" means exactly. Currently I'm on the 0912 buid, and as I know that build contains Sultanxda's kernel, which is more strict as I know. Actually I like it. I haven't had time to test it deeply, but feels better regarding battery. Even switched to conservative governor. Don't fell any drawbacks. (I'm not a gamer though)

EDIT

Can I use the kernel from 0912 to use with 0913 build? Is it recommendable?
[ONE Android Development] Eru Ilúvatar:
Every [MENTION=5284595]YoshiShaPow[/MENTION] build contains a modified version of Sultanxda's kernel.

So, you are using his version of the kernel, based off of Sultanxda's one.

Therefore, the 0913 and the 0912 builds share the same kernel.
[ONE Android Development] kantjer:
New build teaser

EDIT: download

#whiteuimustdie
[ONE Android Development] Whaaaaa:
With /09/13 build i've "Can't check update."
[ONE Android Development] jrn2k:
CAF?[emoji2]

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Android Development] kantjer:
No stock build, but I will push the commits to the SlimSaber source so all builds will have it if [MENTION=1228651]fusionjack[/MENTION] agrees with it ;)

EDIT: done
[ONE Android Development] kanyazsombor:
Not correct. 0912 build exceptionally comes with sultan's kernel. That's why cpu max freq is 2000 there.
[ONE Android Development] Eru Ilúvatar:
Oh, didn't know it, sorry bro' :highfive:

Well, you can extract the boot.img from the 0912 build and flash it via fastboot in the 0913 build

fastboot flash boot boot.img
fastboot reboot

or via flashify app.

I recommend a backup, as always, but I don't think there will be any problem.
[ONE Android Development] adinkwok:
I had previously said that the 09/12 build uses sultan's stock kernel, not mine. The only major difference between his and my kernel is thta mine has his underclock disabled.
[ONE Android Development] chikimonke:
On the 9-13 build, I still get "can't check" error. I'm using [MENTION=3685904]ak[/MENTION] v020 kernel though. I doubt that would make a difference, but figured I'd let you know for full transparency.
[ONE Android Development] inffy:
[MENTION=5284595]YoshiShaPow[/MENTION]

Sent you a PM about something ;)
[ONE Android Development] fusionjack:
does sidebar still under a review in slim gerrit?
[ONE Android Development] yanner2012:
Same here, kernel stock.
[ONE Android Development] HamsterHam:
Anyone else find snapdragon camera not as clear as colour os camera or even next camera?
[ONE Android Development] nadiros:
Oops, have a free thanks.

I've never delved into its features (Snapdragon)but I still find the Camera Next Mod to be the best one for OPO
[ONE Android Development] chikimonke:
I find the clarity just fine, but I definitely needed to change the default Contrast and Saturation as my pictures were far too red for my liking. I personally changed saturation from 5 to 3 and contrast from 5 to 4. This gave me a better color balance in my opinion.
[ONE Android Development] HamsterHam:
Ahh okay. Think I have more clarity issues with front facing camera.
[ONE Android Development] chikimonke:
Big into selfies are we? :p
[ONE Android Development] HamsterHam:
Hahaha, been caught out! Nah, just the one time I wanted to use it wasn't so good lol. :p
[ONE Android Development] Stylo King:
No problem with the camera though, Found the Snapdragon camera more superior.

Clicked via Snapdragon Camera with Stock settings + HDR
[ONE Android Development] kantjer:
AFAIK it isn't pushed to Slim gerrit.
[ONE Android Development] HamsterHam:
Loving your new build.
[ONE Android Development] union1mc:
[MENTION=3306843]kantjer[/MENTION] [MENTION=4876554]Mrwargod[/MENTION] when either of you have time, could you please build Boeffla beta3 for SlimSaber? Thank you very much!
[ONE Android Development] kantjer:
Only the cm ramdisk changed in beta3. We don't use that in the SlimSaber version.

So a new slimsaber build would only have a changed version number

#whiteuimustdie
[ONE Android Development] :
Is it this?

https://review.slimroms.org/#/c/7914/

https://review.slimroms.org/#/c/7915/
[ONE Android Development] union1mc:
Thanks for having a look at it.
[ONE Android Development] kantjer:
Yes that's it, hadn't spotted it on Slim gerrit.
[ONE Android Development] mittimus:
Is xposed working good on CAF build of slim?
[ONE Android Development] Ofthecats:
Yes but still requires arter97's modified zip.