yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] taufiqs:
try flashing the right modem with twrp 2.8.6.0 or via fastboot. Might be come from proximity issue due to improper modem download when came from different version of android or rom.
[ONE Android Development] daltonhrrll:
Good looking ROM. Flashing now.
[ONE Android Development] DrBoleg:
Hi

I'm little bit confused about the downloads, cant find the download for A0001 or should I flash the d850/shamu one?

Thanks for help.
[ONE Android Development] buzzqw:
look here http://blazingphoenix.in/mzo/Turbo/

BHH
[ONE Android Development] hearmeart:
i don't know which one i must download for my OPO shamu or the other one :/
[ONE Android Development] parvesh:
[MENTION=6304619]MZO[/MENTION] hw r u sir, I have been away so wanted to check any luck on the build server and able to build, as only issue I am facing and its mentioned earlier is GPS one. I am on 19th build clean flash all stock, phone not able to find location both on Wifi and Mobile data :)
[ONE Android Development] Juanmiwow:
OPO is Bacon. Do NOT flash shamu, it's not for OPO!!
[ONE Android Development] MZO:
No the 19 is the last build. Haven't been able to make another one since then... :(

Transmitted via BACON
[ONE Android Development] yot2703:
So... the ROM is dead?
[ONE Android Development] MZO:
No, I hope I get a new build lol. I haven't stopped support yet. consider it dead once the thread is closed (not yet)

Transmitted via BACON
[ONE Android Development] MZO:
NEW BUILD IS UP!

Transmitted via BACON
[ONE Android Development] popliuc:
Gps issues are fixed? :confused:
[ONE Android Development] AmyClaraRose:
Until such times that MZO gets his own computer to build there will be no more builds as bacon been removed from server builds sorry all -Amy-Clara-Rose Nexus 6 + 6P Maintainer
[ONE Android Development] MZO:
Yea, I guess time for me to leave

Transmitted via BACON
[ONE Android Development] MZO:
Yea I got nothing to build on, sorry! :(

Transmitted via BACON
[ONE Android Development] Barnett:
Where is the new build?Can you give me the link?
[ONE Android Development] Fufu2:
Hallo MZO i try to download your Rom but it comes error 404.

Please tell me other download .

Thank you
[ONE Android Development] SynisterWolf:
OP closed. No longer supported.
[ONE Android Development] Spider-Vice:
There are two versions inside the download folder, one that says CAF and another that doesn't say CAF, so which one is it?
[ONE Android Development] Setting.Out:
Lol... Really?.. :)
[ONE Android Development] Spider-Vice:
This is an AOSP ROM according to the OP, so I'd assume it's automatically based in CAF sources. But there's one with and without the CAF suffix. I don't see where the surprise is.

I guess I got my answer anyway, thanks.
[ONE Android Development] MZO:
Permissive by default. You can change that you know.
[ONE Android Development] MZO:
The one with the CAF suffix is the one you're looking for. Moving the older one to obsolete directory... Thanks for pointing out

P.S. I'm giving f2fs another go.

Edit: don't use ones in obsolete folder. The main folder ones are the ones you want (y)
[ONE Android Development] aboicu:
Hi,

is this rom available for OPO 16 GB or only for 64 Gb?

Thank you
[ONE Android Development] MZO:
Both
[ONE Android Development] aboicu:
Thank you

