yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] xeizo:
However things are, I've tried a lot of unofficial CM11:s lately and Temasek V7 in combination with your r3p2-kernel is the best, smoothest, highest perfoming and most stable experience so far. Just keep it up, Temasek and Lord Boeffla has the flow right now :D

I'm very pleased with being able to keep an old phone up to date, I guess my S3 will have to do until at least Snapdragon 805 is out in the wild with most perfomance parameters doubled or quadrupled or even more and in the 5.2-5.4" form factor(Galaxy S5 or whatever competitor there will be, preferrably the one gaining most community support) :)
[Galaxy S III Android Development] tisazalay:
OK, please excuse me for this noob question, is it OK to have 2 different busybox (one in /sbin and other in /system/xbin) the mount in them is different. Can it be causing conflicts?

Thanks.
[Galaxy S III Android Development] JustArchi:
No. Type "which busybox" command to know which you're using.
[Galaxy S III Android Development] Egozy:
Could anybody spare a few words on the pegasusqplus governor? Went over all of Andrei's logs and couldn't fine a clear answer. only changes with time.
[Galaxy S III Android Development] JustArchi:
Holy... ****

Andi, did you do anything with init.d in last noselinux version?

I just found out that all init.d scripts are being double-executed. Now I'm making sure it's not AD-specific issue.

Could anyone please create file 98test in /system/etc/init.d and put inside...

Make it 755 chmod and restart. If your test.txt file contains more than one "1" then... well... :D.

Thank you in advance.

---------- Post added at 11:26 PM ---------- Previous post was at 11:19 PM ----------

Oh well, Couldn't reproduce this issue on any other kernel around. Argh!

ANDI WE NEED YOU :laugh:.
[Galaxy S III Android Development] thearc77:
The experimental kernel for Omni (not Temasek) for test about "No SELinux" do not mount /system on RW Mode. Tested from Android Terminal Emulator, the output for mount is the same from JustArchi script and all my app with root capability cant modify system (X-Plore, ES File Manager, Root Free & pro, Titanium Backup)

I flash again the builtin Omni kernel and I have permissions again.

In other way, I do an adb remount (even with adb shell mount -o remount,rw /system) from my (Windows/Linux) and I have total RW access from anywere but when reboot the access I lost.
[Galaxy S III Android Development] nicesoni_ash:
I read here that few have system not mounting writable problem here, I am having the same while installing xposed framework. Can someone suggest a solution please. I am temasek v7 build and 2.1 beta boeffla kernel for temasek.

Edit: reinstalling busybox fixed my problem.

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] Maceee:
Is there a way to get boeffla sound on CM 10.2 without flashing boeffla kernel? Don't think that I don't like the kernel. I think this kernel is the best for CM and also for Stock Samsung ROMs, but I want to test CM with its Stock kernel. Thanks in advance.
[Galaxy S III Android Development] Mickyman:
Sometimes my sound stutters really bad to the point that i cant hear the music at all. And if I unlock my phone, its gone.

Any ideas?
[Galaxy S III Android Development] andip71:
In root explorer it always worked for me.

But this is really getting weird. And honestly, I am running out of ideas now.

I tried to move to another initramfs, to remove any Boeffla-specifics, even compiled with another defconfig.

No success.

I do one last test, removing all features in the kernel code for a test. Then do not know what it could be anymore.

No, the noselinux version is the same as the normal one, just selinux removed.

And sorry to say: I am starting to a full weeks business trip tomorrow and we have project cutover today. Will not be able to work on anything anymore before end of next week.

Yes, read up. This is a known thing. However there is no solution as the issue is not yet clear in terms of root cause.

No, Boeffla-Sound is a kernel driver extension for the audio driver. So you need to compile it into a kernel.

I mean, yes... other custom kernels include it. So you could try a different custom kernel. But stock + boeffla sound, I have seen nowhere around so far.

How would you expect support if you do not provide at least the minimum on information?

Which kernel? Which governor? Which audio player? .... and and and.

We need information!!!
[Galaxy S III Android Development] Mickyman:
Eh, totally forgot about that hehe.

CPU/GPU: both medium UV.

Kernel: CM-2.1-beta1

Governor: zzmoove - battery

I use Spotify for my music.

