yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] dmbkiwi:
When updating through the new cmupdater, my phone reboots to the stock sammy recovery, instead of cwm recovery, and so the update fails. Have to manually reboot to cwm recovery to install the update. Anyone else?
[Galaxy S III General] Theshawty:
I sure as hell hope not!
[Galaxy S III General] eseregin:
Indeed interesting and very
[Galaxy S III General] EquinoxFox:
So true.

Where do I need to vote/sign/write for a kick in Samsung´s ass? ;)
[Galaxy S III General] XDA mark:
Me too. I thought the rumors where thst the HTC One X 5 is actually the Nexus 5. And now there is talk of the next Nexus being announced in 30 days.

Rumors, rumors :P Though this cm10 thread for the s3 is slowely becoming the "we hate Samsung, we are all buying the next Nexus" thread xD
[Galaxy S III General] DenisJ:
Thanks for the answer,

so please help me to understand why i have just 1mt bluetooth range for my headset please ?

I can use so fine with the htc sensation and with out problem at more than 10mt

...so the headset is ok.

Thanks again

Denis
[Galaxy S III General] MisterRio:
Thanks for your answer. The 'solution' is a bit disappointing though. Seems this will just be a shortcoming that we will have to get used to for the time being; it's just broken. Sucks kinda, but I understand this is not at the top of the priority-list..
[Galaxy S III General] Dav_prime:
I also have this issue. It returns: E: could not mount /sdcard/ (no such file or folder)

I have however been having issues with external SD not working at all on my phone (suspected hardware issue) and put it down to that. Your post has made me wonder if it's unrelated though.
[Galaxy S III General] eseregin:
Your situations are complitely different and i cannot see any relations between them
[Galaxy S III General] GabrielSousa:
@codeworkx

strange bug

on last 2 builds

if i disable the touch sounds (

we have to boot with touch sounds disable

)

on a phone call the speaker and the microphone don't work
[Galaxy S III General] dlarge:
I can confirm this. On incoming call I can't hear the caller and the caller can't hear me. After disabling / enabling speaker things seem to work, but with the next call the problem is back. I tried a reboot, but with no succes.
[Galaxy S III General] Jezwick:
I know it doesn't help BUT in call audio is fine on my device on the latest nightly..
[Galaxy S III General] vatvedt:
Here the other day, my friend and I were testing this for the first time. He had unrooted stock ICS SGS3 with TouchWiz, and I was using CM10 (maybe build from 27th of September, not sure) on my SGS3. Worked great! Beaming stuff from my phone to his and vica versa. No problem! :laugh:
[Galaxy S III General] dlarge:
Strange thing is that I received a call this morning without a problem. I've updated to todays nightly, but the problem still persists.
[Galaxy S III General] sjgore:
I've had a similar but slightly different problem with the last few nightlies.

When I first flash the nightly, the speaker and the microphone don't work in all calls, not just the first one. If I tick "Screen lock sounds" and reboot, then untick "Screen lock sounds" and reboot, it is usually enough to make the speaker and microphone start working again. Once working, they work for all calls, and after subsequent reboots.

---------- Post added at 11:09 AM ---------- Previous post was at 11:03 AM ----------

