yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] big_adventure:
I never manage to spend more than a couple of percent at 1400mhz - even browsing, since browsing only bumps the CPU for the render, then shuts it down again. You have some kind of runaway app. It could well be the Media Scanner - lots of people report that it can get a little crazy, and it always maxes the CPU when it does. Download an app to disable it, then see how it goes from there. If not that, it's some other app. Try disabling (at least for the moment) Google Now and Facebook - those are the two that eat my battery sometimes.
[Galaxy S III General] edgarf28:
You can get the latest Gapps here: http://goo.im/gapps/gapps-jb-20120726-signed.zip

Put these 2 files on your SD card:

- cm-10-20120825-EXPERIMENTAL-i9300-BEANPEELER.zip

- gapps-jb-20120726-signed.zip

Boot in CWM

Do a Data/factory reset

Go to Mounts and storage in CWM

And Choose format System and after that Format Preload

And then install those 2 zip files in CWM (cm10 & Gapps)
[Galaxy S III General] big_adventure:
There is no need at all to format /system.

Just do a full wipe data / factory restore. The CM installer will take care of the caches and the system directory. You have absolutely no need to format that before continuing - you will gain nothing at all. You can do it if you want, but it's like a security blanket - it might feel nice, but doesn't have any real benefit and the girls will think you are a little weird if you keep carrying it around / formatting stuff you don't have to.

---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------

By the way, if you don't believe me, just open the CM zip file, navigate to the META-INF/com/google/android directory and check the updater-script. You'll see this:

run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");

So really, don't bother doing it yourself. Zero benefit, only extra write-wear on your expensive integrated flash.
[Galaxy S III General] btemtd:
Thanks guys I am now very clear.... By the way I was just thinking you know when you format wouldnt it format cwm and then if something goes wrong you cant get in recovery mode.. Or is that installed on a hidden system partition i was just thinking where is all that data stored, recovery and download mode data

Ok great so it formats for u
[Galaxy S III General] edgarf28:
You don't will remove CWM when you format the System partition. The System partition is only for the rom.

And yeah CM10 will do it automatically before the installation. I forgot that.

So a Data/factory reset is enough.
[Galaxy S III General] Theshawty:
You guys are saying there's nothing that needs to be done before flashing CM10. I disagree, though. If one's coming from a JB leak, which has the new bootloader, you might wanna odin back to an ICS ROM which has the older bootloader or you will have a broken wifi.
[Galaxy S III General] big_adventure:
Android phones generally have a bunch of partitions:

bootloader - Gets you to "Odin-ready" / download mode on a Samsung, also triggers a system or recovery load - critical.

recovery - Non-android partition that lets you flash updates or "recover" your system (or lots of other stuff with CW)

boot - Your kernel

radio - Your baseband

system - Your ROM, complete with system apps, formatted by most ROM installers automatically

cache - What it says on the tin - formatted by most upgrades automatically

data - Your user apps and data - formatted by a factory reset / wipe data, generally untouched by a ROM install - Dalvik cache is often here as well

sdcard, extsdcard, etc.: Your storage, internal or external.

---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------

True enough - but a VERRRRRY specific case that doesn't apply to the vast majority of people. And the people to whom it DOES apply should know better or at least know how to search and read.
[Galaxy S III General] factor27:
voice dialing?

Bluetooth voice dialing broke for me starting in CM9 RC2 and it looks like CM10 inherited that.

Holding the button on the headset to initiate no longer has the "speak now" announcement and it doesn't seem to accept any voice even though it says "listening"

Can anyone else give it a shot with the build in voice dialer?

