yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] thracemerin:
It's just the Maguro CM9 thread: http://xdaforums.com/showthread.php?t=1398495

It's not any more exciting than this one to be honest, but there is slightly less garbage in it. <- not an invitation to crap it up.
[Galaxy S II General] Testraindrop:
Oh ok thanks, though it was a special Dev-only thread with more development background :D
[Galaxy S II General] thracemerin:
Nothing that exciting :)
[Galaxy S II General] marcosxd:
Does anyone know where to download the LQ6 modem? Thanks in advance!
[Galaxy S II General] minty1978:
confirmed, i get that also. from a fresh full wipe install.
[Galaxy S II General] chrismalla:
You didn't answer my question actually, but thanks anyway ;)

http://veyka.co.uk/radios/I9100_radio_XXLQ6_CWM.zip
[Galaxy S II General] r7s:
This "bug" might exist due to Google deprecating C2DM.
[Galaxy S II General] thracemerin:
The CM base is based on AOSP, but its not the same. If you look at the AOSP repo and compare it to the CM repo they differ significantly, mainly due to the addition of features to CM that are not in AOSP. AOSP base builds completely vanilla Android for Nexus devices (it can be ported to other devices but out of the box it only builds for Nexus). The CM base is updated with every merged patch, they also pull down AOSP changes from upstream if Google updates something, like a new build version, etc... Some of the patches that go into CM are also submitted to the AOSP (upstream) Gerrit for merge to the main AOSP tree as well.

I'm not sure this answers it either, like I said 2 hours sleep and I guess 10 cups of coffee isn't making my brain work better.
[Galaxy S II General] Entropy512:
Yup. On a Nexus device, there are very few of these - frequently just the RIL, GPU binaries, and a few other small bits.

On non-Nexus devices, there are MANY. For example, right now, we use binary blobs for libsensors, libgps, libaudio (bugs and/or deviations from Android standards in this have been the source of many CM issues with audio), and quite a few other things.

These items are where the most likely obstacles to bringing CM to GS2-series devices are going to be - Since we won't have JB-compatible blobs, if Google changed any blob interfaces, the JB source has to be massaged to work with the "old" blobs. In many cases this is done with "wrappers" - designed to adapt binaries for older Android releases to newer devices. As codeworkx mentioned - if incompatibilities cause us to have to rewrite any of the HAL components as open-source, things could take a long time. Libaudio on the MC1N2 will be painful if we find ourselves unable to use the blob, and codeworkx mentioned camera as an area of concern.

Well, depending on the specific subrepository within the CM tree, there are occasionally multiple patches against the same repository, that people might submit in parallel. One patch getting merged in can cause issues with merging another against the same repo, causing the committer of the second patch to have to alter it to apply cleanly. For example, frameworks/base is a HUGE repo that has many changes being applied to it in ICS and prior releases. As I understand it, frameworks/base was split up by Google for JB. This makes applying all of our changes to frameworks/base difficult, but in the future will make it much easier to maintain. In this case, all of the CM patches that have been made will have to be reapplied - some might apply automatically, but in many cases merge conflicts will need to be manually resolved.
[Galaxy S II General] chrismalla:
Haha, it gets there... The AOSP as it is right now can't be working for all nexus devices, is it? :O They all have different hardware and proprietary binaries. If it is, why should it be that hard to port it to different devices and just put the proprietary binaries in?

Proprietary binaries brings me to proprietary blobs/binary blobs . What is that? Reading from wikipedia it's almost like precompiled closed drivers. So whats the difference between binary blobs and proprietary binaries?
[Galaxy S II General] DrunkFuX666:
The latest from the holy Devs of the Android Society...

CyanogenMod

1 hour ago · Desktop · Public

Jelly Bean Status Update

Repositories for all AOSP projects have been created on our github to alleviate any potential mismatches (branch is 'jellybean').

While Jelly Bean won't require a major rewrite of all the CM features, the source has been re-arranged and re-factored enough that a simple merge isn't possible. So we will proceed with manual merging (this was to be expected really).

The plan of attack will be to cherry-pick everything from CM9 and fix the merge conflicts and relocations. It’s tedious but the only way. Ideally the original patch authors will forward-port their changes, so if you are out there and want to help out, join us in #cyanogenmod -dev.

+ Trebuchet might be messy to rebase onto JB.

+ Theme Engine will be messy.

+ SystemUI stuff will need to be restyled.

+ Lockscreen stuff will need to be restyled.