Nothing really done with the sound settings besides changing the equalizer profile.

Is there any more info you need?
[Galaxy S III Android Development] Mostafa Wael:
it is the ZZmoove governor limiting the frequencies in the deep sleep, Are you using any soundmods?

here is what to do:

1. select zzmoove (any profile you want) governor in the boeffla-config app

2. open tunables in the app after selecting your governor and set the "freq limit sleep" to 0

OR --> in case you didn't purchase the boeffla-config pro app, so the tunables is locked

1. select zzmoove (any profile you want) governor in the boeffla-config app

2. go to setCPU and go to the governor settings and set the "freq limit sleep" to 0

and Voila!!! You are done.

send your feedback and tell us whether it worked with you or not.

Press the "thanks" button if I helped you.. :D "it will take you less than a second man LOL"

Mostafa Wael
[Galaxy S III Android Development] andip71:
Normally: Undervolting = no support. Read the op.

But as I am in a reasonable mood today:

1) try once without UV

2) switch for a test to pegasusq, then should work.

3) Or when you stay on zzmoove, increase the min CPU frequency for a test to 400.

Andi

Andi
[Galaxy S III Android Development] Mickyman:
Will give it a go. Thanks alot!
[Galaxy S III Android Development] andip71:
Update: I have pointers now regarding the ro/rw remount issue. Lets see when I will be able to pinpoint the change that finally causes it.

Maybe it takes a week for that now, due to my business trip...

Andi
[Galaxy S III Android Development] JustArchi:
No need to hurry Andi. If you'd also take a look at double init.d execution it would be great.
[Galaxy S III Android Development] arifanwar:
I am on the temasek ROM and kernel 2.1 with no SElinux that battery backup is amazing.. Yes the permission issue was there as well but reinstalling busybox fixed it.. Thank you for your effort's!
[Galaxy S III Android Development] JustArchi:
I have no idea why reinstalling busybox helps but it may be useful information for [MENTION=947981]Lord Boeffla[/MENTION].

---------- Post added at 04:33 PM ---------- Previous post was at 04:30 PM ----------

Andi. I found it!

Question is, do you really need busybox in /sbin if CM has built-in (and compatible) busybox itself?
[Galaxy S III Android Development] andip71:
Thanks Archi, was just about to post the same.

It is the busybox symlink to mount.

I removed it and it works now.

Checking your double executing thingy now...

Andi
[Galaxy S III Android Development] nicesoni_ash:
So does that mean next version will solve this problem of system not mounting as rw?

I have one more problem to discuss, I am on temasek v7 and used boeffla v2.1beta, everything worked fine but few of my settings doesn't stick after a reboot, I have to set them manually like color calibration and zram settings after every reboot.

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
Archi,

the mount thingy is sorted by having me removed the symlink. It seems the busybox 1.21.1 mount implementation is not 100% compatible.

And yes, I need to have an own busybox in /sbin as I cannot rely on

- being the same on Samsung roms (in fact, there it is not)

- being the same for all CM roms

- the other busybox behave as I expect.

But now to the other thing, the double execution of init.d scripts:

I completely removed the init.d processing from my kernel for a test, and guess what - they are still executed.

So this leads me to the conclusion: At least on Temasek the rom executes the init.d scripts as well.

Do you know, by accident, where this is done?

This is a nasty one. I mean, I can easily remove init.d handling in my CM11 kernel. But can I rely on roms doing that consistently?

I know this is why Yank built this switchable into his kernel.

Yes, next version will have this solved.

To your other issues:

- colour calibration do not stick with CM11, they are explicitely mentioned to be for CM10.2 only in the app

- zRam should stick however, do you have conflicting init.d scripts maybe?

Andi
[Galaxy S III Android Development] thearc77:
On monday or Thursday Yank Dev, JP, point me something about busybox but the test was unsuccessful. I already tried reinstall busybox without good result

Glad to see the situation is clear now

From my S3
[Galaxy S III Android Development] nicesoni_ash:
Sweet. My mistake, read it first time but forgot about that and no, I don't have any such scripts but that's not a big thing, I will wait for ur next version and will test it then properly. :)

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] JustArchi:
Good question Andi. If you want my 3 cents, make a switch in your boeffla config app, which creates a file /data/.boeffla/DISABLE_INITD or similar. Then you can modify your kernel init script to something like that:

if [ ! -e /data/.boeffla/DISABLE_INITD ]; then
# execute init
else
# don't execute init
echo "disabling init.d as requested" >> $LOG
fi

Or similar :).

You can also invert this idea and use ENABLE_INITD, which may be useful in long-term if CM is going to stay this way. So users would be able to enable init.d execution if they need it. I think that it's even better than previous one.
[Galaxy S III Android Development] andip71:
Done already like that, Archi. Just the other way round.

I do not like that approach so far, but well...

Let's see if I can ship a new beta out by tomorrow evening or so. Have no time left anymore before I move on to UK.

Andi
[Galaxy S III Android Development] JustArchi:
No need to hurry Andi, as always. I'm very happy that you sorted both of these issues in no time. Glad you're here! :highfive:
[Galaxy S III Android Development] nicesoni_ash:
Meanwhile please have a look at this post, could be useful in system mounting issue related. (when you get free time, no pressure ;))

http://xdaforums.com/showthread.php?p=47796543

Even though you already sort that out but it's interesting.

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] tisazalay:
Please Andi have a nice trip and enjoy good business. Not in a hurry at all.

I don't want to be a PITA but only a small request if you can put in a todo list to allow the kernel to display battery temperature reading (currently only temaseks kernel is fine)

Thanks and have a great week.
[Galaxy S III Android Development] donalgodon:
[MENTION=947981]Lord Boeffla[/MENTION]

Just FYI. With Temasek's V8, the battery temp reading is stuck at 30.0C. Doesn't happen with stock kernel or Temasek's Boeffla kernel.
[Galaxy S III Android Development] rezapatel:
Exactly the same setup and the same issue. Thanks
[Galaxy S III Android Development] Mostafa Wael:
does the issue of the /system mounting as rw exists in the omnirom 4.4 also?
[Galaxy S III Android Development] fndpena:
Same here. Temperature sensor not working :/

It's kernel related. Let's hope Andi fix that in a future update.
[Galaxy S III Android Development] andip71:
Yes, same thing.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] andip71:
With which app do you read it?

And isn't it nice to have a cool phone? Lol.

I am super surprised, never changed that code at all.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] RohanAJoshi:
for me it's working, using latest android tuner, we ca see it in cpu info.

Edit : using this kernel from release, on temasek v8..

I had 1 SOD and 1 random reboot, and I just realized that cpu not coming below 800mhz..

now testing after reboot.

.

all this with same config which I was using from 1 month.
[Galaxy S III Android Development] Mostafa Wael:
No i was just asking, I recently flashed the 24/11 omnirom 4.4 nightly. By having the same issue of remounting the /system as rw in omni too, i will wait till you upload the next version. You really done great work. You solved 2 issues in no time. :good: Wow!

Waiting for next week eagerly. Have a nice business trip man. I think you may have a deep rest "or shall i say deep sleep?! LOL" after sorting out these problems...

Thanks for you work and support

Mostafa Wael
[Galaxy S III Android Development] andip71:
No promises, but I try to have the kernel ready soon. Have my dev Linux with me on an external hd.

So fingers crossed you do not need to wait for next week even :D

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] Yank555:
I tested this, and I can confirm this happens on ALL 4.4 ROMs, both Temasek's with stock kernel (full wipe) as well as OMNI with its stock kernel.

Checked using *#*#4636#*#* in dialer and looking into battery info.

Kernel does report battery temp correctly in /sys/class/power_supply/battery/temp . So it looks like a ROM side issue.

That is CPU temp, not battery temp.

JP.

-------------------------------------------

EDIT : Just spoke to Cedric (dev of Android Tuner), he gets battery info through an API call, so it is a ROM side issue !
[Galaxy S III Android Development] tisazalay:
Thanks, now I read the Edit and think as you explain, it must be the backbones that support the calls, for example, I have current widget to display the battery temp, on temaseks V8, if I use temasek's kernel, it works, if I flash Boeffla, it doesn't show the temp (although as you pointed, the value is under /sys/.... ). Probably the rom is making su calls through a method that is influenced by the kernel, and is failing with some kernels.

