yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] mammenj:
Attached logs for antutu reboot.. this was on previous CAF build.

Hope it helps.

Edit: removed logs temporarily...as it has personal info..:confused:

Edit2: added the log files after removing personal info

Edit3: Bluetooth tethering was not working for me as well (these logs may have some info)
[ONE Android Development] fusionjack:
as far as i can remember 1.5, but i think some cars got blacklisted because it cannot handled 1.5
[ONE Android Development] svnhvn:
Nope, never happened in here. Don't do any benchmark too though. Kinda kindergarten-ish in my opinion.
[ONE Android Development] HaTrED_:
So? Every rom you use!

Every time you bring to the game a complain about something you never give any useful information and your arguments are always the same ending with a going back to this or to that or... Whatever!

If you wanna solve your issues, or at least try, help others to help you providing useful and, if possible, complete information, that's it.

End of discussion.

[MENTION=4278473]Hetalk[/MENTION]

I think you're talking about different users... Antutu is giving you some headaches!!!
[ONE Android Development] Hetalk:
I see he already provided some logs. :good:

[MENTION=2946144]mammenj[/MENTION] please dont respond back. Let's keep this thread friendly without any extraneous noise. :good::highfive:
[ONE Android Development] adinkwok:
Thanks! I took a look at these logs but they also don't show blatant signs of error. I will investigate the matter once I get back on the 9th :D
[ONE Android Development] renaltosonylevi:
You haven't told us about your kernel setup. For example you can undervolt and everything seems fine until you run antutu and heat soak your CPU. All of a sudden you have a hard reboot.

For me I tend to use antutu more as a quick and dirty stability test.

I have had to many ROMs that will benchmark well but are full of Judders and lags to take the results to seriously.
[ONE Android Development] TemplesOfSyrinx:
It's the strangest thing. I've gone on the Mazda forums and others have had this problem using different phones. There was some speculation that it was a CM problem. They also had some suggested work around using a Bluetooth phone book app from the play store, but I didn't want to get into some work around until I did a little more investigation. Thanks everyone.
[ONE Android Development] -iHackerz-:
Which Gapps package should I use with [MENTION=5284595]YoshiShaPow[/MENTION] 's SlimSaber, TK or Slim? Thanks
[ONE Android Development] ravvio:
I am on [MENTION=3306843]kantjer[/MENTION] 's 09/03 or 09/02 build i am facing issues with double tap to wake and Google now. Double tap to wake option is enabled under gestures.

Double tap to sleep works but double tap to wake doesn't.
[ONE Android Development] Whaaaaa:
I use Slim Gapps.
[ONE Android Development] -iHackerz-:
Could you link me the thread please?
[ONE Android Development] Whaaaaa:
http://xdaforums.com/showthread.php?p=53632481
[ONE Android Development] fusionjack:
do you enable "prevent accidental wake up" and cover the proximity sensor while double tapping the screen?
[ONE Android Development] Shyciii:
SlimSaber CAF version contains Snapdragon Camera from Sultan's CAF rom?
[ONE Android Development] iPusak Gaoq™:
is it possible to add this on slim?

http://xdaforums.com/oneplus-one/themes-apps/app-oneplustouchfix-t3152666

if not the apps, the source code alone will be nice since this apps really people that have problem on touch screen....
[ONE Android Development] kantjer:
dttw is working fine for me. Also no issues with Google now (not part of the ROM though)

#whiteuimustdie
[ONE Android Development] kantjer:
It's unclear to me which problem this is supposed to fix. I can't remember ever having a touchscreen problem.

#whiteuimustdie
[ONE Android Development] iPusak Gaoq™:
well a few people like me have a bit of touchscreen problem (i have touchscreen problem on the bottom left of the screen)....i have to press it harder on the bottom left...with this apps, it does help me a lot...the bottom left is now more sensitive and i was able to press it slightly better then before....
[ONE Android Development] BrandoHD:
There is a double tap to wake issue though, but I'm on a completely stock CAF version, so I try to bear with it
[ONE Android Development] kantjer:
The fix is not needed by all users and there will be no difference between adding the app to the ROM or installing it once manually. I like to keep the ROM Slim and not include apps that can easily be installed by the users themselves.

#whiteuimustdie
[ONE Android Development] -iHackerz-:
Is Xposed compatible with SlimSaber CAF? It goes into a bootloop when I flash it. It used to work with CM12.1 CAF...
[ONE Android Development] adinkwok:
I like slim gapps ;)
[ONE Android Development] gordon.shameway:
Have a look at the official slimsaber thread. In OP you will find a guide to make xposed work.

