yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] cKenny:
sorry to hear that, hope you can get it over soon...
[Galaxy S III Android Development] szunyi77:
Hello

The kernel of the problem may be that I did not reset the triangleaway count?

Starters for triangleaway, click the reset binary, restart, bootloader volume up and prints DONE!

But the end result remains "1"!

I tried the 1.2 stable kernel.

The 2.2 beta 4 kernel "does not start" download mode ...
[Galaxy S III Android Development] NickName98:
What are the disadvantages of undervolting cpu / gpu?
[Galaxy S III Android Development] Crythar:
As long as your phone runs stable (no random reboots) with low voltages you should not have any disadvantages
[Galaxy S III Android Development] NickName98:
Thanks :)

Medium undervolt seems to be as stable as stock ;)

No reboots at all
[Galaxy S III Android Development] Crythar:
Same here for me. Also running medium undervolt with no issues
[Galaxy S III Android Development] scorpionhd2:
Not entirely correct. UV too much can give you screen freezing without the reboots necessarily. Also, UV too much can cause the processor to require more time to work thus resulting in higher and faster battery drain than if it were on stock. Just tweak slowly and find the sweet spot.
[Galaxy S III Android Development] NickName98:
Have you found that sweet spot? :)
[Galaxy S III Android Development] thadoukuki:
Is this kernel compatible with Remix Resurrection ROM? I really love this kernel.
[Galaxy S III Android Development] scorpionhd2:
I'm gettin' there ;) :good:
[Galaxy S III Android Development] slim80:
A small donation for you Lord. Good luck bro...

1WG29791YE976842J

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] vulfgar:
Sorry to hear that. This sort of thing always bring plenty of work and trouble so take your time. A small donation 2G3799308U981942J
[Galaxy S III Android Development] andip71:
So what is exactly your problem. You cannot reset the flash counter?

You need also specific boot loaders on your phone (older ones, I have XXBLFB bootloaders even) to make Triangle Away work.

At least this is my experience.

Instability, freezes, reboots, even higher battery consumption as the phone gets unstable and tries to recover.

All phones are different, so you need to find our yourself what your phone can take.

You tell us? :)

Install Boeffla Omnirom kernel, latest beta. Should most probably work.

Thanks guys, I really appreciate your support a lot!!! :o

Andi
[Galaxy S III Android Development] szunyi77:
Yes TriangleAway the problem is not reset. I have the new bootloader and stabil 2.1 kernel !

Sorry for my bad english..
[Galaxy S III Android Development] andip71:
Both bad.

You need a recent beta version (it has been reimplemented in 2.2-beta1) and an older bootloader (like XXBLFB) to reset the counter and manage to keep it on 0.

But I will not advice to downgrade the bootloader as I do not know if you have an affected S3 with the EMMC bug. You need to decide yourself what risk you wanna go.

Andi
[Galaxy S III Android Development] szunyi77:
Thanks for your response :good:

I have UGML2 bootloader, this is new ..

But if you need to downgrade, they would rather not do it!

Not risk your device!

It will be good for me "1" is the counter!

Warranty is no longer in anyway ..
[Galaxy S III Android Development] Choristav:
Andi I'm sorry to say that I had to revert to .1 beta in order to remove the stutter with Temasek's rom.

I might be the only one but it's happening on a clean wipe, and even on and omnirom base.

The freezing parts start after a day or so.
[Galaxy S III Android Development] mad_ady:
I've noticed that this kernel doesn't have a /proc/config.gz available. Is there an alternate method of getting the configuration from the kernel?
[Galaxy S III Android Development] Erik1805:
Keep up the great work. Small donation from my side: 28114554AG852800P
[Galaxy S III Android Development] andip71:
Have you checked if CM or Omnirom kernels in standard have it?

If so, I might have switched it off in the past by accident.

Thanks a lot Erik, much appreciated. Seems I have a big financial loss with my stolen car now, so everything helps.

Cheers

Andi
[Galaxy S III Android Development] SuperAce609:
Hey Andi, long time no speak.

I seem to have found the cause of the distorted external speaker sound. Whenever i amplify the sound to any value higher than 58, it starts sounding different. Is this a kitkat issue? I always had maxed sound at 63 but it seems to not work in this case.
[Galaxy S III Android Development] nainaabd:
Sorry yo hear.Hope things will get better.Just to ask yr Andi2.profile i was using it on 4.3 .Can i use this profile on CM11 ? Tks
[Galaxy S III Android Development] tamage:
Easycap module in kernel I9300

