yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] adityaxavier:
Thanks a lot for the heads up. Would look into the code and check if there is anything we can do.

Regarding the noob thread.. well i never really post until there is something i can give back to the people. So though i have been a member since 2 years never really posted. Hence no access to developer threads. And any of my queries were solved by using loads of Google and reading the Code.

BTW, tuna has the same hardware; wonder how they are managing updating the firmware if they are updating it ever.
[Galaxy S III General] YDardeer:
@codeworks, @xplode, @devtonder, and all other cm devs who post here....

Just speculating here, but WHAT IF the next nexus is made by Samsung. And WHAT IF its powered by exynos..... would that help exynos development on various devices???? Would Samsung be forced to put out good open source drivers and documentation?

When Google and Motorola released honeycomb, did nvidia do anything that helped modders and developers for the Tegra
[Galaxy S III General] chiragkrishna:
any body knows why i get this in the start of the log??

is it my phone or everybody has it??

rom: cm-10-20120923-NIGHTLY-i9300

I/Vold ( 1908): Vold 2.1 (the revenge) firing up

D/Vold ( 1908): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold ( 1908): Volume usbdisk0 state changing -1 (Initializing) -> 0 (No-Media)

D/macloader( 1921): Deleting file /data/.cid.info

D/Vold ( 1908): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)

D/DirectVolume( 1908): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 17, PARTN 1
[Galaxy S III General] :
how did you manage to spell all three names wrong? :eek:
[Galaxy S III General] adjaca:
Here is the log, hope it helps..

http://pastebin.com/zczZHGvT
[Galaxy S III General] codeworkx:
if you look at the exynos kernel google is maintaining... no it will not help because it's totally different. maybe for the s4 then.

but i really dunno if samsung will put a exynos in next nexus and open up the platform. samsung is ****ing closed.

they're hating us, thats for sure but they didn't start fighting against the custom rom community yet.
[Galaxy S III General] Entropy512:
mess with mods, they'll do terrible terrible damage to you.

To some degree, you need to develop a bit of a thick skin. That said, once you've gotten the hang of development and have earned the respect of the useful members of the community, burning noobs to a crisp can be great stress relief.

That said, after a while it gets frustrating dealing with users complaining about stuff you can't change. At least finally users are starting to understand the Exynos situation and why many things stay broken for a long time on AOSP firmwares on these devices. That said, Exynos devices can be a great learning experience in some ways - "trial by fire" for a developer. That said, I'm using "that said" far too much and probably need to rewrite this whole paragraph but I'm not motivated.

Yeah... I would've been happier to see Hacre dismantle someone though. :)

Yeah... Sometimes I get frustrated, but often torching a noob serves to relieve most of my stress. Those who get torched must realize - they are the focus of both noob-induced AND Samsung-induced stress relief.

dvtonder to stop dealing crack.

Based on the posts, it looks like TW firmwares can somehow do the downgrade.

TBH I think the easiest solution is to just say "you must flash an ICS firmware and turn on NFC to downgrade your firmware".

If the next Nexus is Exynos, it's likely to be Exynos5. Unlikely to be useful for Exynos 4412, just like their 4412 stuff has yet to prove useful on 4210.

In the case of Tegra2/Tegra3 Nexus (or other Google Experience devices with AOSP support), it turned out something like:

Tablets used on variant of the Tegra 2, and most other tablets were able to work reasonably well with Xoom stuff. See P75xx and ICS - everything but camera came up fairly early and was quite solid.

Phones used a different variant/architecture that differed greatly for reference sources, as a result, they were MUCH harder to work with.

Same deal seems to be going on for Tegra3 - much of the Nexus 7 stuff isn't too useful on phones, but tablets seem to be doing well.

For Exynos, it's a bit different. It's "How samsung does it in their own products" vs. "Google/reference products". Again, Samsung has a bad habit of diverging from reference source - Hummingbird had the Nexus S, but still the initial I9000 work was quite difficult because Samsung diverged so much. That said, at least when you have an identical SoC, there is much more hope.

So if there's an Exynos5-based Nexus, and Samsung releases other Exynos5 devices, they might be in better shape. That said, if the Samsung device has additional features not present in the Nexus, those can be difficult or impossible to add. See, for example, MHL output on the Infuse, which is the only Hummingbird device with MHL.

Oh yeah, if you're willing to sacrifice camera, things are often much better. We'd probably be able to use the Insignal reference source for nearly everything if not for the broken camera interfaces.
[Galaxy S III General] RorixRebel:
so i was using CM10 and felt like trying oficial stock JB and boy....do i regret that...