[MENTION=3306843]kantjer[/MENTION]

Perhaps the FAQ from official thread should be added to this thread too. Espacially questions about xposed will be repeatedly asked again and again.
[ONE Android Development] adinkwok:
Yes, it has replaced cameranextmod
[ONE Android Development] -iHackerz-:
Thanks! A couple more questions regarding your rom. I noticed when flashing SuperSU and booting the rom up, it immediately removes the app, why is that?

EDIT: Never mind about xposed :P

---------- Post added at 03:59 PM ---------- Previous post was at 03:54 PM ----------

I've read the guide but all I found was a modified sdk21 release, isn't that for 5.0.2 only?
[ONE Android Development] adinkwok:
I've had that before, and it's weird, the app is there but it's not showing. Reflash SuperSU through recovery and *poof*, it'll come outta nowhere :D.
[ONE Android Development] -iHackerz-:
I did 3 times already. When I reboot and open up the app drawer, I can see the icon for about a second or so and then it dissapears :/
[ONE Android Development] Ofthecats:
Are the necessary libs included in your builds?
[ONE Android Development] gordon.shameway:
This is the only version of xposed that is working with slimsaber
[ONE Android Development] -iHackerz-:
Alright, thanks, I'll go flash and test it out
[ONE Android Development] kantjer:
LOL, won't help the same user ask the same question on the SlimSaber thread also. I would do it if there was a change anybody actually reads the OP.

To stay motivated I made myself a promise a long time ago, I won't respond to any post about xposed or antutu

#whiteuimustdie
[ONE Android Development] chikimonke:
SlimSaber has it integrated into the settings. Go to Settings>Advanced and it's the first entry there...

Edit: Sorry for quoting some others there, not really sure how that happened.
[ONE Android Development] adinkwok:
Yes, I mean, it IS compiled from sources ;)
[ONE Android Development] -iHackerz-:
Isn't that supposed to be Superuser, not SuperSU? Correct me if I'm wrong.

EDIT: Oh ok, nevermind. Flashing SuperSU made it appear under Advanced, thanks :D
[ONE Android Development] Hetalk:
Nope. I guess it changes to SuperSu, if you use that one.
[ONE Android Development] -iHackerz-:
Thank you guys for the help! This is such an amazing rom, it's smooth as butter, super fast app switching and animations, lots of features, nice boot animation, can't ask for more. Keep it up! :good:
[ONE Android Development] chikimonke:
Correct. SuperSU isn't included by default because it's not open source. That said, it still tends to be the better of the two options, and has the fewest compatibility issues. More often than not, if a root app is behaving badly using Superuser, switching to SuperSU solves the problem. Because of this, [MENTION=1228651]fusionjack[/MENTION] still includes provisions to show it in the settings.

Come to think of it, why hasn't the same thing been done for Synapse vs KA? Would be nice if Synapse was installed, if it would disable/remove KA and add the Synapse entry instead. If KA could be disabled, it would also help prevent issues of the two apps fighting with one another.
[ONE Android Development] -iHackerz-:
That is also true. I'd love Synapse more than the one included as I use AK and was planning to install it right away on SlimSaber CAF, but I don't know if it's a good move since as you said, those two might conflict. though, I believe the Auditor can be turned off.
[ONE Android Development] Hetalk:
Makes sense. Food for thought for the awesome devs we have here.

BTW, I type like I know you all so well, probably because I've been following these 2 threads(slimsaber and custom slimsaber builds) for a long time, but I don't post much. Some of you guys might know me from gnexus forum from some time back.
[ONE Android Development] chikimonke:
I'm using [MENTION=3685904]ak[/MENTION] and synapse no problem. Pretty sure KA is off by default, or isn't trying to apply anything on boot by default. The problem lies when people are exploring and then forget they set something in KA and then try to use Synapse and start complaining about settings not sticking. [MENTION=6307803]Stylo King[/MENTION] has a great profile for the CAF kernel too.

I've certainly seen you around, but I don't remember where specifically. Nice to see you again.
[ONE Android Development] Guido83:
I am on latest CAF build and all sounds are coming out of the earphone instead the phone apeakers. isn't that odd?
[ONE Android Development] adinkwok:
o.0 that is really odd. I'm on the latest CAF build too and there's no problem...
[ONE Android Development] Nos_20:
I have had this on FJ ROM when I flashed V4A on it. I don't know why but I wiped system/dalvik/cache reflased ROM and sound was fine.

