yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] Moster2:
Hmm, I replaced the user lvl libs with the libs from the leak and rebuild cm. Unfortunately it wont work correctly. The mali libs will fail to load. According to catlog its related to a mismatch of user and kernel drivers. So there are basically 2 things that might help to fix it. Release of the new kernel source or someone can fix it with a hack (which Im not capable of)
[Galaxy S III General] Stevemeister:
Those Mali drivers are about a year old. Does anybody know what version the driver are from the leak?

http://malideveloper.arm.com/develo...source-mali-gpus-linux-kernel-device-drivers/
[Galaxy S III General] JustArchi:
You won't see newer kernel, as Samsung doesn't need to update it. 3.0.31 works and it will work until Android forces specific branch as a dependency. And if google does it then you won't get this version from Samsung anyway.

Of course they can still provide updates of the source but kernel base will still be the same.
[Galaxy S III General] Lctwisk:
I think it's not that easy. Maybe you should look at similair commits of [MENTION=3208754]codeworkx[/MENTION] adding new Mali libs. Can't find them atm...
[Galaxy S III General] Moster2:
Ive seen his commits and he basically did the same, but it seems like the new mali blobs are not compatible with the kernel, so we most likely need to wait for the kernel sources. (this is my unexperienced guess though)
[Galaxy S III General] JHilderbrando:
Hey, I've never updated my modem before is it worth doing? Will I get better reception or connectivity of some kind?

Is it just a zip to flash with CWM version?

Thanks, sorry if its a stupid question.

JohnnyP
[Galaxy S III General] xeizo:
All very exciting! But, even if partly consisting of dated code so is CM 10.2 a HUGE improvement over running a Samsung stock-ROM imho. I haven't tested the leaked 4.3 but I don't feel like since it most probably is bloated :)

I think running this is almost like getting a new high-end phone for free, and the compatibility with the Boeffla-kernel is a nice bonus with all the settings available in Boeffla-config. I will possibly tinker with the Audio/DAC-settings as I'm specifically amused by HeadFi :D

---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------

Im really no expert, rather a newbie, but I flashed it with Odin 3.09. I don't know if anything got any better, bot nothing became worse anyway as everything is working. I'm on "3" in Sweden.
[Galaxy S III General] Moster2:
It can help to get better reception, but also cause the opposite. You need to test and yes, this is a cwm flashable
[Galaxy S III General] prabhjots:
This will most likely also change the efs and ril. Any failsafe way to backup the current partition structure and not just the efs folder.?
[Galaxy S III General] cink40:
Ril is not included, just flash with cwm and your efs will also not be changed...i just did that.
[Galaxy S III General] prabhjots:
You must have updated to xxemg1 upwards series ROM. As far as I understand any stock ROM later than emg1 modifies the efs structure and newer modems do not work on older efs structure and vice versa.

I'm using xxemc2 baseband.
[Galaxy S III General] scoobyjenkins:
I was on xxemg4 after flashing a stock rom, so had nothing to lose! Working fine for me so far.

Tapatalked that shiznit.
[Galaxy S III General] cink40:
You understand incorrectly. Again, if you flashed only modem efs will not change. My phone works with old and with new modems. I never updated to Samsung xxemg1, I am on cm, slim like forever...
[Galaxy S III General] prabhjots:
Seems improbable... Are you sure you never flashed that series? Emg1 series came like forever ago too.. ;)