I tried other dialers (vlingo and some others) but pressing the button only opens the app, and I still have to press the button to start recognition (which is annoying when the phone isn't conveniently accessible).
[Galaxy S III General] Theshawty:
Agreed.

The latter is something which is a dying game here at XDA. People hardly use this underused feature (search) because they want everything to be served on a silver platter right before their very selves.
[Galaxy S III General] josejunior86:
hmm...

but it doesn't make the international version better?

the development of CM10 is more advanced in the US version?

Thanks
[Galaxy S III General] MauricioAedo:
Just got my original MHL HDTV Smart Adapter to connect my S3 to the TV but I see nothing, I detect the HDMI connection but does not connect to display the image, someone has connected you S3 to the TV using this ROM?

Regards
[Galaxy S III General] Joschi75:
http://teamhacksung.org/wiki/index.php/CyanogenMod10:GT-I9300:Nightly:Known_issues

TVOut: unsupported and will probably never be
[Galaxy S III General] MauricioAedo:
Very thanks
[Galaxy S III General] big_adventure:
The International version is faster, definitely. However, the US version uses a Qualcomm processor, and Qualcomm contributes a ton of kernel and driver information and source to CodeAurora. This makes it MUCH easier to develop new versions for those phones. The Exnyos chip is ONLY used in the GS3 and the new Note 2 (only announced yesterday), so there are no JB sources, no JB documentation, nothing out yet. Therefore, we are using Sammy ICS kernels with an AOSP-based JB ROM, and there are some pretty massive driver differences. Specifically, there is the mem leak, which, according to Cody, is fixed in a Mali driver from Update3, but running that driver requires kernel changes, and we don't have the source required to compile such a thing yet.
[Galaxy S III General] Theshawty:
I wish Sammy would hand out the necessary Exynos and Mali documentation and being such up-tight arses.
[Galaxy S III General] mat.hen:
So given the problems with developing for Exynos due to closed-sourcedness, what are the practical differences between CM9.1 and CM10 for us I9300 users? What I mean is, what of the Jelly Bean features are currently working as they should?
[Galaxy S III General] Theshawty:
Hardly any. Basically it comes down to this (CM10)

Not-so-smooth UI (vsync off) with working youtube playback.

Smooth UI (vsync on) with non-working youtube playback (mostly HD videos)

Mem leaks

Other issues
[Galaxy S III General] josejunior86:
Now it's clear, thanks!

:good:
[Galaxy S III General] TecQuality:
My videos are completely broken right now, i still cant see videos into youtube a friendcaster too, someone can give a .zip which i can flash thru cwm with the different composer?

@jnr21: i cant i'm with tapatalk right now :)

Sent from my GT-I9300 eating Jelly Bean
[Galaxy S III General] overflyer:
In my opinion that is a very nice feature about the S3 and if CM wont support it anytime soon I for myself at least will have to move back to stock rom, again. I could imagine that this is a good reason for many people to do the same, though :/. Too bad, I like CM so much :(
[Galaxy S III General] Ramalama:
Here: http://foonode.net/file/92bJ

Cwm flashable zip (old hw composer with working videos)

Cheers
[Galaxy S III General] TecQuality:
Thanks, so with CM10 this is the only eay right? Then we need a fix from the devs or not?

I don't understand if now our composer is working as designed.

Sent from my GT-I9300 eating Jelly Bean
[Galaxy S III General] big_adventure:
Got an SOD today using beanpeeler. Here's the last_kmsg...
[Galaxy S III General] XDA mark:
The devs made a choice: the new HWcomposer. Why, probably because vsync works and it makes our device faster/smoother, but there is the videos bug. In their eyes, this is better then working videos but no vsync (old hwcomposer). So atm, there is no perfect solution.
[Galaxy S III General] stefanACM:
Please tell me that this is not true and that I am crazy ?!?!?!

I just try official JB ROM from Samsung and it have same memory leak like CM10 :|
[Galaxy S III General] jhericurls:
You are crazy.
[Galaxy S III General] DrGomez:
honestly... i've never had any of those "memory leak" problems. I thought It's absolutely normal that the ram is ACTUALLY used when you open an app or even use anything, be it the notifications panel or what not... that's what RAM is there for. I've never had any crashes or freezes as a result of a RAM 'overuse'. That's my experience anyway. I understand that there MIGHT be a memory leak problem especially when developers ay there is... but i also think people overmonitor stuff sometimes and think the world's gonna end while there's actually nothing wrong.

also... about the HW composer. I think the phone was fast already with the old one. I don't see much of a difference. And not being able to watch videos is far worse in my opinion than a lil bit more of a jitter that you can only see with a 1000fps slow-motion capturing device they apparently used at the last google keynote.

This phone has a freakin quadcore CPU. It's fast enough. I want functionality rather than a lil tiny bit of a "faster butter experience you can't see but <<feeeeel>>".

But that's just my opinion... and reading the forum postings on here, i seem to be quite alone with it anyway... or am i?

P.S. Battery's been great in the last builds though. Although i'm still using BACONWARMER. I havent had any problems with it and you know what they say: When there's nothing wrong...
[Galaxy S III General] NIK516:
Waiting on source ........... thanks for all the hard work thus fare guys can't wait to ditch touch wiz
[Galaxy S III General] wolfboy1984:
The very first leak (July build) did. XDLH4, i think.

Not that it matters.
[Galaxy S III General] LJE:
The problem is when the available ram reaches 0 and things start closing down on you. I normally realise it's time for a reboot when my keyboard disappears while I'm typing. (If that ever happens to you check available ram and you'll see what people are talking about)

It IS a definite problem and think yourself lucky you haven't got the problem.

Although easily fixed with a reboot
[Galaxy S III General] Cyb3rGlitch:
The memory leak does exist, and it has nothing to do with how an OS is supposed to allocate memory. If you're not getting the memory leak problem (which I sincerely doubt), then you're either not using your phone at all, you're just oblivious to erratic behaviour, or you just reboot often. The memory leak is a problem. Any bug which requires users to reboot often is not excusable, nor is there 'nothing wrong'. So please, don't pretend you're the only one that has the higher knowledge to discern what is and isn't a real problem.

As for the HWComposer, the 'feel' of the device is very much an important aspect of usability. If you don't care for it, then flash the old HWComposer.
[Galaxy S III General] big_adventure:
Here's the thing - they HAVE to release the source. However, they will not do so and are not obliged to do so until they release the compiled binaries on a phone. And they have not released THOSE because they are not ready. Given how much Samsung figures to make by being the first "flagship" phone with JB, they will definitely release it as soon as they can.

Now, the documentation of Samsung/Exnyos specific features? That's different - that we'll never likely see. And you know why? Because only Samsung uses Exnyos. Qualcomm doesn't make phones - they make chips. They document stuff extensively because their myriad partners use their chips and need to know how to write software for the chips. Since nobody outside of Samsung's fortress builds anything with an Exnyos inside (Sammy easily consumes all of their Exnyos production themselves), Sammy has absolutely zero incentive to support an extensive documentation base. It sucks, but it's business.
[Galaxy S III General] LionRock:
Every day the same. My battery does not last even for one day :/ Any tip what to do? I have the latest version.
[Galaxy S III General] Fate_Hunter:
Did someone realize that the latest CM-10 will make your bottom of the phone hot like an oven.In the old version(cm-10-20120822-EXPERIMENTAL-i9300-BACONWARMER.zip ) I haven't met this problem before, its juz in the new version(cm-10-20120825-EXPERIMENTAL-i9300-BEANPEELER.zip ). Is it the kernel problems or they changed to another kernel?:confused:

---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------

Ok, its simple. Because of the memory leak, its cost your RAM none stop working. So it keep draining your battery life. If you aren't this problem then I can't help you, Sorry
[Galaxy S III General] Flynny75:
Not totally true. HardKernel build the ODROID-X platform on Exynos 4412 http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G133999328931. Perhaps they can help with the JB porting
[Galaxy S III General] codeworkx:
No. They're still using the old mali drivers and the hardware differs a lot.

There's a simple solution: PATIENCE
[Galaxy S III General] Crys7y:
I left my phone turned off and let it to charge the last night because I wanted to do a battery stats wipe. I unplugged it a few hours ago and then I wanted to boot into recovery. Right when the recovery would appear, my S3 restarted. It booted into CM10 and i tried the powermenu method of recovery rebooting. It rebooted itself and blocked at the welcome screen. I could only enter download mode. Finally I maganged to flash the .PIT file and then flashed a stock ROM. I was using CM-10-20120825-EXPERIMENTAL-i9300-BEANPEELER with the stock kernel and an untouched modem.

I'm not mad or something like this. I really loved JB the time it lasted on my phone. The devs did an awesome job coding this. The mem leak isn't that bad and the problem with the videos is still there. I'd call it "acceptable". One reboot per day in my case. Also, it has some awesome features and it can be easily a daily driver. I'm just curious, anyone had my problem so far ? Was it a CM10 fault ? Bad luck ? Or a bad batch ? due to the fact that not all the phones are the same.

I'm sorry for the long post. Gotta flash CM9 right now.
[Galaxy S III General] krfs2094:
Find out what apps are using up your battery. Identify what that is. Your Wi-Fi as well.
[Galaxy S III General] wire103:
What's that? I don't remember seeing any of that around XDA lately ;)

Great job on the releases so far. Except for the daily need for a reboot due to the memory leak, everything is running beautifully here.

Tasker works great for the daily reboot: if my phone is charging and lying face down, it reboots at 2 am every night. That makes the memory leak seem non-problematic.

Thanks for your efforts!
[Galaxy S III General] big_adventure:
From their site:

KEY FEATURES (Click image to enlarge)

* Low-cost mobile software development platform

* Quad core ARM Cortex-A9 MPCore

* 6 x High speed USB2.0 Host port

* 10/100Mbps Ethernet with RJ-45 LAN Jack

* Audio codec with headphone jack and microphone jack

* Android 4.0.4 ICS

* Community-driven projects & supports

The bold and stuff is mine. Do you see the problem? They are using the stuff that HAS been open-sourced by Sammy, since all they are supporting is the same thing that Sammy already publically supports. So no, they aren't going to help at all. We need Samsung's Jelly Bean sources and some magic from Codeworkx & Co.

---------- Post added at 11:50 AM ---------- Previous post was at 11:46 AM ----------

Slightly OT, but why on earth would you do this? Battery stats are stored in /cache, and /cache is erased by the CM installer. The fact that you had beanpeeler means that you erased battery stats at most 5 days ago.

Also, all you ever have to do to calibrate a modern phone's battery stats is drain it pretty much fully and then charge it fully. Done.

---------- Post added at 11:58 AM ---------- Previous post was at 11:50 AM ----------

Check like 2 pages back and you'll see that I left some nice instructions for figuring out what was running your processor, which will also let you know what is running down your battery. You might want to publish a screenshot of your battery monitor WITHOUT drilling down into the screen you drilled into so we can see the subsystem that is eating battery.

First thing to try is to disable Google Now and uninstall Facebook - I always find that those eat battery FAST.
[Galaxy S III General] DrGomez:
I never said that.

And as i said... i never had a freeze problem and my phone never reached 0 RAM. Also... i am a heavy user - I do everything on my phone. Emails, google now, calander, spotify, flipboard, tethering, heavy bluetooth usage and i play games on the wway to work all the time, i even buy my bus and train tickets with my phone. So ya, i never had the problem apparently "everyone is talking about".

I don't know what's different on mine... except that I don't have a locksreen maybe.

Also...I do reboot mostly every morning before i take my phone out of the dock just because i always have with every phone i had, and this one just reboots in less than a minute which is great. Is that the reason? A simple reboot every morning?

---------- Post added at 12:09 PM ---------- Previous post was at 12:06 PM ----------

Seriously? That's 14 HOURS!... how's that not a work day for you at least? You live in Somalia? In my opinion that's pretty decent :/... well for a CM experimental release anyway and with your WIFI turned on.
[Galaxy S III General] big_adventure:
No, the memory leak doesn't specifically kill battery. I get fine battery life, though I do have to reboot daily.

---------- Post added at 01:02 PM ---------- Previous post was at 12:14 PM ----------

I unplug my phone (cm10 beanpeeler) at 7AM every day. I listen to at least an hour of podcasts, sped up to 1.4x, listen to at least an hour of streaming or downloaded music in Spotify, watch often an hour or 2 of video, sync 3 very active Google accounts, I handle at least 75-100 mails, 20-100 Google Talk messages and 5-50 SMSs, and read at least some using Kindle, Currents and the web. I leave wifi on all the time, even though I do not connect to wifi at work. I usually have 15-25% battery remaining when I plug it back in at 1AM or so.

If you look at his curve and data, you'll see that he's barely using the screen, and that there is a relatively consistent background draw of at least 5% an hour under extremely light use. He has something that is consistently wake-locking him. That is not good and not normal.
[Galaxy S III General] TecQuality:
this could be a trouble for who use youtube frequently ... :)
[Galaxy S III General] LionRock:
But I didnt use it for 14 hours. I did use it for about 1 or max 2 hours not any more. Here is SS of the app usage of the Wifi. Dunno from where youtube took so much data, and also chrome... I didnt use it for transfering 417MB.... Strange.
[Galaxy S III General] XDA mark:
Yes indeed. Today I finally flashed the old hwcomp. And I'm happy I did.

All videos (gallery + youtube) are working, but the phone in general hasn't frozen once since I flashed the old HWcomp. Yeah, much better imo. And it's fast, only if you really look closely you can see it's not exactly as smooth as the new HWcomp. While the new HWcomp is, lets say, level 10 of smoothness, but it freezes often, Id rather use the old HWcomposer (smoothness level 8/9) which doesnt freeze at all. :P
[Galaxy S III General] ss2i9100g:
I love CM roms and i hate to say it but rom consumption of battery sucks. I losse 12%/hour which is above normal. The first week of JB was my best experience with battery consumption ever.

CM 10 exp 25.08

Modem.DLH4

Thanks
[Galaxy S III General] wolfboy1984:
XXDLH9 MODEM.

http://xdaforums.com/showthread.php?p=30942957
[Galaxy S III General] big_adventure:
Not with the screen on for most of it, it's not, especially if you were gaming at the same time! you went from 90 to 40 in 5 hours, with more than 3 hours of screen on, including more than an hour and a half straight at one point.
[Galaxy S III General] DocRambone:
cm-10-20120831-EXPERIMENTAL-i9300-ONIONTOASTER cooked..

http://get.cm/?device=i9300
[Galaxy S III General] davewils55:
Downloading ONIONTOASTER now :D

was watching the jenkins build yesterday titled "TOMATOSQUEEZER" - was so sad when it failed
[Galaxy S III General] alexwontlose:
I got no Memory leak on sammy

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III General] ManCityFC:
Can't find a mirror that works anywhere, even ROM Manager. Anybody else having any luck?
[Galaxy S III General] chris170569:
When I click on any of the links I get a page not found error. ROM manager also gives an error when I try to download
[Galaxy S III General] Schrotty35:
Link not working.
[Galaxy S III General] DocRambone:
Hmm, seems removed, maybe a bad build?
[Galaxy S III General] gagg3:
Seems like get.cm download links are down.