if you compare Sammy vs CM10 its turtle slow, coming back to Cyano tonight... hopefully my tethering will work now :D

another small and probably dumb question. Is it possible to watch videos? yesterday i tried to watch HIMYM on my phone and i couldn't....used both stock browser and dolphin HD.
[Galaxy S III General] K Rich:
@Entropy512 and luck with the Netflix fix? I don't really NEED Netflix on my phone, but it would be nice yo have :D

Then again, I could just use the workaround hack. Any disadvantage to doing it that way?
[Galaxy S III General] zombination:
Thanks for your contribution i have same problem
[Galaxy S III General] YDardeer:
Thanks. I wasn't thinking about the s3 in specific (ok maybe I did), I was wondering if it would be helpful for the open source community. Maybe Samsung own version of omapzoom or something. but its good to know there might be hope for future devices (s4 for example) at least

And btw having " Sent from my Galaxy Nexus using xda app-developers app " as your signiture hurts a bit lol

---------- Post added at 12:28 AM ---------- Previous post was at 12:25 AM ----------

First of all, thanks a lot for the thorough reply.

Yeah I forgot about the hummingbird in the nexus s. Seems like there's no hope with Samsung as you and codeworks said. Sigh......

Anyways thanks a lot for all of your contributions to the community

---------- Post added at 12:33 AM ---------- Previous post was at 12:28 AM ----------

Hahaha they have too many "x"es in their names for me to care about their spelling
[Galaxy S III General] alienmind:
Even if it is not possible to write, Is it possible to read current firmware? and let's say, compare it to known dumps (one coming from ICS and the other from JB)? This would be a nasty hack, but having two drivers included (propietary and google's), updater-script could choose which one to use according to comparison.

Sorry if I'm saying nonsense but hey! this is the discussion thread and I'm just another low-level noob ^_^ :laugh:
[Galaxy S III General] SleemLDJ:
Awkward question.

I've always had to press power button to select "screen capture" from power menu. Which kinda sucks.

Someone kindly tell me the combination of hard keys to press to take screenshots? Thanks.
[Galaxy S III General] Fnick:
Hold power and the home button, should work
[Galaxy S III General] Tenacious:
Press Power+volume down button at same time.
[Galaxy S III General] wolfboy1984:
@slimldj

In settings there is option for screenshot in power menu. Turn it on.
[Galaxy S III General] SleemLDJ:
Yeah. I had that on. That's how I've been taking screenshots. I just needed the other option of hardware key combination.

Got the help tho.

Thanks a lot.
[Galaxy S III General] xx1xx:
whats's up with wifi/wpa? I'm unable to connect to wpa2 access points since 0924 (i skipped 0923) I've gone back as far is 09220 (ODIN noob-proof) and still unable to connect. I've also revert back to ICS using alienmind's steps without success.

I've also learnt a valuable lesson...Reset to factory in stock ICS nukes the internal sdcard. not cool!

http://pastebin.com/iDZeP9iT
[Galaxy S III General] Koramchad:
I tried downloading it but its not available on siyah's website anymore. Any idea on how to get it? Or any workaround to make tether work?
[Galaxy S III General] eseregin:
Rrrrrrrrr.....

I start to feel like a dangeon dragon :)

New nightly still not out, oh holly server, why, Why!
[Galaxy S III General] rmont:
Someone already had a system crash where only hard keys are blinking and the screen goes black? Forcing a hard reset. I'm using latest nigthly with stock kernel.
[Galaxy S III General] saintsinner25:
I've already disabled the stock browser :| never liked it anyways.
[Galaxy S III General] rmont:
I will try this, i use chrome :D
[Galaxy S III General] SleemLDJ:
Well. Since its now obsolete I think they removed it.

The only way out which I have done as well is to revert back to nightly 20120921 until there is a work around by one of our awesome devs.

That was the last nightly where it worked.

You don't need to factory reset or anything. Just flash over the current nightly you have.
[Galaxy S III General] encryptioncsta:
why is the browser still there is chrome is the stock browser for 4.1 jelly bean?