Coming from this ROM (http://xdaforums.com/oneplus-one/development/rom-cm-12-builds-t3045053). After wiping in TWRP2.8.6.0 system, data cache and dalvik the phone (16GB) is booting from 15 minutes. Is it normal or is bootlooping?

LE: Maybe i need another firmware?

LLE: It's bootloop for sure cause it's still booting

Any advice?
[ONE Android Development] MZO:
F2FS

New Experimental is UP...

Added F2FS (beta, needs checking) to /data and /cache

Need tester
[ONE Android Development] MZO:
Are you running f2fs on any partition? I don't see why it should bootloop
[ONE Android Development] crisis_trustee:
Have you really made new f2fs build (Turbo-bacon-3.1-OFFICIAL-03-26-2016-F2FS.zip)?

And what is the file librmnetctl.zip in folder Experimental?

Link - https://www.androidfilehost.com/?w=files&flid=52846
[ONE Android Development] aboicu:
Sorry, no. I have ext4. My bad

Any solution ?
[ONE Android Development] Jazz365:
Looks promising. Does it have of screen gestures like torch n music?

Thanks
[ONE Android Development] MZO:
No, this ROM uses tipsy tree and they have disabled it for now. They'll be back once they bring it back.

[MENTION=5165039]Setting.Out[/MENTION] tried a build with those gestures and ended up with lots of force closes.
[ONE Android Development] MZO:
Aah could you try pulling logcats?
[ONE Android Development] MZO:
Never mind that... It was for data fixup. Now I've uploaded my F2FS zip. You're ready to test :)
[ONE Android Development] aboicu:
Where should I take? From TWRP?
[ONE Android Development] MZO:
No, clear the /data (factory reset it)

Connect the phone to PC

Boot the phone and type this command on adb command line

adb wait-for-device && adb logcat *:E > logcat.txt
[ONE Android Development] aboicu:
ok

LE: Tryed but no logcat. Sorry
[ONE Android Development] MZO:
What do you mean? :/

P.S. Which zip are you flashing? From which date? Try one i uploaded now. I flashed it and everything works
[ONE Android Development] crisis_trustee:
I am ready to test your f2fs build. I am downloading one now.
[ONE Android Development] aboicu:
last CAF from today. Problems with drivers on pc from work. Try the new one. thank you
[ONE Android Development] MZO:
Cool

Na that's working fine for me :) well you can try a different one anyways :)
[ONE Android Development] crisis_trustee:
Dear MZO,

What are gapps - BANKS_GAPPS_6.XX or BaNkS_Dynamic_GApps_6.x.x?

And what is diffenrence between ones?
[ONE Android Development] MZO:
Not much of difference, use any of them!
[ONE Android Development] adibeckett:
Nice rom! Two things

1) I got a couple of force closes with android phone and setup wizard with the 3/26 official build after booting so I had to flash unofficial 3/25 build to make it work. I'm using open gapps.

2) Is there a way to enable hardware buttons instead of software in the settings? I may have completely missed that step.
[ONE Android Development] crisis_trustee:
Dear MZO,

Sorry, but I have bootloop with your new f2fs build.
[ONE Android Development] MZO:
Ah I'll look into it. Thanks for testing!
[ONE Android Development] MZO:
I'll add hardware keys soon, they were just there and went missing lol

I'll look into the force close error. Working all fine here. No errors of any sort
[ONE Android Development] Yoshi_Guy:
Hardware keys and phone fc's

Both of these issues will be fixed in the next build [MENTION=6304619]MZO[/MENTION] does, as I will move volume rocker and hardware keys into one category. Sorry for the inconvenience but this ROM does have hardware key customization, not sure why it disappeared. :)
[ONE Android Development] navispidey:
Even I'm having the same issue
[ONE Android Development] Dward40:
MZO, Physical buttons do not work ( when this will be fixed
[ONE Android Development] MZO:
Very soon
[ONE Android Development] Dward40:
so good)
[ONE Android Development] hearmeart:
wait for the fix launch and more stable it's interesting
[ONE Android Development] martinusbe:
hw keys config is disbled https://github.com/TurboROM-Devices...works/base/core/res/res/values/config.xml#L37
[ONE Android Development] MZO:
Oh yeah, I was thinking why I did that :p thanks.
[ONE Android Development] Dward40:
How to use it? or wait for the update ?
[ONE Android Development] MZO:
Wait for an update, it is source based issue. I'm making the build atm
[ONE Android Development] Dward40:
nice), very good rom
[ONE Android Development] MZO:
27-03-2016

Fixed HW keys

