yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] magnamentis:
no problems with synapse's functionality but i second your opionion about Xes and √marks, not only because they, for my gusto, ask too many times to be touched (needy obviously haha.. ) but also because in some situations they are counterintuitive. once the X makes things to be applied and mostly the √ does that. the app is great and has a huge potential but is also WIP, so i'm sure this will become even better in the future. about your settings not sticking, sorry that i have no better answer than mine do and always did ? no idea :(
[ONE Original Android Development] BoOsT:
Thanks magna! You read my mind lol I'm trying synapse again. I uninstalled deleted folders and am doing a clean install. ;)
[ONE Original Android Development] _Beni_:
Yes, but-80mV was working fine on last kernel, now - 50mV seems to be max, sorry i'm to lazy to power on the laptop.

Sent from a OnePlus One with Mahdi's ROM and AK
[ONE Original Android Development] jgcaap:
You cannot say is working fine on previous versions. In other to stress test you have to remove the touch boost, and activate on-demand governor, and limit test by step. Because when you have touch boost or interactive the governor will just be a few time on each frequency and it'll be hard to give an error in order to boatloop.

In the new kernel, v 40 with is beta, according to the tests is a bit unstable but I cannot comment the reason as yet I didn't discover why. The only way to know is by using default settings on voltage.

Been doing stress tests with this kernel for a while now. I am waiting for an update to see if we are able to eliminate the spontaneous loop . Wich happens to some users.

The stables are 0.38 and 39. I am sure ak will solve this quickly with everyone's help.
[ONE Original Android Development] nathlynn22:
Does restoring from a backup before I flashed ak kernel remove ak kernel? Is the cm11s kernel included in the nand I made?
[ONE Original Android Development] acuicultor:
Restoring a backup means this, you restore what you have at the time of the backup.

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] nathlynn22:
Hmm OK I didn't realise restoring from a backup would bring back the current kernel I had at that time. That's great then. Thanks
[ONE Original Android Development] david23c:
Yea when you restore the boot partition you're restoring the kernel at that time. If you want to keep your current kernel you can uncheck the boot partition before restoring and you'll keep the kernel, but this is not recommended since your configuration at that time is for the kernel at that time. This incompatibility might cause overall instability and other problems.
[ONE Original Android Development] funCrash93:
[MENTION=3685904]ak[/MENTION] switched to SmartMax, problems with PowerAMP seems to be solved... at first glace at least...

for me speaker sound quality (via PAMP) was on Slim...

dunno, will further test. :)

btw, MAHDI 09/03 + AK40b5

Send from my bacon.
[ONE Original Android Development] ak:
thanks a lot. :good:

<>
[ONE Original Android Development] teh roxxorz:
Still no problem here on the latest beta, smooth like silk.

Sent from a tablet thingy
[ONE Original Android Development] ak:
pre-changelog:

4f4e4ff636138f33afdfbf2f06622e67a59cecc1 Kernel Version: ak.040_b11.opo.cm11
012800f95cc259fcc46e2459aca6ac2c70628e0d arm: msm8974.dtsi: increased limit-temp for throttling status
474b9b7343f60437b3273bc2135dbdf1d0604fba asoc: msm: Fix compress capture
0578296f7c016448a9aa65fcf9fc16feb9c306f3 msm8974: Add UIO region for NV recovery system
b623a995128ebde5e367fcf3f0fc0f0f5f1c216a Kernel Version: ak.040_b10.opo.cm11
9fc74702f891993b7d18b6c307a387aeaaf31504 arm: msm8974pro-pm: Allow power collapse as minimum l2 gdhs mode
0330d38be962cc38498a6c4ccbafa37f8de979a4 lib/lz4: correct the LZ4 license
da97babd1a675f00cbcdfccecab4c7f9dfbecd68 mach-msm: cpufreq: set safe limit when initializing drivers
732267873e66bda0a1a12d1872f884bfeb8d53f2 Kernel Version: ak.040_b07.opo.cm11
c079c7b1b09c784d23600b5918308e4640c10d57 Remove more kernel debugging
[ONE Original Android Development] _PrEzi_:
ak please don't name me by my details.

