yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Kapiljhajhria:
currently on slimkat v7 stable. omni 2.4 beta 2

whenever i try to enable UMS mode from boeffla config app it unchecks itself within a second. even if remains checked UMS mode still doesn't work.

was on temasek latest version and same thing was happening with omni 2.4 beta 1. so i flashed slimkat to check if it was ROM problem or not. But issue still remains.

its been a while since i used UMS mode. never faced a problem with it just started facing it recently.

its not the driver issue on y system as i have tested it with kali, xubuntu and windows 8. UMS is not working with all three OS.

so my question are

a. are other people on omni 24.beta 1 and beta 2 also facing same problem?

b. if i switch back to omni 2.3 stable version will the UMS work again? as i don't know with which version it was working. so asking for advice.

c. can it be hardware related problem? like something in my phone has been damaged or gone wrong on hardware level?

Edit: found the solution http://goo.gl/Z7wmHF
[Galaxy S III Android Development] XDAMaxe:
I'm running carbonrom+boeffla(omni) for months (ng-version since it was published) and never had any issues with ums mode (- on win xp sp3).
[Galaxy S III Android Development] andip71:
Me neither, working as it should on my side. And I use it frequently, believe me :)

Andi
[Galaxy S III Android Development] flither:
I'm on the same ROM, UMS working just fine on newest and prev version of NG.
[Galaxy S III Android Development] Kapiljhajhria:
i have tried so many things now. nothing seems to have fixed it.

Formated my laptop and desktop. Chnaged their operating system from windows 7 and kali to windows8 and xubuntu. still same thing. (even after isntalling drivers)

did mega wipe and flashed ROM again and again atleast 3-4 times. tried with omni NG beta 1 and beta 2. still same problem.

chnaged ROM from temasek to slimkat. still nothing.

have 3 usb cables at home all working so i tried even all those three cables.

Not even USB port problem since i have tried atleast 6 ports with my laptop and desktop.

will now try to downgrade kernel. 2.3 CM version and omni version.

it works fine in recovery but not with beoffla config app.

can be it be hardware issue? something wrong with my phone's hardware???

if a logcat can help troubleshoot this problem then i can give that. but i think it will take too much time for developer too troubleshoot my issue with logcat. wastage of developer's time, as i seem to be the only one having it.

EDIT: found the solution http://goo.gl/Z7wmHF
[Galaxy S III Android Development] flither:
Have you got USB debugging enabled? Also are you enabling UMS while connected, or before connecting? You never know which combination will or will not work in a custom world ;)
[Galaxy S III Android Development] leleobhz:
Ok, i know [MENTION=947981]Lord Boeffla[/MENTION] dont like Kernel Backports - but we are developers, arent? So, exciting features must be at least cited:

http://lwn.net/Articles/601726/ (Second part of 3.16 proeminent features) says "The ARM architecture has gained hibernation support."

ARM hibernation support may also increase power manager general support.

Also, a question: Why no F2FS? I mean, i know the discussion is very very big about performance gain, etc, etc, etc, but i can't see a Real reason to NOT support it.

Also, its possible think in support LVM auto-assemble drives at boot? I want to make some tests, including using a unique VG in ROM to /system LV and /data LV, so as /system is read-only and dont grow too much, i think in the possibility to mount /system in a more closer free space and reserve the rest to /data, increasing usable space. This approach worked well with p1ln from [MENTION=3031478]humberos[/MENTION] and i want to try doing it too. :D
[Galaxy S III Android Development] andip71:
Hi,

many questions, but almost only a single answer :)

Yes, I do not like kernel backports, so I will not put that in. They are known to cause all sort of weird issues, sometimes coming up quite late or sporadic. This is not matching my stability objective.

F2FS, I have explained many times. I have no plans to support it because I would need to backport parts of the kernel. And the ecosystem around (recoveries) is still not supporting it in a way it is safe for medium skilled users to be used. Last not least, F2FS is a hype in my opinion. Maybe it is faster, but at which cost is not what I aim for. I aim for "close-to-stock" and stability. And it cannot be people even have trouble going back from f2fs to ext4 again etc. etc.

The LVM idea sounds interesting, but also is far away from what I call "close-to-stock".

Last not least... I have maybe 1-2 hours per day available (weekends excluded even). So I am not gonna do any experimental stuff that could cause more trouble than I can support ever.

But I know there are kernel devs around that like to play with the things on the edge, maybe you should approach them in a first way.

