yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
No, it is all fine. It came across the right way.

I would never claim, I do not put bugs in my work. That would not be normal.

However, I was quite sure the temperature should be ok. So yes, I will compare with a few other apps etc. Then we will see.

Andi
[ONE Original Android Development] molonad:
now i was able to saw after boot temasek logo but again bootloop

---------- Post added at 07:09 PM ---------- Previous post was at 07:09 PM ----------

now i was able to saw after boot temasek logo but again bootloop
[ONE Original Android Development] andip71:
Ok, then it is the code changes as of this afternoon.

I will not revert that, so please use beta2 unless the roms get an update OR Cm12 teams reverts the commits in their repo too.

Thanks

Andi
[ONE Original Android Development] magnamentis:
1st boot failed, not worth the effort i think, new blisspop iteration has been provided to testers already :)

2nd attempt in process

2nd attempt bootlooping while the 1st attempt booted and went into an immediate random reboot
[ONE Original Android Development] andip71:
The only "interesting" thing is...

I just went back to CM12 nightly of 12.01.2015, and still beta3 works fine on it.

See screenshot.

Somehow very odd, the other custom roms have some things obviously not yet merged in.

Okay, does not make sense to speculate at all.

CM12 nightlies work, this is the good part.

I will now leave here and come back tomorrow morning, checking if CM team has done some activities and if they put up a new nightly again, etc.

Andi
[ONE Original Android Development] acuicultor:
Typo error

Im using beta3 with 1/14 nightly without an issue, im assuming beta3 still works flawesly on next nightlies. I will test and report.
[ONE Original Android Development] andip71:
Beta33...Wow, you are living in the future [emoji6]
[ONE Original Android Development] pa.pn2:
Strange. Bootloop with vanir exodus 1301 build and beta 3. Dirty flashed..
[ONE Original Android Development] acuicultor:
Sorry typo error. On other side, congratulations for your success.
[ONE Original Android Development] magnamentis:
i recommend the following steps to stay up to date:

a) use the little right arrow on the subscribed threads page to resume reading where you left off the last time

b) if you post a reply, click the user name in the quote to get back where you left

like this you will not miss the 4-5 pages of posts about bootloops with v.3 beta3

in short, read the last few pages and follow the basic rule to read before posting
[ONE Original Android Development] pa.pn2:
I just wanted to report that i have a bootloop on vanir. Someone also on vanir has no probs.

Thats all mr.police. I followed the thread don't worry
[ONE Original Android Development] schmitzekater:
I have the same Setup running without bootloop.

I wiped cache and dalvik, flashed the Rom, rebooted and flashed kernel afterwards.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] magnamentis:
you did not mention that, incomplete info provided then, how can we guess that ?

i did not worry but gave correct and useful "recommendations" in non-rude language according to the info you provided

so don't be oversensitive but perhaps provide proper information so that eventual answers don't look foolish in the aftermath. end of subject
[ONE Original Android Development] pa.pn2:
did the same now.wiped cache,system and dalvik before flashing.still bootloop lol.nevermind.went back to beta 2.all is fine
[ONE Original Android Development] artyfarty:
[MENTION=947981]Lord Boeffla[/MENTION] italian translation of your app seems out of updates. can i edit the xml file?

:good:
[ONE Original Android Development] maxver0:
You release so quick we can't keep up[emoji6]

Oneplus One
[ONE Original Android Development] :
cm12 14th nightly seems unavailable for download.

Vanirs Martin commented on possible harbrickrisk with the firmware loaded in it. Any idea of the truth of this?
[ONE Original Android Development] andip71:
Reference? Which firmware is he referring to?
[ONE Original Android Development] :
http://xdaforums.com/showthread.php?p=58161724

here kind sir
[ONE Original Android Development] magnamentis:
http://review.cyanogenmod.org/#/c/84715/

---------- Post added at 09:32 PM ---------- Previous post was at 09:27 PM ----------

http://xdaforums.com/showpost.php?p=58162481&postcount=4366
[ONE Original Android Development] abhibnl:
Hi Andi,

I had two soft reboots one after one in the span of hardly 2 minutes time. For first time i just work the phone up and launched Facebook app and it soft rebooted. Fortunately i had Kernel Logger On so i hope all the information is there in boeffla debug. For second time, i tried to open the Boeffla Debug log file by X-plore and it soft-rebooted. Attaching both log files. Hope it's not the kernel. But it's the first time happening on boeffla after update to stable kernel.
[ONE Original Android Development] Roman91:
Today I sold my one OnePlus (not swallow the little sensitivity and yellow band ...maybe for a G3)

