yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
Hi!

Well, this is weird. It seems the PC can see your device but not interpret the file system.

What file system is your card formatted in?

Did it work before already and stopped working now?

What is the OS on the PC you connect it to?

I had this issue as well when I tried UMS mode with an exFat formatted sd card in my S3. The PC was running Windows XP without having exFat support, so it could not read it.

If that does not help... uh... maybe Carbon rom has removed something required for it? No clue. I use it with latest CM nightlies without issues.

Just some ideas...

If you are getting freezes ans soft reboots, then something is wrong!

What rom are you using, what kernel version? Without that elementar information, how could you think we can help?

Do not do overclocking or undervolting, and when you use the correct kernel for your rom, you MUST NOT have soft-reboots.

In worst case, reset the whole configuration in Boeffla-Config by going to the menu and select "reset app".

Yes, in order to get stock kernel back, you have to flash over the rom. It is simple and fast, no need to be worried about that. You will not loose data.

I do not know if other kernels implement UMS as well in any way...

Yes, I saw it and installed it for a quick test. However, none of my kernels (cm11 or cm11s) works with it. So it would mean I have to create another kernel flavour. Currently I am a bit reluctant still to do that. Maybe when I am getting too curious again :)

Andi
[Galaxy S III Android Development] nicesoni_ash:
Nope, working fine here on latest Carbon Nightly on Windows 8.1 x86..

_____________

Sent from my "GT-I9300/1+1" powered by Temasek/Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
Ok, glad to hear. Thanks for confirming that.

Andi
[Galaxy S III Android Development] 2phazt:
Well, I notice freezes too since I upgraded to cm11 a year ago. I first blamed the cm11 beta and in the meanwhile the insane memchip.

No change of any setting has helped so far...
[Galaxy S III Android Development] andip71:
Must be something like that... I never had any freeze (not kidding) on my both s3 devices in the past 12 months.

Andi
[Galaxy S III Android Development] Adam3Sixty:
Once again sir, thank u for ur reply.

I now have my Find 7 and I have to say it is damn lovely!!

Never would I ask u to put urself out to build something from scratch, especially for s device u don't own, let alone for one u did in a vain hope it would work on a different device :)

My father is going to be taking on my S3 and I will be leaving the newest kernel on it for him, but he has no idea about phones at all so once it leaves me that will be the end of our glorious relationship, lol.

Gonna keep this, and the OnePlus One threads bookmarked so I can check in every so often, and when the next stable comes out I can flash it for the old man, lol.

I know I keep saying it, but ur work is second to none on XDA, and I think everyone who uses any of ur work would agree with me on that. Expect another donation from me before I fully leave :)

Thanx again.

Adam
[Galaxy S III Android Development] XDAMaxe:
FAT32

yup, nothing changed, only rom and kernel updates

win xp sp3

Most weird is (better: was !) that the sd card itself (outside the phone) was recognized by the pc as usual (card reader) without any problem. (which is good for backup reasons...) and in the phone it works the same - only pc connection failed :cyclops:

After checking everything again and again without any clue I decided to reformat the sd card (32GB Class 10 Samsung ExtremePlus microSDHC 80MB/s) with FAT32 like before, recopied formerly backuped (simply copy&paste) contents and - HELLZYEAH ...... WORKS !

So finally the described issue might be caused by any corrupt data or whatever happened during usage of that memory card.

Anyway I'm happy and bigbigbig thanks for your - made me brainstorming - ideas. :fingers-crossed:
[Galaxy S III Android Development] andip71:
Phew, glad a reformat did the trick.

Yes, maybe some bits were wrong. Fat32 is known to be not the most robust file system.

But hey, most important is - it works :)

Andi
[Galaxy S III Android Development] scholbert:
Where to find some info about the missing parts for MHL

Hi,

first of all thanks a lot for the hard work you put into this project.

Right now i'm using CM11 nightly on my GT-I9305 and i'll check out one of your kernels soon.

It might be a little of topic here, but let me refer to a post from a few month ago and drop a short question here.

As we all know MHL is not supported in CM11/Omnirom. I always thought it was a kernel issue though.

As far as i got it, most basic parts are implemented at kernel level (setup SII9244, I2C transfers, etc).

I found some logs a few days ago about a service failing to initiate the framebuffer... can't find it right now.

Which parts are proprietary and missing?

Could someone please point me in the right direction.