Hope you understand, and anyways thanks for putting in your ideas and thoughts. Very much appreciated, really.

Andi
[Galaxy S III Android Development] Kapiljhajhria:
Never thought about USB debugging as it has always been activated and i never had UMS problem with USB debugging enabled. But after your post i gave it a shot . Still same problem. MTP mode is working fine. its the UMS mode.

and second part of your question. Already tried that.

But i am looking for ideas like USB debugging. a small stuff like that can make a difference. most of the time it is stuff like this. i can't think of anything but i am sure it will turn out to be something like this only. As i am the only one one with such problem.

EDIT: found the solution http://goo.gl/Z7wmHF
[Galaxy S III Android Development] leleobhz:
About F2FS, i can understand but.. Its not possible to compile it as a module and use it in initramfs? This does not affect the core and allow some expansion. About moving forward FS, as Sysadmin i am, NOONE moves FS everyday, its a hell in any place, cellphones will not be different. My concern is about things about TRIM and better abstraction having Flash design in mind.

About LVM, is really far away, but can be a good solution to some ROMs and to increase rational Flash space usage. Also, LVM support does not need to be monolithic in kernel too, AFAIK. Also, i prefer to see LVM now as a possible brainstorm (Different from F2FS).

About close-to-stock, is not a bad idea but Stock from Samsung is a hell (I have a Motorola Razr D3 that i dont need anything from it, even root, because system have a good behaviour). Your kernel provides a VERY VERY important subset of patches and useful things and i think this is you aim. Change too much is bad because needs a LOT of time to do things, but as i posted with the new Hibernation feature of 3.16, somethings can be very usefull too. But i think backport is a bad thing and the aim must be to make newer kernels like 3.16 support nativelly the environment.

About time, its complicated. I like a lot you job specially you appear to do things in a deployable way (Boeffla-config is a must-have app!) and its a proof that have a epic kernel with a big number of features that have no control interface is useless in someway. I tried as example ArchKernel. I liked it but for everyday things and projects is a mess (A simple "workarround" of UMS is a hell if you dont have ADB to control /sys and umount things manually).

I understand, sometimes i'll ask and propose somethings and the only thing i expect is what you do now: Provide a high-quality Kernel and Userland Configurer.
[Galaxy S III Android Development] ansonchan:
If we overcharged our phone like whole night,will it harm the battery?

And or charge it not full yet plug it out and battery haven't done we charge it again,will this harm the battery?
[Galaxy S III Android Development] flither:
...GOOGLE?!
[Galaxy S III Android Development] andip71:
No and No.

You cannot overcharge, the charging logic will take care it stops before.

Not fully charging is also not an issue with todays LiIon batteries.

Andi
[Galaxy S III Android Development] Almin94:
Maybe ART can be a problem.. Now I will switch back to Dalvik, then flash NG kerne to see what will happen.
[Galaxy S III Android Development] astankov:
I'm using Dalvik and have problems with ng kernel. It lags not only in games but in UI too. No problems with standard version. Now I will try the new ng beta and report. Already tried the new standard beta and it is great.
[Galaxy S III Android Development] andip71:
So thats why I have not dumped the standard kernel for good. You still have the choice :)

Andi
[Galaxy S III Android Development] VictorLapin:
And that's why I'm gonna flash the old-fashioned 2.4 beta 2 and see if it helps with my Smartwatch problem :)
[Galaxy S III Android Development] astankov:
Well I tried the new beta ng kernel and it seems that performance is much better but not as good as standard kernel. Good job Andi if you continue with your work one day maybe ng kernel will be the default stable kernel.
[Galaxy S III Android Development] barrtzz:
Can i flash boeffla ng beta 2 on boeffla ng beta 1 or i must back to stock and then flash it?
[Galaxy S III Android Development] VictorLapin:
Of course you can
[Galaxy S III Android Development] quebec1:
[MENTION=947981]Lord Boeffla[/MENTION]

i installed the kernel 2.4 beta2 ng, but i have always the same problem when i put the phone off to charge i see only battery without animation. (attach photo).

what happenes also with kernel 2.4 beta1 ng, 2.4 beta1 and 2.3a stable, while with kernel 2.2 stable is it ok

I used aosp neatrom v7 android 4.4.4

what do i do?

sorry for my english
[Galaxy S III Android Development] boyheadkick:
This has been explained countless times now..please please please search and read