also tryed the latest nightly and still no damn buggy gallery still broken and netflix anf catchuptv domt work:(
[Galaxy S III General] rmont:
But it would be interesting to know the reason for a possible fix.
[Galaxy S III General] SleemLDJ:
Revert to ICS using wanamlite 2.3 ICS

I did it for mine and both wifi and NFC worked.

Steps:

1. Download wanamlite rom from http://netkups.com/?d=50f3150065651

(Download the torrent and then put it on your SGS3 SD card)

2. Make a nandroid backup of your current nightly from cwm

3. Wipe and factory reset

4. Install the wanamlite ROM from your SD card and boot up as usual.

5. After boot up and set up go to WiFi turn it on and try to connect to any network. Also turn our NFC on and off to make sure it works.

Go to settings and make sure your baseband version ends with "XXLH1"

IF ALL CHECKS!,

6. Boot into recovery and wipe/factory reset and install CM10 again or restore your the nandroid back up you made.

*if you don't wipe/factory reset you might get bootloops"

7. After boot up and set up of your cm10, go to WiFi and connect. It will work. Also play around with NFC.

Your baseband version will remain "XXLH1"

Done!

Don't install JB leaks if you want to keep this alive for future cm10 nightlies.
[Galaxy S III General] eseregin:
Your method works for me. NFC started working. :)

PS

IMO should be in first post to all can use it
[Galaxy S III General] awesomeusername:
has anyone made a petition to get samsung to open up the drivers or whatever is needed?

I would happily sign it :)
[Galaxy S III General] adityaxavier:
NFC Fix.

Guys I don't think downgrading to ICS just to downgrade the Firmware of NFC Chip is a brilliant idea.

So just made a simple Zip file to update the CM NFC Firmware.

WARNING :- Only meant for devices which have been through JB and unable to have NFC working in CM. All other devices, NFC can be harmed so dont install this.

PS:- Usual warnings employ !

PPS:- All thanks to our great CM Team. Cody, thanks for pointing me in the right direction.
[Galaxy S III General] mistersixt:
That worked for me, thanks a lot!

Regards, mistersixt.
[Galaxy S III General] eseregin:
Ok i see your point, thanks

Couls you tell me why 2 folders with file - one strange MACOS name folder - think this is kinda not needed. CWM does not matter if you used windows or macos to compile zip

PS

Though every time you flash new nigtly ROM you will need flash it again...

Downgrading solves problem for all future time...
[Galaxy S III General] Multisaft7:
I got a problem, when i connected my bluetooth headset to call (everything works great) someone and after I used it and break the bluetooth connection, i hear nobody when i take a call, the oponent hears me but i heard nothing. No reboot helps etc., after i connected again to my bluetooth headset, everything works again....:confused::confused::confused::confused:
[Galaxy S III General] adityaxavier:
Well the MACOS folder is created by MacOS automatically, and has nothing to do with CWM.

Yeah you would have to flash the Fix everytime you flash a Nightly, but its the same with fonts as well. Going through ODIN is a pain.
[Galaxy S III General] eseregin:
You dont need ODIN in this case, just CWM flash ICS of for example WnamLight 2.3 :cowboy:
[Galaxy S III General] GalaxyGusta:
I think we should all send Samsung an email at the same time and maybe when they will get 1000 emails or something like that stuff will start moving
[Galaxy S III General] mistersixt:
Is it safe to install a newer baseband after this procedure or do I have to stick with "XXLH1" ?

Thanks, mistersixt.
[Galaxy S III General] teriemer:
Hi Fouks

One simple question here. I'm sure somebody know.

How is the process for releasing a new nightly?

I see there is a lot of changes implemented in the next nightly. Is there a process to determine when it's ready or how does it work.

Thx in adv.
[Galaxy S III General] XDA mark:
The robot should automaticly make new builds every day. Even when there are no changes, the robot still builds.

Don't know why it's taking so long for the next nightly. Maybe somebody else knows.
[Galaxy S III General] eseregin:
Think something wrong with compiler - needed manual operation of resolving config make file or about so.

Probably some change broke compilation procedure

---------- Post added at 12:15 PM ---------- Previous post was at 12:15 PM ----------

Yes

I am on latest LIB modem
[Galaxy S III General] kobazik:
Where I can find ril for LIB modem? Google drive links posted earlier doesn't work for me.
[Galaxy S III General] eseregin:
Where all modems are

http://xdaforums.com/showthread.php?t=1740061
[Galaxy S III General] :
links still work for me at least, but here (although it is the same as LI8 one).
[Galaxy S III General] kobazik:
Thanks. I applied it using CWM but GetRIL still shows I9300XXDLI2; I9300XXDLI3
[Galaxy S III General] XDA mark:
That's normal. Happened with LI8 ril as well.
[Galaxy S III General] eseregin:
Probably last commit will solve issue with impossible to build CM

https://github.com/cyanogenmod/android_build/commit/5e703b2ecd1056f926f3a3270d3ad7f2cab8b3e7
[Galaxy S III General] SleemLDJ:
I'm not too sure if its safe to as I haven't tried doing it.