I read the comment by rovo89 regarding a deeper lock on "block devices", but that deeper lock is bypassed by some su calls on some cases/kernels (for example, the su calls from File Manager always work, on all kernels, while the su calls from ES File Manager only work on some kernels).

Now I'm 100% sure that's the layer that's bothering (the interaction between busybox - su - kernel - rom), the API calls are sort of incompatible. Now where is the layer, I have no idea (if in ramfs and is getting corrupted or somewhere else).

Thanks
[Galaxy S III Android Development] JustArchi:
For me battery works fine on stock kernel and temasek's kernel, but it doesn't on yours and Andi's kernels. It shows static 30.0C. I'm using Cool Tool.

Strange, but that's a misc issue.
[Galaxy S III Android Development] nicesoni_ash:
Correct, in 4.4 the file provide this information to battery temp is changed and it's fixed by temasek in his latest build v9.

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] temasek:
V9 introduced android 4.4 way of reading battery.

https://github.com/temasek/android_...mmit/3a05ddadae64e5589e7b2f9cfbda89f497763e0b
[Galaxy S III Android Development] Yank555:
OK, that confirms my findings ;)

Perfect, problem solved :D

JP.
[Galaxy S III Android Development] floykoe:
Sorry it has taken so long for me to get back to you regarding this. Kernel was flashed to an ATT specific version of AoCP Final. I have confirmed it is a brick, but not completely sure whether soft or hard. No external buttons work, but I can get led to turn on in battery is removed and I plug it in. I can fix either, but I need a Phillips small enough to open the sucker up (which I don't have).

I have not kept up to date with the thread. Have any other bricks happened? If so, I will post the instructions for the fix (not for the beginner).
[Galaxy S III Android Development] tisazalay:
Now I'm on temasek v9, with the patch, still no reading of batt temp on some kernels.... Probably in the future :)
[Galaxy S III Android Development] rezapatel:
Exactly the same setup and the same issue. Cheers
[Galaxy S III Android Development] andip71:
Hi all,

as promised, I was working on a test kernel this evening in the hotel room.

The kernel should have in:

- fixed the remount /system rw not working

- fixed double execution of init.d scripts by rom and kernel

- removed selinux

I sent a test link to Archi, as he was first reporting/confirming these findings.

If he is happy with it, I can give it to you all.

Andi
[Galaxy S III Android Development] nicesoni_ash:
Waiting, waiting, waiting... Hehe. Come on Archi.. :p

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] Maceee:
How is battery life with this kernel on CM 10.2? Is it even a little close to stock ROMs battery life?
[Galaxy S III Android Development] simono_pl:
I think is better compared to CM stock kernel.
[Galaxy S III Android Development] andip71:
Not on Archi anymore. He confirmed already last night, all was running fine for the test kernel for him.

So, it is ready to go basically. The only thing blocking me currently from giving it to you guys: I am at work and need to run Windows on my laptop. So can only switch over to Linux today evening in the hotel again to recompile the versions (incl. Omnirom) and upload it.

But if you want an inofficial sneak peak already on the two CM11 kernels, you can go here already:

https://www.dropbox.com/sh/fhsv3irrea38kcg/E4b5DbGNwT

Cheers

Andi
[Galaxy S III Android Development] nicesoni_ash:
This is strange, these posted ones are new fixed one, right?

I am still getting the same error, system read only. Tried with a clean wipe v9 temasek. Tried with inbuilt su app, now trying with chainfire su and will post my findings soon.

Edit:

Yup, exactly as I thought. With chainfire su worked perfectly. Also screen color calibratios work after reboot, lol. Everything sweet now. Thanks again. :D:beer:

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
How did you check it?

I opened a terminal session once, second trial was with an adb connection.

Then I used:

su

mount | grep system

mount -o remount,rw /system

mount | grep system

mkdir /system/test

It worked for me...

Andi
[Galaxy S III Android Development] nicesoni_ash:
Sorry, edited my post. It worked. :D

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
Great to hear.

I was quite sure it would work because Archi and me tested it individually with the same results :)

Andi
[Galaxy S III Android Development] muncheno:
Running beta 2.1_1a now.

Anybody notice there is different in the screen color?

It is more vibrant & brighter now on auto brightness.