Hi!

Now I use this kernel with CM11 Temasek v46 cooked rom. Can anybody any idea that how can use my I9300 with easycap

module? ( Video input with easycap USB capture dongle ).- I founded that with nexus7 it works fine......

Bests:

Tamage
[Galaxy S III Android Development] raphman:
Hi Andi,

I'm having issues when charging my phone (I have tested 3 different chargers) when I plug the charger, the charging current is first 400mA, then I unplug / replug multiple times, and if I'm lucky, the current shown became 600mA or 800mA if I'm very lucky...

I have double checked the charge parameters in boeffla settings...

I discover this issue when a morning, I picked up my phone after a long charging night, and my battery was at 65℅...

I'm running the last boefla kernel and the last temasek ROM.
[Galaxy S III Android Development] szunyi77:
hello

I am now trying out the zzmoove governor.

I do not see things exactly 1-2

The battery-zzmoove extreme yank the battery friendly than the zzmoove-battery?

I tried to yank the battery extreme, but I have less operation time.

The yank what exactly?

What better battery? The battery or the battery yank?

I hope you understand ...
[Galaxy S III Android Development] boyheadkick:
Enable ignore unstable power and ignore safety margin options

Battery for a little better performance, battery yank for little better savings..

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] andip71:
Maybe Kitkat sends a higher input signal, so it distorts quicker. As I am not a ROM developer, I cannot comment in a serious way about it.

Yes you can, but do not forget to reset LMK settings after importing and loading the profile. CM LMK settings are quite different to Samsung ones.

Maybe someone can help on that, I cannot. Do not have that dongle, however - does it expect HDMI input or analogue? You need for sure a dongle with HDMI input as the S3 does not have anaolgue video out (maybe Nexus7 has??)

Yes, if you would search the thread - basically every thread on roms or kernels - on the words "charging" and "i9300" you would have found enough information.

1) you are using stock charger -> crap -> replace with a proper charger

2) your usb cable has a problem -> replace it

and if you do not want to do any of that, you can do the following on your own risk:

3) enable the two "ingore" options in Boeffla-Config charge settings

zzmoove battery yank is a slightly newer profile which is supposed to give better balance on battery vs. performance.

I think zzmoove battery is still more battery saving, but comes with more lags.

I generally use "battery yank" myself when using zzmoove.

Andi
[Galaxy S III Android Development] boyheadkick:
Actually Andi i have this problem too..ive attached some screenshots...back when i was running touchwiz i never had charging problems, always quick and fast..but now on cm, well, see for yourself :( been using the same original charger and cable on both screenshot instances, with ignore unstable current and ignore safety margin always enabled..and im actually using a 2A galaxy tab2 7" charger on the slow charging screenshot, which i took just now..i initially thought it was just a CM nightly problem, but ive changed rom and running supernexus now..

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] andip71:
Interesting... mine is charging normally fast.

But could you please for next time:

- switch the ignore functions to off pls

- then connect your charger

- then look at the first page in boeffla-config and check which charge current actually is used. I bet it is far below what you configured...

Andi
[Galaxy S III Android Development] tamage:
Originally Posted by tamage View Post

Hi!

Now I use this kernel with CM11 Temasek v46 cooked rom. Can anybody any idea that how can use my I9300 with easycap

module? ( Video input with easycap USB capture dongle ).- I founded that with nexus7 it works fine......

Bests:

Tamage

Maybe someone can help on that, I cannot. Do not have that dongle, however - does it expect HDMI input or analogue? You need for sure a dongle with HDMI input as the S3 does not have anaolgue video out (maybe Nexus7 has??)

Dear Boeffla!

Easycap has analogue input. It has linux driver and available the suorce code too. I have an integrated HDMI otput and OTG cable with USB support and input for external USB+5V. SOmebody integrated fo the kernel of nexus7 and use it for example in the car for an additional usb-webcamera. So the question that how can integrating the linux driver to the kernel?

Bests: Tamage
[Galaxy S III Android Development] boyheadkick:
I just did...it sits at 400ma

So, is it normal for this to happen?or do the sammy and cm kernels have different impact on charging?

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] raphman:
Andi,