..andd ...why I write here?

because boeffla (firstly like dev) and then like kernel is my only regret :crying::crying:
[ONE Original Android Development] andip71:
Interesting stuff.

From what I know so far, the last two nightlies came with a new firmware, which in the end broke some oppo find7 devices. I couldn't find an evidence for the OnePlus so far.

But I cannot look into it, it is not part of the kernel. So don't know if it can be potentially dangerous for our phone as well.

There was a kernel commit recently, which I merged into beta3, which obviously needs this bee firmware in place. If you have it, all is good. If you don't, boot loop.

Tomorrow I will revert this commit (https://github.com/andip71/boeffla-kernel-cm-bacon/commit/7d84658ddaeea3eeacef3d533ffc8ba6f892230d).

This is not a solution for this nice mess, but should be a safe workaround until all is in line again with cm.

Beta3 is safe to use when it boots, so no worries.

If it doesn't boot, just fall back to beta2 until I create a beta3a tomorrow with the reverted commit.

Cheers

Andi
[ONE Original Android Development] andip71:
Remind me again tomorrow please, then I can send you the xml to translate.
[ONE Original Android Development] andip71:
Which rom are you on?

I cannot look at your files right now, no pc here in bed, lol. Tomorrow.

But cm11 and cm11s kernel updates were so minor, can't make a difference.

Also running for hours at my side, no issues.
[ONE Original Android Development] maxver0:
Did anyone found explanation for various GPU governors?

Oneplus One
[ONE Original Android Development] andip71:
No. If you find something, please let me know...

Andi
[ONE Original Android Development] andip71:
Ok. Battery temperature incorrect will be fixed tomorrow with an update of Boeffla-Config app.

Know already the issue ☺

Andi
[ONE Original Android Development] maxver0:
Faux Simple gpu gov

http://www.androidpt.com/index.php?...ntalx-42-ocuvgpu-ocs2wl2wdt2wl2mthermalbln43/

Oneplus One
[ONE Original Android Development] abhibnl:
Sorry! I'm on CM11s 44S. I don't know the sodt reboots happened in a short span of time.

Well please let us know cause i'm to unable to find any documentation about that. I will try each governor daily as we have GPU time stats now. I would like to use a governor which keeps it at 27mhz for maximum tym possible.

Sent from OnePlus One Powered by Boeffla
[ONE Original Android Development] :
there used to be one called conservative which improved batterylife significantly for me in september, on the early days of ak. would be nice to see it return but on boeffla :)

performance and userspace seems unstable at times
[ONE Original Android Development] maxver0:
Well I think simple Ondemand will be more battery friendly than msm, but that's just my thought.

Is there any gpu freq monitor? Or I need to wait for beta3a :(

Oneplus One
[ONE Original Android Development] Fenvarien:
The new Beta3 kernel runs great with Euphoria ROM build 20150112. No bootloops or other hiccups ;) Thanks again for your hard work Lord Boeffla! :good: :)
[ONE Original Android Development] Mandrake2010:
Time in state deepsleep for cpu and Slumber for gpu max value 100.0s 0,46%.

Wrong calculate time??

Inviato dal mio OnePlus One
[ONE Original Android Development] P1nGu1n_:
I have exactly the same, deep sleep is 100 sec, even though my uptime was 104 hours [emoji14] so I did a reboot and it's still 100 seconds. Running beta 2 and config app released a couple hours ago.

Sent from my phone, please forgive any tpyos.
[ONE Original Android Development] NickosD:
Boot loop on bliss 12/01 with the latest, no problem with previous.

Sent from my SM-T320
[ONE Original Android Development] andip71:
Hehe. Yes, I see it too. Funny thing.

So will have to fix this as well on top of the battery temperature thingy.

Thanks, but has been discussed upside down already yesterday.

Read up.

Thanks

Andi
[ONE Original Android Development] andip71:
Good morning

Good morning folks,

so I see, nothing has changed on CM side.

The kernel repo is exactly having the same code in as yesterday + there is no new nightly than usual. Last nightly is therefore still the one from 12.01., both nightlies of 13. and 14. remain pulled.

So, I would like to ask one of the guys who returned back to beta2 due to boot loops to please test this attached test kernel.

