yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] FDisk80:
The whole OS was 194mb and 18mb (10% of the OS size) is just for Focal app. It should of never been in there in it's current state in the first place.
[Galaxy S III Original Android Development] Yank555:
As if that was of any importance, the ~1.2Gb of unused space in the /system partition is lost space one way or the other.

But you can be happy, since it's out now, so your "issue" is gone...

Instead of posting such a statement, you should rather wonder why it's been removed in the first place (the real reason).

And it's still WIP, so yes, there still are issues to be looked at for now.

JP.

EDIT :

And keep looking, as I checked for you, Focal accounts for 13Mb, so you're still short of 5Mb of other stuff !
[Galaxy S III Original Android Development] petrolcan:
What a load of sh!t. If the developers didn't develop where would we be now?
[Galaxy S III Original Android Development] temasek:
I'm not keen in reply as such but your post is really bad taste but that's just me. Fwiw focal dev xplodwild was our device maintainer. You wouldn't even taste cm if not for xplodwild and codeworkx support.
[Galaxy S III Original Android Development] Yank555:
I'll second and sign that statement as is !

JP.
[Galaxy S III Original Android Development] FDisk80:
That doesn't change the fact that Focal was less then half baked.
[Galaxy S III Original Android Development] sewer56lol:
I triple agree
[Galaxy S III Original Android Development] petrolcan:
Blimey, you do like to stick the boot in.

Focal was very much an app in development and with any luck will continue to be developed.

At the end of the day no-one was forcing you to use it anyway.
[Galaxy S III Original Android Development] petrolcan:
Just caught up with that :victory:
[Galaxy S III Original Android Development] Yank555:
With that statement, I have a hard time understanding why you are running a CM nightly, as it's also not fully 'baked', all WIP, different each day, potentially broken from one day to the next.

Touchwiz is beta-tested

for you

by Sammy, so why not relax and enjoy that 'stock' feeling instead of b*tching around where actual development is / has been going on ?

JP.

Sent from my SlimBean 4.3 build 1 / Yank555.lu CM10.2 kernel v1.6g-beta2 (Linux 3.0.96) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] peramikic:
CM nightlies are half baked as well by that extention. Focal is a decent camera app that is work in progress just like CM 10.2 is , the whole thing is BETA, no RCs yet. Since Samsung cam port would not run on 4.3 Focus provided me options that are not present in aosp or jb+ or any other camera app...

But go ahead and write your own and be sure to release it only when its completely baked. Just mind when you are a guest in someone else's house since this is xploidwild's thread you are in...
[Galaxy S III Original Android Development] dkionline:
Has anyone problems with flashplayer? Is it works normally?

[tapatalk]printed, scanned and faxed...[/tapatalk]
[Galaxy S III Original Android Development] KKTHX:
Interesting it is that lates build is experimental.

"cm-10.2-20130922-EXPERIMENTAL-i9300.zip "
[Galaxy S III Original Android Development] festr:
Hello, since there is not much progress on developing for S3 regarding battery issue I want to ask if Temasek build also suffers battery drain after phonecall? Or is this bug fixes in the latest? Anyone can confirm?

p.s.: nexus 5 without SD card slot is no go. I just cannot live without my 64GB sd card....
[Galaxy S III Original Android Development] lcrponte:
Wrong thread to make this question don't you think?
[Galaxy S III Original Android Development] festr:
I do not think so. Since the battery drain after phonecall is cm 10.2 nighlies issue.
[Galaxy S III Original Android Development] lcrponte:
Nope, you want to know if Temasek build has the bug. So you have to go to Temasek's build thread and ask that question there... Please, don't play naive on me, I hate that.
[Galaxy S III Original Android Development] oae08:
Didnt you just answer yourself?
[Galaxy S III Original Android Development] festr:
oh my god, you both generated more spam than my out of topic question. The question if Temasek build contains the bug is not completely irrelevant since they are based on CM. I also asked if the latest CM still contains batt drain after phonecal so I did not answered.

If you have nothing to say stay silence or send me private message.
[Galaxy S III Original Android Development] Uqbar:
Experimental?

The changelog says little about experimentality... any link?
[Galaxy S III Original Android Development] lcrponte:
The "you did more spam than me" excuse, because you don't want to acknowledge that you didn't use the search button, doesn't work with me either.
[Galaxy S III Original Android Development] Eddiemc:
Any possibility of reformat the internal memory to free up the 1 gig wasted space? For those dedicated aosp users that don't care about Samsung, warranties, etc..