Has anybody else found that Chrome is currently (ie. last few nightlies) quite unstable with CM10 when entering text? It's rock solid when just browsing, but it freezes almost every time I try and type something.
[Galaxy S III General] big_adventure:
If you can deliver DOCUMENTED closed-source Sammy source (for kernel, hwcomposer, and, while we're dreaming, camera and everything else), something could almost certainly be done with it.

The issue is the interraction between the hardware and the software - Every manufacturer does things that require modifications from the "ideal". They all put in workarounds in frameworks and in their closed-source code bits (like the HALs, hwcomposer, camera drivers and software, etc.). The specific problem here is that Samsung doesn't publically document those workarounds - so inside Sammy's closed-source code, they might have a weird Samsung-specific command instead of the "normal" command (see the Gralloc problem that caused the infamous memory leak). And since those are not documented at all, the only chance of finding them is if they happen to sneak into something that gets opensourced. In this case, the kernel is OSS, and HAS to be open-sourced and buildable. That public release still doesn't have to be well-documented, though it sometimes is depending on the provider.

The reason why the Exnyos devs in particular have it bad is that, unlike Qualcomm or TI, Samsung doesn't sell the Exnyos to all comers - they have more than enough uptake in their own parts to use pretty much their entire manufacturing runs - so they don't have any specific reason to publically release all the kludgey stuff. Since they have no vested interest in doing so, they just don't do it. They might try it if people stayed away from their kit, but that's obviously not the case - they sold 20+ million in the first couple of months. The 0.001% of S3 users who install AOSP-based ROMs just don't carry enough weight to make any impact on their bottom line. This might only change if Sammy starts selling Exnyos SOCs to other phone makers.

Qualcomm doesn't make their own phones with their own chippery* - they just sell the chips to others, so they have a vested interest in all the secret sauce being totally available to anyone at any time, hence their strong participation in Code Aurora. They absolutely need Sammy, HTC and anyone else to be able to easily produce full-function devices quickly with their parts, and it's easier to support that once (in CA) rather than individually with each buyer. Give the devs the necessary tools to do 99% of the coding themselves and you don't need to pay for as many support people. This is different from Sammy, since they are already paying all of the devs involved.

*OK, outside of their dev platform parts, but they make no more than a couple hundred/thousand of those, not hundreds of thousands or millions, and they are most definitely not consumer-facing devices.

So, if you can legally get that code, it would be a huge boon for the dev efforts.

But since it's closed source code that Sammy has shown zero impetus to give away, AND it's been the holy grail for all outside devs for both Exnyos 42 and 44 platforms, I'd question the "legally" part heavily and even the "get" part quite a bit.
[Galaxy S III General] eseregin:
I remember same bug was solved on HTC HD2 time ago by - during call turn Speaker on and after off

Someone implemented it even in kernel - after you answer for half a second turning On speaker and automatically Off.

Dunno why all this happened
[Galaxy S III General] Dav_prime:
I am inclined to agree. However, I'm interested to see if any workarounds will also work for me. Until then (or I get it fixed) i'll stick to updating manually in cwm.
[Galaxy S III General] BoO_:
First i'm sorry for my Bad English..

My problem with Cm 10 I loses notification by Led when my telephone are in wakefulness. it is it possible to restore to see my new SMS?

Thanks..
[Galaxy S III General] big_adventure:
You are thinking of the wrong problem - disabled UNLOCK sound killing call audio is well known.

This is dial-pad sounds killing audio, and that's a whole 'nother story.

You probably had no need to be dismissive to 2 posters with as much history as they have, anyway.

If you're not sure, don't post.

---------- Post added at 12:50 PM ---------- Previous post was at 12:48 PM ----------

CyanogenMod ROMs don't support Samsung-specific features, like motion controls or the high-end camera functions/mods.

You could add those features yourself, if you like - that's the CM10 advantage. But the thing is, most CM users don't care for those things - they are sort fo why we're here to begin with.

"stick with Sammy" means stay on a Samsung-based ROM if you want those features.
[Galaxy S III General] :
@big_adventure

and why don't u stop being a smartass and telling others what to or not to do (like you were saying flash bootloader to get wi-fi back and it had nothing to do with bootloader).

THE BUG is that if after reboot/before first call no sound is played (bootanimation sound, keypress sound, lockscreen sound) audio won't be properly activated and there will be no sound during calls. And it exists on Samsung ROM's also, but Samung ROM's have sound during boot so it is less noticable to most.

attitude is everything..
[Galaxy S III General] zombination:
+1 ...

About my BT car problem all is OK since i changed modem to LIB

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III General] Daelyn:
:laugh:
[Galaxy S III General] jaju123:
Can we not use xiaomi quad phone jelly bean source when it comes out? That's exynos I believe.
[Galaxy S III General] asc366:
Same here in todays nightly (from October 2nd).
[Galaxy S III General] kroat999:
will the i9300 also benefit from this new patchset for mali http://review.cyanogenmod.com/#/c/23580/
[Galaxy S III General] TecQuality:
just noticed a weird thing: if you try to install the LI8 RIL (from cody's rep) it doesn't install the correct RIL, as getRIL told me i've LI2 or something else, but i've no issues with the LH4 RIL.
[Galaxy S III General] stefanACM:
I am .NET developer for a long time (mostly C#) and if I understand all what developers need is "commented" open source from Samsung ?
[Galaxy S III General] :
it is normal.. LI8 RIL is LI2 or whatever getril reports.
[Galaxy S III General] TecQuality:
XXDLI2/XXDLI3 correct? but getRIL gives me an 'error'.
[Galaxy S III General] :
both XXDLI8 leak and XXDLIB official are coming with that RIL.
[Galaxy S III General] DvTonder:
The i9300 already has it.
[Galaxy S III General] Daelyn:
GetRIL is partly wrong. LI8 and LI2 are the same, therefore GetRIL can't differentiate and will say it does not match.
[Galaxy S III General] chrisjwild:
I love CM10 even got my girlfriend to install it on her GS 3 but have to go back to stock as my Nexus 7 arrived and I have to be able to tether. hopefully either Bluetooth or WiFi tether gets fixed soon.
[Galaxy S III General] Entropy512:
Why are you posting this in the thread for a completely unrelated device (I9300)?

that's a backport of stuff I9300 has had for two weeks.
[Galaxy S III General] big_adventure:
Oh, the irony here is rich. To explain, since I'm pretty sure you won't get it, you are being a smartass and telling me what to do here, in a situation where you are invalidating that type of behavior. Nice.

I actually try to be helpful with the VAST majority of my posts. If you look at the post in question (the one you are referencing but not bothering to quote), I say that the user needs to flash a Sammy ICS ROM, which, you know, is generally the solution to the problem. Since others who had or did some actual troubleshooting of the problem stated that it was likely linked to the fact that Odin ICS ROMs often include a bootloader flash, I added that in there.

I never had a single Wifi problem - I simply recounted what had been stated by others who had solved the problem.

On to this issue - the poster that I rebuked there (Daelyn) didn't bother to find out whether the problem is the one you assume it to be.

The stated problem was that turning off dial-pad sounds killed call audio. Not lockscreen sounds. Daelyn never bothered to find out whether the person still had lockscreen sounds enabled or any other sounds. It's kinda hard to justify a "RTFT NOOB" response when all you are doing is assuming you know the issue based on wildly incomplete information and a piss-poor reading of the evidence furnished.

All Daelyn had to do was say "Vlad, do you have lockscreen sound turned on?" or something similar and then he'd have had a good idea of where the problem is coming from. Not bothering to do that invalidated his response, and making that response a "RTFT" made it worse.

Don't agree? You have that right.
[Galaxy S III General] Theshawty:
What does actually cause the wifi to bug out for some? I mean, when I went to aosp from JB, all I did was to flash some ICS-based rom with cwm, boot up and connect to wifi and enable nfc then reboot to cwm and flash aosp and both wifi and nfc works.
[Galaxy S III General] mistersixt:
wifi stopped working out of the sudden for some users starting from NIGHTLY-20120927, last version where it is working fine is NIGHTLY-20120926. And it was fine for the last roughly 30 nightly CM10 versions, too. I have no clue what is going on here :( .

Regards, mistersixt.
[Galaxy S III General] :
I hope so too..
[Galaxy S III General] HaruSoul:
I have flashed every NIGHTLY since they started getting released, came from CM9, never had a problem with WiFi.
[Galaxy S III General] w1nter456:
It seems that mali r3p0 had merge. :), means better butter :)

http://review.cyanogenmod.com/#q,status:merged+branch:jellybean,n,z
[Galaxy S III General] gokussjx:
Posts like this initiate rumors & false expectations. Later, the users blame the devs when they find nothing new.

The commit is for kernel smdk4210. It's for Galaxy S2, Note, & about 7 other devices, not S3.

Galaxy S3 uses kernel smdk4412.

Try & check the commit data next time as well.
[Galaxy S III General] f0xy:
We need project butter shall we get something trending on twitter for Samsung and also see if xda can do a front cover story for advertising?
[Galaxy S III General] :
EOD for me. btw. it was not personal.
[Galaxy S III General] w1nter456:
Deleted.
[Galaxy S III General] :
.... LOL :banghead:
[Galaxy S III General] mvdbosch90:
Wifi problem

I'm also having the Wifi problem on my S3. I have been running WanamLite's official Jellybean release before I went to CM10. I stepped in with the 0927 nightly. Backed everything up with titanium, wipe cache, wipe dalvik cache, factory reset, and I even emptied the entire internal SD (through windows explorer). Then flashed CM10. Basically everything works fine and incredibly smooth (thanks for that:) ). I solved the call sound with a restart and lock audio on, but I just can't get the Wifi to work. I read some things about first reflashing a 4.0.4 rom, setting up wifi and then go back to CM10, but that also doesn't seem to work for everyone... I hope you guys can find a solution for this in one of upcoming releases, my provider is not gonna like the amount of data I'll be using :P