I have made searches before posting, I found people reporting bad chargers. That's why I have tested 3 different chargers (each one having it's proper usb cable) before posting in this thread : the original i9300 one, the new one of a galaxy tab 10.1 2014, and an another old one I have in stock.

On the 3 different chargers, the same behavior happens.

This behavior didn't happens at all when I was on 2.1 beta11.

Maybe this is an hardware problem (the usb connector on my phone), maybe this a software one, I don't know This is why I made a report here, and just ask you if something related to "the way charging is handled" have changed in your kernel...
[Galaxy S III Android Development] andip71:
Well, I think for this very specific requirement, you need to find someone putting this energy in. He can fork my repo and implement it then. I am sorry, but without having the hardware and only on request of one single user, there is no way I can do that for you.

Well, it really sounds like your charger can - in a STABLE way - only supply 400 mA.

If you can exchange the cable of the charger, it might be worth doing it. And cleaning the plugs.

The charging logic and driver is the same in Samsung as in CM/Omnirom kernels. So there is no difference.

I just plugged my 2A HP Touchpad charger into my phone on CM11... this is the result... 1200 mA, just as configured (I have the ignore functions off).

Please refer to screenshot and please do not mind I am on (my internal) beta5 already...

2.1 beta11, wow... was just going through the github, last time the charger driver was touched by me was in 2.1-beta2 on 03.12.2013.

So, I really do not know why this should have changed for you. You still can go back to 2.1-beta11 and test if it goes better for you.

Andi
[Galaxy S III Android Development] krige:
I flashed boeffla kernel 2.1 Omnirom on a Carbon KK nightly 20140223 and everything worked seamlessly.

I ran an Antutu benchmark before and after the kernel installation and I obtained about the same result, around 19000. The phone seems to be much more snappy and responsive now. What other differences should I notice in comparison to before installing the kernel?

---------- Post added at 07:31 PM ---------- Previous post was at 07:27 PM ----------

What settings did you apply?
[Galaxy S III Android Development] krige:
Do I need to flash again the kernel after I flash a Carbon nightly update?
[Galaxy S III Android Development] akz1x1:
Thanks so much for touch led settings...

Was looking for it everywhere...

I really hate it when the capacitve keys light up when I touch anywhere on the screen...

Wanted it to light up only when I press either back or Manu key...

Thank you soo much...

You're the best...

But it's really sad that you won't implement dual boot ?
[Galaxy S III Android Development] kp.nikhil:
i have set charging output to 1200ma but charges only at 1000ma..ignore safety margin and unstable margin is on.. i switched from devil kernel to this... in devil kernel it was charging at 1200ma..

Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
[Galaxy S III Android Development] andip71:
How would you measure you are only charging with 1000 ?

I do not know any reliable way of doing this, as the S3 has no chip built in to measure that.

Andi
[Galaxy S III Android Development] Nic2215:
Galaxy current lite apps in the play store works pretty accurately
[Galaxy S III Android Development] andip71:
I somewhat disagree. It interpolates battery voltage changes over the time and tries to calculate the current out of that.

This is pretty inaccurate, honestly.

Andi
[Galaxy S III Android Development] 8afri:
Default settings plus some recommended settings by [MENTION=1470009]boeff[/MENTION]la on his web. It's more like a trial-and-error attempt.
[Galaxy S III Android Development] dungquoc:
I had seen kernel this you used. CM 11_2.2. Beta 5 (modified on 26/2).

So when will you upload for everybody use?
[Galaxy S III Android Development] andip71:
When I have tested enough and I am happy with it.

But seems it is not too far away anymore.

Andi
[Galaxy S III Android Development] dungquoc:
Ok. Thx

Hope soon!
[Galaxy S III Android Development] andip71:
Out of curiousity... why do you want for the new version?

Is anything wrong with the existing beta, anything I should know?

Or are you (as many here) "flashaholic"? :)

Andi
[Galaxy S III Android Development] dungquoc:
:laugh::silly:

I love the second which do y think about me!
[Galaxy S III Android Development] paour:
Tasker CPU task

Hi Andi, I'm coming from the Temasek kernel, and one of my Tasker tasks fails to run on Boeffla 2.2b4, complaining that "Action CPU isn't available on this device". Based on the Tasker help, I think it's looking for /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies.

Would it be possible to support that pseudo-file in your sysfs?