Cheers,

scholbert
[Galaxy S III Android Development] evilperro:
ROM-info is provided in the post. Also haven't changed any settings = no undervolting/overclocking.

Kernel info: 3.0.101-CM (Boeffla-Kernel-2.3CM11.0-i9300-20140708@anip71)(gccversion 4.7 GCC) #1 SMP PREEMPT tue jul 8 07:33:34 CEST 2014

Kernel branch: stabel [i9300/cm/cm11.0]
[Galaxy S III Android Development] andip71:
Then something is severly wrong with the rom installation or the phone.

I cannot say. I know many people that have no issues.

Usually I would recommend a clean install in that case (but then maybe with a recent nightly + the latest beta kernel)... but it is up to you of course :)

Andi
[Galaxy S III Android Development] mad_ady:
I too am interested in mhl support, mostly because I'm pissed at Samsung that I can't use some piece of hardware I paid for. :)

I don't know what's missing except for hearing that there are some touchwhiz apis that are missing. It would be interesting to find out if there is any Samsung device (Note, S4, S5) that supports MHL with AOSP and work backwards from there...

Let us know if you find anything out.
[Galaxy S III Android Development] andip71:
I also do not know what all is missing. I guess nobody exactly knows.

And I do not want to discourage you, however I think some people tried hard to get this done already 2 years ago and gave up.

It is the same as with wifi direct / screen mirror... this is also broken and will most likely never be fixed.

So feel free to investigate, if you find something, let us know.

I do see the chance not higher than 1-2%, so I will not join the club at that time and spend my time with it as it is very likely wasted.

But guys... if you find more about it, you are the heroes :)

Andi
[Galaxy S III Android Development] flither:
Tried something like 5 different kernels last month, forgetting about Boeffla. I'm back like a hungry, thirsty guy after an all-week party ;) Home sweet home, there are no better kernels around :)
[Galaxy S III Android Development] cba1986:
Hey [MENTION=947981]Lord Boeffla[/MENTION]

Take a look at this:

http://xdaforums.com/showpost.php?p=56569791&postcount=621

It looks pretty interesting
[Galaxy S III Android Development] NeGriTa79:
Hello, I installed the Liquidsmooth of 29/10, which kernel version should I download ??? CM11 or Omni ???

thanks
[Galaxy S III Android Development] Stevica Smederevac:
Omni Ng.
[Galaxy S III Android Development] VirusPT:
Have a great holidays!
[Galaxy S III Android Development] XDAMaxe:
my 2 cents: I stayed for month with max. 1.6 Ghz (due to Exynos specs this is no oc) and had really nearly same batt drain as with 1.4 Ghz stock setting (probably because on the one hand 1.6 Ghz requires more power than 1.4 GHz but on the other hand tasks will be processed faster and therefore time for needed power is shorter compared with 1.4 Ghz - so all in all nearly same power for both clock speeds while not exceeding specs.)
[Galaxy S III Android Development] 2phazt:
I recognize a hot phone on 1704 and it seems a bit instable but this could have been also caused by insane zzmove ?
[Galaxy S III Android Development] kenzolo:
I have a strange problem, often the connection stop workin even if I can see the icon "H+" next to the signal bars,

Could be a kernel related issue?
[Galaxy S III Android Development] gtsfreak:
Can't wait for lollipop version of this kernel love it so much :D:thumbup:

Sent from my GT-I9300
[Galaxy S III Android Development] andip71:
Very unlikely.

Most probably provider or modem.

The kernel has almost nothing to do with signal reception.

Once there are some working cm12 builds out, I will look at it of course.

Andi
[Galaxy S III Android Development] gtsfreak:
[MENTION=1045701]lordbo[/MENTION]effla Thanks bro appreciate your work :D:thumbup:
[Galaxy S III Android Development] exwan:
I cant find omni ng downlad link. Its empty.
[Galaxy S III Android Development] andip71:
Then you looked into the stable releases folder?

There is not yet a stable release for any NG kernel so far, so you need to look into the test folders... latest beta.

Andi
[Galaxy S III Android Development] exwan:
Yes. Thank you. I have use the beta.
[Galaxy S III Android Development] SlimFatso:
Hey, [MENTION=947981]Lord Boeffla[/MENTION] there is a pretty stable lollipop for our device. It has almost everything working, or are you waiting only CM12 ?
[Galaxy S III Android Development] andip71:
I am waiting for the first CM12 nightlies. They should not be too far away I guess.

