yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Original Android Development] tys0n:
In order to flash it to a different device you first have to remove the assert in updater-script, which I don't think he did.

Anyway..Macław is not to blame since it works fine for everyone else.

Did it get interrupted in any way?

..Don't know what else could have happened.

Sent through time and space from my s3mini/CM11
[Galaxy S III Mini Original Android Development] Groot:
You are one conservative type of person, which keeps you away from lags and bloatware :D

Sent from my E151
[Galaxy S III Mini Original Android Development] Allan_Hun:
You are the first person EVER to call me conservative :D

But I guess related to computers and such I am kind of old and conservative, I have learned this the hard way...
[Galaxy S III Mini Original Android Development] Dzombache:
Ok, after more than 7 days of closely monitoring and no freezes, I think the cLock may be just the thing behind the clock freeze bug. I didn't even uninstall it, just removed it and disabled it.

No freezes (at least I didn't notice any) and a dozen alarms that worked just as they should. :)

Tnx to the one who suggested to try this...

Послато са GT-I8190 уз помоћ Тапатока
[Galaxy S III Mini Original Android Development] tickmaster:
Depends how much those devices are different. All S3 minis may use same updater script.
[Galaxy S III Mini Original Android Development] slon11:
Prabobly you woulden't believe but i move to the newest stock firmware and i'm....... Happy :D everything works no FC no freez no problem with BT, so i stay here for time when CM will be fully usefhull for me
[Galaxy S III Mini Original Android Development] koragg97:
Yep. I love the latest stock firmware :)
[Galaxy S III Mini Original Android Development] Allan_Hun:
cLock freeze

Im glad you solved your problem but I don't believe its as simple as you make it sound. I have read A LOT of posts regarding the clock freeze and users seem to fix it in many different ways. I have only personally experienced this bug one time on my phone even though I use clock daily and have tried to provoke the bug be doing the opposite of what users have claimed solved the bug for them. So I am a strong believer that its actually something, probably an app, setting or maybe even our "special hardware", that's not playing nice with cLock and not clock alone. Of course this doesn't matter a lot if people suffering this incompatibility can fix it by removing cLock, but some users have reported that removing cLock and reverting to another app didn't solve their problems. That is why I would REALLY like to know what the true cause of this recurring plague is. With all the users reporting this problem on latest release I guess we will soon find out if its reliably cured by removing cLock.

Would you dare to reinstall clock to test if the clock start freezing again?

Have sony phones with Novathor soc also suffered from this clock freezing bug?
[Galaxy S III Mini Original Android Development] que.no:
My cLock has been disabled for a long time, but today the clock froze again... the alarm goes off, no matter if clock is frozen or not, but only the clock app displays the right time
[Galaxy S III Mini Original Android Development] jaboleq:
WiFi direct

WiFi direct is not working at all. Even I cant change device name.

What about fixing it?
[Galaxy S III Mini Original Android Development] Allan_Hun:
When you say stock does it include samsung touchwiz and all the bloatware? Unrooted?

---------- Post added at 04:48 PM ---------- Previous post was at 04:46 PM ----------

Well as long as the alarm works I could live with that. Its a very weird bug

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

I think you are more than welcome to fix it :rolleyes:
[Galaxy S III Mini Original Android Development] mauam:
Oh yeah! Finally, the battery stats are right now. Thanks NF team & of course TeamExhibit for the fix:cool::good:
[Galaxy S III Mini Original Android Development] DustArma:
What did they exactly fix?
[Galaxy S III Mini Original Android Development] Balino:
Latest updated stuck on s3 mini logo, is it booting for you? Corrupted download?
[Galaxy S III Mini Original Android Development] KoRnFactory:
It boots normally for me.
[Galaxy S III Mini Original Android Development] mauam:
The temperature & voltage are wrongly displayed on CM11 since the first release. Now is fixed thanks to exhibit team:)
[Galaxy S III Mini Original Android Development] Balino:
Re-downloaded and stucked on s3 mini logo yet... Wtf I never had those kind of problem...
[Galaxy S III Mini Original Android Development] mauam:
Have you any script installed when you updated the rom!? Or something different from the other times you update. Anyway, restore your backup from yesterday or so, if you have one:)
[Galaxy S III Mini Original Android Development] Balino:
I'm on omni now eheh I don't use backups, not so many things to restore. :)