+ The current UX of Settings is good, no reason to change anything there.

A manifest (Cyanogenmod/android.git) will be going up later this afternoon, so the masses will be able to sync directly from our source at that point as well.

This will be it on the updates (so we can focus on actually working). Next post referencing JB should be when the merge/cherry-pick process is complete.

-CyanogenMod Team

https://plus.google.com/app/plus/mp/183/#~loop:view=activity&aid=z12pt3arlxu1zbwdx221hl44tznvd3hhv04

Can't wait...!! :D

Sent from my Galaxy ICSII
[Galaxy S II General] thracemerin:
No difference. binary blobs = proprietary binaries

Yes, it works for all the Nexus devices that Google released binaries for (Maguro (GSM Nexus), Toro (Verizon Nexus), Grouper (Nexus 7), they promised the rest "soon"), I've been having some issues with it on my Nexus, but i think that's my fault not Google's.

Using proprietary code isn't as simple as taking 1 blob from 1 device out and slapping in another, the AOSP base is coded to work with the binaries that Google released for Nexus devices not for any device, often as Entropy512 said above non-Nexus devices have significantly more binaries which are often incompatible with AOSP (why? who knows, OEMs hate open source probably) so it requires modification of the code that references the binaries so that they will work properly, there is an added complication that since proprietary binaries are closed source they often don't work the way you think and there is no way to see how they might actually work.
[Galaxy S II General] r7s:
Suddenly the push service started working again, maybe because I cleaned Play Store and the download manager cache.
[Galaxy S II General] chrismalla:
Aaha, so no modifications have or can be made to the binaries? Why are they doing that!? What are they gaining by closing all up? Hate maybe, they can literally f*** off. Hope they read this.
[Galaxy S II General] Entropy512:
Some examples:

The light sensor implementation in our blob HAL doesn't behave well at all

When we attempt to use an opensource HAL, the version of libakm our device uses doesn't seem to work correctly, making compass misbehave

Our GPS library has an extra unknown field in the satellite status data structure. We don't know wtf it is there for. There are also control interfaces for sensor aiding and such that are totally undocumented. It took me 3-4 evenings to figure out why we weren't getting sensible satellite status back in March.

Our RIL has required all sorts of funky hacks to play nice

Our audio HAL doesn't behave like Android's code expects - this was the cause of the notification volume bug stuff

The list goes on...

Fortunately many of these hacks/abnormalities are now known and we can work around them - but if something in JB completely breaks one of the HAL interfaces to the point where we can't use it, it may need to be rewritten from scratch. See codeworkx's comments about the camera...
[Galaxy S II General] RochasMan:
About CM10?

I really love the work being put into the CyanogenMod 9 and now that the source-code for Jelly Bean has been released, how soon can we see a version of that in this device, I've heard that all CM9 devices are being "transformed" into JB CM10...?

Thanks!
[Galaxy S II General] beston94:
Have you read the rules of CM?

The most important rule clearly states: "Don't ask for ETAs" or something like that.

Try to read and people won't flame you.
[Galaxy S II General] RochasMan:
Sorry...! I've obviously missed that part... :/

Thanks!
[Galaxy S II General] CRXed:
Here ya go! http://xdaforums.com/showpost.php?p=28534385&postcount=39354
[Galaxy S II General] pschjelderup:
sublime

Followed this thread for a while. Finally decided to get in on the action. What a great ROM. Of course most of you already know this. Browsing the thread though, one can get the impression that there are lot of issues. I've had none. A significant improvement for me - coming from stock NEE LPG 4.03 - is that getting GPS lock now takes approx. 10 seconds, compared to 2 minutes previously. Thanks to all the people contributing.
[Galaxy S II General] Fr33L4nc3r:
Tried today Apollo, Google Music, PowerAmp on 708 nightly with my Sony MEXBT3900U car head unit (supporting BT 2.1 - AD2P 1.2 - AVRCP 1.3, phone listed as compatible)

