yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Original Android Development] c1b3rz:
Because he is accountable for what he says. And he can and will only assure that it works on that one.

With other recoveries it may or may not work. But then you're on your own.

Get it?
[Galaxy S III Mini Original Android Development] need4steer:
Yep.

And what about my issue?

Why do you think I'm getting <OSM> All threads completed. (succeed 0 / failed 1) in ODIN3 when I'm trying flashing the tar.md5 file as PDA?

Do you think I should root or flash that recovery before?
[Galaxy S III Mini Original Android Development] c1b3rz:
Dude, I really don't know.

Some people advice you to have KIES installed in order to have all the necessary files for win/android communication.

Also try with the recommended recovery.

If none of that works, you bring this back here and I'm sure someone with more knowledge than me will be able to help you :)
[Galaxy S III Mini Original Android Development] guidosl:
work perfect!

thanks!
[Galaxy S III Mini Original Android Development] bePig:
Can anyone check if it still does the brrrrrrr sound?
[Galaxy S III Mini Original Android Development] Clostry:
Anyways this is a forum about development bugs/features etc., if you really need help you may ask in this board http://xdaforums.com/galaxy-s3-mini/help ... ;)
[Galaxy S III Mini Original Android Development] need4steer:
I didn't installed KIES yet, and to be honest, I'm not intending to if I don't really need it.

I'll probably try the recommended recovery before.

Thanks a lot for your suggestions.

Are you sure it's not a bug?

Maybe there are other people who are having the same problem? Maybe there is a problem with the tar.md5 file?

It's a problem regarding this ROM, and not other, so I really don't understand your suggestion, at least not completely.
[Galaxy S III Mini Original Android Development] cybernight:
To flash with odin, everything you need is on download site. Odin, usb drivers and rom (kitkat or other)

No need for root or recovery, only download mode (vol- + Home + Power)

USB 3 doors, some cables and windows 8 can give you problems with comunication to mobile and it will give you an error like the one you explained.
[Galaxy S III Mini Original Android Development] need4steer:
Thanks a lot for your suggestions!

I have most of the stuff from Maclaw Studio site, and what I don't have from there, I make sure to have the same md5 and sha-1 values - what means it's the same.

I have Windows 7 Ultimate Service Pack 1 64-bit.

I'll update my original post with this information to make it more clear.

BTW, what do you mean by "USB3 doors"?
[Galaxy S III Mini Original Android Development] cybernight:
ADB comunication with the android device has some problems with usb3 drivers. I had problems flashing Samsung S III mini, Sony Xperia Go, Samsung Galaxy S and BQ Edison tablet in usb3

What happens is that Odin can't comunicate correctly with the mobile phone, and the flash operation doesn't get completed.

Sorry all, I know this isn't the place to discuss this issues
[Galaxy S III Mini Original Android Development] lexihel:
And you might also want, if you're using a desktop computer, to ignore front usb ports or usb hubs and aim directly to your motherboard's own USB ports behind, sometimes (it has happened to me a lot), the usb hubs or ports in front of the case simply don't work. Motherboard's ones work everytime
[Galaxy S III Mini Original Android Development] need4steer:
Thanks a lot for your explanation.

I'm using USB 2 ports, and I tried different USB 2 and USB 3 ports, so I believe that at least it's not a USB port problem.

Thanks a lot for this tip.

I'm aware to this issue, and therefore I'm doing this myself.

However I'll update this in my original post so it'll be clear.
[Galaxy S III Mini Original Android Development] Clostry:
Really guys.... This is not a Odin troubleshooting thread. If every person having problem flashing this ROM with Odin ask for help here this thread will be unreadable.
[Galaxy S III Mini Original Android Development] need4steer:
Why are you so sure it's an ODIN3 problem and not a file problem?

Is it working for other users? If so - then it's only my problem, and I'll try to solve it.

If not - maybe there's an issue that should be fixed.

If you'll search in this forums and in Google, you'll see that there are a lot of cases in which the file that was inserted into ODIN3 was bad, and that was the reason to this exact error: <OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy S III Mini Original Android Development] jnicaragua:
I just update to 20140204