Thanks in advance
[Galaxy S III General] Entropy512:
Yeah... All that commit does is give 4210 users most of what 4412 users have had for TWO GODDAMN WEEKS.
[Galaxy S III General] ididnt:
Nightly 2-10-12 keep getting popup saying CM updater needs to close. Reboot doesn't fix.

---------- Post added at 02:53 AM ---------- Previous post was at 02:50 AM ----------

Same here...all cm10 nightlies without any WiFi issues.
[Galaxy S III General] chrisjwild:
Has WiFi tethering worked for you?
[Galaxy S III General] nerotix:
Yeah same.. last samsung device for me aswell. Never again!
[Galaxy S III General] DvTonder:
What is your updater settings set to? Please post a logcat.
[Galaxy S III General] TecQuality:
I got this issue with the 1001 nightly, so I've disabled this feature.
[Galaxy S III General] :
:good:
[Galaxy S III General] TecQuality:
Re: CyanogenMod 10 Discussion Thread

His about the reset threshold into the automatic backlights settings? What is you experience? Right now I've disabled this feature.

And also what is the best value for the hysteresis? This decrease the auto backlight by scaling the light?
[Galaxy S III General] tux821:
I just love my Samsung Galaxy S3 with CM ( ( me kissing my awesome S3 ) )
[Galaxy S III General] DvTonder:
That's not very helpful. People should not report issues they are not willing to provide supporting information for. How are we supposed to fix things with vague 'it wasn't working' type statements?