You can try and let all of us know. Problem is if it doesn't work again, you have to revert back to ICS
[Galaxy S III General] eseregin:
I DID try it.

Everything is Ok
[Galaxy S III General] antisystem:
build just got uploaded:

http://www.get.cm/get/jenkins/8794/cm-10-20120926-NIGHTLY-i9300.zip
[Galaxy S III General] eseregin:
Yeah, finally!!!
[Galaxy S III General] victorator:
cm-10-20120926-NIGHTLY-i9300.zip multiupload mirror
[Galaxy S III General] mariotme:
Is screen auto brightness working?
[Galaxy S III General] eseregin:
On prev build worked.

Now flashing only
[Galaxy S III General] ipguy:
Sorry if this is a stupid question but ill ask anyway

If I use the noob-proof method, will it install CWM and JB including root for a stock s3?
[Galaxy S III General] SleemLDJ:
That's awesome. Which one did you try and where did you cop it from?

Thanks.
[Galaxy S III General] eseregin:
Yes, it is for me
[Galaxy S III General] teriemer:
Wuuuhuuu :p

So many changes - wup wup
[Galaxy S III General] eseregin:
The last one modem from here LIB

http://xdaforums.com/show....php?t=1740061
[Galaxy S III General] band_aid:
Torch finally works :)

Sent from my GT-I9300
[Galaxy S III General] eseregin:
It worked on prev nightly as well
[Galaxy S III General] eseregin:
I am not professional but looks like log made after reboot?

Cannot see where exactly the fail happened...
[Galaxy S III General] zi1x:
The phone crashed when it was plugged in, it has just booted up. I started adb logcat and the last line kept repeating.
[Galaxy S III General] SleemLDJ:
Works well. Thanks.
[Galaxy S III General] sjgore:
Is 26/09 nightly Android 4.1.2?

Changelog shows lots of AOSP merges, and build is JRO03R, but version number still shows 4.1.1.
[Galaxy S III General] Xbto:
Hi guys,

One question: is it possible to read NFC tags while the screen is off? I read somewhere that this would be a feature on CM but not sure if it applies to GS3 as well. This is the only thing preventing me to switch to CM as I use NFC on a daily basis.
[Galaxy S III General] edgarf28:
4.1.1r6
[Galaxy S III General] SleemLDJ:
Android 4.1.2? Say what???

I think I've been sleeping on CM10 change log site that I forgot about other aspect of android.
[Galaxy S III General] Kung-Fu-Tse:
*rofl* :silly:

Here, for you: Android version
[Galaxy S III General] gwak:
Just flashed latest build. No dial tone when ringing number. Does anyone have an answer please
[Galaxy S III General] ThunderBolt_BR:
No issues here.

[]'s
[Galaxy S III General] siapakahaku:
What bugs still remain on latest nightly?

Just curious :D since there are so many aosp merged
[Galaxy S III General] Entropy512:
Months ago. Didn't do jack ****.

Someone broke the build, happens occasionally.

no hdmi, "project butter" is fake veggie oil "butter", piles of other exynos-specific ****, try reading the thread
[Galaxy S III General] XDA mark:
Flashed 2609, everything working fine.

Are there any new "major" things added? I look at the changelog but sometimes I dont know for sure what everything means.
[Galaxy S III General] SleemLDJ:
Still a couple.

Camera with auto focus and flash

WiFi tethering
[Galaxy S III General] eseregin:
In your url no any info about exactly 4.1.2 version

Did you check it?

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

Some fake SMS ability as i understand begining to implement
[Galaxy S III General] respider:
I think that's his point
[Galaxy S III General] saucey2438:
As far as I'm concerned, these developers have every right to be frustrated. If I was being paid to deal with some of the idiotic drivel that appears in a constructive development thread, I would quit. And they are doing it in their spare time? Hats off to their patience.
[Galaxy S III General] ThunderWolf78:
Can't we all just shut the **** up and STOP this now. This is a thread about general CM10 discussion, NOT politics or anything else. You realise that this thread too will be closed if we don't shape up do you?

And more on-topic, will eventual call related fixes trickle down into CM9 code aswell?

painstakingly sent from my h4x0r3d up GT-I9300 with Tapatalk 2
[Galaxy S III General] XDA mark:
Will all this idiotic fighting stop before I fart so hard the earth will explode? No seriously, we are all wasting our free time.