Anyhow, my only question was about a full fledged efs partition backup, not just the folder.. No harm in taking such a backup, is there? :)
[Galaxy S III General] cink40:
Just read some posts back about this efs issue and you will learn. And yeah I am 100% sure, I was on Samsung ROM back in 2012, and absolutely no harm in backing up efs. First thing I do after rooting the phone...
[Galaxy S III General] adkamath:
Hmm so we wont get new blobs after all... :( ... still beats stock FW.
[Galaxy S III General] ajobbins:
My Nexus 5 should be ready for pickup within the next few hours :D

Goodbye S3, Hello N5 with KitKat :D
[Galaxy S III General] bornlivedie:
Who told you? It's too soon to tell.
[Galaxy S III General] vldesco:
Deleted. Wrong thread
[Galaxy S III General] Moster2:
Those questions dont really belong here. This is the cm thread
[Galaxy S III General] adkamath:
well I dont see anyone actively working on it. Also the one person who did attempt the blob integration ran into troubles so.. i am not very hopeful. Still fingers crossed. :fingers-crossed:
[Galaxy S III General] yaniv30:
Official 4.3 for i9300 ?

What this means to us (CM 10.2 users) ?

http://www.androidcentral.com/international-galaxy-s3-android-43-update-rollout-begins
[Galaxy S III General] tmantanner4:
Nothing until kernel source drops, then it will help.
[Galaxy S III General] yaniv30:
Oh well.... :(
[Galaxy S III General] simono_pl:
Maybe better modem.
[Galaxy S III General] FDisk80:
That you already can have. But that got nothing to do with CM itself.
[Galaxy S III General] padraigdoran:
When in in gallery and press back button it keeps reloading the camera, anybody else getting this?

On latest nighty.
[Galaxy S III General] cmanon:
After the announcement for the official 4.3 Samsung added support for ANT+, that seems to be a firmware update for the broadcom chipset, are those updates landing on the 10.2 anytime? I just don't know exactly how that works.
[Galaxy S III General] dhiru1602:
Maybe the GPU blobs. I am trying them now. Will report back.
[Galaxy S III General] Moster2:
Maybe you can fix the issue I got when I tried them. Catlog showed that the version of the kernel driver is not matching the lib version. So I assumed that we need to wait for the kernel sources.
[Galaxy S III General] dhiru1602:
Yes. We need the kernel source. The userspace gpu driver version doesn't match the kernel.
[Galaxy S III General] Moster2:
Ok, so I wasnt too stupid to correctly integrate the libs :D
[Galaxy S III General] zomebody:
Everything freezes

Hey friends.

Ive recently had some problems with my phone freezing randomly. Its like when i use it, sending a text, listening to music or whatever, it just freezes and i have to press Vol up + power + home so it reboots. Has anyone had this problem or a similar one? And what information do you need so you can help me the most?

Thanks in advance
[Galaxy S III General] simono_pl:
For some people helped back to stock and then again flash CM. I don't have any freezes.

Send from my GT-I9300
[Galaxy S III General] d1rekt0r:
I still dont get it .... :S

What are those libs/blobs/whatever are supposed to help with in CM10.2 ?

Better gaming performance (3D) or its 2D or Camera ?
[Galaxy S III General] zomebody:
So basically flash a stock android and then root the **** out of the phone once more?
[Galaxy S III General] Moster2:
better performance in 3d and maybe also 2d
[Galaxy S III General] bornlivedie:
2D performance, specially with animations and 3D performance.
[Galaxy S III General] adkamath:
Here is a simple explanation

Samsung does not completely disclose how their hardware works. (e.g. Graphics etc). The CM team basically takes the code from AOSP and others and examines the kernel(which is the linux kernel for which samsung is legally bound to release source code). Now technically the kernel and supporting source code should contain all the drivers for all the hardware ( Graphics , sound , camera etc). And here is where it gets dirty, Sammy releases only the kernel as source code but the supporting files ( which contain the detailed information of hardware workings) are only released as compiled "executables " aka blobs.

What CM team does (on a very abstract level) is that they open the source code. "Reverse engineer" how sammy uses their blobs , supply the blobs with their own kernel which is modified to use those blobs. So as far as I understand we are using 4.2 blobs with 4.3 because the 4.3 kernel has been modified to use them. Now we have 4.3 blobs with the new leak but since we don't have source code we cant "see" how they are supposed to be used. So we wait till sammy releases source code,tweak our code and enjoy better performance.
[Galaxy S III General] tontiv:
can somebody please send me the dark abstract wallpaper with green hints? can't seem to figure out which apk to extract it from :(
[Galaxy S III General] d1rekt0r:
Now that's an explanation ! Thanks !

But I used used to do some programming in different languages and reversing compiled file was nearly impossible , is it the same here , i mean do they really go that far to please us ....now my respect for cm team and contributors got to a whole new level!
[Galaxy S III General] blazevxi:
I'm sure the team solved (or fixed) the issue with t2f thanks to something like that
[Galaxy S III General] adkamath:
They dont actually "reverse compile" they just try to understand how samsung uses the blobs. For example suppose you find the following line in samsung kernel source

so you see how samsung uses the graphics blob to create a "new window "/ dialog what ever.So if I give you a blob and ask you to create a new window you can easily do so!!Of course this is a very very simplified example and it is pretty hard to understand how these blobs work and how to properly call/address them. Thats why all the nightlies. And thats why all that noise was being made over sources during CM 10.1 ... we were literally, and still are, "Flying Blind" especially in Exynos. :(
[Galaxy S III General] dhiru1602:
Blobs are userspace components which correspond to the HAL (Hardware Abstraction Layer). It is this layer which is responsible for communication between the kernel and the operating system. GPU kernel driver is opensource, but the GPU HAL is closed source. This is the case with all the devices, but on our device, much more components of the HAL are closed source like FIMC, FIMG, HWJPEG, TVOUT. Samsung doesn't release the source code for this components because it doesn't necessarily have to. Without the source code, we are forced to use the compiled binary which may or may not work properly. Since we are left without options, we often mess around with the Android framework, making dirty hacks to get them to work. We will not be able to futureproof our device with newer versions of Android unless we have the source code since making edits on compiled binaries is not possible and hence we have to wait for official releases so that we could get newer binaries (blobs). Here is the list of all the blobs that we use on our device. Having proprietary code is not uncommon, but Samsung doesn't release the source code for essential parts of the OS like Graphics subsystem, OMX and DSP, which makes things more complex provided there is no documentation for the SOC, nor they are wiling to help developers.
[Galaxy S III General] EcPercy:
I had a random question, but it's something that has bugged me for some time. Whenever I flash any CM rom the device serial number always changes from what the label on the device has. Does anyone know why? I noticed that if I flash back a stock rom the serial number is correct.
[Galaxy S III General] prabhjots:
Same problem for me.
[Galaxy S III General] Lctwisk:
4.3 kernel source is dropped http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=I9300
[Galaxy S III General] adkamath:
Thanks Dheeraj for the technically sounder explanation. As far as I understand ( and its very little I assure you) , most pressing issues are the Mali blobs for which memory allocation is tricky?

Also can you comment on OpenGL 3.0 ES support for SGSIII on CM?
[Galaxy S III General] Xnexto:
In stock JB 4.1.2 i couldn't play games like dead trigger 2 due to the lag, but now with cm 10.2 i can use the tegra 4 graphic settings with better performance than stock. That is amazing :D

But how so?

Using gs3 i9300
[Galaxy S III General] d1rekt0r:
Hey [MENTION=4604352]Moster2[/MENTION] , maybe you should try to integrate those blobs now with this kernel before we get more official/CM integration , just to see if it works :D ?
[Galaxy S III General] Moster2:
I can try to, but there is a much higher chance that dhiru gets this done :P
[Galaxy S III General] yaniv30:
+1

Can't stop giggling :)
[Galaxy S III General] Moster2:
Im not able to merge it yet and probably wont be, but what I find kind of interesting is that there is a new folder in /driver/gpu called mali400. Looks like samsung included some sources for the mali gpu
[Galaxy S III General] FDisk80:
In todays nightly:

[B]vendor/samsung[/B]
25abb7a jf: Update blobs

So this is it? :eek:
[Galaxy S III General] yaniv30:
Sorry for the noobish question but, in a day to day use what this will do to our phone?

Thnx!
[Galaxy S III General] bornlivedie:
Make it magical :D

btw, I don't see it. It's not on the gerrit.
[Galaxy S III General] simono_pl:
I think it's for S4

Send from my GT-I9300
[Galaxy S III General] Moster2:
Jf is not our device. Isnt that the s4/i9505?
[Galaxy S III General] alki4:
Adding new contacts

Is there an easier way for creating new contacts from call logs? When adding phone numbers from call logs to contacts, it seems to require an existing contact for me to attach the number too. What I really want to do, is to create a new contact profile.
[Galaxy S III General] bornlivedie:
That explains everything.

As far as I know, no mali blobs available for 4.3 right now. We do have the kernel sources, but it will be a while before we see those implemented.

Maybe 1 or 2 weeks.
[Galaxy S III General] prabhjots:
When it requires you to select an existing contact, see the"create new contact" button at the bottom :)
[Galaxy S III General] alki4:
:silly: I see it now. Bloody hell, I feel like a dumbass. The theme I have been using camouflaged it so well, it's virtually hidden.

edit: found the thank button immediately after i clicked submit.
[Galaxy S III General] d1rekt0r:
Thanks for trying man :D

I guess we wait for [MENTION=2875964]dhiru1602[/MENTION] to respond :D :good:
[Galaxy S III General] Lctwisk:
How can you give an ETA for new blobs? If someone takes time to add them, we will get them. If not, we will never see them.
[Galaxy S III General] bornlivedie:
Learn to read. I'm talking about the kernel sources... Samsung released them today.

Blobs? I don't know... could be maybe next year or never.
[Galaxy S III General] Lctwisk:
Learn to read? The blobs everyone talks about van easily be extracted from the 4.3 ROM released yesterday..
[Galaxy S III General] Moster2:
Extracted easily, but not added unfortunately. We need to integrate parts of the new kernel sources into the current smdk4412 kernel.
[Galaxy S III General] ayoubij:
I miss the days [MENTION=3208754]codeworkx[/MENTION] added the blobs at the same second the rom is released :(
[Galaxy S III General] aCoZz:
GApps

the link for the GApps is broken...
[Galaxy S III General] prabhjots:
http://xdaforums.com/showthread.php?t=2397942
[Galaxy S III General] Moster2:
Adding the blobs is not hard. I have also already done this :P But this time the blobs are incompatible with cm's current kernel. Merging the new sources is not done within a few minutes unfortunately.
[Galaxy S III General] simono_pl:
Yeah but also update 11 is on the way http://review.cyanogenmod.org/#/c/47982/ not merged yet. I think update 12 also will be waiting if someone put it .
[MENTION=3208754]codeworkx[/MENTION] must lock at this but we all known that he don't have time on this year :crying:
[Galaxy S III General] d1rekt0r:
Is it true that they gave us mali sources ?
[Galaxy S III General] Moster2:
Yes, it seems to be true, but totally undocumented :D
[Galaxy S III General] d1rekt0r:
So we basicly need nothing more from Samsung now right ?
[Galaxy S III General] tmantanner4:
Anyone got any idea on how long it takes to incorporate these sources into cm?

I'm a little eager :P
[Galaxy S III General] Moster2:
At least regarding the mali gpu it looks good. I hope the sources are also useful :P

We will see if someone is able to do it. Yank555 has already merged the sources into his stock kernel. This is easier to achieve though, since you dont need to worry about the whole patches and customised stuff of the current cm kernel.
[Galaxy S III General] tdcfpp:
You can try to imagine: diff between u11 and u12 is ~90 MB. Not every change is relevant for us.
[Galaxy S III General] guerouig:
guys, I flashed latest 4.3 leak from samsung (XXUGMJ9), that wiped everything. If I were to flash again cm 4.3.1, would I run into trouble with efs?
[Galaxy S III General] d1rekt0r:
Well, someone is working on 4.4 build for i9300 for sure, he knows that sources are released , so i guess we will see them implemented in 4.4 builds ?
[Galaxy S III General] Moster2:
Cm doesnt care about that. As long as the modem fits the efs version, everything is fine
[Galaxy S III General] angelus249:
Installed lates Samsung leak before, just wanted to have a look at it and upgrade BL/Modem in the process. Worked nicely.

Can't get any cm10.2 running. tried nightlies from 11/06 and 11/05.

Modem: I9300BUUGMJ3

recovery: twrp 2.6.3.0

can install it, boot one time right from recovery, setup, get cell reception.. everything works. Until I reboot... it wouldn't boot up anymore. Just the b/w Samsung Galaxy SIII sign shows up. Thats it. Of course wiped data/system etc. before installing, also tried wiping cache/dalvik before booting the first time

any suggestions?
[Galaxy S III General] Azmil2307:
Like it!!

I like this rom :)
[Galaxy S III General] FDisk80:
Latest nightly:

[B]vendor/samsung[/B]
898fb32 Blob updates from MJ7

Still not ours? :silly:

Edit: yep, thats S4.
[Galaxy S III General] oae08:
The recommended recovery is CWM. Im using latest philz recovery which is based on CWM recovery
[Galaxy S III General] dhiru1602:
Managed to get a build booting with Mali400 r3p2 driver. Patched the kernel in a very lazy manner and hence it would have broke a lot of stuff. Please make a backup before flashing.

The source built HWComposer needs changes and doesn't currently work with the new GPU driver. I had to remove it from the build to get it working.

Build is based on latest nightly.

Download: http://d-h.st/7Su

Source: https://github.com/dhiru1602/android_kernel_samsung_smdk4412/tree/cm-10.2-mali-r3p2
[Galaxy S III General] xrad:
So maybe you can help me, too.

I used to use Philz as well and had not issues with this. Two days ago I also briefly switched to stock 4.3 to have a look. Obviously flashing stock killed my working version of Philz. So I reflashed Philz using the latest released version. But for some reason it wasn't able to mount /storage/sdcard1. I googled a bit but was not immediately able to resolve that, and then just installed CWM, which worked. Long story short: I'd like to stay with Philz (mainly for the file manager). How do I restore access to the external sdcard?
[Galaxy S III General] Tanogeek:
Two infernal storage
[Galaxy S III General] svetloslav:
Wait, I thought nobody from CM wanted to even touch the S4. Between that stance a few months ago, and now what has changed, so that S4 sports a working CM build with updated blobs, while we are left in the dust?
[Galaxy S III General] Moster2:
Some people said that they had bad performance if they didnt, so I would recommend it
[Galaxy S III General] Pheoxy:
Apparently some had problems with the External Memory as well if you didn't do a full wipe.

You should anyway because of the jump from 4.2.2 to 4.3 Android anyway.

Sent from my GT-I9305
[Galaxy S III General] SweetCupcake:
Hav everybody the link to the gapps jb43 20130729

SGS 3 /CM 10.1 Android 4.2.2 / Tapatalk 4 Beta
[Galaxy S III General] Moster2:
http://d-h.st/9V3
[Galaxy S III General] SweetCupcake:
Thx :)

SGS 3 /CM 10.1 Android 4.2.2 / Tapatalk 4 Beta
[Galaxy S III General] simono_pl:
Guys did You see this http://www.androidpolice.com/2013/07/25/app-ops-android-4-3s-hidden-app-permission-manager-control-permissions-for-individual-apps/.

I hope this will be also on CM.
[Galaxy S III General] masze:
Temasek kernel working great...

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III General] miozao:
Merged contacts