Thanks

Andi
[Galaxy S III Android Development] ayoubij:
No more developing for 4.4.4 kernel?

I say one more "stable" version? :p

Im on omni ng kernel but its not updated from one month
[Galaxy S III Android Development] ayoubij:
Whats dynamic filesync? I didnt find answer in FAQ

Also wanted to know in GPU i have profile none, isnt this same as default profile?

Anyways i want to try to overclock gpu a little to gain performance, any tips on how to? Thanks
[Galaxy S III Android Development] JustArchi:
I'm sad to inform you that due to no active maintainers, it IS far away.

In best scenario, if we accomplish something stable and fix all remaining bugs, CyanogenMod MAY accept our pull request on their gerrit, but still, nobody said that any nightly for i9300 will arrive.

Literally no one cares about us at the moment. We're doing quite well on our own with alpha cm12 for i9300.
[Galaxy S III Android Development] abhibnl:
I second that. There's not even a single commit relating to i9300 in cm gerrit. Though they're merging their features pretty fast which is good.

Sent from Galaxy S3 Powered by Nameless KK + AK
[Galaxy S III Android Development] andip71:
When CM team drops a stable or at least a final M version, I will put latest changes in and declare the kernel version stable as well.

I think they are close to the end on CM11, so I am happy to wait for some more time.

It means, sync requests will not be carried out when the screen is switched on. This should make UI a bit more fluid in general.

When screen is off (or going off), the data will be synced back.

You should get some basic explanation when you search for "dynamic fsync" and "faux" (who implemented it years ago...).

Andi
[Galaxy S III Android Development] k.d.s:
Quick reply.

what is a diff between normal and NG kernel ? may be a noob question but will be help full if i can get answer quickly.,

............................................................................

Oh k i founded the answer myself :D
[Galaxy S III Android Development] XDAMaxe:
:good:that you aquired advanced user functions ...;)

NG version is recommended because of genuine samsung sources with latest updates from [MENTION=947981]Lord Boeffla[/MENTION] (despite that the old kernel sources are a real crap because they are based on try and error but imo never reached an as satisfying level as NG did from the start)
[Galaxy S III Android Development] simplicio11:
[MENTION=947981]Lord Boeffla[/MENTION]

take a look: http://xdaforums.com/showthread.php?p=57054443

[emoji106]
[Galaxy S III Android Development] andip71:
If that means I have to add another kernel variant to my existing S3 kernels, then it is a no-go for me.

If it is possible to make a kernel compatible with Nameless and normal other roms too, then it might be an option.

Anyways, not doing any quick shots at the moment, due to lack of time.

Andi
[Galaxy S III Android Development] nicesoni_ash:
I think you could wait at least till they release a beta first.

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
For sure, not working based on alphas anymore. I am too "old" for that :)

Andi
[Galaxy S III Android Development] abhibnl:
Well assuming from how things are going so far, both cm12 and nameless will be having hwc from dhiru as archi will b the one working on cm12 and he already decided to base it on mali r4p0 drivers. So i guess you'll only have to build one kernel for two L builds. [emoji106] [emoji106] [emoji111] [emoji111]

Sent from Galaxy S3 Powered by Nameless KK + AK
[Galaxy S III Android Development] Moster2:
Sry, but I was the one to base it on r4p0, since it was time to move ahead.
[Galaxy S III Android Development] nicesoni_ash:
And you did good. :beer::beer:

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] abhibnl:
Oh sorry man! Didn't mean to offend you in anyway. We all know how hard you worked on the kernel and drivers part and not to forget, bringing stweaks for full customization of kernel. Yes, all the credits go to you for the r4p0 bringup. I mentioned Archi just to generalize the cm12 topic. and BTW, you rock dude!!! Sorry if u felt any kind of disprespect! It was never my intention. :highfive: :highfive: :D
[Galaxy S III Android Development] ayoubij:
Does using zram affect negatively the life of my phone or the sd card?

Also if i keep swapiness override to off, what will be the default value?

Im currently using 4 zram device 800 is it too much? Whats recommended

Thank you for the time

Edit: nvrmind ive read it in the faq on the website
[Galaxy S III Android Development] kadopt:
Zram only drains battery and uses cpu time to compress and decompress data inside ram. Default swapiness is 60. I use 400mb with 1 device.
[Galaxy S III Android Development] andip71:
Honestly, the zRam overhead is almost not noticeable.