---------- Post added at 11:29 PM ---------- Previous post was at 11:28 PM ----------

Always do a clean install, nothing different from other releases
[Galaxy S III Mini Original Android Development] mauam:
So I have nothing to say. Maybe you are switching to much between roms;)

P.S: & without backups!!! You're my hero from now on:laugh:
[Galaxy S III Mini Original Android Development] Balino:
Other Roms and 07 release works fine ;)
[Galaxy S III Mini Original Android Development] Dzombache:
I agree with you. I'm just happy to have found what seems to be the problem on my device.

Btw, I don't think I'm in the clear just yet. Would love to keep monitoring and see if I can survive 10+ days. After that, I'll try with the cLock again. ⌚?

Послато са GT-I8190 уз помоћ Тапатока
[Galaxy S III Mini Original Android Development] ozg33k:
One issue... The mic on my headphones doesn't work. Any way around this?
[Galaxy S III Mini Original Android Development] Ikkuh84:
With 08-04 version Betterbatterystats can't read the partial wake-locks. Before this build it worked, icm Xposed module for reading battery stats. Now it doesn't, with or without the module.

-edit- Stupid, had charger on, so that's why BetterbatteryStats didn't read the right values. Now it works great :)
[Galaxy S III Mini Original Android Development] mahdik.m:
hi. in previews update 06 my battery draining while charging . why ?

im updating now to see it is for rom or not .
[Galaxy S III Mini Original Android Development] Allan_Hun:
Tapatalk reboot

I just had a reboot while using tapatalk. So uninstalled tapatalk, I didn't really like the interface anyway.

I'm updating to 0408 now, hope I won't experience more reboots.
[Galaxy S III Mini Original Android Development] Ikkuh84:
Unfortunatly there are still some reboots/freez of screen.

So the only mayor bugs are:

- Sometimes reboots

- Sometimes screen get stuck on black

- Sometimes he doesn't connect to WIFI, which fixed with a reboot.
[Galaxy S III Mini Original Android Development] Allan_Hun:
Novafusion custom auto upgrade wanted

I just upgraded to 0408 and out of curiosity I timed the optimizing apps process, thats art compiling right?. 102 apps optimized in 7½ minute.

First 100 apps finished in 6½ min. so the last two apps must have been big.

The whole process of updating, incl sys. backup first is rather time consuming, so I think I will begin to upgrade less frequently.

I am aware that I could save time by going back to Dalvic but I don't want that.

It would be nice if novafusion would integrate their own upgrade feature with auto backup, but I guess novafusion is to busy for that.

---------- Post added at 10:00 AM ---------- Previous post was at 09:48 AM ----------

I guess smartphones isn't really designed for daily rom upgrades so im a little worried that it could potentially wearout the cheap flash memory. But i'm also thinking the official CM has a ton of users updating daily without breaking their phones. So have anyone of the many experienced users ever heard of a phone with worn out flash memory?
[Galaxy S III Mini Original Android Development] mahdik.m:
update : problem fixed :p:laugh:
[Galaxy S III Mini Original Android Development] Panderawan:
And an other Clock freeze over here. I'm having one every day around 8-10am. I've tried every proposed solution, but nothing worked. It's like the most annoying bug out there :/ I really hope that our beloved M&M will identify the source of the freezing, and fix it. Deep Sleep mode bug maybe?
[Galaxy S III Mini Original Android Development] Groot:
Flash memory? First time i heard of that, if it's close to flash counters try using chainfire's triangle away app.

Sent from my E151
[Galaxy S III Mini Original Android Development] varianceness:
I was about to say that I don't think there's any wear and tear on flash memory but then I came across these articles:

http://searchsolidstatestorage.techtarget.com/definition/NAND-flash-wear-out

http://en.wikipedia.org/wiki/Flash_memory#Memory_wear

http://spectrum.ieee.org/semiconductors/memory/flash-memory-survives-100-million-cycles

I guess flash memory are commonly rated at 10000 P/E life cycle. Give or take a couple of thousand. So I guess we are safe.
[Galaxy S III Mini Original Android Development] Groot:
Indeed we are, so many years of flashing stuffs and still no issues about it.

Sent from my E151
[Galaxy S III Mini Original Android Development] Allan_Hun:
Risks when flashing daily