-aL

tapatalked from my super duper palm top computer
[Galaxy S III Android Development] adripred:
Boeffla-Config: UMS mode / MTP mode

[MENTION=947981]Lord Boeffla[/MENTION]

I'm having a problem with the Boeffla-Config app / kernel 2.4 NG beta2 / latest CM11 nightly:

When I enable UMS mode everything works fine, but disabling UMS mode the external SD does not return to the MTP mode and is not available for applications in the smartphone. Restarting the smartphone everything back to normal.

Regards!
[Galaxy S III Android Development] quebec1:
Is possible insert this explain in first page?

Read 496 pages for this solution are very much.

What is the solution?

And however I try to read

Sorry for my English
[Galaxy S III Android Development] VictorLapin:
Exactly the same here
[Galaxy S III Android Development] gtsfreak:
[MENTION=947981]Lord Boeffla[/MENTION] I'm using omni 2.4 ng kernel with du 7.8 official rom and my loudspeaker volume is very low I tried everything in boeffla app to make it louder still very low dunno why :confused:
[Galaxy S III Android Development] ayoubij:
I have same problem with omni NG latest beta 2 and latest carbon rom nightly.

Didnt find solution except change to CM version ? But i thought carbon need omni version better. Should i change or what
[Galaxy S III Android Development] boyheadkick:
this was posted just two days ago :rolleyes:

this 3 days ago :rolleyes:
[Galaxy S III Android Development] andip71:
Although many times explained, I will explain it one last time again:

CM and Omnirom Teams changed something in their roms around 09.07.14 that breaks this stupid charging animation (I never charge my phone switched off, there is no real point doing that) with older kernels.

2.3 stable was the kernel that worked with all roms up to that day in regards to this charging animation.

Everything higher, means 2.3a stable and any 2.4 beta (NG or non-NG) require a rom that is NEWER than 09.07.14 !!!

Unfortunately, the implementation has been done in a way it does not have any forward or backward compatibility. Stupid, yes, but thats life.

So, your guidance is:

If charging animation does not work with 2.3 stable -> go to 2.3a stable or any higher kernel version.

If charging animation does not work with 2.3a stable -> go to 2.3 stable or install a newer rom.

As simple as that.

UMS mode is unfortunately very tricky and as it is also partially rom functionality, I cannot make it 100% safe.

However, if you stick to the following way when disabling UMS mode again, it works for me:

1) lets assume you want to use UMS mode

- enter boeffla-config

- check ums mode switch

- plug cable in

- DO NOT CLOSE Boeffla-Config

- use ums as you want

2) lets assume you want to go back to MTP mode

- eject your drive on your windows or whatever pc (to keep data consistent)

- unplug cable

- now uncheck the UMS checkbox in Boeffla-config

- wait for the message to display in the statusbar, the external sd card will be prepared

- after this message disappeared, plug your cable in again and MTP should be fully working

- also the external sd card should be back in your system

This is a known issue with roms based on Omnirom.

It works fine however on CM.

Nothing I can do about it from kernel side.

Andi
[Galaxy S III Android Development] ansonchan:
what if it is li po battery? as i have bought a redmi note for my dad so i want to know...:)
[Galaxy S III Android Development] andip71:
Lithium Polymer batteries also have no memory effect, so you can partial charge them without issues.

They are more sensitive for overcharging than LiIon, but the charging logic does cover it, as said.

Andi
[Galaxy S III Android Development] quebec1:
ok i hope that omni team upgrade his rom with a good initramfs, is it ok?
[Galaxy S III Android Development] ginzo:
Boeffla Omnirom NG 2.4 beta 2 with temasek v121

Very smooth and stable and good battery life!!!! ☺☺☺☺

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] andip71:
Too bad beta3 is already around the corner in a few hours. So you have to flash and test again :)

Andi
[Galaxy S III Android Development] _Negan_:
Same config here same optimal results :D
[Galaxy S III Android Development] andip71:
New beta3

All,

2.4-beta3 is out for all 4 kernels: CM, CM NG, Omnirom, Omnirom NG

Change log for all:

Latest Samsung sources GT-I9300_JB_Opensource_Update14 merged in

exFat driver updated to version 1.2.7 (Samsung OSRC from KitKat sources)

BFQ scheduler updated to version v7r5

Update su to version 2.02

Further simplified and optimized debug info file creation (credits to ZaneZam)