Synced with repos.
[ONE Android Development] Dward40:
The left button opens hw Google now
[ONE Android Development] MZO:
You can change their actions from Settings>Turbo Tweaks>(right most) System>Buttons>Hardware Keys
[ONE Android Development] WhiteWashed:
Rom doesn't boot for me :( I'm stuck at the Rom bootlogo....tried to flash the latest cm13 nightly before the Rom but didn't help. Any ideas?
[ONE Android Development] Dward40:
rom used ex4 file system
[ONE Android Development] MZO:
Which build are you talking about? The ROM is 100% fine here. Lot's of guys are using it.
[ONE Android Development] WhiteWashed:
Latest 27/3/16

I finished reading the whole thread and looks like I'm not the only one stuck at bootlogo...I'm coming from tugapower rom anyway.
[ONE Android Development] MZO:
No clue about it.

Can you check the logs?
[ONE Android Development] WhiteWashed:
Here's a logcat

--------- beginning of main

--------- beginning of system

01-31 02:29:51.405 266 266 E QSEECOMD: : Listener: index = 0, hierarchy = 0

01-31 02:29:51.407 266 266 E DrmLibRpmb: rpmb_init succeeded! with ret = 0

01-31 02:29:51.408 266 266 E QSEECOMD: : Listener: index = 1, hierarchy = 0

01-31 02:29:51.410 266 266 E SSD : ssd_init_service succeeded!

01-31 02:29:51.410 266 266 E QSEECOMD: : Listener: index = 2, hierarchy = 0

01-31 02:29:51.410 266 266 E QSEECOMD: : Init dlopen(libsecureui.so, RLTD_NOW) is failed....

01-31 02:29:51.410 282 282 E QSEECOMD: : Listener: index = 0, hierarchy = 1

01-31 02:29:51.413 282 282 E QSEECOMD: : Listener: index = 1, hierarchy = 1

01-31 02:29:51.413 282 282 E QSEECOMD: : Listener: index = 2, hierarchy = 1

01-31 02:29:51.414 282 282 E QSEECOMD: : Init dlopen(libsecureui.so, RLTD_NOW) is failed....

01-31 02:29:51.414 282 282 E QSEECOMD: : Listener: index = 3, hierarchy = 1

01-31 02:29:51.425 282 282 E QSEECOMD: : Listener: index = 4, hierarchy = 1

01-31 02:29:51.819 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 2

01-31 02:29:51.819 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 3

01-31 02:29:51.819 261 261 E qdutils : int qdutils::getHDMINode(): Failed to find HDMI node

01-31 02:29:51.821 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 2

01-31 02:29:51.821 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 3

01-31 02:29:51.821 261 261 E qdutils : int qdutils::getHDMINode(): Failed to find HDMI node

01-31 02:29:51.822 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 2

01-31 02:29:51.822 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 3

01-31 02:29:51.822 261 261 E qdutils : int qdutils::getHDMINode(): Failed to find HDMI node

01-31 02:29:51.822 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 2

01-31 02:29:51.822 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 3

01-31 02:29:51.822 261 261 E qdutils : int qdutils::getHDMINode(): Failed to find HDMI node

01-31 02:29:51.822 261 261 E qdhwcomposer: hwc_getDisplayConfigs display (1) is inactive

01-31 02:29:51.833 261 261 E cutils-trace: Error opening trace file: No such file or directory (2)

01-31 02:29:51.854 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 2

01-31 02:29:51.854 261 261 E qdutils : int qdutils::getHDMINode(): Failed to open fb node 3

01-31 02:29:51.854 261 261 E qdutils : int qdutils::getHDMINode(): Failed to find HDMI node

01-31 02:29:52.276 367 374 E cutils-trace: Error opening trace file: No such file or directory (2)

01-31 02:29:52.290 367 374 E BootAnimation: couldn't find audio_conf.txt
[ONE Android Development] MZO:
Yeah I've found the issue in your logs. The audio.conf not found issue. But that's not happening with me... Maybe put that from somewhere else
[ONE Android Development] WhiteWashed:
What do you mean?:confused:
[ONE Android Development] MZO:
Nvm, I'll look into it further. Seems weird
[ONE Android Development] WhiteWashed:
Okay, I'll wait then :)
[ONE Android Development] clone217:
Clean wipe

