yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] deepaklunked:
[MENTION=5284595]YoshiShaPow[/MENTION]

Hi.. I've been using this ROM for the past two hours.. Its smooth and fast. But I feel that the camera quality is not as good as [MENTION=4800121]Sultanxda[/MENTION]'s ROM. I am saying this because I am coming here directly after using his ROM. I am not complaining; just letting you know. I actually don't use camera much but I just wanted to let you know.. And yea, I have managed to successfully install v4a by flashing lolliviper zip. More testing going on. Will report whatever I find. Thanks for your work..

Sent from my ONE

---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------

Another report. Snapdragon Camera does not have HSR and HFR stuff. I am sorry if it was intended to be that way. Also, the videos seem to be noisy.

Sent from my ONE
[ONE Android Development] kantjer:
Yes I know, I used lollviper before. But for my own satisfaction I need to fix this without the need for any fixes or workaround. That's how I learn things ?

#whiteuimustdie
[ONE Android Development] kantjer:
The fix should work on stock kernel and also on AK because it uses stock ramdisk. Next step wil be building Boeffla with slimsaber ramdisk instead of the current cm one. That also mean we don't need to modify the ramdisk anymore to make it compatible.

#whiteuimustdie
[ONE Android Development] pa.pn2:
Did the same but v4 doesn't seem to stick. If i open it there always occurs the info bout the driver update even after applying and rebooting

Any advice?
[ONE Android Development] deepaklunked:
Are you on his latest ROM, coz his latest version does not have v4a. So installing the zip will not lead to any conflicts. Try removing the apk (use root explorer if it is a system app), then again flashing lolliviper zip. Personally, on the phone speaker, I don't find a big difference; I am using realpac's profile. Have to test with earphone though. But "I" feel, audiofx is better. Frankly, that's only my opinion.

Sent from my ONE
[ONE Android Development] Ofthecats:
https://github.com/anarkia1976/AK-OnePone-Reborn/commit/be0dd7cb3ddf6705c7e198bcb4189d372f6440a7

I brought it to [MENTION=5438598]RenderBroken[/MENTION] attention and he said he's looking into possibly tweaking it first because it may be too aggressive
[ONE Android Development] adinkwok:
Oooh I thought you were talking about ROM based commits (which I don't think is very logical). I'm not going to be modifying anything kernel wise. I'm just going to let Sultan do his magic (y).
[ONE Android Development] Ofthecats:
OK cool. It seemed rom side to me
[ONE Android Development] inffy:
The 15th CAF builds batterylife seems much better than the previous.
[ONE Android Development] kantjer:
[MENTION=4876554]Mrwargod[/MENTION] instead of unpacking, modifying and repacking the cm ramdisk from Boeffla's source I made a build using the unchanged SlimSaber ramdisk.

The kernel boots fine and is running stable. The advantage is we don't need to change the ramdisk for every build and we have all SlimSaber ramdisk changes, like the v4a fix, available in the Boeffla kernel (if my theory is correct)
[ONE Android Development] fusionjack:
if i correctly remember, boeffla kernel is using linux 3.4.64. it'd be better if you could patch it to 108 (or even newer). this is linux upstream patches which are good. i patched stock kernel to 108.

edit: last time i patched sony stock kernel from 3.4.0 to 3.4.107. it was around 4000+ commits [emoji14]
[ONE Android Development] kantjer:
Correct Boeffla sticks to an older Linux version. I will give it a go, thanks for the tip

#whiteuimustdie
[ONE Android Development] Mrwargod:
I'll try to figure it out. I'll have a look at your git and see if i can do it. :good:
[ONE Android Development] kantjer:
It's easy.

https://github.com/kantjer/boeffla-kernel-cm-bacon/commit/922740d0a9b91412e275bb105cdca41a29813d81

I used the tools in post #2 to extract the ramdisk.gz file from my ROM build
[ONE Android Development] w0rinal:
take your time. school takes precedence over, well, hobbies. if I had the chance I'd go back and push myself into (into? sounds strange) learning a little harder than I actually did :silly:

unfortunately, my SIII stopped booting one day, constantly bootlooping, I assume it's something hardware related. none of my backups changed anything, neither did clean flashing.

sd-card slot it something I'm really missing on the opo. everytime I wipe partitions I'm scared I ticked "internal storage" by accident ...

thanks for the link btw. did you know you can be "out of thanks"? :D

I think I'll stick to SlimSaber 5.1.1 for now. MM ROMs just don't offer the features I want for everyday use by now.

[MENTION=4921047]gwindlord[/MENTION]'s build with LightningKernel is running very smooth right now. just so that you know: there are russian strings in CameraNextMod settings
[ONE Android Development] sien1996:
Hey. I was at your point a few years back! Make the right choice! Choose something that you love!
[ONE Android Development] gwindlord:
Anyway even for striken out: the build is odexed, I believe (but cannot prove) that it makes the UI snappier. The difference briefly is about the code, which can either unpack and run under Just-In-Time compiler every time you start the app (deodexed) or already be outside and that's why be started faster (odexed). I also know some people installed xposed on this ROM and it went fine. The browser is a bit customized Chromium CAF, it is just named Chrome Beta - I made this dirty hack to be able to install Chrome Beta Layers themes on it :o that's why it takes more space than the usual browser, but try it and you'll understand it's worth to :)