Error fixed that cause Boeffla-Config to show an exception in the log file

Enjoy

Andi
[Galaxy S III Android Development] RohanAJoshi:
Any Possibilities to support Nameless Rom ? (hwc, r4p0 etc gains) ..

.

I am asking again cause other kernels start to porting it, I am missing this kernel very much..
[Galaxy S III Android Development] adripred:
Hi,

Actually, I did not use the MTP mode because I think too slow, if it were possible to leave the UMS mode enabled by default when plugging the USB would be great, but you already told me some time ago that this is not possible there.... :(

Anyway, the procedure to return to the MTP mode and make the external SD available to the system again in CM11 and CM11 NG kernels (tested with beta 3 now) is not working here (tested following your procedure also). After disabling the UMS mode, the message of the external SD is ready does not appear in the statusbar .

In the stable version 2.3a this is working normally here.

Regards!
[Galaxy S III Android Development] andip71:
I think I wrote it already yesterday... I tend to wait until this support is official in CM and/or Omnirom.

I will monitor how this topic evolves however, and then decide when to jump on the train or not.

Weird, I was doing that many times today that way with NG as well, no issue there. Might be then a dependency on the rom. Which one exactly do you use?

And yes, basically the UMS mode control is a bit shaky. As it is officially not existing in Kitkat anymore. So we should be thankful we somehow could still enable and use it.

Andi
[Galaxy S III Android Development] adripred:
I always use the latest CM11 nightly. What ROM are you using for your tests? This feature may have been broken in the latest nightlies.

Yes, I understand that the possibility of at least switch the UMS mode is already a breakthrough ... I was just remembering what you told me some time ago.

Regards!
[Galaxy S III Android Development] nicesoni_ash:
Returning to MTP works fine here with Andi's way, tested on temasek rom..

_____________

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

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
Yep, right. On CM11 nightlies it does not work.

Was on Omnirom before, there it worked.

Then I do not have a solution to make MTP work after UMS was used for CM at the moment, sorry. Only a reboot seems to help.

Andi
[Galaxy S III Android Development] adripred:
What is different in the stable version 2.3a in which this functionality is OK?

But, no problem, I was thinking of testing the Omnirom anyway ...

Regards!
[Galaxy S III Android Development] andip71:
So, with 2.3a it is working for you.

And which 2.4 version are you trying exactly? NG, no NG?

But reading through the change log, in 2.3a I was not unmounting the sd card correctly for UMS. Now it is done, to avoid data corruption due to access clashes.

It seems, the rom does not mount it in a way afterwards, MTP is working again...

That is the only change I can see.

So we have the choice:

- not doing a proper unmount and risk corrupted data (like in 2.3 kernels)

- making sure the data stays intact and sacrifice coming back to MTP after UMS (in 2.4-beta2 kernels and higher)

I vote for the second option, which is the current implementation. Instead of putting my data at risk, I prefer to do a reboot if I really need MTP after UMS again.

Andi
[Galaxy S III Android Development] adripred:
CM11 2.3a - It's OK

CM11 non NG 2.4 beta 3 and CM11 NG 2.4 beta 3 - is not OK

The problem for me is not the MTP mode because I do not use it, the problem is that the external SD is unavailable after returning from UMS mode.

What is different between CM11 and Omnirom this case? What did the CM11 for that functionality to crash?

Regards!
[Galaxy S III Android Development] Almin94:
For CM11 better to use CM11 kernel or Omnirom?
[Galaxy S III Android Development] andip71:
Than try again. The card gets mounted again on my side with CM11 from last night and 2.4-beta3 NG kernel.

Look for /mnt/media_rw/sdcard1... CM mounts it back to that path for me.

And about your question what CM11 did do to break it, what is different to Omnirom - I cannot answer. I am a kernel dev, this needs to be commented by the rom devs, at least they need to contribute to the answer.

Why do I maintain a homepage where everything is already listed on the very first page???

I think this question has been asked 284757389 number of times already.

Look at www.boeffla-kernel.de, and then you will know.

Andi
[Galaxy S III Android Development] XDAMaxe:
I'm on latest omni NG 2.4 beta 3 (on carbonrom as a cm11 based rom) and have the same issue but found out that it works (gaining access to sd card after untick ums mode and unplugged cable) if you do this:

Settings-storage/memory-unmount sd card (in german it is named as 'SD-Karte entnehmen'), then answer the question with 'OK' and then immediately mount sd card (german 'SD-Karte bereitstellen') again. WORKS !

Maybe it's useful for [MENTION=947981]Lord Boeffla[/MENTION] too :)
[Galaxy S III Android Development] andip71:
Yep, indeed interesting.

But also not surprising as it triggers the rom functions for mount and unmount. If that would even not work, it would be a disaster.

Unfortunately I cannot call that from kernel or config app side.

I think we need to close this specific topic now. Especially as you guided us to a workaround for this specific case.

Maybe this is even history again in a week with new nightlies... in the CM/Omnirom world you never know... things break, things get fixed, every day :)