Since you know a lot about these things, perhaps you'd consider creating a partition tool for the hardcore cm/aosp users to only allow max 300-400mb for system?

Regards
[Galaxy S III Original Android Development] temasek:
I've politely asked not to mention me or any of my stuffs in official threads. That's why the response by other users.
[Galaxy S III Original Android Development] festr:
Ok, I just discovered this information. Apologies to everyone for my spamming.
[Galaxy S III Original Android Development] gfreeman86:
Battery Statistics wrong for apps using GPS

Hi, I'm reporting a little bug found on CM10.2 (and also on CM10.1):

When using GPS-enabled applications like "Ingress", the battery statistics that indicate the amount of time the app uses GPS is not real.

I mean:

1) I open Ingress

2) I manually activate GPS

3) Use the application some time

4) Exit the application and remove it from the memory (long press Home button and swype it away)

5) I manually disable GPS

Now on the battery statistics for the Ingress app, the timer indicating GPS continues to increment (and I think draining battery).

See the screenshots attached , taken at a few seconds distances with Ingress completely closed and GPS disabled.

I found this problem on CM10.2 (latest nightly) , then resetted the phone, installed CM10.1 (RC2) and had the same problem.

Thanks for you hard work, hope my report will help.

Greetings

Max
[Galaxy S III Original Android Development] Yank555:
Well in theory there is such a tool, that would be "fdisk", but to be honest, I have a 32Gb S3, and I'd not take any chances to repartition the internal memory to gain the 1Gb or so with the risk of bricking it... considering the time to gain enough info to be sure to do it right. But I don't know why it wouldn't work, so if you want to try ;)

On the HD2 rapartitioning was a basic thing to do, in fact going WinMo to Android it was an absolut necessity and after that, when switching ROM first thing was to repartition to the correct size.

Then when I got my htc Sensation and I asked that very same question here, and I got more or less almost excommunicated for even bringing it up.

Well with the S3 and the space we have (for /data, that was the issue with both other devices), I haven't looked at that ever since to be honest...

JP.
[Galaxy S III Original Android Development] alexferdean:
[MENTION=2502833]gfreeman86[/MENTION] interesting discovery. Great job!

Galaxy S3
[Galaxy S III Original Android Development] KKTHX:
New build is up

cm-10.2-20130923-NIGHTLY-i9300.zip

But strange in this nightly is that it is not trusted... That what CWM say...
[Galaxy S III Original Android Development] Math_Apolo:
wow, what about:

i9300

Samsung Galaxy S III (Intl)	stable cm-10.1.3-i9300.zip 168.61 MB 2013-09-23 15:45:21
[Galaxy S III Original Android Development] kornelius1982:
Great news!

I`ll give it a try, but there`s another thread for CM 10.1
[Galaxy S III Original Android Development] Math_Apolo:
I did not saw the version, sorry about

---------- Post added at 09:14 AM ---------- Previous post was at 09:08 AM ----------

Well I use ES file explorer.

How to use WiFi direct, I can see and connect with others devices but I can't transfer anything because this file manager doesn't show me the option.

I know this is wrong tittle for this question but maybe one of you understand and can help with that.
[Galaxy S III Original Android Development] IlBella95:
Someone can suggest me a good kernel to use with cm 10.2 :) i need a good battery life

Inviato dal mio GT-I9300 con Tapatalk 4
[Galaxy S III Original Android Development] basrawi:
Googy max. You'll find it in the development section
[Galaxy S III Original Android Development] petrolcan:
This thread is not the place to be looking for different kernals.
[Galaxy S III Original Android Development] sewer56lol:
*Kernels
[Galaxy S III Original Android Development] IlBella95:
Ok sorry.

Inviato dal mio GT-I9300 con Tapatalk 4
[Galaxy S III Original Android Development] petrolcan:
Grrrrr

:o
[Galaxy S III Original Android Development] Yank555:
Off-Topic :

Kernal exists, and it's computer related, but ... ;)

JP.
[Galaxy S III Original Android Development] petrolcan:
Don't you start too! ;)
[Galaxy S III Original Android Development] Math_Apolo:
I'm using this ROM about 1-3 months, well just to know

This rom supports OTG USB cable and MHL HDMI S3 cable?

Thanks
[Galaxy S III Original Android Development] scoobyjenkins:
I've used an otg cable but had to reboot or power on after connecting a device via the cable for it to be read.