With or without zRam, I always had the same battery life. It is not that Gigabytes of data are affected, we are talking Megabytes, and to compress/decompress a few megabytes or portions of it is a piece of cake for the S3 Exynos SoC.

Andi
[Galaxy S III Android Development] simono_pl:
What size zRam do You recommend?
[Galaxy S III Android Development] andip71:
If you do not have any strong reason for it - stay away from zRam.

But if you need it, I always used 4 devices, 600 MB total size.

Note: zRam works completely dynamic. It does not consume any memory or CPU when it is not being utilised. And it only consumes the memory it needs, so nothing wrong to go with a high total size.

Andi
[Galaxy S III Android Development] HorstiG:
Aha ?

HGT - Galaxy S3 - S5 - Tesla TTL7 any AOSP ROM
[Galaxy S III Android Development] ayoubij:
After about a day with 4 devices 800 total i can really feel true multitasking without having to restart apps. Btw what value for swapiness you recimmend because i didnt rly understand its meaning from the faq
[Galaxy S III Android Development] paour:
And useful LMK values would also be great. Whenever I tried zram, I seldom noticed any improvement in multitasking, my apps would still be restarted... or slow to a crawl.
[Galaxy S III Android Development] XDAMaxe:
This won't be an easy one...

Search infos at xda about [MENTION=3357461]zeppelinrox[/MENTION] V6 supercharger and patching services.jar (only possible by editing manually with kitkat custom roms) to learn how to improve lmk and multitasking. Because of lots of dependencies you cannot talk about lmk in general; memory management is extremely phone dependant and requires a certain common understanding how things work under android/linux and especially regarding phones capabilities and running android version and - most of all - users preferences.
[Galaxy S III Android Development] mad_ady:
[MENTION=947981]Lord Boeffla[/MENTION]: I require your advice.

I plan on building a custom variant of your kernel (Omnirom-NG variant) with a custom patch (specifically this patch that can turn your phone into a USB keyboard: https://github.com/pelya/android-keyboard-gadget/issues/11).

I'm not sure of the following things:

1. Is this the correct git repo for the omnirom-ng kernel? https://github.com/andip71/boeffla-kernel-omnirom-s3.git If yes, then how do I select between NG and non-NG?

2. I managed to build test kernels in the past, but I never bothered to flash modules so I had issues with wifi not working. I wanted to ask what steps do I need to take after building the kernel to get to a flashable zip? (I used to flash the kernel with dd previously). A point in the right direction would be appreciated.

Thanks!
[Galaxy S III Android Development] andip71:
Hi Mad_ady,

to 1) Yes, this is the correct repo. There is a second branch in the repo, called ng_boeffla. You need to fetch this branch to build the NG kernel.

to 2) After the compile run, the modules are spread across the build directory. You need to collect them together (e.g. with a find command) and move them into the /system/lib/modules folder in the flashable zip (you can take my zip as example).

Hope this helps

Andi
[Galaxy S III Android Development] mad_ady:
Thanks for the help. I started to build it. However I get this compile error:

CC drivers/gpu/mali400/r3p2/ump/common/ump_kernel_common.o
arm-linux-androideabi-gcc: error: directory: No such file or directory
arm-linux-androideabi-gcc: error: directory": No such file or directory
make[3]: *** [drivers/gpu/mali400/r3p2/ump/common/ump_kernel_common.o] Error 1
make[2]: *** [drivers/gpu/mali400/r3p2/ump] Error 2
make[1]: *** [drivers/gpu] Error 2
make: *** [drivers] Error 2

I ran these commands up to now:

git clone https://github.com/andip71/boeffla-kernel-omnirom-s3.git
cd boeffla-kernel-omnirom-s3
git checkout ng_boeffla
make boeffla_defconfig
make menuconfig
make

I haven't looked into the error yet, but I wanted to ask if there are incomplete changes pushed to git that could lead to such an error. The non-NG kernel compiled just fine.

Thanks - I will look into it later.
[Galaxy S III Android Development] ZaneZam:
Take this one in and u should be good : https://github.com/zanezam/boeffla-kernel-cm-s3/commit/20e9c1f878bf7e1a4e05d29b4f9a21bf8d63c22f
[Galaxy S III Android Development] andip71:
I think you saw ZaneZams post already. No, there is no broken code in the repos.