V4A is working correctly for me now and I am on slimsaber caf with AK caf v013.

Try to format system first and reflash ROM

#whiteuimustdie
[ONE Android Development] Zeus20:
I do not have that issue at all running the caf build of slimsaber
[ONE Android Development] Guido83:
that did it, thanks
[ONE Android Development] martinoff:
just made a build for weekend

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

don't forget to flash gapps and supersu alongside rom

have fun
[ONE Android Development] imam.krismanto:
What different with [MENTION=3306843]kantjer[/MENTION] build? Any changelog?
[ONE Android Development] gugas123:
Love your striped down builds !

:good:

Only if you can... build more often

;)
[ONE Android Development] Whaaaaa:
Me too i would like to know the difference with the other Slim rom.
[ONE Android Development] imam.krismanto:
No Gallery..??
[ONE Android Development] martinoff:
From an older post

build with oracle jdk and removed packages browser,calendar,mail,exchange,gallery,almost all scrensaver,audiofx (replaced by v4a)

You can always use search button
[ONE Android Development] ChefChaudart:
Where ?

Is there a specific thread for Paradaox CAF Slimsaber's :confused:
[ONE Android Development] xneoon:
Too much bugs & FC for me (security dongle, phone, sms, resize icone more and more...) i do a clean flash and use AK caf kernel. I come back on Sultan.
[ONE Android Development] kantjer:
Just a leftover from a previous V4A install. Removing the sh script in addon.d or as you suggested fromat the system partition before flashing will fix it

#whiteuimustdie
[ONE Android Development] renaltosonylevi:
Really nailed it right there.

And those logs really helped everyone out. It is really good that you use the ROM as released and don't go flashing different kernels and introducing unpredictable variables.

But what really impresses is the complete humility you show and the selfless desire to help.

In fact that is the XDA post of the year.:thumbup:
[ONE Android Development] skodaslx:
Why does the CAF rom didn't work as second rom with latest multirom? Only bootloops. Kantjers rom boots fine as second rom. What is missing in the caf rom?
[ONE Android Development] renaltosonylevi:
I am no expert on multirom but have you tried dirty flashing the CAF build over Kantjers? I have herd of similar method's working with CM 12.1.:)
[ONE Android Development] Nos_20:
I have been running the CAF build as my second ROM in MultiROM, with AK"s CAF kernel. I have Fusionjack's ROM as primary.

The trouble I am having with the CAF build is the mobile signal drops away all the time. Should I flash a different modem on the CAF build, if so any suggestions???

#whiteuimustdie
[ONE Android Development] skodaslx:
Are you using the latest version of multirom and multirom recovery?
[ONE Android Development] dead0:
I generally find antutu reboots occur due to sultans thermal threshold settings. Currently in Thailand so can not provide further details or threshold settings to assist as running an older build with renderkernel
[ONE Android Development] kalpik:
Excellent ROM (running the CAF version). Just wanted to point out two things:

1. The option to hide data activity icons on the wifi icon doesn't work. No matter what it's set at, you can still see the arrows.

2. Well, this is a request. Could the option to hide heads up when you touch elsewhere be implemented? It's annoying to have the heads up till the timeout.

Thanks, and good job on keeping the ROM up to date :)
[ONE Android Development] Nos_20:
As far as I am aware I am... Yes.

#whiteuimustdie
[ONE Android Development] kanyazsombor:
Do you have the signal drops when caf is primary? What is the case with the original Slimsaber regarding these drops?
[ONE Android Development] gargeya_369:
[MENTION=5284595]YoshiShaPow[/MENTION] Compass is not working in the CAF rom...

Is this a known thing?
[ONE Android Development] Nos_20:
I couldn't run CAF as primary. Bootloops. with Slimsaber as primary I get no such signal drops.