Thanks to our Lord B.

Sent from my GT-I9300
[Galaxy S III Android Development] andip71:
Thanks for that Muncheno. But I wanna be honest: I have not changed anything that would cause this in the code :)

But anyways, if it is better for you now, I am happy.

Andi
[Galaxy S III Android Development] mNiosu:
Hi there Boeffla!

Kind request from one of your users. Using your CM11.0-r3p2 kernel for some time now on temasek's ROM but I experienced a problem since his V8 version with your kernel:

In V8 he applied a extSdCard fix (see bellow) that seems to work fine with stock kernel or his kernel but not with your version of kernel.

Can you look into the problem for a fix please! Thanks in advance!
[Galaxy S III Android Development] Mostafa Wael:
i don't see an update for omni kernel?

Does that mean that the System rw mount issue doesn't exist in boeffla omnirom kernel?

just to be sure.... :D
[Galaxy S III Android Development] thearc77:
Exist, Andi will provide an update for all his kernels.
[Galaxy S III Android Development] skodaslx:
Just read 8 posts above yours.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] ImShadix:
I can install this kernel on my teamsek ROM ( KitKat ) ?

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Android Development] thearc77:
Yes you can (CM11.0-r3p2) but i suggest wait new version comming with nice fixes.
[Galaxy S III Android Development] tisazalay:
yes, just make sure to match kernel and version of temaseks rom (older ones are without the new mali drivers, that is before v5), the newer ones v5+ use the new mali drivers so you should use that kernel (r3p2)

---------- Post added at 05:40 PM ---------- Previous post was at 05:35 PM ----------

Hi Andi, when you have time can you look at the battery temperature thing, I know Yank555 wrote about it (mentioning it was sort of a rom problem), but still, when I use temasek's rom, the reading is fine with temasek's kernel and it shows 30ºC with Boeffla, only changing kernel.

Thanks for fixing the system rw issue.:good:
[Galaxy S III Android Development] ImShadix:
OK thanks so I wait the next release, I'm V10 so no problem :)

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Android Development] Doppiadi:
Hi, is anyone else getting bootloop with latest Omni nightly (27) and latest Boeffla kernel? I made a dirt install only wiping cash and had no luck, tried again without Boeffla and it works..I'd assume that's the bootloop cause.
[Galaxy S III Android Development] andip71:
Sure, but will not be looking into anything before next week. Still on my business trip the full week in UK and during day hours no capacity to work on something. Only 1 hour in the evenings is not enough to investigate that properly.

Most likely I would need to refresh the initramfs then.

Which I cannot do before weekend unfortunately (see above). So, please stick to Omni stock kernel for the time being then, or fall back to previous Omnirom version.

Andi
[Galaxy S III Android Development] Doppiadi:
I'll give it another try later and report here because it seems that other guys in a forum of my home-country are not having problems. I know you're busy, I appreciate that you take the time to follow the thread nonetheless, but I can totally wait some days ;)
[Galaxy S III Android Development] andip71:
Version 2.1-beta1a

Hi all,

finally managed to now upload two updates for the CM11 kernel (with and without new mali drivers) now:

2.1-beta1a

Change log

Fixed bug which prevented remounting /system folder to rw by mount command

Fixed init.d script handling (init.d scripts were executed twice, once by kernel and once by rom)

Selinux switched off

Sorry for the delay, really busy this time on my business trip, not giving me lots of time for this atm.

Enjoy

Andi
[Galaxy S III Android Development] Doppiadi:
Ok Andi, a second flash was enough to solve the omni bootloop, then Boeffla-config notified me with the error dialog box, I re-entered root permission but the app still didn't work. After a reboot everything is working fine. Strange behavior!
[Galaxy S III Android Development] andip71:
Good it works now!!!

Gives me some time back to care of Omnirom kernel things during next weekend/ next week.

Andi
[Galaxy S III Android Development] xeizo:
Works great here with Temasek V10 and PA Gapps 131126! :)
[Galaxy S III Android Development] sayaksark:
thanks for ur valuable time
[Galaxy S III Android Development] andip71:
I am curious about that... what does it fix actually?

I have a 64 GB exFat formatted card in my phone and never faced any exFat issues?!?

Andi