If it boots, I will release it as beta3a and pull beta3 for the time being.

I basically reverted one commit from the CM kernel code which was in question to cause these loops + reverted ramfs back to 12.01.14 nightly for safety reasons.

Thanks for quick feedback how that version goes.

Andi
[ONE Original Android Development] schmitzekater:
Good morning folks.

Speaking of wrong values, is anyone else facing ridiculous high memory usage in the Boeffla app?

Right now it shows that only 110MB are free whereas the system menu shows 1.8Gb free.

Have a nice day. ;)

Edit: will attach screenshots later when I'm at the pc.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
No screenshot required this time. Both are completely right, the Boeffla-Config app and the system menu.

Boeffla-Config app is a kernel control app, so it shows the memory usage the kernel sees.

The system shows the memory consumption from rom view.

And this is by nature not the same. Kernel loads the rom in, the rom itself has an own memory management on top for apps.

So, it will always be different what you see.

I get this question over and over again, so will add it to the FAQ soon (which will then also nobody read, haha).

Andi
[ONE Original Android Development] pa.pn2:
Beta 3 test 2 boots fine for me. Thx
[ONE Original Android Development] andip71:
Sorry to ask again. But you were having a bootloop with official beta3 too?

Just to reconfirm.

Andi
[ONE Original Android Development] andip71:
Boeffla-Config 2.1.64 pushed out

Hi all,

new app pushed out just now.

This fixes the wrong battery temperature and also the wrong deep sleep / slumber calculations.

The latter one was indeed a "funny" error. I put some code in to cap the percentage values on 100% max, caused by rounding errors sometimes. But I put it on the values itself, not the percentage. That is why it was going up to 100 and not further :)

Cheers

Andi
[ONE Original Android Development] pa.pn2:
Jepp. Or did u removed the commits from official? Shall i download this?
[ONE Original Android Development] andip71:
Thanks mate. Then I will recompile it as an official beta3a and I will pull beta3.

Andi
[ONE Original Android Development] CounterC:
I also had a bootloop with beta3 yesterday. I'm on bliss pop 1.6. even worse, after restoring the beta2 I lost all the data of my apps. hooray for titanium backup but still I had quite some work setting everything up again. this makes me quite reluctant to flash the test2 kernel....

can someone please test kernel beta test2 on bliss pop 1.6 09/01?

thanks
[ONE Original Android Development] andip71:
Come on... be BRAVE :)

And for that you always have an up-to-date nandroid backup before you flash something. Isn't it? :)

This is a MUST when doing lot's of flashing. Brings you back to a working phone within 5 minutes again.

I am using the OBackup app to automatically create nandroid backups every night. So I am always save.

Andi
[ONE Original Android Development] DanteGR:
Good morning my friend.

I'm on official cm12 20150112 build with yesterday's beta 3 kernel.

Not facing any real risk right? Should I flash the latest beta 3a that you'll be releasing?

Everything seems to run fine atm

---------- Post added at 08:30 AM ---------- Previous post was at 08:26 AM ----------

EXACTLY the same happened to me with [MENTION=4804871]DerRomtester[/MENTION] kernel 2 days ago.

Flashed latest, didn't boot, tried to flash the one before that, lost all my data (God bless TB as you already said), started cursing lol.
[ONE Original Android Development] andip71:
You can keep beta3. The potential risky firmware is and was never part of the kernel but obviously included in the nightlies of 13. and 14. which have been pulled consequently.

But you still can flash beta3a, so we are all on the same page again.

Andi
[ONE Original Android Development] andip71:
And the explanation is also quite logical. When the boot process is aborted, it can lead to your /data volume become corrupted. This will result in a loss of apps, the setup wizard showing up next time etc.

What do we learn? Boot looooooooooop is never gooooooood :D

Andi
[ONE Original Android Development] CounterC:
thanks for explaining.

so we got one positive confirmation of flashing 3a on rom versions older then 13/01 and 14/01.

i will wait for some more results before flashing :)
[ONE Original Android Development] andip71:
3.0-beta3a

Hi all,

ok, here we go. I pulled beta3 for CM12 now and replaced it with beta3a.

Expected this will work around the boot loop issues on some custom roms for now. At least, until CM brought everything back in line again.

Version 3.0-beta3a

15.01.2015

Note: You need Boeffla-Config version 2.1.64 to use all new functionalities !!!