#whiteuimustdie
[ONE Android Development] skodaslx:
You couldn't run the caf as primary and I couldn't run it as secondary. Kantjers rom is running fine as primary and secondary. So there is definitely something wrong with the caf rom.
[ONE Android Development] arifqur:
I have the same problem as you guys with the CAF rom on Multirom
[ONE Android Development] kantjer:
It could be the CAF kernel doesn't have the MultiRom patch.
[ONE Android Development] skodaslx:
Thank you. I think it is so, because the rom booted as secondary with AK caf kernel.
[ONE Android Development] arifqur:
Tried it with AK's CAF kernel also but no luck
[ONE Android Development] -iHackerz-:
Anyway to fix the faulty auto focus when recording with snapdragon camera? I enabled HSR 1080p but it keeps getting out of focus, all is blurry, and takes a long time for it to actually focus.
[ONE Android Development] iPusak Gaoq™:
I'm having root authorization problem in Clean Master apps...I already granted root excess on superSU but when I try to use 'disable autostart apps' in Clean Master, it failed to gain root..I have remove Clean Master from superSU list and reauthorize root excess but still unable to gain root excess....

Don't have any problem with SlimSaber official build but having this problem on kantjer build....
[ONE Android Development] kantjer:
Make sure you use the latest build. I removed the SuperSU integration, it isn't working.

The I haven't changed anything else related to superuser access.

You can also disable auto start in privacy guard, no need to use a separate app for that

#whiteuimustdie
[ONE Android Development] ravvio:
Double to wake seems to be a prominent issue for me for all CAF builds of [MENTION=3306843]kantjer[/MENTION] . It doesnt work most of the time i have to either reboot the phone or turn off/on wakeup control under kernel auditor setting. Any way to resolve it ? Soft reboot issue has reduced from 5 times a day to once. :)
[ONE Android Development] kantjer:
Great to hear, I never knew I had made CAF builds.

#whiteuimustdie
[ONE Android Development] Natakranta:
I have CM12.1 May.15 firmware and radio. Kanjer's Sep.03 as primary ROM with stock karnel. BTW, works like a charm.

I wanted to see this CAF magic for some time already but I didn't have time for clean flash. But I read reports of successful dirty flash of YoshiShaPow's CAF build over Kantjer's build so I made a nandroid of my primary. Than I used this nandroid to create new secondary ROM. Then I wiped dalvik and cache on it (no option to wipe system in secondary ROM). Then I flashed CAF Dec.03 ROM on it, than Kantjer's custom Slim gaps Dec.03, than SuperSU 2.49.

Booted it and no problems encountered. No Force Closes, no soft reboots, no freezes, Nada.

Works fast and smooth. Now I'll take a good look on that snapdragon camera.

Edit

About CAF battery life.

Deep sleep overnight, WiFi on, mobile on 2G (because WiFi on), full signal strength on both.

Not bad, heh? ;)

Then I need to do few reboots so I charged it to 100% again to see usage during day. Not much time spent today on phone. Busy with family Sunday. Mostly browsing, reading and a bit playing with snapdragon camera video recording.

Again full signal WiFi 5GHz, and mobile on 2G. Brightness set manually to 20%, that's enough for me indoors.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] MMWolverine:
Hi [MENTION=5180758]Natakranta[/MENTION]

did you by any chance manage to change radio on Slim CAF as secondary? I flashed cm11s radio in twrp 2.8.6.0, changes fine for COS12.1 primary and cm12.1 based secondaries, but on all CAFs baseband stays DI.3.0.c6-00241-M8974AAAAANAZM-1. :D
[ONE Android Development] iPusak Gaoq™:
I'm on latest build (09/03) and I use Clean Master to clear out unwanted files only...I only notice root excess problem when I try the disable autostart....
[ONE Android Development] f41lbl0g:
I think that it does change, but it just shows DI.3.0.c6-00241-M8974AAAAANAZM-1 because on my phone, the proximity sensor is not working after flashing the modem (which is supposed to happen), which would not be the case if it didn't work. The proximity sensor fix for cm12 does not work though, so right now I cannot pick up calls or hang them up. Better to keep the radio how it is until something is figured out or I realize that my proximity sensor is actually destroyed.
[ONE Android Development] MMWolverine:
Strange, in my case prox sensor worked and didn't even bother flashing the fix. I agree, better leave it as is for now.
[ONE Android Development] kantjer:
The proximity issue is firmware related, not modem related. The CAF build has the firmware files included so regardless of the installed firmware the proximity sensor should work on CAF builds.

#whiteuimustdie
[ONE Android Development] CounterC:
So flashing the 44s modem shouldn't break the prox sensor?

Edit: I just tried flashing only the cm11s modem. In twrp 2.8.6.0 it says flashing is succeeded. Prox sensor works because I don't flash the prox sensor fix however in settings => about phone it still says modem 241... It's unchangeable, I've tried a lot of options...
[ONE Android Development] vng10:
sorry if i am out of line, but i have searched through the Slim Saber original thread and the xposed file to flash on that post hasnt been working on the latest Slim Saber CAF 09/03.