Seeing how no other build is downloadble.

Rommanager is linked to get.cm =)

Seems we'll have to wait.
[Galaxy S III General] ageva:
None of the ONIONTOASTER devices links works so maybe just need to wait a little bit more.
[Galaxy S III General] GabrielSousa:
:( damm
[Galaxy S III General] DocRambone:
Mirror: http://speedy.sh/u9WeZ/cm-10-20120831-EXPERIMENTAL-i9300-ONIONTOASTER.zip
[Galaxy S III General] Maesedroid:
Thanks working and downloading!:highfive:
[Galaxy S III General] Theshawty:
You think memleaks are fixed? Checked changelogs, found nothing related to it, so I'm not gonna hold my breath. :/
[Galaxy S III General] GabrielSousa:
we need the JB kernel source from samsung to fiz the memory leak

this was told 100x times...
[Galaxy S III General] Theshawty:
I had hoped old Sammy could release the kernel source before releasing the OTA's, but looks like I was wrong. :p
[Galaxy S III General] DroidModder:
have u updated your modem?
[Galaxy S III General] btemtd:
Only problem with this is you cannot make folders in drawer on stock launcher... And if u have heaps of apps u can just imagine how messy it is
[Galaxy S III General] etchemkay:
F5 F5 F5 F5 !!

Edit: i'm talking about the broken links for the new build..
[Galaxy S III General] Flynny75:
Can you upload somewhere for free? Not paying for premium account!
[Galaxy S III General] DocRambone:
Try this: http://www.multiupload.nl/8QNSD7813J
[Galaxy S III General] TecQuality:
So every time we upgrade the rom we should reflash this fix correct? :rolleyes:

Sent from my GT-I9300 eating Jelly Bean
[Galaxy S III General] XDA mark:
Its not really a "fix". Its just the old HWcomposer, from previous builds (I believe before 17th of August). And yes, if you flash a mew build the new HWcomposer will be included, so you need to flash the old one again if you want it.
[Galaxy S III General] aelael:
Torrent download works for me...

http://get.cm/torrents/cm-10-20120831-EXPERIMENTAL-i9300-ONIONTOASTER.zip.torrent

Someone tried this build? Can i flash?
[Galaxy S III General] big_adventure:
Oniontoaster seems smooth as a baby's bottom so far. Great touch sensitivity, seems better than beanpeeler, though that could be build-desperation talking.
[Galaxy S III General] XDA mark:
I wonder why we cant download the newest build from get.cm

Maybe something wrong with the build? Im downloading it from the multiupload link some nice gentleman posted. But I'm still paranoid if I should flash it :P
[Galaxy S III General] Tricky103:
Is the from manager link not the same build?
[Galaxy S III General] DocRambone:
Use the torrent?

http://get.cm/torrents/cm-10-20120831-EXPERIMENTAL-i9300-ONIONTOASTER.zip.torrent
[Galaxy S III General] Theshawty:
Maybe server overload?
[Galaxy S III General] Tricky103:
Hey Doc

Have you got any cm10 mods??:)