Have any way to import contacts merged from stock rom app, to cyanogenmod?

I have many contacts merged (googe + facebook + skype, etc)
[Galaxy S III General] Moster2:
Shouldnt it already be there, just not unlocked? :D

e: Ok, it is there.
[Galaxy S III General] simono_pl:
After syncing contacts witch Google and FB application etc. You must again merge it on CM.
[Galaxy S III General] miozao:
:(

ok, thanks!

Let´s try CM 10.2 :P
[Galaxy S III General] AthlonGFX:
Help please!!!

HI there i installed this rom this morning and went by the instructions step by step and all went great but now i wanted to go back to cm10.1 but i cannot open my internal sdcard and i have already wiped, can anyone help me i need my phone real bad:crying:... Thanks in advance:fingers-crossed:

-CJKaufman
[Galaxy S III General] overflyer:
You didnt do any backups at all beforehand? Data copies? Nandroid? Titanium?
[Galaxy S III General] Moster2:
Go into your recovery. then you can push the cm10.1 zip with: adb push cm10.1.zip /sdcard/

Replace the zip name with the correct one. You need to have the android sdk installed/configured
[Galaxy S III General] AthlonGFX:
I did and i tried to restore still unable to open my internal sdcard but cache is able to mount aswell as /efs; /preload... i was able to flash illusion rom but it sits in the boot anim:(
[Galaxy S III General] ereziel:
Does anybody have problems with root file explorers?

I can't remount /system filesystem to read write with fx file explorer for example. However, I can remount manually via root console.

Anybody having the same issues?
[Galaxy S III General] AthlonGFX:
Sorry im not so good with ADB can you explain a little more.. thank you for the quick reply's guys:cowboy:
[Galaxy S III General] Moster2:
I dont know if I probably misunderstood you, but you said that you cant access the /sdcard/ storage, right? Since this is an issue of the rom, you can still access /sdcard/ via the recovery. Therefore you need adb.

So download the android sdk for your system http://developer.android.com/sdk/index.html (sdk tools only)

Extract it, open a shell/cmd, browse to the extracted files within the shell. Then enter the folder tools (cd tools/). There you start the program "android", on linux you simply type: ./android. I think on windows you can also just start it via the windows explorer.

This will open the android sdk manager. There you install the android sdk platform-tools. Then you will have a new folder called platform-tools in your android sdk folder. Go there in the shell. Now you have the adb executable in there and you can try to use it. Type for example: adb devices.

You will see the devices that are connected to the adb. This should be your phone in recovery.

Now put the cm zip into the platform-tools folder and type this: adb push cmzip-name /sdcard/

This will copy the file to the device (takes some time).

You can also later add the platform-tools folder to your environment variables, so you can run adb from everywhere.

My text was of course completely useless if thats not your issue :D
[Galaxy S III General] AthlonGFX:
Unfortunately my /sdcard is completely inaccessible but for some reason i can install roms just fine but it will just sit in boot and eventually my phone will vibrate and soft-key lights will switch on but it still sits in boot ... roms tried: Sotmax ult v16 beta, CM10.1, CM10, Illusion and MIUI V5

It could be my eMMC so i will try flash stock with odin and Re-Partition but someone said it might be a bad idea:silly: any advice?
[Galaxy S III General] shassino:
Just download platform tools from google repository:

http://dl-ssl.google.com/android/repository/platform-tools_r18.0.1-linux.zip

http://dl-ssl.google.com/android/repository/platform-tools_r18.0.1-windows.zip

then open a shell or command prompt change dir to platform tools one than run "adb push C:\folder\file.something /sdcard/file.something"