It compiles fine for me as is, however for some the mentioned commit is required.

Andi
[Galaxy S III Android Development] andip71:
New betas...

Hi all,

as CM team is still presenting CM11 nightlies (same goes for Omnirom team), I will put an intermediate maintenance version out for you. It is basically a refresh of components and some internal bug fixing and hardening.

Betas are for all 4 kernel variants:

CM11 - Version 2.4-beta8

28.11.2014

Update zzmoove to version 1.0-beta4 (credits to ZaneZam)

fstrim in Boeffla-Config app using internal fstrim command now

Option in Boeffla-Config to install full busybox deactivated (CM/Omnirom roms come with fully stuffed busyboxes already, so this was useless)

Kernel code updated by all recent commits of CM kernel dev team as of 27.11.14

Internal Boeffla-specific hardening and bug fixes in startup- and controller scripts

Update internal su to version 2.35

Updated ramdisk to version of nightly 26.11.14

CM11 NG - Version 2.4-beta8

28.11.2014

Update zzmoove to version 1.0-beta4 (credits to ZaneZam)

fstrim in Boeffla-Config app using internal fstrim command now

Option in Boeffla-Config to install full busybox deactivated (CM/Omnirom roms come with fully stuffed busyboxes already, so this was useless)

Kernel code updated by selected recent commits of CM kernel dev team as of 27.11.14

Internal Boeffla-specific hardening and bug fixes in startup- and controller scripts

Update internal su to version 2.35

Updated ramdisk to version of nightly 26.11.14

Omnirom - Version 2.4-beta8

28.11.2014

Update zzmoove to version 1.0-beta4 (credits to ZaneZam)

fstrim in Boeffla-Config app using internal fstrim command now

Option in Boeffla-Config to install full busybox deactivated (CM/Omnirom roms come with fully stuffed busyboxes already, so this was useless)

Kernel code updated by all recent commits of Omnirom kernel dev team as of 27.11.14

Internal Boeffla-specific hardening and bug fixes in startup- and controller scripts

Update internal su to version 2.35

Ramdisk is still up-to-date (nightly 26.11.14)

Omnirom NG - Version 2.4-beta8

28.11.2014

Update zzmoove to version 1.0-beta4 (credits to ZaneZam)

fstrim in Boeffla-Config app using internal fstrim command now

Option in Boeffla-Config to install full busybox deactivated (CM/Omnirom roms come with fully stuffed busyboxes already, so this was useless)

Kernel code updated by all recent commits of Omnirom kernel dev team as of 27.11.14

Internal Boeffla-specific hardening and bug fixes in startup- and controller scripts

Update internal su to version 2.35

Ramdisk is still up-to-date (nightly 26.11.14)

Let's hope, CM and Omnirom teams will begin with CM12 soon and finalize CM11, then I can also close that topic with a set of stable kernels.

Thanks

Andi
[Galaxy S III Android Development] scholbert:
Hi,

do you think NG kernel is ready for GT-I9305 as well?

Maybe i should create my own config and give it a go...

Thanks for your efforts!!!!

Cheers,

scholbert
[Galaxy S III Android Development] andip71:
The kernels do not run on lte s3.

They need specific kernels.

Sorry

Andi
[Galaxy S III Android Development] scholbert:
Yeah, i know that the binaries are for GT-I9300.

How about the sources... do they differ a lot?

Would be nice to get NG running on the LTE version as well.

Anyway thanks for your reply and have a nice weekend!

Cheers,

scholbert
[Galaxy S III Android Development] mad_ady:
Thank you [MENTION=3279788]ZaneZam[/MENTION] and [MENTION=947981]Lord Boeffla[/MENTION]. Indeed, I have svn 1.8.8 but you've saved me a lot of headscratching in debugging this. I would have never guessed that there are scripts checking svn version (probably to extract the patchlevel of some component) that run from the Makefile. I assumed any error you get after make must be a compilation or linking error.

Well, I learned something new, so thank you both.

One more question - are the ramdisk files (in ramdisk_boeffla) automatically added to the kernel zImage during make, or is there an extra step I need to make? I don't see a separate ramdisk file in the original update script...

Edit2: Never mind - I figured it out. zImage is a part of boot.img. ramdisk is the other component. I'm packing it now with mkbootimg