Issues: I did a dirty update and start having problems with the data and wifi connections, and with the playstore app (the app keep asking which of google accounts wanto to use) i tried to fix those 1. erasing the apn and put it in again 2. erasing the data/cache of playstore; none of that works

is kind of sad that the brrrrrrrrr sound in some app still exist...

As i dont have the patience to find what the problem was; just did a full wipe and is ok.

P.d trebuchet as a small bug, when u mmm press the desk to find options (widgets, wallpaper, options) the desk go "back" and those options appear but the problem is that appear in the middle (not in the usual bottom) and is kind of uncomfortable to use.
[Galaxy S III Mini Original Android Development] need4steer:
Please note that 20140205 was releases a few hours ago.

Maybe you should try it.

Please post back if this issue continues so other will know and so that developers will consider if and how to fix it.
[Galaxy S III Mini Original Android Development] cvkef:
Flashed it but didn't help. Still no GPS for me. Thank you for your help!
[Galaxy S III Mini Original Android Development] jnicaragua:
[Q] How to Update CM?

---

So, i probably did something wrong?

I just went to the recovery (TWPR) and install the zip file.

And that was the "correct" way to do it ...

Do i have to perform a wipe? data wipe maybe?

*Downloading 20140205
[Galaxy S III Mini Original Android Development] need4steer:
I'm not sure if you did something wrong, but if I was you I would've perform at least a data wipe.
[Galaxy S III Mini Original Android Development] need4steer:
My issue was solved by simply flashing the newer version that was released today

My issue, the <OSM> All threads completed. (succeed 0 / failed 1) error in ODIN3, was solved by simply flashing the newer version, 20140205, that was released today.

So apparently the previous tar.md5 (20140204) wasn't flashable via ODIN3 for me (and, most probably, for everybody).

To sum it, we can easily install ROMs in ODIN3 with simply flashing the tar.md5 file which will install, in addition to the ROM, custom recovery (MaclawStudio's TWRP 2.6.3.0), and it'll root the device (the ROM is rooted).

Thanks a lot for everyone for the great tips and suggestions that was given, and especially thanks a lot to New Macław for his great contribution and for his awesome effort.
[Galaxy S III Mini Original Android Development] Kevinjs:
Is there any news on the suprise?
[Galaxy S III Mini Original Android Development] albertusac:
yeah, there's no unfortunately :crying:
[Galaxy S III Mini Original Android Development] need4steer:
Issues with version 20140205

I have the following issues with version 20140205:

I'm getting "trebuchet has stopped working" on the first boot after a fresh install

The location settings aren't saved, so anytime I use location it asks if I want to allow Google to use my location.

I can't play wmv or wma files - what causes the gallery not to show these videos and songs, and to the sound settings not to show these files.

I need to download an app to play them, and to convert wma songs to mp3 in order to use them as ringtones.

The data connection is extremely slow. When I'm using Google Play I often get an error about the connectivity. In WiFi, though, everything is okay.

These issues are also documented by other users in the comments section of the ROMs post in Maclaw Studio website.
[Galaxy S III Mini Original Android Development] Balino:
Mmmm didn't test ringtones, but I had none of those problems.

Trebuchet screwed up my google search widget
[Galaxy S III Mini Original Android Development] Balino:
Working fine with google home
[Galaxy S III Mini Original Android Development] schrickz:
Spended 4 gb of data but still can't download any single 173 mb of ROM from MaclawStudio ..
[Galaxy S III Mini Original Android Development] xAbsoLx:
Go trebuchet launcher config via config/main page/config (trebuchet), homescreen/searchbar turn it off then turn it on again & it will work my issue is... trebuchet go 4x5 & i like 5x5 :/
[Galaxy S III Mini Original Android Development] Axaion:
Unable to get into trebuchet config here, looks like launcher3 with no settings, when I tap the menu button or hold down a tap on the home page I just get the normal settings with about phone display sound and so on

Had this issue since the change to trebuchet

Done full wipes every time even formatted internal sd card

(I always get trebuchet has stopped working on fresh install the first boot)
[Galaxy S III Mini Original Android Development] Bodo_1:
Carbon dead??
[Galaxy S III Mini Original Android Development] ztandroid:
Go to Settings>Home>Settings (trebuchet checked).

I also get something wired when first boot my phone shut down immediately..trebuchet bug? I doubt it..
[Galaxy S III Mini Original Android Development] tom1491:
Hey. Anyone here faces a problem with airplane mode? When switching it off and then on, the phone signal won't get back. It's empty and needs a reboot to fix the problem
[Galaxy S III Mini Original Android Development] cvkef:
Well I'm getting something similar to that but with no Airplane mode.

From times to times the phone signal drops totally. And nothing but a reboot can restore it.
[Galaxy S III Mini Original Android Development] jaboleq:
Clock bug is the worst.

Maclaw please fix it :)