You're welcome. As I've said - have a beer (or two ;) ) on me.
[ONE Original Android Development] ak:
fixed ;)
[ONE Original Android Development] jgcaap:
dam.. Great spoiler hehe.

waiting for new edition to flash. Hope is more stable :)
[ONE Original Android Development] ak:
The kernel is stable. no problem so far with cm11 nightly. i have tried also your settings.
[ONE Original Android Development] jgcaap:
ahhh . Perhaps with CM11S is not stable. :( oh wanted to keep mostly stock . I'll test again when you upload new kernel
[ONE Original Android Development] HTCTOUCHPRO91:
I'm back to STOCK + Ak nighlty and I really love it ;) Rock solid and so much battery :victory:
[ONE Original Android Development] jgcaap:
can you share your processor version just to compare information ? Thanks!
[ONE Original Android Development] BoOsT:
MORE STABLE? What issues are you facing? I've found zero on latest Beta. Please, post all of your issues here so that we can determine the problem. Im always happy to help if I can.
[ONE Original Android Development] kecinzer:
Great news!
[ONE Original Android Development] jgcaap:
reboots... in one day got like 5/6 reboots.

day 13/09 was my last day testing version 40.

https://www.dropbox.com/sh/mnobhvtxmxesu50/AAD44O4vlEvqBtVEmZxAiLQwa?dl=0

I canceled the undervolting...

Since i do not know what it is... Perhaps the voltage for some frequencies on this chip (PVS7) we need to boost a bit more voltage... Thats the other idea i got...
[ONE Original Android Development] BoOsT:
Do you prefer cm11s? Over a ROM such as mahdi or other custom ROM?
[ONE Original Android Development] Glatzi:
Regarding reboots I've found out that Synapse sometimes seems to be quite foolish in choosing e.g. more than one hotplug cpu driver (e.g. MPDecision & CPU Boost Driver enabled at the same time). Happened to me; Synapse now resets all settings after installing a new kernel and the default settings seemed not to be very plausible...

---------- Post added at 03:18 PM ---------- Previous post was at 03:15 PM ----------

I'm having multitouch issues with CM11 v40_b08 and crdroid b5. Only 2 touches at the sametime are recognized. Realized it when I was playing Leo's Fortune. Installed MultiTouch Tester from Playstore and it seems to be messed up. Kernel or rom issue? I'm going to revert to a previous kernel version and will see if this helps....

Edit: [MENTION=3685904]ak[/MENTION] installed v40_b05 and multitouch is fine again?!
[ONE Original Android Development] ak:
I dont have touch nothing related to touch, probably kernel is updated to last cm11 but madhi no. :good:

My rom is cm11 nightly - 15/09
[ONE Original Android Development] Glatzi:
Not using mahdi ;)

Cristianos crdroid build is from 14th of september, changelog states that it is synced with CM11 nightlies & new touch firmware commits are included. Link Google Plus Posting
[ONE Original Android Development] ak:
for now im using nightly .... too problems with custom roms.
[ONE Original Android Development] Glatzi:
How often do you update your nightly CM11?
[ONE Original Android Development] ak:
every day :angel:
[ONE Original Android Development] Glatzi:
:D OK where do you get from? directly from CM?
[ONE Original Android Development] gulp79:
I'm too, now waiting for today M10 (maybe there is some problem on One, for others device is already out).

Anyone is interested/able to build a plain CM11 nightly with sabermod/graphite/Archi's optimizations?
[ONE Original Android Development] jgcaap:
i wish someone would do with Archi... will be the only thing pulling me out from stock!
[ONE Original Android Development] nazfalas:
http://download.cyanogenmod.org/?device=bacon