Yeah I also think we should be pretty safe.

But then again I think dead usb dongles is rather common. The last few years many SSD manufacturers have increased the over provisioning (spare area) to make drives more reliable. I believe they did this partly because they encountered problems with flash less reliable than rated. And we probably all know that cheap electronics, made in the far east, quite often doesn't last nearly as long as the rating would indicate.

Does phones have flash spare area? I dont know, but i'm guessing even a single dead cluster in the area reserved for rom would be problematic, but this is only my assumption.

So my own conclusion is that flashing roms always include a small risk of some **** going wrong :cowboy:

---------- Post added at 11:30 AM ---------- Previous post was at 11:22 AM ----------

No issues about it? If you talk with someone from samsungs/sony/htc rma department Im pretty sure they would disagree about that...

Of Course most bricked devices come from people who simply doesnt know what they are doing when flashing, but not always.
[Galaxy S III Mini Original Android Development] padlockedtight:
Interesting but your more than likely to drop your phone down the toilet or something long before the Flash memory goes so not worth a second thought!:laugh:

Okay Guys so who's stuck with sio scheduler and who's gone back to noop?

Anyone still getting battery drain with latest update?
[Galaxy S III Mini Original Android Development] koragg97:
yes, it includes TouchWiz, but no bloatware and it's rooted with chainfire's SuperSU :) I'm using the S5StyledANA2 v1 ROM from [MENTION=4394833]galaxy mini[/MENTION] also i've got a lot of xposed tweaks (DVFS Disabler module really helps a lot in performance)
[Galaxy S III Mini Original Android Development] padlockedtight:
Interactive Guvernor

I found this useful post on our default Governor and preferred settings;)

http://xdaforums.com/showthread.php?t=2649820
[Galaxy S III Mini Original Android Development] prototype74:
I don't know if someone asked it already but why is SELinux disabled?
[Galaxy S III Mini Original Android Development] Allan_Hun:
But disabling dvfs eats battery right? Is it really worth it for someone like me who doesnt game and cares a lot about battery life?

---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------

I think its because when maclaw tried to enable selinux it didn't work.
[Galaxy S III Mini Original Android Development] Groot:
If and only if they do anything stupid, but are there common and re-occuring issues? No right? Simply because people are capable of adapting to a certain knowledge on how to do things with safety precautions, with hundreds of how-tos in the internet. My point is why bother for something that is not THAT threatening? The s3 mini won't last for like a century anyways, sorry for the off topic anyways

Sent from my E151

---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------

Not trying to be sarcastic but the answer you are seeking is in your statement itself, why bother disabling the dvfs when you care a lot about battery life?

Sent from my E151
[Galaxy S III Mini Original Android Development] scattoit:
Very good rom! My only trouble is BT.
[Galaxy S III Mini Original Android Development] Allan_Hun:
Interesting but the source you link seems to mainly focus on how to get a snappy phone, without any real world test of battery life.

I personally don't mind if I have to wait 3ms vs 5ms when press something simple like a setting, if I did care much about a snappy interface I would not have purchased a dual core 1Ghz s3 mini!

Like a lot of normal android users my main concern is battery life, but I also hate to wait what feels like an eternity just to load a web page!

I have thought about trying a more conservative governor because my phone seems to jump to 1Ghz even when there is no obvious reason for that.

It quickly returns to 200mhz so its only short bursts but I know max cpu speed consume a lot of energy, so I would rather my phone stayed at like 600-800mhz when its only syncing or what ever its doing when i'm not using it.

Can I limited my phone to 600mhz when the screen is off and then automaticly remove this limit when the screen is on?

---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------

Balino doesn't look very intelligent trying to show muscles in a tight white T Shirt, but his comments doesnt seem stupid. Didn't he just brick his phone?

---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------

Well I dont have any experince with dvfs but have read somewhere that fast speed to idle can help battery performance, thats why I asked.
[Galaxy S III Mini Original Android Development] Groot:
At least we could've considered some side issues like bad downloads or something, but if it must be the flash thingy, i can agree with you mate, he flashes rom almost every day and we can't blame him for that :laugh:

Sent from my E151

---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------

I stand corrected, i sure would like to know about dvfs too and it's impact on our s3 mini.

Sent from my E151

---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------