Wysłane z mojego GT-I8190
[Galaxy S III Mini Original Android Development] kanjac:
I really do not know what you're doing with these phones? For me everything is working awesome! The only problem is the video uploaded on instagram ...
[Galaxy S III Mini Original Android Development] Fred6681:
I do not have not at all more, just the normal parameters
[Galaxy S III Mini Original Android Development] MitsG7:
You should have this option....on personalization the first option..when you press it you should find two launchers..

Στάλθηκε από το GT-I8190 μου χρησιμοποιώντας Tapatalk
[Galaxy S III Mini Original Android Development] Fred6681:
No, i have not installed Google launcher. This ils probably why i can not fond the settings trebuchet

I understand now, thanks
[Galaxy S III Mini Original Android Development] MitsG7:
Wich version are you using??

Στάλθηκε από το GT-I8190 μου χρησιμοποιώντας Tapatalk
[Galaxy S III Mini Original Android Development] deskSX:
if the clockfreeze bug is no "rombase" bug, whers it come from?

I installed last CM, unchecked sync, uninstalled cLock - clock stopped at night.

Only way the clock doesnt freeze is (no matter sync on or off) is to keep WLAN on.

Any idea?
[Galaxy S III Mini Original Android Development] Fred6681:
The last with my GApps them not to googlehome in, no need to duplicate.

too bad for the trebuchet settings they will come with time
[Galaxy S III Mini Original Android Development] Pangadaywalker:
Not sure if this is carrier or something in the ROM but I am facing some issues with SMS. I try to send one and it won't go. I wait a bit and try again the same message then it goes. It is becoming more and more frequent.

My wife uses the same carrier without this issue, so I believe it might be something in the ROM causing this.
[Galaxy S III Mini Original Android Development] need4steer:
I'm getting "trebuchet has stopped working" on the first boot after a fresh install too.

What about

"trebuchet has stopped working" on the first boot after a fresh install

The location settings aren't saved

can't play wmv or wma files

The data connection is extremely slow

You don't have any of these issues?
[Galaxy S III Mini Original Android Development] Fred6681:
Can be GApps ?

http://xdaforums.com/showthread.php?t=2604991&p=50014634
[Galaxy S III Mini Original Android Development] Axaion:
No such setting

I don't even use GApps
[Galaxy S III Mini Original Android Development] Fred6681:
So, if you want the settings trebuchet must install a second launcher
[Galaxy S III Mini Original Android Development] apriores:
Launch Settings from App Drawer, not from Menu button.

Edit:

Ups, I might miss understood about your issue... :P
[Galaxy S III Mini Original Android Development] deskSX:
nope, using Zgapps. problem is not the alarm or any widget, its the system time freezing.
[Galaxy S III Mini Original Android Development] Bodo_1:
Loundness bug here
[Galaxy S III Mini Original Android Development] caiiostylle:
In version 4.3.1 there is the option to move app to memory card, this summer will be no more 4.4.2 this option does?
[Galaxy S III Mini Original Android Development] lexihel:
I don't know what language you are using or what SMS app but I'll give you a tip that solved that problem to me when I faced it several versions behind: SMS structure is built around Unicode characters, if you use any non standard characters SMS app will go nuts, from counting one message as five different ones, to not sending the SMS at all. So:

In native SMS app and in 8SMS, hit Menu/Settings while you're in inbox.

Scroll Down until you see an option that reads something like: "Strip Unicode in SMS" or something silimar or relative in your language. Tap there...

Tap Strip Unsupported characters.

Retry...