You can get the nightlies right there. After you've installed the latest nightly I would recommend using the CyanDelta app from Playstore.

It allows you to only download the difference (=delta) between the currently installed and updated nightly (=usually <20MB) and can also automatically flash along with kernel, SuperSU, etc. (under settings).

That's the way I use - switched back to CM nightly from Vanir...
[ONE Original Android Development] ak:
do you have the link to CyanDelta app? is it from official cyano?
[ONE Original Android Development] jgcaap:
the nighlty have same stock apps as stock?
[ONE Original Android Development] nazfalas:
Of course:

http://www.cyandelta.com/

https://play.google.com/store/apps/details?id=com.cyandelta

And no, not official CyanogenMod work, but I've been using this with CM for a long time now. Works very well.
[ONE Original Android Development] Glatzi:
Found two of them:

https://play.google.com/store/apps/details?id=com.cyandelta

https://play.google.com/store/apps/details?id=com.paolinoalessandro.cmromdownloader

They don't seem to be directly from CM...

What can you say about stability with the nightlies? Often got serious bugs? Is headups & peek integrated? Really dont whant to miss them anymore :D
[ONE Original Android Development] ak:
No problems for my personal use, you have headsup, no peek i think.
[ONE Original Android Development] gordon.shameway:
Yeehaa! CarbonRom has finally arrived!

https://carbonrom.org/downloads/?device=bacon&type=nightly
[ONE Original Android Development] nikzDHD:
Nice good to see another rom. I remember using Carbon ages ago on my older devices took it for a spin on my N7 and it's just how I remember it.
[ONE Original Android Development] Vortex1969:
New official Carbon ROM running great with ak b08..
[ONE Original Android Development] kd8bny:
[MENTION=3685904]ak[/MENTION] Was there ever any answer for the washedout colors on beta 8? Was in the the partial display update?

Thanks!
[ONE Original Android Development] drp1:
Is this the 9/16 nightly? Or some other version?
[ONE Original Android Development] :
Do you update and then flash your kernel every day?
[ONE Original Android Development] ak:
Yes

ak@a0001
[ONE Original Android Development] ak:
Probably you have enabled one of this: cab sre ce.

You can try to disable sre or ce.

ak@a0001
[ONE Original Android Development] Vortex1969:
Yes the 9/16 nightly.. They just opened there official thread.
[ONE Original Android Development] kd8bny:
Problem still persists when disabled. CM control doesnt change the values either. Worked in B05

Thanks
[ONE Original Android Development] magnamentis:
fix included in next nightly

the reactivation of color control settings is under way ( you can look it up in the nightlies page:

http://www.cmxlog.com/11/bacon/

and more goodies are incoming
[ONE Original Android Development] Nagasaky2x:
Any place to know what this governors do?

smartmax

smartmax_eps

interactive_pro

slim

ondemand_eps

I can find explanations for other more usual ones, but I can't find anything about this ones. Trying the kernel again as I had some random reboots with previous versions (AK032 b10 was the one I used earlier).
[ONE Original Android Development] jgcaap:
Question. When you tested, how long was it? Because the reboots are random while we use.
[ONE Original Android Development] magnamentis:
are you ready haha...

if you are really interested to find out somehting do the following:

a) boot into recovery

b) use the UKM uninstaller ( from the op )

c) uninstall synapse

d) flash rom and kernel or only kernel ( both is better )

e) go with default kernel settings for one day

my promise: no reboots, conclusion, reboots come from tweaking and reminders from earlier tweaks ( dirt )

i cannot explain why after heavy tweaking it can be a little effort to really get ALL defaults back but only the above procedure gave me

a clean restart with the kernel and it's sub-tools (ukm/synapse)

EDIT: my reboots happened by the way when i started to play with those "hero" memory settings and such. no blaming, just sharing my experience :)
[ONE Original Android Development] ak:
Not so long ... Because I'm flashing ROM and kernels every day ....