Theoretically you can delete the unnecessary .apk, I did not do that for Email, because the build fails, or for DocumentUI, because it is linked with Downloads, and it's the only reason they are there. So you can try, but ensure to have backup just in case. As for hosts and build.prop, I think you can do that, but be sure to re-sign zip after any changes inside the archive.

Crap, I'm really sorry for that, I did not test on the other languages and was hoping the translated version will switch language. Seems the guy, who did the translation, avoided thinking of the right process. Once again, if you want to do something (e.g. translate camera), do it yourself >_< So sorry :( For now you can just download and install CameraNextMod of the same version (if you're not planning to update the ROM often).
[ONE Android Development] Natakranta:
Hi, Could you please link again your build?

Link from your part directed me to

and I can't download it.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] gwindlord:
Well, this is the first link, which points to .md5 file, and the second link, which points to the archive, is a bit lower :) Let me add some space between them.
[ONE Android Development] Natakranta:
Thank you for making me feel old and blind :D

My only excuse is it was before I had my morning coffee.

Downloading now. I'm so happy to see fresh SlimSaber LP build. What will there be updated over last official SlimSaber LP build?

My primary ROM is still last Kantjer's build:

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] gwindlord:
Sorry mate, didn't mean anything like that :D

What will be updated... not so many things, couple of small additional things in the buttons/settings (like non-intrusive calls and custom app lock screen shortcuts), all recent Google security bulletins and some apps removed (like wallpapers packs, Eleven or SlimLauncher) and other ones added (like CameraNextMod - incorrectly translated and having Russian strings in English locale, shame on me >_< or CMFileManager, or Nova Launcher, or custom built Chromium CAF browser, which is really cool to my mind). Some changes are under the hood (like adaptive lowmemorykiller, UBER 6.0 toolchain built kernel, recent [MENTION=4800121]Sultanxda[/MENTION] changes in his kernel), but the UI looks same I suppose.
[ONE Android Development] Natakranta:
Cool, that's what I was counting on, under the hood updates and apps updates to stay on the top. That should keep me going until MM ROMs get more features (Slim recents in particular).

Hit us with a link if you fancy building another SlimSaber refresh.

Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] trotos:
Hi, and thank you for latest slimsaber update. Does this rom includes latest 2016 security patches?

---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------

Just seen that... Please ignore my previous post
[ONE Android Development] gwindlord:
Took a look into Russian strings in the CameraNextMod - I was afraid of much worse :) Nevertheless I think I've fixed that and placed it into my github, feel free to install it on top of the existing camera.
[ONE Android Development] w0rinal:
thanks for the detailed answers :good:

actually, I installed xposed and it does work fine. shame on me but I can't live without it :p

sorry, I forgot mentioning I'm running the ROM in english. to be honest I hate german translations. they just do not fit right sometimes or don't even make sense in rare cases and most apps I'm using are english only anyway, so I'd have a bilingual phone which feels odd.

I never thought about translating it, might do so if I can find some time. the problem about camera in particular is that it's quite hard for me to find the right translation (see above) if I don't know about the topic well. I still don't know what the focus mode exactly does, for example. same goes for timelapse, iso, exposure, etc, etc. I'm simply using the stock settings and I'm fine :D