Of course, I'm talking about a problem where non standard charsets are used (my mother tongue is Spanish so we use those a lot)... If that's your case maybe it could work. :)
[Galaxy S III Mini Original Android Development] Fat Cookies:
Could someone (preferably one of the developers) enlighten me on the situation with adding NFC support for the GT-I8190N? What is preventing it happening, is it the lack of knowledge of the NFC hardware, is the software just not there, is it simply not a priority to get it implemented?

Thanks in advance.
[Galaxy S III Mini Original Android Development] AssToast:
Missing sources are causing developers to get a working code and its also not a priority
[Galaxy S III Mini Original Android Development] evildog1:
try install Go SMS pro and it should work.
[Galaxy S III Mini Original Android Development] jnicaragua:
Hello!!

Using 201401205

Issues:

1. Problems with trebuchet: suddenly and randoms stops. The launcher dont let to configure/access to options. --> stay with "selector"

2. The clock suddenly stop, i have try: 1. uncheck the automatic system (red and time zone) 2. check the automatic xD . Im using Aroma Gaaps (Maclaws ver).

3. The direct Wifi is not working

4. High consumption of battery

5. The "auto brightness" is not working ( ...or have never work )

6. The Sound issue still there! even when in the CM11 (official) is solved.

7. Cant unistall Trebuchet! :/ not even with a root app.
[Galaxy S III Mini Original Android Development] PTGamer:
restore a backup with a previous stable version. a lot of users are having problems with trebuchet. or wait for todays release to see if it fix those problems

anyway

you can remove trebuchet by browsing to your phones memory system apps and them removing the trebuchet apk
[Galaxy S III Mini Original Android Development] GXGOW:
I don't get why so many users are using Trebuchet. It's, like, the worst part of CyanogenMod and it's still way too buggy at the moment. Just wait and use another launcher in the meantime.

That is, at least, my advise and opinion.
[Galaxy S III Mini Original Android Development] asyba:
Maclaw can you add the new gallery beta from Cyanomod ?
[Galaxy S III Mini Original Android Development] ztandroid:
Never ask about auto brightness, it's hardware limitation.

You can simply delete trebuchet.apk from its directory, check your explorer capability to do root things.
[Galaxy S III Mini Original Android Development] deskSX:
Its not a matter of fev'-05 build, have it on many others (and currentl on fev-04). exactly the same, two different times and both of them are not the proper one :crying:,,,, also unsynced time/zone, zgapps/uninstalled cLock.

I hope once will be realized, thats not a configuration problem.
[Galaxy S III Mini Original Android Development] Pangadaywalker:
Foun options:

- Remove characters not possible to code

- Remove all unicode characters

Which one do you refer? 1st or 2nd option?

And I am from Brasil. :) Portuguese is my ML.

Thansk, will give it try.

Will the message arrive properly to read?
[Galaxy S III Mini Original Android Development] lexihel:
I would try both... I use "Remove characters not possible to code" but again, results may vary.

Select that first and try... If fails, select the second and retry... If it fails again then we have to look somewhere else.
[Galaxy S III Mini Original Android Development] PTGamer:
yes, i will explain the process to you in portuguese check you inbox (PM)
[Galaxy S III Mini Original Android Development] Fat Cookies:
It's a shame I'm not confident with low-level programming or I'd happily have a nose around and try to implement it myself! Yes it's not a core feature, however Card Host Emulation sound very appealing and is now trivial with any NFC enabled phones running KitKat, that's the reason I'm interested.

The question is probably more aimed at Benzonat0r, whom as far I know used to create some NFC ROMs but they suffered from problems.
[Galaxy S III Mini Original Android Development] jnicaragua:
I really hate that launcher, gonna erase it ...

x2 ...

Not gonna use an other launcher, will keep "selector" ... but thanks :)

Not true, in the AOKP and Slim you can use it.

Im gonna check that, thanks
[Galaxy S III Mini Original Android Development] jnicaragua:
Hey men!,

Well, that is the point; why keep something that is soooo unstable in a rom that is getting better and better.

Today at morning I just update via odin (never again...) to 20140206

The trebuchet gives problems even when u use the cm launcher ( selector ? ); for example early today i wasnt using any launcher and puff something went wrong and trebuchet appear! O.o ... try to change and nothing ... -> restart the phone, back with no launcher.