Lets focus on using CM10, helping each other by repprting bugs/telling how to possibly solve them. Making jokes is fine, being happy is fine, but since when is this thread all about fighting and not about love? Because Xplodwild closed the dev thread, you are all blaming each other? Somebody needs to be the bad guy? There will always be some users (like 0,1-1% of the people) that will not read the OP, post question that makes the devs/experienced users go "-.-".. it's normal, like in real life we don't like everybody. But learn to remain calm, because when you get mad you only do harm to yourself.

Now let me flash preview 5 :victory:
[Galaxy S III General] jnr21:
Not gonna happen...i quess...
[Galaxy S III General] ickyboo:
XDA needs a upvote and downvote, People should be able to self moderate and downvote all the stupid questions which then gets hidden depending on whatever settings they want. So for nosey people or mods they can set the downvote mod to show all questions while for normal people it can hide -5 or -10 posts.

Or just copy Reddit.
[Galaxy S III General] pinku1:
that's what I was also thinking!
[Galaxy S III General] ethanfel:
I confirm, audio issue are resolved in the last preview, awesome.
[Galaxy S III General] sir_earl:
First of all, most of us appreciate greatly what the devs do for this community, and in a sense that does elevate them to a godly status, and they should be respected for donating their free time and energy, even if they're only doing it for personal reasons.

One small suggestion though, and I might be out of line here, but wouldn't it make much more sense to post the preview build (which you already know has tons of issues) as just a preview, and not bother yourselves with bug reports or logcats until you have something slightly more stable. This would enable you to focus on fixing the plethora of bugs you already know exist, and when you do open the forum up for testing feedback, the signal to noise ratio should be much higher. You can't get rid of the idiots, but you can reduce the volume that post rubbish!
[Galaxy S III General] ethanfel:
How could they make more stable realese without bug reports and logcat ? :cyclops:
[Galaxy S III General] hefonthefjords:
This thread should be closed since there is nothing to discuss now.

I would also like to thank you all for pissing off the developers to the point that they will now withold their developments.

Cheers.
[Galaxy S III General] ilovebytes:
sadly its the same procedure as nearly every time - a little bunch of idiots - gets it all down - i fully understand the devs - its just frustrating for them.
[Galaxy S III General] sir_earl:
It took me all of 5 minutes to discover almost all of the bugs reported thus far, so I would be surprised if the devs weren't already aware of most of them...
[Galaxy S III General] on2a:
This thread should NOT be closed. If you have nothing constructive to say, don't say anything at all.

What kind of idiot asks for a discussion thread to be closed. Just stop reading if you don't like it.
[Galaxy S III General] sir_earl:
+1 Also, no one said anything about withholding developments!
[Galaxy S III General] SnakeHaveYou:
I think that the 'DEV' thread should be more helpful for the user, not the Debugging thing that was for..
[Galaxy S III General] s3lover:
Hi just like to say what a great rom, im loving it.

My question is i cant find s-voice as it been taking out or im i blind lol

Cheers
[Galaxy S III General] teh-maz0r:
S voice is a Samsung bloatware app so its not included in an ASOP build, you should just use GoogleNow its soo much better.
[Galaxy S III General] XDA mark:
Yeah I have been thinking about something similar. You should be able to +1/-1 a post, so good posts that sumarise all the bugs for example will probably get a lot of +1's (you know occasionaly sombody gets mad and summrisez all the problems with the ROM). The posts with the most +1's should end up somewhere sticky'd on each page, I don't know exactly. But the idea is to make a system that highlights the good post so new users will see them easier and faster.
[Galaxy S III General] Tectas:
S-voice is touchwiz, cyanogenmod is aosp. There is no and will never be s-voice, but check google now.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III General] tanjiajun_34:
Doubt so. My CM10 on Galaxy S feels smoother in the animation than on my S3's CM10. Give them time it will soon be coming to our phone.
[Galaxy S III General] peterperfect:
Yes.
[Galaxy S III General] crazyharry:
Great work! Thanks
[Galaxy S III General] Kung-Fu-Tse:
really :eek: I know it so I post this link for the incorrect guy :cyclops:
[Galaxy S III General] gavin-phelan:
Omap chip not been produced anymore

http://m.gsmarena.com/texas_instruments_backtracks_from_smartphones_goodbye_omap-news-4861.php
[Galaxy S III General] Codekrypt:
Sorry though can you please post this in the general forum because one person goes off topic alot of others do as well. I am sure people would like to know how the new nightly performs instead. Thanks. Sorry again.
[Galaxy S III General] thelastwilson:
I'm still on 0924 and it works fine for me.

Edit: I mean I'm still on 0921 and it's been working fine for me.