That being said, we did a major rewrite to several components that got committed late yesterday and some additional fixes were added this morning. Try again on a new version that includes these changes.

If you get the problem again, submit a logcat so we can figure out what the issue is.
[Galaxy S III General] TecQuality:
You're right mate, but I'm using ROM manager for my updates, so I put the CM Updater on 'manual'.

Anyway, please remind me a little thing, what files do you need for the SODs?
[Galaxy S III General] ManCityFC:
I ditched HTC after owning 3 of their devices - due to the lack of sources and bootlocker rubbish. Now looks like this will be my first and last Samsung if they don't help out soon. It's ridiculous.

I am kicking myself now. I thought long and hard about the Nexus but decided on this phone instead due to the superior hardware.....not a mistake I'll make again. I hope Samsung don't prove to me that this was the wrong decision and help these devs out before they lose all the community. Crazy to completely piss off your most loyal customers, crazy. Don't they realise that it's us that evangelise about their phones and influence others to buy them. People listen to techies like us. I've sold loads of phones for them and persuaded loads to ditch Apple in Samsungs favour.
[Galaxy S III General] on2a:
I get the feeling the next Nexus device will sell in the high millions. I for one will be switching from my S3..
[Galaxy S III General] Theshawty:
Samsung in general isn't at fault, I believe, only Samsung Korea. They're the ones to use the exynos chip. Samsung USA uses only (unless I'm mistaken) Qualcomm. and Qualcomm provides all necessary documentation and sources. Samsung Korea, on the other hand, is a company I have few good words for now actually. I used to think highly of exynos, before I owned an exynos device.. The first Samsung I had was actually the Gnex.
[Galaxy S III General] ManCityFC:
Well that might be the answer for us in the UK. We are getting 4G, so could switch to the Qualcomm devices I guess, well in theory anyway. But to be honest this whole mess is leaving a bad taste in my mouth like HTC, and Korea live or die by their decisions. I can see me just walking away from Samsung like I did with HTC, which would be a crying shame because the phones are pretty goods despite this issue. Hopefully someone in Korea will wake up and understand the backlash this could potentially cause. It might not be a killer blow, but the developer community turning their back on Samsung doesn't just mean a couple of phone sales lost, iits unquantifiable how much revenue they lose by people no longer buying phones, TVs etc etc - and geeks like me who have people on Facebook weekly saying "you know about phones, which should I buy, the iPhone or an Android?"

It's a dangerous game they're playing. Look at what happened to Sony when they pulled Linux from the PS!
[Galaxy S III General] DvTonder:
Best way:

If you are connected to a PC with adb available, run adb shell logcat and then cut and paste the error part of the logcat. You may have to leave it running and trigger the issue. If the issue is on bootup, search back in the logcat output - it starts from the moment the device boots
[Galaxy S III General] mat.hen:
Nah mate, the 4G phone is the i9305, it's Exynos too. As far as I know, EE 4G is on different bands to the USA LTE 4G so we can't import one of those either.
[Galaxy S III General] Entropy512:
I used to think highly of exynos too when I was just working down in the kernel itself... But as soon as you venture up into the HALs, it's time for epic pain and suffering.
[Galaxy S III General] Theshawty:
Yeah, because that's where the hacked down **** starts, right?
[Galaxy S III General] Entropy512:
There's a decent amount of badness in the kernel... But we have complete source to it and while it gets a little annoying fixing the same thing over and over again, it's often pretty easy to just reapply patches. See for example the situation with the Tabs and the New Mali patch - mach-px.c was missing some stuff which is why things didn't work. It was pretty easy to start reading through the files, looking for differences, and noticing some stuff was obviously missing.

The blobs are a different story - figuring out what is wrong with them is tough, and very often, problems you solve with one version of the blobs are completely different when new blobs come out. It's a black box and you don't know what the hell is going on inside it.
[Galaxy S III General] Kickasskev:
is there any way we can the new NOTE 2 camera .apk on CM10? It's in the theme/app section but not sure if there is a way to make it work, tried flashing but got froozen bootup screen
[Galaxy S III General] Theshawty:
Samsung Blackbox 4412. :)
[Galaxy S III General] _Man0waR_:
And you had no idea why it did not work ? Have you ever seen an app using TouchWiz running on any CM rom ? This does not work and will never work. I know you are not the only one to post this question. Come on people, search/read before posting.
[Galaxy S III General] gokussjx:
We can't even get the stock S3 Camera app to work with AOSP framework.