Tapatalked that shiznit.
[Galaxy S III Original Android Development] xywojtek:
9/28 anyone else experiencing 4-5s freezes in whatsapp or other apps? Wiped cache + Dalvik + fixed permissions, but it didn't help
[Galaxy S III Original Android Development] HallOfSacrilege:
Works fine here. Flashed over 24/9 nightly.
[Galaxy S III Original Android Development] Chirag219:
Why is the sound from the speaker distorted at full volume??

I m on 23/9 nightly.
[Galaxy S III Original Android Development] xywojtek:
My phone becomes unresponsive, I'm experiencing a lot of default browser crashes, a few launcher crashes, and really annoying freezes... What would you guys recommend? Full wipe? Wiped cache, dalvik, fixed permissions already ...
[Galaxy S III Original Android Development] NHNXDA:
FC when scrolling the call logs screen, anyone else come across it?

Getting fair few FC's on different screens tbh, doing a dalvik, wipe, permissions & still problems, guess this nightly is a tad buggy, any suggestions as to a more stable version please, TIA.
[Galaxy S III Original Android Development] 1-0-1:
Tried the call log scrolling but I do not get any FCs. Actually I cannot recall when last I got a FC and I just do a normal update every second nightly without wiping anything. Have you tried removing your apps?

The only problem I am getting is that my data and cellular connection is very slow if I switch from 2G to 3G. This also applies when I am switching from and to wireless. By the way - what does it mean when my data, cellular or wireless signal icon stays grey but does not turn blue? Seems also I still have connectivity when its icon is grey.
[Galaxy S III Original Android Development] NHNXDA:
Its does it everytime I use scroll within call lists, flick the scroll so it self scrolls & does it.

What also is confusing me is why whatsapp data is stored in 2 places now, having to manually move it about to one location is a pita.

I use rerware mybackup pro to restore call lists, contacts & sms etc, but not apps, I reinstall from scratch tbh as I know this can cause issues.
[Galaxy S III Original Android Development] 1-0-1:
Try posting a logcat as you can reproduce the problem. But it seems you contact restore is not working as expected. By the way - I never lost or backed up my contact as I use the Google and Exchange Active-Sync to keep my contacts safe. Maybe worth it trying this as well as it is seemingless.
[Galaxy S III Original Android Development] slipar:
blue mean your device connected to google service..

grey mean connected to data but not to google..
[Galaxy S III Original Android Development] 1-0-1:
Where did you get this info?
[Galaxy S III Original Android Development] NHNXDA:
Well seems there is an issue when restoring call logs.

I have tried using cyanogen & carbon, both based on same code practically, same issue.

I tried just installing the rom with no gapps & restoring the logs, still the same problem.

However, installing the rom & then making say 50 new calls without restoring old call logs didn't present the same issue when scrolling through these new call logs created fresh.

What is obvious is, the FC always happens when it scrolls to a specific point in the call logs, always FC at the same point, about 2.5 pages down, I've meticulously tested if it was related to how fast I scroll, how slow etc, but doesn't matter if I scroll at any pace, same place it gets too & FC's.

This is no good to me as I'd never be able to recall numbers dialled lol, I use this part allot, I'll check for a updated nightly & test again.

To further add, I have installed the RC release & it still does this with restoration of logs, I will now try the stable release.

I've used mybackuppro for ages now without issues, it maybe compatibility issue, but certainly its an issue as its a widely used app,