I know you also offer the ability to use Tasker to switch whole profiles in your Config app, but I'd like to keep this kernel-agnostic if possible (several other people use the same Tasker task, not all of them on the same device/kernel).
[Galaxy S III Android Development] dungquoc:
Hi Andi, Do you share your Ultra Power save Battery (bcProfile) for me?

Thx
[Galaxy S III Android Development] cKenny:
May i know whether boeffla kernel support paranoid? I'm quite interested in this rom and would like to give it a try, and i hope to have a good kernel to play with it together :p
[Galaxy S III Android Development] krige:
That is very interesting, I would like to set that too! Where is that option? I only managed to disable them everywhere, but I'd like them to still lit up when I press them and not the screen, like you wrote.

Edit: found it! I installed Boeffla-Config V2 and turned off the Touch LED when touch screen option in DISPLAY+LED / Touch LED Settings (Only CM)

---------- Post added at 10:57 AM ---------- Previous post was at 10:54 AM ----------

On which post these settings are recommended? If they are recommended why haven't they been set by default?
[Galaxy S III Android Development] 8afri:
Try this http://www.boeffla-kernel.de/index.php/kernel-settings
[Galaxy S III Android Development] krige:
Thanks! That is a really good source of information :)

I see there is an option to Clean init.d which creates a backup of the content in the directory /system/etc/init.d and clean the directory afterwards.

What would be the reasons to clean the init.d directory? How do I know whether the files in my init.d are legit or not? Whether they are safe to be deleted?
[Galaxy S III Android Development] 8afri:
For that I would suggest you to seek [MENTION=1470009]boeff[/MENTION]la help/explanation. I'm sorry I can't be of much assistance on that.
[Galaxy S III Android Development] andip71:
Which kernel are you on? I can see it in the path and it is filled correctly?!?

(you can have a look yourself with root explorer etc.)

Well, I am afraid, the only way to find out if an init.d script is good or bad or right or wrong is to read and try to understand it :cyclops:

I put it in because especially in the Samsung area, there are many roms around which come with outdated scripts etc. that create more bad than good.

And this is an easy way to get rid of them.

In the CM world I did not come across problematic once so far in the past months.

Personally I think: There are only rare occasions where you should rely on init.d scripts at all. Mainly I use it when I write them on my own, then I know what they do.

Andi
[Galaxy S III Android Development] paour:
I'm on your Omnirom kernel v2.2b4. Whether on the command-line or with a browser that file is not there…

Screenshots:
[Galaxy S III Android Development] krige:
Do you think it is safe to just clean it without compromising the proper functioning of the device? Once I do that, will a reboot be enough to clean all the work that they have done or do I need to flash the rom and the kernel again?

I had imagined that after flashing ROMs, flashing kernels and formatting the sdcard, all the files on the device, pre-existing to those operations, would have been wiped out. I have come to notice thought that certain files in certain directories (like system/etc/init.d, system/addon.d and maybe others) they survive those operations. I wonder why is that and if there is a way to truly wipe out a phone and clean it from all the pre-existing files, including those persisting ones in those directories.
[Galaxy S III Android Development] andip71:
This is really confusing.

Disregard I am already on my (internal) beta5... but I can see it clearly, see Screenshots.

So now: Anyone else can check this on his side as well please?

Also, can you send me your configuration? Just to avoid some other setting is the root cause for it (which I would not know to be honest).

Thanks

Andi
[Galaxy S III Android Development] paour:
That is indeed odd. I've sent you my boeffla-debug.txt via email as instructed. I hope that was what you meant by configuration. If not, how should I proceed?

Thanks for looking into this!
[Galaxy S III Android Development] daviddema:
Hello, I see it has been asked before, but is there still no support for the tun.ko module? This is a show stopper for me and anyone who wants to use openvpn.

Cheers and thanks for the great work on your kernel.
[Galaxy S III Android Development] mad_ady:
Well, I have had a couple of hours to do some tests with regard to my freezes experienced with the Samsung Dock.

All the tests were done with 4.4.2 ROMs, and with the same dock and power cable/charger. None of the kernels had a /proc/config.gz to look for changes in configuration.

Here are my results:

Tests done:

1. NeatRom 3.2 with original kernel (Linux localhost 3.0.80+ #1 SMP PREEMPT Mon Feb 17 02:26:42 PST 2014 armv7l GNU/Linux). Dirty install, with some xposed modules - the regular running system.

Result: The dock works every time. No freezes whatsoever. The phone charges normally

2. NeatRom 3.2 with Boeffla 2.2-beta4. Dirty install, same system as above.

Result: The phone freezes instantly when plugged into the dock. Only action you can do is reset via holding the power button for 5 seconds.

3. Neatrom 3.2 with Boeffla 2.2-beta4. Reset to factory defaults.

Result: Everything was ok when the phone was plugged into the dock the first time. The phone responded to commands and was charging normally. After removing the phone and reinserting it, the phone freezes. The phone freezes instantly on reinsertion after every reboot. If I do a reset to factory reset, the first insertion is fine, but on subsequent insertions I get instant freezes.

4. Slimkat 3.2 with original kernel (Linux localhost 3.0.80+ #1 SMP PREEMPT Sat Feb 15 15:10:26 CET 2014 armv7l GNU/Linux). Reset to factory defaults.

Result: Same as #1 (works every time).

5. Slimkat 3.2 with Boeffla 2.2-beta4. Reset to factory defaults.

Result: Same as #3 (works the first time, freezes until reset to factory defaults).

6. Temasek v49 (unofficial CM11) with original kernel (Linux localhost 3.0.64-CM-g4b16826 #6 SMP PREEMPT Tue Feb 25 09:54:19 SGT 2014 armv7l GNU/Linux). Reset to factory defaults.

Result: Instant freeze when connecting the phone to the Dock every time.

7. Temasek v49 (unofficial CM11) with Boeffla 2.2-beta4. Reset to factory defaults.

Result: When connecting the phone to the charger it seems to work fine for about 2 seconds after which it freezes. Tested about 3 times.

I'm not sure what conclusion one can draw from these tests, but I'm up for more tests if anyone has any suggestions.

So far the Boeffla kernel has behaved the same way in all the tested ROMs. The good news is - it can be fixed, since it's working on some kernels (slimkat). We just need to find the right setting...

I wonder if other 4.4 ROM users have noticed this issue as well - I can't be the only one! :)
[Galaxy S III Android Development] andip71:
Yes, you are right. Demand for tun module is not high, so I decided to not yet put it in. Especially as there seem to be some good app alternatives.

The conclusion is, it is most probably one of the following:

- upstream to latest Linux 3.0.101

- tool chain

- one of the changes I did to the kernel configuration

I could build you a test kernel once beta5 is officially out, would then revert some of these changes back step by step until we probably find what is causing it. Time consuming (for both you and me), trial and error, but this is the way.

Andi
[Galaxy S III Android Development] NikitoGR:
Great kernel, very stable. Only issue I have is the charging. Many times it drops to 700, 500 or even 100mA. I have this issue since the kernel install, maybe it's just the charger, it needs some further investigation. -Archidroid 2.3.7 with 2.1v kernel.
[Galaxy S III Android Development] andip71:
- buy a good charger

- clean your plugs

- replace usb cable at charger

if all does not help: enable the two switches in Boeffla Config to ignore unstable power and safety margins.

Andi
[Galaxy S III Android Development] andip71:
I just looked it up again.

tun

IS

enabled, but not as a separate module but rather it is hardwired into the kernel.

So whatever you have requiring tun functionality should work straight away.

Andi
[Galaxy S III Android Development] NikitoGR:
Alright I switched the 2 buttons and cleaned the cables, seems to be stable now :good:
[Galaxy S III Android Development] mad_ady:
I'd like to minimize the time wasted on your side for this, so two questions:

1. Presumably I could learn to compile the kernel myself and hunt it down myself (I believe in the teach a man how to fish approach). Can you point me in the right direction to set up a build environment like yours? Yes, it will take longer to troubleshoot and I will probably bug you a lot during the process, but I will gain experience (I have about 14 years of linux experience, but not so much android/embedded).

2. Since 3.0.64 doesn't work but 3.80 works I would guess your kernel supports it as well. It even works ok on the first connection. I would try to compile the vanilla source of 3.0.101 and see if the problem remains.

Again, thank you for helping me out. I'll do my best not to be a leech :)
[Galaxy S III Android Development] tisazalay:
Hi, I'm on Omni 2.2b4, with latest Config app but I wonder if The touch wake charger mode is supported or not on this kernel, I can't toggle it on. Touch to wake is working fine.

Do I need to set anything special for it to work?

Thanks