Reverted an official CM12 kernel commit to work around boot loops on some custom roms

Reverted ramdisk back to nightly of 12.01.15 (CM pulled all newer nightlies again)

If you are happily on beta3, you do not need to flash this. Although I would recommend to be all on the same page again.

Enjoy

Andi
[ONE Original Android Development] marcowind80:
http://xdaforums.com/showthread.php?p=58182493

In bliss thread there is only an update file instead of cm nightly
[ONE Original Android Development] :
fix for that is fastboot flash userdata userdata64 (if phone has 64gb) right?
[ONE Original Android Development] andip71:
Well, a format partition (/data) in recovery should do as well.

The file system can get corrupted, the partition itself should be intact.

Andi
[ONE Original Android Development] :
thanks, spend multiple hours checking in past if I could get chckdisk to run on it lol. Plus numerous flashes of multiple roms for issue no one else had. Now I know I just needed to format the whole thing haha.
[ONE Original Android Development] pa.pn2:
Had a couple of reboots with 3a now.

Sended a debug mail to your info email
[ONE Original Android Development] andip71:
Nothing logged in it which points to a reboot or a kernel panic. Log is clean.

Not much more I can say... apart: Maybe you should do a fresh install to ensure, none of the previous failures have caused any left over issues.

Cannot think of more...

Andi
[ONE Original Android Development] lchiocca:
Andi, just wanted to say: thank you for all the hard word and personal sacrifices that you did over the past years and for the future years to come. I admire your motivation and perseverance that drives you. Thanks!
[ONE Original Android Development] pa.pn2:
Strange. Ill grab another log if it happens again..
[ONE Original Android Development] andip71:
What is your rom?

When did it happen? During sleep = display off? When using some specific app?

I have zero reboots for several weeks now on all my 3 OPOs. Sometimes wonder what is different for some...
[ONE Original Android Development] molonad:
Thanx Lord, you really care about all people , not only about most of people. ? everything is great ☺ everything works
[ONE Original Android Development] pa.pn2:
Im on vanir exodus 1301

The reboots happend when the device was in my pocket while screen was off.

I did not change the setup regardung beta 2

Just flashed katinez UNOFFICIAL twrp 2.8.40

Do you think it could be the recovery?
[ONE Original Android Development] andip71:
No, the recovery is for sure not guilty.

Can you do me a favour and put min cpu freq on 422 for a few hours? Just a test, because with 268 MHz the cpu voltage was very slightly lowered. Not that this is causing an issue in the end, maybe you have a super sensitive phone.

Also, you can try - for a test - to switch off dynamic fsync for some while. Not likely, but... you never know.

Just two hints...

Andi
[ONE Original Android Development] andip71:
Just trying my best for you guys...

Andi
[ONE Original Android Development] pa.pn2:
Ill do that sir.

First test ill raise the min freq

Second ill do the dyn fsync

Thx for quick answers andi
[ONE Original Android Development] andip71:
Curious for the results a bit later :)
[ONE Original Android Development] maxver0:
I just had reboot on lastest version. It happened when i switched to cpubw hwmon gpu governor.

After this reboot i was able to set it successfully with no freeze or reboot.

https://docs.google.com/file/d/0B6BS4V_hlZC7VV9ZZ1ZKYWJBTms/edit?usp=docslist_api

Oneplus One
[ONE Original Android Development] molonad:
I had bootloop when my screen was off, I was medium undervolted I will try without undervolt and test, how can I send you log? Where can I find it? ☺ thanx
[ONE Original Android Development] andip71:
Also log is clean. No indication of a reboot or a reason.

Makes me believe, some roms are not very stable these days.

What is your rom?

Boeffla Config -> Action -> Create debug info file.

But yes, remove any undervolting and overclocking.

When I see it, I will not have further look at it as this can make any device completely mad.

What is your rom?

Andi
[ONE Original Android Development] molonad:
Ok I will not send you it now, becouse I was undervolted, I will try without it and if it will happen I will send, thanx. ☺ I had no reboot like this when I was undervolted on beta2 so I was surprised ☺. Iam going to work, then I will send how all work ☺ thanx for trying to help. Iam on temasek 5.0 linaro.
[ONE Original Android Development] maxver0:
Temasek 4.7. Now I switched to "cache.." gpu governor and my device keeps rebooting after loading system and when (I think) boeffla profile is loaded. I haven't testing it on previous kernel release tho. Managed to change it back to stock gpu gov.