Ok now tested with stable release & still has the same issue, so either there is an inherent issue with log restoration or its just the app isn't compatible to a degree.
[Galaxy S III Original Android Development] SaphirX:
That is common android knowledge...
[Galaxy S III Original Android Development] 1-0-1:
Let me search again but with Android a lot of these things are not readily documented.
[Galaxy S III Original Android Development] jumoog:
How you fix the opengl errors? My build without opengl booted but crash if you want open any app :(

Gapps mirror:

http://usprobam.no-ip.org/gapps-jb-20130726.zip

http://euprobam.no-ip.org/gapps-jb-20130726.zip
[Galaxy S III Original Android Development] Drizzy xS:
Can't seem to send text messages on the latest version,not sure why.
[Galaxy S III Original Android Development] UrbanDrawer:
Someone should start a 10.2 discussion thread in SIII general, like [MENTION=3208754]codeworkx[/MENTION] did with 10.1.
[Galaxy S III Original Android Development] :
Apologies for a non development comment, deleted the contents. Now, coming back to development (if not, request [MENTION=1895945]lolmensch[/MENTION] to correct me). The fact that sdcard does not mount, is it related to some changes in AOSP 4.3 or something that changed in CM? Since no partitions have changed, would CM10.1 vold/fstab not work on CM10.2? I am trying to learn and not question anyone here.

edit: Read the OP, there is a mention on storage crash but nothing beyond. [MENTION=3074503]Code124Y[/MENTION], please let me know what am I missing? I have even seen the code diffs on gerrit. There is a fix from xplodwild around fstab on gerrit
[Galaxy S III Original Android Development] Code124Y:
there is no need to apologize if you do read OP, go and read now~

edit: [MENTION=2618159]hackworks[/MENTION], sorry if i misunderstanding but, do "storage crush" mean storage got bugged? maybe he used "storage" without defining more detail mean most thing related to storage~ it could be internal or external too~

well i apologize if i misunderstanding your question... cheers up...

Sent from S3, power By Temasek'Rom and Kernel!
[Galaxy S III Original Android Development] JK-FINN:
Maybe better to leave that action to CM developers, not to some random xda reader.
[Galaxy S III Original Android Development] ereziel:
It may be kernel related, not detecting a device node or similar rather than only fstab. Unfortunatelly without root I can not test correctly and I don't know how to apply the fix, so I have to wait to test further.
[Galaxy S III Original Android Development] E.Cadro:
[MENTION=1895945]lolmensch[/MENTION] I have removed your post as it was quite aggessive if you have a problem with someones post please use the report feature in the future and let us decide if any actions are warranted.

Thread cleaned
[Galaxy S III Original Android Development] troufiniou:
The new version include Focal and other apps of the nemesis project ?
[Galaxy S III Original Android Development] AvivEliyahu:
Focal maybe,but i guess the rest of the nemesis stuff wont be included yet because its not yet published.
[Galaxy S III Original Android Development] Millenium3:
CM10.2 Discussion Thread (codeworkx)

http://xdaforums.com/showthread.php?p=44046260

Sent from my 6th phone.

Dreams don't work if you don't do them.
[Galaxy S III Original Android Development] ayoubij:
Are there that vast 'under the hood' differences between cm10.1 and 10.2 ? Im asking to take a guess of how long can cm10.2 take to become as stable as the current state of cm10.1 :)

EDIT: sry added in the discussion thread
[Galaxy S III Original Android Development] GR0S:
Visual glitches exist in 10.1, this is not 10.2 issue.
[Galaxy S III Original Android Development] MisterRio:
Wow, this is fast, many thanks.

Flashing now!
[Galaxy S III Original Android Development] FlemishDroid:
I think Focal is not in the rom cause the camera is in the gallery.apk and it looks like "normal" 4.3 camera.

Verstuurd van mijn GT-I9300
[Galaxy S III Original Android Development] guerouig:
Xplodwild is saying expect focal, later today, together with important fixes and a surprise.
[Galaxy S III Original Android Development] bartekxx12:
So... This build still has a lot of bugs, crashes and all of that since it's just been started. BUT, the way it is now is enough to conclude that ALL other mobile OS's are dead... The speed and smoothness is just... :D :D :D
[Galaxy S III Original Android Development] Millenium3:
Yup, that's why is an experimental build.

And please, in discussion thread. ;)

Sent from my 6th phone.

Dreams don't work if you don't do them.
[Galaxy S III Original Android Development] RiverSource:
Is BLE (Bluetooth Smart) working with this build?
[Galaxy S III Original Android Development] troufiniou:
I don't have materials for test it, but I think not, it's too young
[Galaxy S III Original Android Development] NHNXDA:
Has anyone tried 1001 nightly yet?
[Galaxy S III Original Android Development] NHNXDA:
I would like to know if anyone else experienced the call log issues I have please, even with 1001 just out, as this is the only thing stopping me from reinstalling atm.
[Galaxy S III Original Android Development] suntzu123:
use different app.

https://play.google.com/store/apps/details?id=com.idea.backup.smscontacts

This app work for me. I have same problem with some other apps.

You have to restore your old rom, make backup with this program, send to mail, install CM, download from mail, restore.

This is sure a CM bug, and it happen while backup from another ROM, restoring in CM. It should be on "long bug list", but I can't see it.
[Galaxy S III Original Android Development] NHNXDA:
Here you go :)

http://xdaforums.com/showpost.php?p=46072340&postcount=780