No track info appeared while streaming (switched between album/artist/track display and all were empty) :(

Will try with stock GB, and maybe CM7 tomorrow. :fingers-crossed:

If it doesn't work on stock, I think it's safe to assume the head unit is faulty :crying:
[Galaxy S II General] readon1:
Wooow just saying bumping the first step of the gpu to 100mhz really helps for a smoother UI :rolleyes:
[Galaxy S II General] vitoski:
Guys just a quick question. Does anyone have a problem with lagging video?

I am on CM9 (right now on the latest nightly) and have problem with playing videos.

When I record short movie (i.e. 1080) and then play it with either stock player directly from gallery app or with other movie player (mxplayer etc.) it lags. It happens also with other movies I took with another phone.

Tried changing kernels but no joy. It happens both on stock CM9 with its kernel and on custom kernels a well:-(

Anyone can help?

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II General] chrismalla:
About this proprietary binaries thing... Nexus 7 got a Tegra 3 chip from NVIDIA. Who is making sure it will work with JB? I guess Google don't have a clue about the inside of NVIDIA's chip, so. Did Google send the Jelly Bean codebase to NVIDIA prior to the release to let them create their proprietary blob for it? Or did NVIDIA already have it done, they have their Tegra 3 chip in numerous devices, so they maybe had it ready. If so, the only thing left to do was to write/optimize the code for the link between the android system and the chip/binary. Did Google or NVIDIA do that? I guess that's the only code NVIDIA had to reveal to the world.
[Galaxy S II General] :
I think NVIDIA will make this. NVIDIA is just a sell out slut. Why would they release the code to Google? BTW, NVIDIA, fu.* you ;)
[Galaxy S II General] Entropy512:
And not only that, XDA rule #1 - SEARCH BEFORE POSTING. Considering that almost the entirety of the prior 2-3 pages has been discussion of the various roadblocks in the way of moving to JB (many of which are still "unknowns that could really bite us in the ass"), there's no excuse for posting an ETA question like that.

Google may have access to the documentation under NDA - but are unable to release source or documentation.

Google has been fighting for as much as possible to be open source, open documentation, but in some cases they just haven't won the fight. Some examples:

No GPU vendors have permitted opensource drivers to exist (in some cases, there is some kernel "glue", but in all cases, major parts of GPU support are in blobs)

On Samsungs, the RIL is always handled by blobs. That may have been the case for the N1, but eventually many of the HTC RILs were reverse engineered and replaced with an open source one. Back then, the radio interface was often a serial connection with an AT command set, so sniffing the interface and reverse engineering was much easier than it is with more moden radio chipsets and RILs.

I'm almost absolutely certain that Dimitry Schmidt at Google has access to BCM4330 (our wifi chipset) datasheets, and is allowed to work on an open source driver, but it is also clear that there are restrictions on how much documentation he can put into the code (such as comments). The bcmdhd driver is incredibly poorly documented/commented, and I believe that in that case, it isn't due to lazy developers - it's due to Broadcom limiting the amount of public information on the chip.

On devices with an Asahi Kasei magnetic/orientation sensor, the libakm blob is a closed undocumented annoyance. It's why our opensource sensor HAL is proving extremely difficult to get working.
[Galaxy S II General] chrismalla:
Hahah, yeh, it's sad. I wonder for how long Google will keep the support up for the Nexus 7. They will certainly not pay NVIDIA for their proprietary blobs forever ;) Google should have their own open source SoC so that CM easily can have support for it even after Google has dropped it. Is there any OEM manufacturer that has nearly a open source SoC?
[Galaxy S II General] soyef:
Yeah I have this issue, assumed it was because of the lack of open source drivers from Samsung, could be wrong though...
[Galaxy S II General] unease:
Aspalt 6 Issue

Anyone having concern with Asphalt 6 game? Am having an issue where the game kinda freezes up at the career races selection screen (mind you, the background music keeps playing). Its a random issue but happens atleast 7 times out of 10 attempts to play the game. Any ideas? Am on stock kernel and the latest 20120710 nightly.
[Galaxy S II General] :
Remember, with Nexus 7, NVIDIA will get it's share. They must keep support for it. Don't know the answer for the final question.

AMD should enter mobile mobile market. Personally, I prefer a AMD video card instead of a NVIDIA video card on desktops. Since the competition on desktops is so big [but maybe a draw between they], surely they would do some masterpiece on mobiles [maybe also opensource drivers?]
[Galaxy S II General] vitoski:
That's too bad... Galaxy S2 is so powerful phone and simple video lag:-(

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II General] veyka:
AMD used to be in the mobile graphics market, who do you think qcom brought the Adreno stuff from, back when it used to be called ATI Imageon, then AMD Imageon ;)

It was pretty damn nice stuff as well, first gpu with ogl ES for the embedded market! (so says wikipedia).
[Galaxy S II General] cobhc:
Adreno is even an anagram of Radeon :D
[Galaxy S II General] veyka:
Nice spot, never noticed that :good: :laugh:
[Galaxy S II General] juniperus.dx:
USB on the go