Full wipe ,Flashed open gapps, Work perfect NP.Good rom so far.
[ONE Android Development] praveen7682:
Just flashed the new update and it's good..Thanks for this amazing ROM..Going to stay on this for a week and see how it performs..I don't bother about sot..So far no fc, looks stable..
[ONE Android Development] drmuruga:
Buttons not working.any fix ~
[ONE Android Development] MZO:
Fixed in latest build bro. Flash today's 27/03/2016 build
[ONE Android Development] adibeckett:
3/27 works great. Hardware buttons is fixed however I get a forced close when trying to change the "LCD density" in turbo tweaks.
[ONE Android Development] MZO:
Just checked. The can do it just fine
[ONE Android Development] Juanmiwow:
I love this ROM! Thanks [MENTION=6304619]MZO[/MENTION], everything is working like a charm here!
[ONE Android Development] adibeckett:
I get a "Unfortunately, settings has stopped" message every time I try to change it.
[ONE Android Development] MZO:
I'll check it out after I get another build working with Lightning kernel!
[ONE Android Development] chuna004@hawaii.rr.com:
I'm using the latest CAF version and data not working on AT&T. Everything else working great.
[ONE Android Development] MZO:
Working fine here mate. (Signal strength is weak due to me being 2 floors underground
[ONE Android Development] WhiteWashed:
That's exactly what I did...three times :/
[ONE Android Development] Juanmiwow:
Great ROM, I just miss Quick Unlock and Disable Quick Settings on Secure Lockscreen. What do you think, [MENTION=6304619]MZO[/MENTION] ?

I'll try to search commits later on BrokenOS Github!
[ONE Android Development] iRhyiku:
Well now I'm interested!

This ROM looks really good!
[ONE Android Development] paarkhi:
[MENTION=6304619]MZO[/MENTION], Just flashed the ROM and it is very fluid, smooth. Will check on SOT as I use.

Just one suggestion though, I had a problem flashing SuperSU while flashing the ROM as Secondary in MultiROM/MultiBoot (THIS PROBLEM IS NOT ROM SPECIFIC but it is more like SuperSU specific) I think you are using system-less Supersu which is not compatible while flashing the ROM as Secondary. I had to change the SuperSU with the older version in rom.zip file and it flashed perfectly.

Just to clear few doubts others are having.

1. ROM flashes/Boots perfectly (even as secondary)

2. No Bootloops

3. Flashed Xposed and working fine

4. No crashes/freezes.

5. LCD Density Changer working perfectly (changed to 280 DPI from it)

6. Hardware buttons working fine.

Hope you keep up the good work.

Specially like the Turbo Tweaks organized in tabs :)

Can you please include the Kexec Hardware patch in the kernel so that I can make this ROM as primary and use it with MultiBoot

Thanks for the Wonderful ROM :good: :good: :good: and sorry for the long post.
[ONE Android Development] MZO:
I'll look into it

Uh yeah but I added lightning kernel as stock now which has kexec patch applied..
[ONE Android Development] paarkhi:
is it in the next version because 27.03 has sultan kernel
[ONE Android Development] MZO:
I've changed the host to this... Refer to first post please
[ONE Android Development] paarkhi:
Any changelogs for the version hosted on BlazingPhoenix.in? I've flashed 27.03 from Android File Host, so what's the difference between both version apart from Lightning Kernel Compatibility.

Thanks
[ONE Android Development] drmuruga:
Yes.working superbly. thank you for this excellent rom.
[ONE Android Development] Juanmiwow:
Commits:

--> Quick Unlock:

https://github.com/BrokenROM/frameworks_base/commit/f484915ee5f23f7022deca62de08932bce82393e

https://github.com/BrokenROM/frameworks_base/commit/e5c49111495bdd3333f70f2cd738673fcf417c20

https://github.com/BrokenROM/packages_apps_Settings/commit/0e803aaf2dadc2f01b2bc49cc28da51ecd21dd0f

--> Disable Quick Settings On Secure Lockscreen