do you want me/us to 'report back' bugs I/we find? if so, do you prefer pm or in this thread?
[ONE Android Development] gwindlord:
I think PM would be nice for that, thank you, feedback would be useful, though I cannot promise I'll fix everything :D
[ONE Android Development] Natakranta:
Thanks for the camera apk. It instead without problems and returned English menus in app settings.

I installed ROM over last Kantjer's SlimSaber LP build (regular, non-CAF) , only wiping cache, system and dalvik cache. I didn't notice your build is CAF. Because it its CAF? Or I'm losing my mind?

Anyway no problems noticed apart of one I have with CAF LP builds (like yesterday clean flash latest CAF build from YoshiShaPow), some pictures are not loading on Facebook on browsers, be it AOSP Browser, Dolphin, Opera or the beta Chromium browser in your build.

No such problem in regular non-CAF builds.

Any ideas what it may be?

Anybody is still building updates for regular, non-CAF SlimSaber LP and don't mind sharing link?

I flashed last SlimLP January build from Minix, Thanks buddy!, all is good, running great, just missing one important feature for me, a volume tile in Quick Settings. I thought Robbie's SlimLP builds had it back in the autumn, but maybe he was cherry picking the commit. His bacon builds weren't exactly stock SlimLP.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] gwindlord:
Thank you for the test! Well, you can check the kernel version in About settings and ensure it is CAF :) Also TricksterMod or maybe KernelAdiutor or Synapse would show more info about the kernel. Btw system applications are actually the same as in the regular SlimSaber, almost without changes, so it's not so unusual that they work.

As for the pictures issue - cannot even imagine, just checked - the only images missing in the facebook are advertisement ones, which are blocked with the Browser internal ad-blocker. Could you please share some pages you had this issue on?..
[ONE Android Development] Natakranta:
I feel so lame now, I discovered what it is with pictures not loading. Update on AdAway is to be charged guilty. I switched off ads booking and all pictures are loading back. I need to track specific URL and white list it. Probably something like facebook.com [emoji1]

Thanks again for your build!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] Natakranta:
[MENTION=4921047]gwindlord[/MENTION], does karnel in your build support MultiROM and has kexec hardboot patch?

MultiROM Manager app shows karnel is patched but secondary ROM can't boot erroring out lack of kexec patch in primary (your) ROM karnel.