ak@a0001
[ONE Original Android Development] RobbieL811:
I was actually thinking about doing a Sabermod CM build w/ optimizations & all, but I'm not sure that I could devote enough time to it to build it every night. I already have a lot going on.
[ONE Original Android Development] ak:
It will be fantastic my friend ...

ak@a0001
[ONE Original Android Development] Setting.Out:
Could you build the 11s or M versions?.. Less building.. :)
[ONE Original Android Development] chikimonke:
Nightly could be a bit much, but maybe a weekly? However, if it means taking away from your Slim builds, then I selfishly vote no :D
[ONE Original Android Development] ak:
[emoji16]

ak@a0001
[ONE Original Android Development] RobbieL811:
It won't be 11s. It will just be built from CM's nightly branch.

I will see what I can get together when I get back home. Will try to get a build up tonight. We'll see. If people wanna use it, maybe I'll open up another thread.
[ONE Original Android Development] om22:
I use slim which is basically a smarter ondemand. Smooth! Don´t know about the other ones.
[ONE Original Android Development] ak:
Yes ... I think New thread is the right way ... And if you want I can help to give all the support for users for resolve problems. Thanks a lot my friend.

ak@a0001
[ONE Original Android Development] RobbieL811:
That would be awesome. I'm already setting everything up remotely via my 1+1 lol.
[ONE Original Android Development] DerRomtester:
[MENTION=3685904]ak[/MENTION] is sabermod 4.8 booting with -O3 optimization?

Gesendet von meinem A0001
[ONE Original Android Development] Setting.Out:
Sign me up as a tester.. ;)
[ONE Original Android Development] jgcaap:
Hehe Ok. I'll do a new flash and try again =)

---------- Post added at 10:25 PM ---------- Previous post was at 10:21 PM ----------

This issue happens only after some use. This makes jump some kind of protection of the watchdog timer, which is a chip protection. I'll find the issue =p hehe if happens again I'll share logs.

---------- Post added at 10:27 PM ---------- Previous post was at 10:25 PM ----------

I would love if was archi... :( lol (request hehe)

---------- Post added at 10:46 PM ---------- Previous post was at 10:27 PM ----------

Flashed again. All stock Except logs..
[ONE Original Android Development] shaker2k:
Your awesome bro! Count me in!
[ONE Original Android Development] elitekernel:
Ak, sorry for the Nooblike questions; keep in mind this wasn't my first rooting a phone, but my first time flashing a ROM & starting to digg in. least im honest ;)

Details;Mahdi ROM 9/03 release; twrp recovery. ( All I did was root, flash mahdi, superuserzip,scrollingmod No issues at all :))

Questions

1.I'm running Mahdi ROM 9/03 release, when flashing ROMS, do they essentially re- flash everything (kernel,radio,etc) or when you go from ROM to ROM just the ROM flashes? - might give me a better understanding

1b. Did my kernel change when i flashed Mahdi ? What kernel do i have to flash before yours ? - Mahdi or the stock cm11s kernel ?

---------- Post added at 11:10 PM ---------- Previous post was at 11:05 PM ----------

@ak is there a little detailed guide on flashing your kernel ? or is what is on the first post all i need to know ?

Anything needed please tell this noob, so i dont brick my phone. lol thanks bro.
[ONE Original Android Development] venky716:
Mahdi ROM won't change your radio only the system and kernel will be changed to Mahdi.

To flash AK kernel just flash the CM11/AOSP zip from the first post after flashing ROM zip in recovery.

You can change ROMs by factory resetting from recovery and flashing a different ROM zip.

Hope this helps. Happy flashing.
[ONE Original Android Development] Heisenberg:
When flashing a ROM it always flashes the stock kernel as well, otherwise your device simply wouldn't boot. So if you update your ROM you will need to flash whichever custom kernel you are using again afterwards.

Radios aren't usually flashed with custom ROMs, CM11 nightlies are the exception to that rule (some flash radios).