Hey allan, so i read about the dvfs via xposed framework, it's basically TouchWiz affiliated so i don't think it has something to do with aosp/cm roms. :)

Sent from my E151
[Galaxy S III Mini Original Android Development] Panderawan:
And an other clock freeze, 2nd one today. It's driving me crazyyyy :mad:

I wish Mauam had one of his magic solutions for this one :eek:
[Galaxy S III Mini Original Android Development] padlockedtight:
Okay, first and foremost. personal attacks on another members appereance isn't cool and remarks like that aren't positive and don't help anyone.

Secondly while I agree that all users want great performance at little cost to the battery a conservative Governor can cause thrashing when surfing the net and playing games etc so whilst you get great battery, performance suffers.

I can always recharge my phone and use a deep sleep battery saver or tweak to compensate for the great performance. it's harder imho to do it the other way round.
[Galaxy S III Mini Original Android Development] Allan_Hun:
Sorry if my comment about the tshirt was out of line, I don't want to attack anyone just couldn't resist.I guess I was jealous because i'm a skinny guy with no muscles to show.

Im not trying to argue that flashing is dangerous because it will wear the flash memory out, but if you can't agree there is always a slight risk of something going wrong when you flash a phone, I think you just need to experience a bad flash your selv. No it doesnt only happen to stupid persons, thats a faulty generalisation no better than my tshirt comment. Typical warnings like don't blame the developer if your house catch fire, is there because there is a small risk right?
[Galaxy S III Mini Original Android Development] Groot:
I concur. Still users should be aware and should be ready always because some things are inevitable.

Sent from my E151
[Galaxy S III Mini Original Android Development] mauam:
To enable SELinux, you can use SELinuxModeChanger, works just fine. Anyway, don't blame me nor the dev, if you screw up your phone, so make a Nbackup before start playing with that stuff. Have fun:)
[Galaxy S III Mini Original Android Development] padlockedtight:
No worries Buddy;)

Just try and remember that we are ALL here because we love Xda, sharing knowledge and helping others.

regarding bad experiences. When I was a noob ( well, more noobier than I am now:p) I tried flashing an CWM kernel through twrp and hardbricked my 2 month old £250 phone! So yes, I also have learned the hard way:D

There's always a risk regardless of human error like you say. that;s why now whenever I buy a phone, tablet, whatever (& I know I just can't resist playing around with the inside) the very next thing I do... IS BUY FULL INSURANCE ! There's also this little Gem..

http://www.ifixit.com/
[Galaxy S III Mini Original Android Development] factorexh:
i just bought a otg cable. and give some movies to my friend via usb disc:) it works perfect. got 04.09 release and everything is fine. its stable for daily use no doubt. but that notification sound issue is annoying :good:

i hope r you guys find out how to disable output voltage after unplug otg cable:)

Sent from my GT-I8190
[Galaxy S III Mini Original Android Development] prototype74:
Thanks :D
[Galaxy S III Mini Original Android Development] Balino:
??? No, i didn't brick my phone.

I don't understand what are you talking about!

Anyway downloaded for the third time 08 release but IT doesn't boot.

I don't get where the problem is...?!
[Galaxy S III Mini Original Android Development] koragg97:
well, i personally haven't experienced any huge battery drain after disabling DVFS, BUT my games run much smoother now.

I can suggest that you try it with DVFS Disabled for a couple of days and if it drains too much battery for your needs, you can always re-enable it via the DVFS Disabler app (requires reboot to apply changes) :)

my battery lasts from 15 to 20 hours on one charge with medium usage with DVFS Disable (it was something like that when it was enabled too).
[Galaxy S III Mini Original Android Development] Allan_Hun:
Like I have always said: Real men don't backup -But we do cry when our harddrives fail...
[Galaxy S III Mini Original Android Development] koragg97:
:D your post just made my day :D
[Galaxy S III Mini Original Android Development] padlockedtight:
Hey Balino:)

Are you installing via TWRP or Odin?

I know some peeps have had trouble with Odin install method.

If it is indeed TWRP, Clean install?

post edited

If you've downloaded it 3 times it can't be a corrupted or interuppted file.

Last resort is go back to latest stock firmware and then try flashing 08 release from there.

Good Luck!
[Galaxy S III Mini Original Android Development] Allan_Hun:
Sharing backup?