Yes - for FAT file system. Just plug and exploring the folders

No - for NTFS file system. pls see some previous pages
[Galaxy S II General] Kevin433:
Is it just me, or does the camera touch focus still not work? Cleared camera app cache, did a factory reset including wipe cache & wipe dalvik cache, restarted the phone several times.

Running cm-9-20120710-NIGHTLY-galaxys2 and Siyah v3.3.2
[Galaxy S II General] Bl@ck:
Did you perform undervolt on the gpu? I have similar issues on graphic intensive games, but I'm undervolting.
[Galaxy S II General] shotta35:
You are using another Kernel - GTFO! :p

It works just fine, don't post here if you've made any modifications to CM as then it's no longer CM9.
[Galaxy S II General] Aroldoa:
Camera is working almost fine (menu is crazy and scene don´t change) but I´m using all CM9, I think you will not have support here using another kernel
[Galaxy S II General] unease:
No Bro. Just stock. No mods. I tried with Siyah and it seems to work fine now.
[Galaxy S II General] :
Still experiencing crashes with stock Danish keyboard and dictionary when typing certain letter combinations (eg. 'li', 'kl', etc.). Is this a genera problem in all ICs ROMs, or just CM9?
[Galaxy S II General] Deanflame:
Quote you!! isn't possible to disable secondary mic? i have the same problem! :(
[Galaxy S II General] Aroldoa:
open your dialer, than go to settings and disable noise suppression(or something like that, my menu is in portuguese)
[Galaxy S II General] shotta35:
Umm yes it is possible and been that way for a few days now. Just go into phone settings and turn off noise supression, either that or get your phone fixed as it's broken if an intended feature isn't working correctly.
[Galaxy S II General] Juzman:
Works fine for me using Siyah 3.3.3b. (Before anyone says GTFO, I know its not supported here.) ;-)

I am just informing the OP it works fine. :-)

Sent from my Galaxy S2 running Cyanogenmod 9
[Galaxy S II General] brads27:
My phone was not recognized but if you have USB debugging on look at the top of your phone .the task bar it will say USB.click on it to allow it to show on your PC.it works for me.
[Galaxy S II General] :
Follow up:

Data not breaking because deep sleep not possible on 3G ;)

Bell, Canada, blah...blah...
[Galaxy S II General] KaliKot:
Famous? what are you smoking, every XDA member knows that Samsung was the first with Gingerbread on non-Nexus devices.

Why would you even buy an S2 if Samsung was "Famous" for being worthless with their updates.

I get what codeworkx is getting at but your post is pure ignorance
[Galaxy S II General] sorrowrain:
i am sorry but do you not see that they are not going to release ics for galaxy s.

and that is because of the ram.

you dont know if galaxy s2 1gb ram is good for future android releases.

those are thing only time can reveal.
[Galaxy S II General] Bene2k11:
Newest build with LP6 Kernel&Modem seems to work fine. No data loss. Nothing else tested so far.
[Galaxy S II General] pewpewbangbang:
hows the LP6 modem? most of the ICS modems have been battery drainers IMO.
[Galaxy S II General] TheMorpheus:
They can do whatever they want with Stock Samsung ICS, what it really matters is that they must release the kernel source...soon!!
[Galaxy S II General] Nerijusss:
so where can i find lp6 everyone's talking about?!!!
[Galaxy S II General] Ogy77:
Read and then flash !!!!

http://xdaforums.com/showthread.php?p=20671183
[Galaxy S II General] Phone_Guru:
Can someone please post the new LP6 kernel, preferably as a flashable zip?
[Galaxy S II General] pik1:
Phone_Guru (seriously???)

maybe i'm retarded...
[Galaxy S II General] Narzsa:
Well Just installed the new version. Feels snapper but nothing much has changed so far. Gps and data work and I ll monitor battery life. Backlights for hardware buttons have gone. YouTube still broke. Oh well one day ;-)
[Galaxy S II General] t0ph0id:
Why have you called him retarded and then posted a link that's not what he was looking for?

That thread doesn't contain the new kernel.
[Galaxy S II General] lowkey81:
I also flashed, but hardware button backlights are working for me...
[Galaxy S II General] carloslopescj:
So, new release features?
[Galaxy S II General] KennyLegend:
Anyone know if cm9 modems work on a Sammy rom?
[Galaxy S II General] Fabriciohss:
It is not supposed to be working...for now.