It needs Samsung Touchwiz framework.

Me going on a date with Scarlett Johansson, is more probable than Note 2's Camera app working with AOSP Derivatives.

BTW, if either of the above two is ever possible, please let me know... Wouldn't want to miss it for the world!
[Galaxy S III General] nerotix:
mod edit: I love everyone and I will be nice from now on :)
[Galaxy S III General] Kung-Fu-Tse:
stop insulting, THX
[Galaxy S III General] Zatta:
I for one love my SGS3. All the banter about Samsung being not so developers friendly has been known for years now. CM10 is running (near) perfect on it because we have had great dev's on the machines. I still love the intial work Codeworkx and Atinm did on my SGS1 and I am glad Pawitp took that over when they jumped over to the SGS2. The same ritual is happening again and I am sure the SGS3 will keep getting love from dev's also in the future.

Teamhacksung rocks.
[Galaxy S III General] LuLuke:
What do I have to take for the motion featured + how to install it ?

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III General] ManCityFC:
Can I ask, but why hasn't someone taken the near perfect buttery Sammy ROM leak and stripped out all the touchwiz crap, and built an AOSP ROM on top of it ala MIUI? Seems like a decent halfway house until the devs can disassemble the crap that the Samsung nutters have cobbled together?

I love AOSP and CM, but for the time being, I would happily live with something that had all the AOSP features and simplicity laid over the Samsung ROM.

Just a thought, don't flame me, I know it isn't perfect, but it would keep everybody happy for a while at least as you'd have the best of both worlds.
[Galaxy S III General] dagonas:
Which kind of bluetooth do you have in your car? Mine is Volkswagen's bluetooth premium
[Galaxy S III General] kickassdave:
I agree with you strongly. MIUI used to use cm as a base and stopped, probably partly because of all these problems.

MIUI is very fast, the phone/messaging and other default apps are faster to load than the default touchwiz apps yet it is based on the same framework. So I think what you are saying is possible... but I am starting to stray too far from the current topic :)

(Please don't flame me either! I'm sure some would agree it'd be nice to see some of the cool themes in MIUI reach our beloved AOSP ROMs!)
[Galaxy S III General] mat.hen:
Is there a Jelly Bean MIUI ROM for i9300 floating about? Not the AOSP one, the Touchwiz one.
[Galaxy S III General] hellsgod:
AOSP will never base on sammy.

hells
[Galaxy S III General] superfire71:
I appologize for off topic. I just made one with sammy ICS if your interested. Like If wanam and jkay roms had a two headed baby. I enjoyed supplanting sammy apps
[Galaxy S III General] graffixnyc:
Thread cleaned.... please respect each other. You all do not have to agree, but you can disagree in a respectful non insulting manner
[Galaxy S III General] w1nter456:
Lollolll, hahaaaaaaaa, nice one moderator, I really like your style.