I have been thinking a lot about this bug that seems very random and affect so many users.

I don't experience this bug so if you have exactly the same model phone, plain I8190, I could make a complete backup of my phone and share it with you so you can restore my backup. I'm not sure it will help but I do think its worth a try?

Or am I overlooking something that makes this impossible?

---------- Post added at 05:08 PM ---------- Previous post was at 04:57 PM ----------

-And some people get the clock freeze bug.

So far 0408 runs perfect on my phone. I'm going to test BT in my car later today.

Am I the only one who can't make the sort apps by Launch Count setting stick?

I think its a Trebuchet related problem. It has been nagging me since I first moved from stock to Maclaws rom.

---------- Post added at 05:44 PM ---------- Previous post was at 05:08 PM ----------

Personally I believe flashing with twrp is safer than flashing via Odin, because it eliminate the pc as a source of errors.

Windows isn't known for its great security, your pc might be unstable and there is also usb drivers involved.

But the inconsistent behavior I experienced flashing with twrp the other day has forced me to reconsider this.

So Balino please forgive my childish behavior and share details about your flash troubles, if don't mind and have got time for it.
[Galaxy S III Mini Original Android Development] webgringo:
The 20140408 version still have the BT crash bug.

Seems like it happens more after short calls. Thing is, still works to send info to display of car stereo, but after crash it wont send sound. Turning BT on and off wont solve it, to get sound the only fix i found is to reboot phone.
[Galaxy S III Mini Original Android Development] Balino:
Version 09 works fine :)
[Galaxy S III Mini Original Android Development] padlockedtight:
Pleased to hear it:)

Did you get to the bottom of why 08 wouldn't work for you?

By the way peeps...

That CM11 Theme Neon Colors is freakin Sick!!
[Galaxy S III Mini Original Android Development] scattoit:
I agree. BT for music only is perfect. When I start a voice call my BT on car make a sound like when the phone try to connect to it. Then, after the call too. In the end often BT crashes. BT is very important in my life ;)

No other bug on my phone now.
[Galaxy S III Mini Original Android Development] Allan_Hun:
My father wants me to update his s3 mini, I think this would be perfect for him, he only use his smartphone for talking and sms :laugh:

---------- Post added at 01:12 AM ---------- Previous post was at 01:09 AM ----------

Yeah I also got the BT crash today, but after the crash my headunit still displays my phones battery status...

New stable realease sure sounds nice, will try it asap.

---------- Post added at 01:32 AM ---------- Previous post was at 01:12 AM ----------

I prefer the google keyboard, but would really like it to show the small numbers on top like the AOSP keyboard. Is this possible?
[Galaxy S III Mini Original Android Development] Groot:
There's a modded Google keyboard with numbers on top row at the Android development section matey

Sent from my E151
[Galaxy S III Mini Original Android Development] Balino:
No, it just didn't boot :confused::confused:
[Galaxy S III Mini Original Android Development] padlockedtight:
Can someone please tell me (hopefully Maclaw) if Marcin is still working on this ROM?

I notice he's working on something else entirely which is great but does it mean we're gonna go back to this.

CM SOURCES UPDATE.

STABLE RELEASE.

I Bloomin well hope not!!!

sent from the tips of me fingers!

please hit thanks if someone helps.
[Galaxy S III Mini Original Android Development] Allan_Hun:
Thank you for answering my question. I found the modded google keyboard with the extra row on top, but thats is not what I want.

Would really love a google keyboard v3 with small numbers displayed on the Q,W,E,R,T,Y,U,I,O and P keys just like the AOSP keyboard.

In the attached picture I have marked what I want in the blue "circle"

If it's somehow possible to use the Danish spellcheck and next word prediction from Google keyboard v3 on AOSP keyboard that would also satisfy me.
[Galaxy S III Mini Original Android Development] cmgonzalez:
20140409 is working sweet, even on ART!

Great Job, i haven't found a single complain yet.

The only missing thing is FM (i know about spirit), but the native CM FM app will be great.
[Galaxy S III Mini Original Android Development] vytorhugo:
I can not leave the mobile phone network in 3g only. she is switching back and forth between 3g and 2g sometimes
[Galaxy S III Mini Original Android Development] dreamH6:
try to flash with odin instead of TWRP last release. Keys do no work yet.