Oh well I do need to cool down and relax.
[Galaxy S II General] carloslopescj:
Nice try, not funny.
[Galaxy S II General] Batskoning:
Everybody is talking about great battery life etc..

Only using whatsapp, and this is the result:

Build 01232012

Kernel KP9

Modem KP8

CF-Root KP8 (if flash 01232012 not change the CF-Root)

I do something wrong..?

Now i'm on:

Kernel XXLP2

Modem XXLP1

CF-Root KP8 (if flash 01232012 not change the CF-Root)

How can i check wich CF-Root i use..?
[Galaxy S II General] Gustopher:
It's a new build based on a new kernel - not unreasonable to at least investigate whether the bothersome Youtube has been fixed
[Galaxy S II General] Narzsa:
They sprung back to life for me a few moments ago :-)
[Galaxy S II General] :
Works for me 2

Sent from my Galaxy S2 running Cyanogenmod 9 tweaks
[Galaxy S II General] anto.danny:
@Bl@ck I am Facing the same issue on asphalt 6,Blood and Glory.:crying::crying:

Edit:I'm on the latest build with Stock kernel, no uv or oc,everything stock.I always do a full wipe before flashing a nightly
[Galaxy S II General] ronald_loulan:
I recently change my Galaxy S2 i9100 frm stock ICS 4.0.3 to CM9 Nightly 07/07...

I notice that Blood and Glory & Big Time Gangsta were running faster FPS compare to the stock ICS..

But there's 1 issue,both game will freeze like after playing 1 min n freeze another 1min...

It happens all the time..

but when im connected to the internet then the problem disappeared...

Any idea??:confused:
[Galaxy S II General] Spiralzz:
Is there a way to alter the settings (maybe in some system file) to alert battery low at 1% instead of the default 4%? I often ignore the one at 4%, thinking that I still have time. I know I could use some app, but I don't want to install one app just because of this. It's a trifle thing, but just asking ;)
[Galaxy S II General] mhanis:
Same issue for me.. :confused:
[Galaxy S II General] anto.danny:
Exactly i forgot to mention this,when wifi is connected everything runs flawlessly...And also when i open dead space it checks for updates on start on the older builds the games starts within few sec but now it checks for updates for min or less and the enters the game...:crying:

Edit:i even tried the kernel with old wifi driver
[Galaxy S II General] ronald_loulan:
anto.danny, i think we are facing the same issue...
[Galaxy S II General] unease:
Noticed that setting backlight timeout to 1 second disables Kill App Back Button!

Sent from my GT-I9100 running CM9
[Galaxy S II General] jetshinoda:
Anyone tried the differences between XXLQ5 and XXLQ6 yet on the latest build?
[Galaxy S II General] LenAsh:
The Modem? It has nothing to do with the ROM and depends on region and carrier...
[Galaxy S II General] coversnail:
If this problem occurs on the rc1 build after full wipes etc, then get a logcat of the problem and post a bug report code.google.com/p/cyanogenmod/issues/list
[Galaxy S II General] fede_79:
If the rom has nothing to do with rom why using cm9 I have a lot of dropped call with drop signal using the same modem version with stock don't have one? With this I don't want to say that one rom is better than other. Sure I'm using Cyanogenmod and I like it :beer:

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II General] thunderger:
I reproduced the issue with "kill app" back button and one sec backlight timeout. Logcat doesn't show any helpful information.

Bluetooth pairing with my car audio often doesn't work correctly.
[Galaxy S II General] rakeshishere:
Where can I find the backlight timeout setting? Using 08/7 build here

Sent from my Galaxy S2 powered by CM9
[Galaxy S II General] #illidan:
Its in the latest nightly.
[Galaxy S II General] g3ckospy:
Upgrading to latest nightly build

hi,

i was wondering if there are a few here who's having some problems upgrading to the latest nightly build?.. i always have some weird bootloop while upgrading to the latest build. tried the clean install but it only stocks at the bootscreen where the CM9 icon appears.. Can somebody help me?

Thanks,
[Galaxy S II General] vitoski:
Guys am I the only one with video stuttering on CM9?

I have tried right now MXPlayer with ARM7 codec and still no joy:(

Wired thing is that sometimes the video plays fine, but it's like one for 20-30 times. All the other times it stutters.

Moreover I just checked the movie I took with SGS1 (it was running completely smooth there) and it stutters as well on GS2:((

Is this a problem with codecs/player/rom? Anyone can help me with this? That's the only thing that drives me mad about my phone:(