https://github.com/BrokenROM/frameworks_base/commit/8d20c985f5c5db5983132dd15971a10f717a8d70

https://github.com/BrokenROM/packages_apps_Settings/commit/7dac330c0e0e75d56f942caa54b4064144cc7040

I think this is everything you need!

Thank you!
[ONE Android Development] MZO:
Nothing else.
[ONE Android Development] MZO:
That will probably speed things up! Thanks a lot
[ONE Android Development] taufiqs:
Hi [MENTION=6304619]MZO[/MENTION], I am using your rom 27/03 and I have this high idle drain (mostly freq on 1109000 or highspeedfreq with interactive stock tunetable) on your stock kernel which I realise that it is based on sultan xda's kernel.

I dont find it in lightning kernel. Is this your reason to use ligthning over sultan's?
[ONE Android Development] MZO:
Yea that's my reason to change to lightning kernel, my frequencies were stuck even after disabling mpdecision hotplug and wiping ART cache. Plus it has many many more features
[ONE Android Development] buzzqw:
any hope for OTA update ?

BHH
[ONE Android Development] taufiqs:
Yups. Couldn't be agree more. Btw, it would be great to provide flashable zip who wants to disable capacitive keys.

If I may suggest dont add too many features at . It's great already. Keep it simple and keep up the good work!
[ONE Android Development] MZO:
No, not possible till all the official builds are merged to one download host. Which might be a problem :p

Well, we can disable capacitive keys via -> settings>turbo tweaks>hardware keys>disable leds>remove their actions manually. This option is far more better as you can keep as many hardware keys on as possible (and disable others)
[ONE Android Development] taufiqs:
yups it'll do but you are still getting the haptic feedback (unless you disable the haptic feedback). Just leave it be. I can live with it LoL
[ONE Android Development] paarkhi:
[MENTION=6304619]MZO[/MENTION], Can we flash the CAF version of Lightning directly from the thread because the version you included is not supporting Synapse?

Thanks
[ONE Android Development] MZO:
This version supports Synapse but you'll need to flash UKM zip, this version is same as that one so no need to bother flashing same kernel again :) anyways it's up to you

UKM ZIP link
[ONE Android Development] nikhil18:
Why don't you include ukm in your ROM from the source just upload the ukm to github and add it to your ROM because there was another ROM which had my kernel with ukm
[ONE Android Development] MZO:
Ah, thanks for suggestion :) I'll work on it :good:
[ONE Android Development] MZO:
New build uploaded. Resynced with manifest.
[ONE Android Development] adibeckett:
Thanks! I can now change LCD Density, I had to reflash root I think.
[ONE Android Development] IronJacob:
Downloading this rom. Seems interesting and i want to try it.

Just one question about the camera because it's not clear: this rom has sultan optimizations or colorOS blobs? Or none of these?

Thanks

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] MZO:
Sultan's camera
[ONE Android Development] psycholyzern:
Hi, I got a little laggy on some few places like changing tab & scrolling in chrome, switching through recent. It is barely can be seen with eyes, but it pretty much affecting my user experience. I can't feel the smoothness. You got any recommendation that I can try?

See this video demonstraying the lagginess

https://youtu.be/XAafzif1d_Q

This ROM behave like it is heavily bloated with apps, or like a phone with almost full RAM usage. There are delay on switching app through recent.
[ONE Android Development] venky716:
Change the CPU governor. Choose any of these Alucard, Blu_active,Smartmax,Yankactive.

They'll all perform better.

If possible [MENTION=6304619]MZO[/MENTION] could you use Sultan's kernel as default, that would be the best balance between battery and performance without having to tinker too much.
[ONE Android Development] MZO:
That's why I used this kernel so you can mod it upon . it is very fast on proper mods