If you update your ROM the stock kernel is also updated (as stated above) so you can skip that step in the instructions. The only time you need to flash the stock kernel before flashing AK is if you were previously using another custom kernel (like Franco).

The instructions at the start of this thread are all you really need to know.

Transmitted via Bacon
[ONE Original Android Development] SuRPasser:
Hi everybody, what scheduler is optimum? And what about 2.8 Ghz, should i use it as max value of the processor of Oneplus?
[ONE Original Android Development] Heisenberg:
You need to test for yourself to find which scheduler works best for you. And it's your choice whether you overclock or not, but remember that overclocking is pushing the CPU past its designed limit.

Transmitted via Bacon
[ONE Original Android Development] elitekernel:
Thanks guys, so tell me if i got this right, if i flash to another ROM, say PA, - i would have to re-flash my custom kernel (ak,franco, etc.)

if

i wanted. Say for instance, what kernel is on my phone now ? after flashing Mahdi...

Do I have to clear cache or wipe anything in between kernels ? & Roms ? - Besides the factory reset,

When do i wipe dalvik, cache, and or other wipe settings ?

makes me feel alot more confident about flashing.... gonna do a little bit more research. thanks guys,.
[ONE Original Android Development] ninjanurse:
That would be amazing, just do as often as new AK kernels..that way its easy and awesome.. Not that I could do anything, yet. You guys are like phone phoenix's who resurrect my phone every time I flash.
[ONE Original Android Development] Heisenberg:
Correct

When changing ROMs you should always do a full wipe (system/factory reset/cache/dalvik cache). When flashing a kernel you only need to wipe cache/dalvik cache.

Transmitted via Bacon
[ONE Original Android Development] jgcaap:
Got Reboot, with last kernel on cm 11s testing with ondemand.

https://www.dropbox.com/s/ig1rv23pk913y22/last_kmsg-2014-09-17.01.02.04.txt?dl=0

Next test will be with interactive .

Stock settings.
[ONE Original Android Development] BoOsT:
DO IT DO IT DO IT!! I will switch BACK to CM lolz
[ONE Original Android Development] RobbieL811:
I am working on it now. It's a little different than compiling aosp w/ Sabermod. Running into a few problems. I'm not going to sleep until I figure it out! Lol.
[ONE Original Android Development] BoOsT:
Omg I remember when i use to build/port miui from CM. Talk about fun!
[ONE Original Android Development] elitekernel:
When changing ROMs, Full wipe as mentioned then flash new ROM correct ? In that order.

When flashing kernels, wipe cache/dalvik cache after or before flashing the kernel ?
[ONE Original Android Development] BoOsT:
Go buy a Cuba Lima Monster energy drink you'll be fine ;)

---------- Post added at 08:07 PM ---------- Previous post was at 08:05 PM ----------