Post referenced: http://xdaforums.com/showpost.php?p=61620150&postcount=11249

What are people using for 09/03 to get xposed?

Thanks!
[ONE Android Development] Natakranta:
I just disagree on bass of my experience with different combinations.

ROMs proximity sensor problems, appearing as screen not switching on and off during call accordingly or even SODs on 4.4.4 ROMs, come from incorrect radio flashed in primary (or manually assigned in secondary). It all started January 16th when new radio was introduced by CM12 and new sensor blob (that's the file you are modifying flashing the sensor fix zip, which can be done manually with root file explorer).

Basically user must match radio with proximity sensor blob:

system/vendor/lib/hw/sensors.msm8974.so

You either use any KitKat / CM11S radio (NON-HLOS.bin) with sensor blob (sensors.msm8974.so) from ROMs before 16th January,

or use LP / CM12.1 radio with sensor blob from ROM built after 16th January.

I'm assuming YoshiShaPow's CAF SlimSaber has firmware built in as regular SlimSaber (kantjer's trick [emoji106]). Is this ROM included firmware containing radio as well? If so, I don't see how user would be able to change it. Whatever user do, flash other radio on primary, assign other radio using that function in secondary ROM, it shouldn't matter because ROM will use and display is built in radio. [MENTION=3306843]kantjer[/MENTION], am I right here?

Logic makes me think that in other case, if radio is not included in the built into ROM firmware, than ROM should respect whatever radio is on primary or whatever radio is assigned to it on secondary. Will ROM display actual radio number?

CM radio files naming policy, or rather lack of it, doesn't help us.

My setup is really simple and trouble free.

Since MultiROM TWRP facilitated assigning separate radio.img for every secondary ROM, I decided it will be easier to move SlimKat from primary to secondary (especially that I'm hardly using it) and go full CM12.1 firmware (firmware base + radio) instead of previous mixture of CM12.1 firmware base and CM11S radio.

Firmware.zip = firmware base + radio

I use now CM12.1 May.15 firmware (full, with its radio) and have no problems with any lollipop ROM I flash (not many of them...)

I still keep SlimKat 9 as secondary ROM. 2 tricks here. AK karnel to boot it on CM12.1 firmware. In MultiROM TWRP I assigned CM11S 05Q radio for it (not flashed! Do not flash firmware or radio zips on secondary ROM! Use the "add radio" option for each ROM menu, rename NON-HLOS.bin to radio.img).

The whole joggling with sensor blob (proximity sensor patch zip) starts when user wants to use LP radio with KK ROM or opposite for any reason (particular radio signal strength efficiency?).

I personally never had problems with any of radios which came for last year. On the other hand I don't bother with it much because I'm most of the time in strong WiFi areas (home/office).

If I wrote something wrong, please correct me. Not feeling well and my three year old running around don't help in concentration.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] skodaslx:
Thank you for your detailed instructions. I followed them as I can't make caf to boot as secondary. So your way may be a solution for me. But no luck. Only bootloops. The only difference that could be is the used multirom recovery. So what version are you running?
[ONE Android Development] Natakranta:
Latest MultiROM and MultiROM TWRP

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] _ASSASSIN_:
Just want to say that the title should be "Slimsaber based custom ROMs" not ROM's with the apostrophe.

/ot
[ONE Android Development] MMWolverine:
Great response! Hope you feel well soon. :good:
[ONE Android Development] Natakranta:
Thanks my friend! Fell free to copy and edit as you wish to your support thread.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] f41lbl0g:
How did you get the multirom to boot with ak caf kernel as primary? or is it the regular ak on primary with SlimSaber caf as secondary? Mine is simply a black page that proceeds to boot after 5 seconds with primary ak caf.
[ONE Android Development] :
[MENTION=3306843]kantjer[/MENTION] any plans on adding App Bar from Slim? I miss it.
[ONE Android Development] chikimonke:
App Bar?
[ONE Android Development] :
Yeah, Robbie's last build included it. Here is how it looks like
[ONE Android Development] Guido83:
Any chance to add the wakelock blocker feature to the CAF build?
[ONE Android Development] arifqur:
Hope you feel better.

BTW what is the second screenshot which says "Manage Roms"? Like is it an app?
[ONE Android Development] kantjer:
Plans yes, I only need to find the time.

#whiteuimustdie