I'm having too many issues in Sultan's, sorry
[ONE Android Development] nikhil18:
Bro flash my caf kernel zip and all your lags will be fixed this happened because the rom did not have cpu boost settings for my kernel and sultans kernel has 1400ms boost which is way too high so you won't notice any lags because CPU is at 1.19 GHz frequency most of the time
[ONE Android Development] MZO:
Yeah, or flash my latest build as I included it from your caf sources :)
[ONE Android Development] darkness_78:
[MENTION=6304619]MZO[/MENTION],finally i can use ur rom. Great rom. No issue here. I have question there are two rom 03/28 is it the same or different?
[ONE Android Development] archer.mekhael:
Anybody else having issues with the alarm clock? If i set it to alarm at a certain time, it alarms and I snooze, the alarm clock app crashes.
[ONE Android Development] hkjr:
Can confirm same happened to me, but removed a rro overlay. Will see what happens in the morning..
[ONE Android Development] cesarp3791:
I installed this zip on 3-28 version, and Synapse doesn't work.. Settings deemed unstable, haven't been able to restore a profile due to "Unfortunely Synapse stopped working", always is the X or tick at the top of the app no matter what i do..

Already uninstalled, wiped data of app, nothing seems to solve this error.. Right now using Kernel adiutor but tweaks do not stick, it goes back to stock after a while[emoji53]

Any ideas? It's the only issue as of now, was hoping to fix it to apply a battery-friendly profile on Synapse, even though on stock settings do not seem to be too much drain..

Thanks!
[ONE Android Development] archer.mekhael:
I just uninstalled the clock via system app remover and installed the google one from app store as a temporary fix.
[ONE Android Development] MZO:
Both are different, they're having different dates too

Github.com/TurboROM/documentation update the bugs list with your error. I'll merge
[ONE Android Development] MZO:
Uh well you could try clearing the dalvik cache as you see I've applied my profiles just fine, running my power saver profile pretty fine. Plus yes I get Synapse FC when I restore my profile but I can then apply my restored profile without errors (after I open synapse when fc closes it), if your profile is constantly giving you FC then make a new profile with same settings.
[ONE Android Development] MZO:
P.S The new rom is up, with ColorOS camera blobs (better camera then CM)
[ONE Android Development] parvesh:
where.. as the link in OP still take to 28/03 build :o
[ONE Android Development] MZO:
Experimental folder

Edit: nvm fixed.
[ONE Android Development] buzzqw:
Hi

i miss the network monitor (show up/down speed).. is present ?

thanks!

BHH
[ONE Android Development] MZO:
It is noted. Will add soon :) please note this s ROM is pretty new. It's maybe a month old and 4 days old on XDA (as old as this thread) so :) it'll take time for features to evolve. Be patient and wait for it ;)

Thanks
[ONE Android Development] Setting.Out:
Looks like my phone needs a Turbo installed.. ;)
[ONE Android Development] MZO:
Haha, P.S. Added more features in that build too
[ONE Android Development] buzzqw:
my phone had already a Turbo installed ! :p

BHH
[ONE Android Development] Setting.Out:
Reverted that CM commit I mentioned?
[ONE Android Development] MZO:
No, at the moment the blobs aren't same as Omni, only photo quality has been improved. RAW is still broken and shutter speed is capped
[ONE Android Development] dwaipayanray95:
Where can I taste the new color is blobs?
[ONE Android Development] MZO:
It's there on the host :)
[ONE Android Development] IronJacob:
Like this rom, no problem at all. Everything is working fine here. And i love all of the features here. I'm also happy you reverted to colorOS blob.

P.S: just sharing a tip i've read on darkobas community on G+: on the camera settings switch a few time on and off on red eyes correction and you'll have more options on the camera

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] MZO:
Uh I don't get the P.S. section? Elaborate please :)
[ONE Android Development] IronJacob:
Sorry for my bad english :)

Just open camera app, go to red-eye reduction and switch on and off a few time to have dev options for the camera

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] dwaipayanray95:
Keep tapping the option and it'll unlock a lot many features!

Could anyone report if the preview on color is lags?
[ONE Android Development] MZO:
Thanks! I didn't knew that haha

And no ColorOS cam doesn't lag :/
[ONE Android Development] hkjr:
I was about to do the same, but removing the layer over the clock, worked.
[ONE Android Development] MZO:
Edit:nvm