So thinking in future i just uninstalled it, via link2sd. -> trebuchet -> actions -> turn into user app -> delete app *have to be done with the last version.

Since i did that i have no problems, even not reboot charging via usb or clock problems ... fault of the laucher? dont know; but since i deleted it the ROM is smoothly and working fine (audio bug still a pain in the ass but other few things went from bad to stable).

note: I also use aroma - maclaw gapps.
[Galaxy S III Mini Original Android Development] Fred6681:
If trebuchet and removed by Maclaw, it will be more cyanogenmod but a fork and therefore no longer able to be called CyanogenMod
[Galaxy S III Mini Original Android Development] AssToast:
I dont see the reason in removing trebuchet

1. You have root permissions, you can delete anything you want from your device

2. You can download another launcher and set it as default

3. Trebuchet is included in CM sources

4. Stop whining for gods sake
[Galaxy S III Mini Original Android Development] honeyx:
Belive me he got told about this but didn´t change his mind about it. And when you ask for fixing the exising bugs you will get always the same answer. (It´s because they are missing some NovaThor sources and because the sources are closed and because Mali doesn´t like their sourcecode to be published)

Just the Sony guys who are developing for their NovaThor devices are keeping their CM sources open and are not trying to tell the whole ROM exists only by a few closed Mail GPU drivers.

I bet the bugs over there in the Sony section will get fixed sooner because those guys are keeping their CM sources open so more people can watch the code and suggest some fixes. Noone is expecting them to publish the closed source drivers, but they are doing it the right way. Everything else which is not closed source is kept open source, so the more ppl can watch the code the sooner the bugs can be found and fixed.

I for myself did a simple test. Modified the kernel a bit, recompiled it and all the sound and notification isssues I was having are gone now though someone here wanted me and the others to belive this is because of the missing sources and (buggy) drivers.
[Galaxy S III Mini Original Android Development] grinder777:
Would you mind to publish that kernel? Would be nice... maybe you could fix this issue that alarm is not waking up the phone too. I'm pretty sure it's kernel related...

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Original Android Development] Laserman49:
I had general freezes, not only clock, when I tried to unlock my phone, it was completely freeze, I had only one thing that worked, push the On/Off button until 10 s to shutdown and restard the phone.

It was the only times, and I flash the new ROMS every day. And at every Flash, I make Wipe Dalvyk/Cache.
[Galaxy S III Mini Original Android Development] honeyx:
Not yet as this kernel was just a try and it´s sometimes tearing on scrolling. But thats the only little issue I´m having with it. Just to publish a custom Kernel I need to fix this first and for this I need to set up Linux completely new as I replaced meanwhile my PC against a more powerful one.
[Galaxy S III Mini Original Android Development] Fred6681:
I'm pretty sure it is not related to CyanogenMod or kernel, my alarm rings 2 times a day and I've never had this problem.

If the clock freeze my alarm does not sound like some one reported

Why does not do it to everyone if it was really right ?

look here --> http://xdaforums.com/showthread.php?t=2604991&p=50014634
[Galaxy S III Mini Original Android Development] grinder777:
First of all, I'm at 0204 build and I'm using green power to disconnect all data connection when screen is off.

My clock was never frozen, in earlier builds also never.

The issue I have is that my alarm is not always working. Sometimes it does, sometimes not. When it didn't and I turn on the phone after, it starts alarming or tells in notification that alarm was missed.

So IMO the alarm could or would work, but it is not able to wake up the phone. It seems to be related to the sleep state of the CPU and that should be kernel related. I have had this at carbon as well as in AOKP. Different ROMs, same kernel...

Why are you sure it is not kernel related?

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Original Android Development] Fred6681:
Because there are only a few who were perssone this problem

The kernel is the same since at least December and I think it is the same for all Roms android 4,x of Maclaw (someone confirm?)

Why in the other it does not ?
[Galaxy S III Mini Original Android Development] grinder777:
Maybe some people have some apps running that keep the phone alive all time..? Some message apps perhaps, email sync... or something else.

That's all off in my case - no sync, no email, no Facebook... when screen is off, phone sleeps, completely. But alarm should wake it up. At this configuration I've never had any trouble with SGS on all ROMs I used up to 4.4.1...

Gesendet von meinem GT-I8190 mit Tapatalk 2