Comparing msm-adreno-tz to simple_ondemand. Simple_ondemand governor is way more aggresive, it ramps gpu freq more often and wayhigher. msm-adreno-tz is way more balanced (more battery friendly).

Powersave same as in CPU, locks down minimal freq.

I haven't tested cpufreq and userspace yet.

Also I played Need for speed most wanted with powersave gov. which locks down minimal frequency and there's was minor difference in smoothnes...
[ONE Original Android Development] truewt:
Like to check, anyone tried vanir exodus with the kernel? Just wanted to be sure
[ONE Original Android Development] r0hit.s3n:
[MENTION=254166]Lord[/MENTION]

My busybox states version 1.22.1 and version 1.23 is ready to be installed but a handle sbin warning, just curious what will it do if I press yes and install the latest busybox
[ONE Original Android Development] andip71:
It could mean, it breaks certain functions of the kernel and the configuration.

Boeffla-Config app and the kernel itself relies on a busybox installed in /sbin. If someone deletes it from there, it will cause issues.

I had a long chat with Stericson on that, and after the chat he put this warning in to not break custom kernels anymore.

So, you can install the busybox, but you should not press Yes here.

Andi
[ONE Original Android Development] andip71:
Well you know. When undervolting you can reach the edge, so any small change can make big differences.

Also, it can be a result of it which comes over the time. "silent data corruption", which becomes apparent after some time only.

It is hard to say, I would really advice everyone who is running into frequent reboots to

- do a fresh install (with formatting system and data before)

- stay away from undervolting for some time

- ideally use CM12 standard, it seems this is causing by far the least issues

Yeah, I never even thought about switching the gpu governor to someing else than the stock governor or simple_ondemand. The other stuff just sounds weird. But of course, playing around is not wrong, you just need to take the consequences and learn.

BTW again: Whenever you have your device not starting anymore due to a misconfiguration - go into recovery, flash the reset zip you find in the boeffla-kernel-data folder and you start with a fresh default profile.

Just remember this tip :)

Andi
[ONE Original Android Development] maxver0:
I don't mind :)

Have you tried switching it? Do you experience reboots too? If yes then i vote to delete these governors to avoid further issues with new users.

Oneplus One
[ONE Original Android Development] andip71:
Yes, the cache...blabla governors were fine. However switching to cpufreq gov rebooted me too.

In general, switching the GPU governors seems to be quite sensative. So I think we should declare that an expert function.

I will check if I can remove the governors which nobody uses anyway, so just msm-adreno and simple_ondemand stay in. Let's see.

Andi
[ONE Original Android Development] pa.pn2:
increasing min freq didnt solve the reboot issues andi

i flashed now updated vanir exodus 1501.lets see if it helps:)
[ONE Original Android Development] andip71:
Check your PM :)
[ONE Original Android Development] molonad:
Ok now is all ok I think, what is exactly silent data corruption please and how is it created? Thanx I will report back in the evening
[ONE Original Android Development] andip71:
What I mean by that...ever unplanned reboot can cause some bits and bytes not be written correctly back.

So for example, the system wanted to write in the app database for youtube app (just an example).

If you do not use the youtube app frequently, you probably only notice one week later, something is wrong. And you probably put wrong conclusions in, because you did a rom or kernel update the day before and think, that caused it.

Now, when you think about that happening to vital system settings of the rom itself, it can silently make the configuration tables corrupt more and more and finally you have a completely unstable system. Kind of a "chain reaction".

That is why I say: Hot reboot, or multiple? Make sure you are not suffering that.

When I have hot reboots during development, I always set back to my last nandroid backup again, to not run into that ever.

Hope I was able to bring my thoughts across in an understandable way...

Andi
[ONE Original Android Development] molonad:
Ok understand, if I will have more and more reboots I will try format all and do a fresh install, thanx for typ

---------- Post added at 11:41 AM ---------- Previous post was at 11:33 AM ----------

Next reboot, when I get back from work I will format all, so clean install
[ONE Original Android Development] andip71:
I mean, one more thing to try, just to be safe.

To ensure, over the time no bad kernel configuration has sneaked in... reset your configuration to defaults.

- either flash the reset zip in recovery

- or start the boeffla config app -> menu -> settings -> app maintenance -> reset app

And yes, if that does not help... more is odd and I would try a fresh setup.

Andi