---------- Post added at 12:21 PM ---------- Previous post was at 12:14 PM ----------

I've checked the app, but it seems you have to individually backup each system, which is a little annoying as mybackuppro does it a little less painfully lol.

What problems with apps did you have?

What do you mean by send to mail, why would I need to send a backup via email to anyone?

I cant see any mention of this on bug list tbh, tried the IRC channel & nobody responds which tbh isn't very good support, they direct you to the channel but nobody is supporting on there.
[Galaxy S III Original Android Development] suntzu123:
I have a bug...

When I turn on smartphone Voice Action don't work. It's look like don't gent any sound from microphone, after re-tap it get sound and it's fine...

It's really annoying because I used DS Battery Saver so it turn off sync, data etc... It happen each time. But for you all that doen't use this app it will happen one time after boot your phone.

I can't see this bug on bug list. It's realated to 4.3. I tried gapps from 4.2 same problem but on 4.2 everything is fine. Same problem is on Cyberon Voice Commanger so it's related to voice recognize engine

I have NO problem with APPS

1. I have problem with APP-> CM Dialer!

2. What happen? When I scroll down after certain point it FC.

3. When this happen? After restore Call Log from Sammy

4. Why would I send to mail (my mail)? 4.3 Android change mount points compare to sammy 4.1.2, and I can't see original backup file, on mail they are save.
[Galaxy S III Original Android Development] NHNXDA:
Ah yes I see now, it does say Dialler as the system that's causing FC's, so glad its not just me with this issue.

Ah ok I see, you cant access backup file, well I usually plum into my laptop, download the backup files then restore later via sd card as its a fairly large file that would never go over email :)

Does anyone have any experience with CM via the IRC channel, haven't had any response from them whatsoever, is this normal, as I'd like to report this call log restore issue.
[Galaxy S III Original Android Development] NHNXDA:
The issue isn't with being able to restore the log, I can restore the logs no problem, however, if you then go to the call log screen & scroll down, after 2.5 pages of scrolling, it causes a Dialler FC everytime.

It would appear its not solely an issue with mybackuppro, which would indicate it being a CM issue, I do wonder if its because its backed up from 4.2.2 & being restored to 4.3 CM flavour, who knows.
[Galaxy S III Original Android Development] NHNXDA:
I've now flagged it as a possible bug & added to CM's jira system, I'll report back with an update when they do :)
[Galaxy S III Original Android Development] xywojtek:
Installed latest nightly, from recovery, full wipe etc. and problems disappeared. However, when I go to settings > FN Buttons I get FC every time?
[Galaxy S III Original Android Development] NHNXDA:
Ok the call log FC issue is known & there is no fix.

Here's what CM had to say:

"This is an issue with restoring Samsung call logs on CM. Samsung has changed the call log database in an incompatible format by introducing a separate call type for rejected calls. There's not much we can do about it as there's really no way for us to deal with call log DB formats from various vendors which may be incompatible in itself (e.g. HTC incompatible to Samsung)."

So only option is to start call log from fresh.

I do wonder if you went through & deleted any rejected call logs & left others intact, if it would then work, something to test I guess.
[Galaxy S III Original Android Development] kornelius1982:
Can`t confirm that. I didn`t full wipe more than month and didn`t experience any FC on call log.
[Galaxy S III Original Android Development] NHNXDA:
Contact CM, as quoted directly from there Jira reply form.
[Galaxy S III Original Android Development] petrolcan:
OTG cable works.

MHL doesn't. Something to do with Samsung and code and stuff.
[Galaxy S III Original Android Development] suntzu123:
... clear call-log it's not solution. You restore call log to have call log! This happen after restore with some programs.

Buggy CM with no bug list :P
[Galaxy S III Original Android Development] Bei60:
In cm 10.1 I could use hebrew as my interface language with no problems.

Now, when I change to hebrew all the interface is in the wrong side. battery, signal, wifi, etc move to the left side of the screen when they are supposed to stay on the right side.

Same with menus, the button to access quick toggles, any anything really. When will it be fixed?
[Galaxy S III Original Android Development] suntzu123:
Man I read it...

Yes you did not write that this is solution, but you wrote what will help to solve his problem, and what thing have he to do as you to not have this bug... Yes you did write about solution for his problem and yes you did not write word solution.
[Galaxy S III Original Android Development] guhvanoh:
Hebrew is a RTL, hence everything switching sides is not a bug but a feature. Plus you never added a logcat to your post and this is not the support thread.

HTH