Andi
[Galaxy S III Android Development] Almin94:
I know that, but I ask because I have less stuttering with Omnirom kernel on my phone...
[Galaxy S III Android Development] ginzo:
Hahaha very good Andi, thank you!! I am never worried to flash and test again ??? I just dowload it and test it! Thanks a lot!!!! ???

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] andip71:
But why do you ask then?

I recommend the CM11 kernel for CM11 - stated on the homepage consequently.

I will not recommend the Omni kernel for CM11, also not when you ask :)

But if you prefer the Omnirom kernel on it, it is ok, just do it.

Andi
[Galaxy S III Android Development] adripred:
The folder /mnt/media_rw/sdcard1 is empty here using ES Explorer and not empty using Root Explorer and survive disabling the UMS mode. My default folder for external SD is /storage/sdcard1 and that folder is empty after disabling the UMS mode.

Worked here! Does my workaround for now! Thank you!

Regards!
[Galaxy S III Android Development] gtsfreak:
Flashed the latest beta of omni one thanks Dev for awesome work :D:thumbup:
[Galaxy S III Android Development] WhoDunnit:
healthd

Thank you for fixing the auditd complaints! Glad you could fix it without using my suggestion (which I won't repeat here to avoid a new lively discussion :angel:).

Would you mind updating healthd in ramdisk to get rid of the kmsg complaint

healthd: Could not open '/sys/class/power_supply/battery/batt_current_now'

Possibly you do not see this complaint yourself if you use an older version of CM11, but a couple of months ago the path was changed to /sys/class/power_supply/battery/current_now
[Galaxy S III Android Development] andip71:
Quick question: Is temperature reading meanwhile fixed with an updated healthd? I included it in the past because it was not working with the version coming with CM11...

EDIT: Yes, seems to work, at least on latest CM11 nightly. Just tested that with a test build. Will also test on Omnirom and if it works, I can revert back to the original healthd which come in the ramdisk of the both original kernels.

Thanks

Andi
[Galaxy S III Android Development] ginzo:
I used a lot the phone, as I had wifi but also data connection, and the results are good ☺☺☺

Latest Boeffla 2.4 beta 2

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] kadopt:
[MENTION=947981]Lord Boeffla[/MENTION]

I have noticed the following situations with my device when using v2.4 NG betas (and temasek v121):

After a reboot wifi can't find any networks, only a wifi toggle wil sofve this (some times I have to retry the toggle),

Blutooth either takes too long to connect, fails file transfers or file transfers are slow.

With build v2.3 these issues don't exist, maybe the samsung sources are to blame?

Cheers!
[Galaxy S III Android Development] f0xy:
I had the WiFi issue and a kind user told me to load and flash the kernel again through the boeffla app it solved it
[Galaxy S III Android Development] kadopt:
Oh! Just tried it and it actually fixed both issues! But why flashing from boeffla config gives different results from flashing with a custom recovery (i'm using philz latest 6.x version)?
[Galaxy S III Android Development] f0xy:
Not sure lol.. But I took it :)
[Galaxy S III Android Development] khanmein:
bro try flash omni NG. currently using v2.4b3 omni NG no wifi issue. previously v2.4 NG betas also no wifi issue.
[Galaxy S III Android Development] kadopt:
It was the same but [MENTION=2876905]f0xy[/MENTION] suggestion fixed my issues. Still don't understand the difference between flashing with Philz and with boeffla config... Should be good same.

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] adamsuail:
Need some help, I am on liquid smooth 3.2 and using omnirom kernel 2.4 beta 3.

I usually disable the haptic backlight without any issue on the stock kernel but once I flash this kernel the backlight goes to the default behavior and can't be turned off.
[Galaxy S III Android Development] kadopt:
Boeffla config, display + led, touch led settings.