Correct order. And wipe before you flash kernel. You may also wipe after if you wish.
[ONE Original Android Development] elitekernel:
Now i dont know weather to pick AK or FRANCO :(
[ONE Original Android Development] Tunasty:
If you would just read the op, 90% of your questions will get solved.

-Tunasty
[ONE Original Android Development] chachin:
[MENTION=3916928]robbie1811[/MENTION] could you be awesome and build DarkUnicorns rom too?
[ONE Original Android Development] chayjinn:
ak.040_b08.opo.cm11.zip

ak.040_b05.opo.cm11.zip

i am facing random reboots on this 2 kernel.. anyone facing same issue with me ?
[ONE Original Android Development] prstorero:
Wiping caches doesn't affect a kernel so you really don't need to wipe them. I've been flashing kernels for years without wiping those and never have an issue.
[ONE Original Android Development] chikimonke:
As awesome as he is, I have a feeling this won't happen. He's one guy doing it as a hobby. I'm sorta surprised he's taking on CM to be honest. He's also supporting builds for N5 and N7v2 with his Sabermodded Slim builds if I remember correctly. He is, however, generally willing to help you get setup your self. Or do a search for the Slim Builders Collective, lots of smart folks in that thread that can help you get up and running.

Found the link for you http://xdaforums.com/showthread.php?t=2861778
[ONE Original Android Development] BoOsT:
Is the app data not stored in the cache? I agree it isn't always needed but good practice to avoid any issue that could possibly arise.
[ONE Original Android Development] otisman:
But when you wipe cache don't it format too fresh base?
[ONE Original Android Development] treChoy:
Pretty sure that the latest CM Nightly breaks compatibility with custom kernels. With a custom kernel installed, the baseband is unrecognized, so WiFi, Bluetooth, Cellular Connectivity, etc., are all non-functional. People have been having issues with Franco as well.
[ONE Original Android Development] ak:
Strange, im using nightly without problems.
[ONE Original Android Development] treChoy:
I can only confirm that one other person was having the same problem as I had, and that was with Franco. Are you using your latest beta?
[ONE Original Android Development] ak:
Yes, probably related to the fact im using updated kernel, today

I'll upload a new kernel then.
[ONE Original Android Development] ak:
Logs = last kmsg?

Previous kernel?

configurations?
[ONE Original Android Development] ak:
I dont see problems related to kernel.
[ONE Original Android Development] oriveradel:
Just experienced same problem no WiFi, etc
[ONE Original Android Development] prstorero:
Some is, but a kernel doesn't know what cache and dalvik cache is, so generally wiping them does nothing in terms of kernels.
[ONE Original Android Development] stab244:
WiFi works for me on latest CM nightly, but not cellular. Guess I'll wait for a kernel update.
[ONE Original Android Development] saikm:
cm11 rom also have
[ONE Original Android Development] elitekernel:
okay, how to i undo settings in synapse, how do i revert to original settings ?

---------- Post added at 06:44 AM ---------- Previous post was at 06:42 AM ----------

@chikimonke [MENTION=3685904]ak[/MENTION] how do i revert any settings made in synapse ? i did not screenshot
[ONE Original Android Development] chikimonke:
2 options. Go into Synapse Settings and uncheck set on boot, then reboot. Other option, go to the Tools tab in Synapse, scroll down and select Clear Synapse Data. Reboot. 3rd option for the future, save a profile of the default settings and you can load up the default profile whenever you want to reset.
[ONE Original Android Development] elitekernel:
Also, Disable HW overlays settings unchecks unreboot fix ?
[ONE Original Android Development] Tunasty:
If you're not on cm11s and using the latest kernel, then yes disable HW overlays.
[ONE Original Android Development] elitekernel:
yes it stopped all the screen glitches, but it resets the option on reboot, any fix for this ?
[ONE Original Android Development] ak:
new kernel online

[ KERNEL v.040_b12 - NIGHTLY ]

ak.040_b12.opo.cm11s

ak.040_b12.opo.cm11

[ SMALL CHANGELOG ]

removed some debugging

allow power collapse for l2 gdhs

limit-temp for throttling set to 70C from 60C

make default lmk debug messages useful

merged with cm > 17/09/2014

ecc ecc

Please press Thanks button and rate thread. :p
[ONE Original Android Development] ak:
I think you can add it to your build.prop.

http://xdaforums.com/showthread.php?t=2664332
[ONE Original Android Development] Sick1:
First thanks fornthe best kernel for my use on this device.

Question: Is there anywhere i could "echo" any thermal throttling limits? Ive now ran SoC temp at aronnd 53 celsius under heavy pressure which is amazingly cool IMO, and after you raised the throttling temp i havent tested yet but wanted to know if it can be tweaked if necessary?
[ONE Original Android Development] Tunasty:
@ak, what rom are you running these days?
[ONE Original Android Development] ak:
nightly 17/09
[ONE Original Android Development] RobbieL811:
Initial cm test build is almost done compiling. I think I might have worked out all of the errors. I THINK!!! Lol.
[ONE Original Android Development] ak:
if you want im here for testing.