I flashed AK.026.OP1.CAF.zip on your ROM (primary in my setup) and now my secondary ROM (Fusionjack's OmniBear) boots.

I'm guessing there must be something wrong in CAF karnel kexec hardboot patch implementation. No complains, just giving heads up to anybody with similar to my MultiROM setup to save them investigating.

Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] gwindlord:
[MENTION=5180758]Natakranta[/MENTION], AFAIK [MENTION=4800121]Sultanxda[/MENTION] tried to implement the kexec hardboot patch, but it caused reboots, so he rejected it, that's what I remember. As a result, I think kernel does not have kexec, not sure about MultiROM support tho - I've never made experiments like that :)
[ONE Android Development] fusionjack:
that is a pity. i still keeping 5.1.1 as primary rom in order to use multirom.
[ONE Android Development] gwindlord:
[MENTION=1228651]fusionjack[/MENTION], I can revert these commits and rebuild kernel for you, but it breaks encryption (not reboots, sorry), that's why [MENTION=4800121]Sultanxda[/MENTION] reverted them.
[ONE Android Development] fusionjack:
hmm...why reverting those when multirom patch is working fine on 5.1.1?
[ONE Android Development] gwindlord:
These ones are for kexec hardboot, not multirom (though I'm not really good in multirom topic). Thank you for checking! :)
[ONE Android Development] Natakranta:
FJ meant he is using SlimSaber LP as primary because it has correctly working kexec hardboot patch in 5.1.1. kernel allowing booting secondary ROMs in MultiROM and testing MM builds he does. He can't use 6.0.1 ROM as primary because MM ROMs or at least Omni based don't have working kexec hardboot patch in karnelkarnel.

Meanwhile your last SlimSaber LP build with AK 26 CAF running great. Thanks!
[ONE Android Development] gwindlord:
Thank you for explanation, as I've said, I'm not really good at multirom stuff :o
[ONE Android Development] w0rinal:
Hi guys,

I finally managed to remove the unnecessary stuff, re-sign it and flash it and it's actually working now

for some reason navbar/hw keys couldn't "trigger" recents or home, then statusbar wouldn't expand qs or notifications, but everything's fine now :)

it's question time again if you don't mind lol

- what do these scripts in init.d do: 00banner, 50selinuxrelabel (can I delete this safely? is it a ROM necessity to leave selinux set to permissive? does deleting this script set selinux to enforcing or does it do something else?), 90userinit

- can I somehow hide the userswitcher? imo it's a nice idea for tablets but why would you need several 'users' on a phone?

- can I force the (slim) recents screen to show only apps I launched since boot? eventually, there will be every app I ever launched and that renders a screen showing 'recent' applications useless

-- can I simply delete /data/system/recent_images/* and /data/system/recent_tasks/* with tasker on every boot to accomplish what I wrote above?

- does anyone know what com.android.provision, com.android.wappushmanager (or something like that), com.android.managedprovisioning, com.android.backupconfirm, com.android.sharedstoragebackup and com.android.keychain do? most of them are never run at all and everything's working fine it they're disabled or even removed

fyi the menu in privacy guard shows the item "help" twice

Edit: removed the three scripts above, device boots up fine. it still shows selinux status: permissive
[ONE Android Development] adinkwok:
00banner basically shows a welcome sign to logs. Userinit allows user to run user scripts from boot. You cannot hide the user switcher because (don't know any rom with that feature). Clearing recent_tasks will accomplish what you said (removing the *useless* recents). Deleting recent images doesn't help with clearing the recents, it just removes cached images. I 100% do not recommend disabling any of those system services that you listed as it can lead to instabilities whenever they are called upon. Do that at your own risk :P.
[ONE Android Development] w0rinal:
yeah, did some research. didn't find the information I was hoping for but deleting these scripts seemed to be a stupid idea so I restored them

of course it can't be considered "useless" but it's a downgrade compared to prior versions of android imo. swiping away from recents screen = clearing it out of memory.

recently didn't achieve the desired effect, going to try the "only show running apps" option. but I'd like to see even those killed by LMK if they were started after boot

couldn't I clear the recent_tasks folder using a script? I've been interested in scripts for some time now but I never felt like getting into it
[ONE Android Development] gaspolo:
i have made a rom based on last gwindlord version, but all app like usually slimsaber caf ;) ( like slimlauncher, viper4android ). ( removed novalauncher)

work perfectly with xposed ;)

https://drive.google.com/open?id=0Bw0l2qeHF2U2dklCeFNIZTdJOUU
[ONE Android Development] kalapapa:
Nice work

Just out of curiosity does it contain the latest caf kernel patches from sultan
[ONE Android Development] gaspolo:
yes.
[ONE Android Development] kalapapa:
Which xposed version does it work well with? Because if I remember correctly, on slimlollipop regular xposed would cause a bootloop due to fusionjacks special art hooks. Does it work with the latest xposed version? Thanks for all your help
[ONE Android Development] gaspolo:
xposed framework

https://drive.google.com/open?id=0Bw0l2qeHF2U2WjJVUEQySVBOcmM

xposed app

https://drive.google.com/open?id=0Bw0l2qeHF2U2RkJ1ZFVENUZWYlk

slimgapp

https://drive.google.com/open?id=0Bw0l2qeHF2U2MHhGWDNrd0VOaGs

last firmware H2O

https://drive.google.com/open?id=0Bw0l2qeHF2U2Y0dpNTVyallWWTA
[ONE Android Development] w0rinal:
I saw this somewhere before, but I didn't find out what's the difference to the "regular" firmware (I think the one I'm currently using was linked in kantjer's signature)

Google search only showed firmware updates for a tablet which seems to be called H2O :laugh:
[ONE Android Development] adinkwok:
All the officially released OSs by OnePlus come with different firmwares. OxygenOS has its own, CyanogenOS has its own, and HydrogenOS has its own. H2O is usually referring to HydrogenOS. Some people experience different upsides and downsides to the different firmwares.
[ONE Android Development] wingedpanther:
Exactly.I've used h2os's and cm's but cm's fw is working well on my device
[ONE Android Development] middendorp:
Just wanted to say that i'm really satisfied with the build by [MENTION=592770]gaspolo[/MENTION] which gave my oneplus a new feeling. Would be nice if you provide new builds with security updates. Thank you so much!
[ONE Android Development] gaspolo:
:) i use it as daily rom
[ONE Android Development] middendorp:
[MENTION=592770]gaspolo[/MENTION] will u provide an update especially because of security fixes?
[ONE Android Development] gwindlord:
Here is my recent build (built for myself), just in case if someone is interested:

SlimSaber odexed, built with UBER 4.9;

Based on AOSP 5.1.1_r37 with April and previous security patches;

Sultan's CM13 kernel without upper freq underclock, built with UBER 6;

user build profile instead of userdebug for better speed (need to flash SuperSU);

SQLite 3.11.1;

Removed AudioFX, KernelAdiutor, SlimOTA, ScreenRecorder, Eleven, AOSP-browser, wallpaper packs;

Added NovaLauncher, CameraNextMod, CMFileManager;

Custom Chromium Snapdragon M46 (full Google sync, internal ad-blocker, package name is Chrome Beta - which allows to apply layers for Chrome Beta);

Custom SnapdragonCamera (with grids and RAW shooting for both front and rear cameras - use BayerQ10RGGB format and "Save DNG" option to get good DCIM/Camera/raw/*.dng photo);

Fluence and wideband calls enabled (work fine for me);

Adaptive LMK, F2FS support, Slim non-intrusive calls;

Sultan's patches;

Auskunft people search provider;

Call barring feature;

Changelog in Settings - Advanced - Build changelog;

Increased media and ear speakers volume;

Some small under-hood fixes;

Also I like IT Crowd ;)

MD5: https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160405-0927.zip.md5

ROM: https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160405-0927.zip
[ONE Android Development] gordon.shameway:
Thanks for the build, going to try it when i have time.

Would you mind sharing chromium build, so one could use it on mm roms? Very cool that its themeable!

Regards!

#whiteuimustdie
[ONE Android Development] gwindlord:
The browser in the ROM is built as system one, hence it is not just a single apk and you cannot take it from zip directly. So please use this link for separate browser download: https://dl.dropboxusercontent.com/u/66673431/SWE_Browser.apk

Also just to remind that on MM you will need to grant permissions to browser, as it is described here.

And well, it is not 100% themeable, as CAF Chromium has a bit different interface, so overlay applies there partially (at least ones I had). I did not want to set name as just Chrome, because it can conflict with installed real Chrome, and it seems there are no overlays for Chrome Dev.
[ONE Android Development] gordon.shameway:
Thanks a lot! Really appreciate it mate!

#whiteuimustdie
[ONE Android Development] abhibnl:
I really appreciate it alot mate. I was waiting for an updated build of slimsaber 5.1.1. I'll certainly flash it. However just one request if i may, could you please build a deodexed build as well if you have the time available? I'm no expert but i think the layers wouldn't have any issue with the odexed at all and i know it'd be lighter on the ram as well. But since we know deodexed provides better modification support, so just checking if you can build a deodexed version as well?
[ONE Android Development] joefso:
[MENTION=4921047]gwindlord[/MENTION] downloading now - does the rom incude the opengapps gconfig patch? I like webview google
[ONE Android Development] gwindlord:
[MENTION=558778]joefso[/MENTION] I'm unaware of this patch unfortunately, so probably no. Is it the one, which is specified at OpenGapps page for 6.0 gapps?..
[ONE Android Development] joefso:
Just tried it with the gapps config and it works! The page states that CM has incorporated it in their repos... :)

thanks for the build!
[ONE Android Development] IronJacob:
Seems really interesting...i'll flash this in next hours.. Thank you!

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] gwindlord:
Could you please try the modifications you like as is?.. Technically it is possible to build the deodexed one, but it is a bit uneasy for me and I'd like not to do it without real necessity.
[ONE Android Development] chetchuakaka:
i'm using full f2fs with your rom, it very very smooth and the battery is very friendly. tks very much.
[ONE Android Development] abhibnl:
Well i don't have any specific modifications that i use. I was just checking with you to make sure if the odexed build can be an issue in any system modifications. And one more question if you won't mind asking, does this build has in-built dpi changer? I have noticed that you have made the build as user-build rather than debug so local.prop method won't work to change dpi without touching build.prop
[ONE Android Development] gwindlord:
Well, I've tried xposed on it, and it worked fine, but it was more than six months ago, so this can change. And yes, on-the-fly dpi changer is located in screen settings.