yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Original Android Development] :
OmniROM only supports TWRP.
[Galaxy S III Mini Original Android Development] golden-guy:
Yeah, there's plenty of 2.6.3+ versions around here, either as flashable zips (for CWM) or both .tar.md5 (Odin) and .img (Heimdall) You can find an .img version in my downloads folder as well.
[Galaxy S III Mini Original Android Development] wreckler:
Hi Golden, great Rom!! Big Ups!!:good::good:

one little problem....i cant remove system-apps(like Email, Apollo, etc)....i flashed the superSu which you had posted, after then i can´t find some SuperSu @ my phone...what can i do? it seems there no root anymore after flashing Omni

Greets from south Germany!
[Galaxy S III Mini Original Android Development] :
If you flashed SuperSU, then you should be rooted. Go to settings, and you should notice SuperSU as the third last option. If it's not there, then you need to reflash SuperSU in recovery again. After doing so, obtain a root delete app (such as Titanium backup, or just search for "root delete" and choose an app) and you should be able to delete the system apps, I believe. Although I highly recommend making a backup in TWRP before you do so, just in case you delete the wrong app! Though I don't understand why you would want to? It's debloated, and is pretty bare, and doesn't take up too much space.
[Galaxy S III Mini Original Android Development] wreckler:
allright, thanks a lot, everything is right!!:good:
[Galaxy S III Mini Original Android Development] :
golden-guy, exothermic and all the ppl. involved in this:

thanks for the work!

I got it built from source and it is running good. Did not had any longer test though.

To flash my build I had to flash maclaw 2.7.0.0 twrp first.

The twrp which is included in the omnirom sources is still 2.6.3.0 which is NOT working when someone tries to flash a custom build of omnirom.

Anyway, just waiting for the camera fix now ;)

golden-guy, keep up the good work.
[Galaxy S III Mini Original Android Development] wreckler:
I got a little issue with my BL in my car....can't hear anything, and my phonepartner can't hear me....
[Galaxy S III Mini Original Android Development] LMH1998:
Overview

So I've been using this rom for 2 days which is enough to tell you my exprience.

The good thing about this rom is that it doesn't random reboot like on CM11.

The ROM is been really smooth and very fast so great performance!

The battery is been good too, better then I expected!

As you can see on the first picture, that's a day of really not heavy usage.

On the second picture, I used it pretty heavely.

I do use Greenify to hibernated some apps to get more free RAM. I get around 350-450MB of free ram.

I'm really hoping that video recording would be fixed soon so the ROM would be perfect!

I will be reviewing this rom on Youtube, which would be soon.

Make sure you subscribe already!

https://www.youtube.com/user/BelgiumTechVideos

You did a really good job golden-guy!
[Galaxy S III Mini Original Android Development] golden-guy:
Thanks alot for this review mate, and yeah fully agree, things like video rec definitely have to be sorted out. Video review sounds great - looking forward! :)
[Galaxy S III Mini Original Android Development] Bodo_1:
Golden-Guy you are my favorit
[Galaxy S III Mini Original Android Development] :
BUG: Volume down button

EDIT:

Problem solved. Seems it had something to do with the gapps-package I used. Reflashed it and the volume button problem is gone.

There seems to be a bug with the volume down button.

It is not possible to complete mute the phone by pressing the volume down button. I can lower the sound to the lowest value but it does not switch to vibration and mute. Or am I wrong and this is not supposed to work? In CM11 it is working this way.

Btw: I've set the button to ringer but that does not do the trick so I think it's a bug.

The LogCat output while pressing the volume-down button in the home screen from highest volume to lowest:

03-21 16:22:25.944: I/sec_anm_ahi(27722): adm_api: ste_adm_client_set_cscall_downstream_volume(4)
03-21 16:22:25.944: I/ADM(1678): 4: 9805162326: [INFO] api_cscall:2111 csapi_set_downstream_volume: volume = 4
03-21 16:22:25.944: I/ADM(1678): 6: 9805162418: [INFO] api_cscall:2020 csapi_apply_vc_vol_mute: Not connected
03-21 16:22:27.005: I/sec_anm_ahi(27722): adm_api: ste_adm_client_set_cscall_downstream_volume(3)
03-21 16:22:27.005: I/ADM(1678): 5: 9806227908: [INFO] api_cscall:2111 csapi_set_downstream_volume: volume = 3
03-21 16:22:27.005: I/ADM(1678): 9: 9806228153: [INFO] api_cscall:2020 csapi_apply_vc_vol_mute: Not connected
03-21 16:22:28.367: I/sec_anm_ahi(27722): adm_api: ste_adm_client_set_cscall_downstream_volume(2)
03-21 16:22:28.367: I/ADM(1678): 4: 9807588107: [INFO] api_cscall:2111 csapi_set_downstream_volume: volume = 2
03-21 16:22:28.367: I/ADM(1678): 9: 9807588382: [INFO] api_cscall:2020 csapi_apply_vc_vol_mute: Not connected
03-21 16:22:30.398: I/sec_anm_ahi(27722): adm_api: ste_adm_client_set_cscall_downstream_volume(1)
03-21 16:22:30.398: I/ADM(1678): 8: 9809616641: [INFO] api_cscall:2111 csapi_set_downstream_volume: volume = 1
03-21 16:22:30.398: I/ADM(1678): 3: 9809616916: [INFO] api_cscall:2020 csapi_apply_vc_vol_mute: Not connected
03-21 16:22:33.722: I/sec_anm_ahi(27722): adm_api: ste_adm_client_set_cscall_downstream_volume(0)
03-21 16:22:33.722: I/ADM(1678): 2: 9812948856: [INFO] api_cscall:2111 csapi_set_downstream_volume: volume = 0
03-21 16:22:33.722: I/ADM(1678): 5: 9812948917: [INFO] api_cscall:2020 csapi_apply_vc_vol_mute: Not connected
03-21 16:22:33.762: I/libblt_hw(1671): Library opened (handle = 8, fd = 70)
03-21 16:22:33.882: I/libblt_hw(1671): Library closed (handle = 6, fd = 56)
[Galaxy S III Mini Original Android Development] golden-guy:
Can't confirm this here, it's working just fine for me (currently on the 20140317 build). Which version are you on atm?
[Galaxy S III Mini Original Android Development] :
I did built it from source on the 20th... Mh. No idea what the problem might be.
[Galaxy S III Mini Original Android Development] joelalmeidaptg:
What??? It's been like 21 days after this post and I didn't notice it!! I just love OmniROM, specially the ActiveDisplay thingy for the notifications! Going to try this right now!
[Galaxy S III Mini Original Android Development] stenc55:
I would like to try, but I'm not moving from Touch CWM.

Will it be compatible to CWM someday?
[Galaxy S III Mini Original Android Development] meduza:
I feel the same! But I remember, someone reported it works with CWM... You could try... I`ll wait till all components are working. I`m to happy with my carbon :)

m.
[Galaxy S III Mini Original Android Development] :
download recovery.img from golden-guy´s host, replace it in the twrp.zip of maclaw and flash it via recovery. Then you get his recovery on your device.

I flashed omni-Rom clean this morning, device started after reboot, but during setting the setup wizard stopped. Tried to reboot but hang in bootloop.

Don´t know what went wrong :confused:
[Galaxy S III Mini Original Android Development] tetakpatak:
If there isn't a strong reason to use GNow I would recommend Nova instead anyway.

tetakpatalked from N7100
[Galaxy S III Mini Original Android Development] sirjohn7x:
I do have Nova installed and I have problem even with it
[Galaxy S III Mini Original Android Development] meduza:
...maybe you could change the app`s permissions...

m.
[Galaxy S III Mini Original Android Development] Parliamert:
Guys, which app causes this situation. It seems like my phone can't deep sleep effectively? Can Twitter or Whatsapp prevent my phone to go deep sleep?
[Galaxy S III Mini Original Android Development] jstath1972:
Use better battery stats or wakelock detector and see what do your phone while "sleep".
[Galaxy S III Mini Original Android Development] Parliamert:
I installed Greenify and hibernated 4 apps that causes wakelocks. Thanks :)

But, now with WhatsApp hibernated, will I get my messages instantly?
[Galaxy S III Mini Original Android Development] jstath1972:
Sometimes yes and sometimes no.
[Galaxy S III Mini Original Android Development] exwan:
guys. any way i can change back my system from f2fs to ext4? i cant even flash stock rom now because of this. it make my phone bootloop.

i dont want to be using nova fusion release forever.

tried tenshi way, but twrp failed to flash the file. so in the end im stuck with no rom installed in my phone. the only way is to flash nova rom using odin then flash tenshi PA rom back.
[Galaxy S III Mini Original Android Development] golden-guy:
Inside TWRP, do a "Wipe"->"Advanced Wipe" then tick all those f2fs formatted partitions /data, /cache, /system (or one by one) and "Change File System".
[Galaxy S III Mini Original Android Development] exwan:
u cant do it with system. maclaw made it default as f2fs with his rom. tenshi tried making new updater script and mfsa. i've tried it and it's not working on PA rom.

man, this whole thing just defeat the purpose of android. which is freedom of choice. wth kind of dev made something that irreversible.
[Galaxy S III Mini Original Android Development] golden-guy:
Cut updater-script inside your flashable zip down to the bare minimum (see below) and re-flash. That should do.

ui_print("Formatting /system with ext4");
format("ext4", "EMMC", "/dev/block/mmcblk0p22", "0", "/system");
ui_print("Done!");
[Galaxy S III Mini Original Android Development] golden-guy:
New 4.4.4 build 20140801 is up!

Hey guys,

a new 4.4.4 release 20140801 is up. It contains the latest Omnirom code base and 3.0.44+ kernel (with JB_Update2 applied).

Some new features have been introduced by Omni team, like Launcher3 custom app drawer icon and charging animation for percent style.

On the housekeeping side, the (non-functional) auto-brightness entries have been removed in both display and button settings.

DOWNLOAD

Enjoy!
[Galaxy S III Mini Original Android Development] exwan:
So, just swap my updater script with the one u paste? That enough? Will try when I'm free. Thx man
[Galaxy S III Mini Original Android Development] golden-guy:
Yeah, that reformats /system back to ext4 so you should be able to flash. But make sure that all three partitions (/system, /data and /cache) are back to ext4 before you are to flash a "regular" (that is, non-f2fs) ROM zip.
[Galaxy S III Mini Original Android Development] golden-guy:
Forgot to mention: With de-activation of the auto-brightness code, the brightness changer on status bar swipe now keeps correct brightness state on screen-off. Also, the custom buttons settings toggle state issue has been resolved (by Omni team)
[Galaxy S III Mini Original Android Development] joelalmeidaptg:
Guys, has anyone got Adaway no longer blocking ass in Google Chrome? Lately I see lots of them in the browser, but not when using apps. Ideas in what's going on?
[Galaxy S III Mini Original Android Development] Android-Andi:
[MENTION=5473651]golden-guy[/MENTION] rebuild if you have time https://gerrit.omnirom.org/#/c/8946/

Gesendet von meinem GT-I8190 mit Tapatalk

Edit:

Correct me if i am wrong, but meight be because of this http://bluebox.com/technical/android-fake-id-vulnerability/
[Galaxy S III Mini Original Android Development] el-figurin:
Some ads are not being blocked in the YouTube app on my end.
[Galaxy S III Mini Original Android Development] jstath1972:
Try AdFree by bigtincan. http://adfree.bigtincan.com/:good:
[Galaxy S III Mini Original Android Development] 1N4148:
One question. This rom's having the same problems playing back videos with hw+ accleration (mx player) and youtube pixelation like others since cm10.2. I'd like to understand why this happens.
[Galaxy S III Mini Original Android Development] golden-guy:
Not using MX here, but imho Youtube videos play back just fine (without pixelation) both inside the app and in the browser. Of course, as always also depending on video material and available bandwidth...
[Galaxy S III Mini Original Android Development] Android-Andi:
[MENTION=5473651]golden-guy[/MENTION]

just found this: https://gerrit.omnirom.org/#/c/8963/

reduce PB size from 2MB to 512KB this allows us to enable h/w acceleration
on low-end devices while keeping memory usage down.
[Galaxy S III Mini Original Android Development] golden-guy:
Thanks, please let me know if that works out. Actually, the S4 is not really a low-end device which would qualify for such a hack, is it? ;)
[Galaxy S III Mini Original Android Development] Android-Andi:
[MENTION=5473651]golden-guy[/MENTION] maybe because there is no way found ATM to fix on kernel and fixing it native as workaround.

I added it to my latest SlimKat now, commit merged on slim already. Now waiting for feedback.

Gesendet von meinem One
[Galaxy S III Mini Original Android Development] dapeterle:
Hi golden-guy,

first of all thank you very much for your super work for s3 mini!

Unfortunately I have some problems with not working GPS. In this thread I posted some more details and also some debugging information of apps GPS tester and google maps (verbose and errors). Rest of rom works totally fine.

In this thread you find more detailed information and attached debug logs (taken with DDMS).

http://xdaforums.com/galaxy-s3-mini/help/problem-gps-stock-roms-t2807788

I tried so much to get GPS working but I do not get it running on kitkat roms. Changing gps.conf files, manually etc does not fix the problem. On stock roms everything works fine I see many satellites, I get a fast fix 10s. The phone is an i8190N 8 GB version, I just bought 1 month ago from an offer of Tchibo here in germany.

On kitkat roms omni, slimkat, cyanogen etc. I never see any satellites. GPS symbol is appearing if I start an app which wants to access gps. I also checked on all android settings I know controling GPS.

I also tried to find out the vendor of the agps chip and if it is maybe change to a newer version of galaxy s3 mini, but I wasn't successful. Sensor suppliers are Invensene, Sharp, etc. I don't think the hardware changed.

Can you maybe try to help me understand why GPS works fine for custom stock roms like R-Mod 3 (4.1.2) and does not work for > 4.1.2 roms omni, slim, cyanogenmod. I am sadly not advanced analyzing debug informations, but for now I found some errors with 08-03 20:44:46.514: E/SensorManager(7240): sensor or listener is null.

If you need more information of my device or I can provide your more detailed informations just ask.

Greetz and thanks in advance,

dapeterle
[Galaxy S III Mini Original Android Development] 1N4148:
MX is crashing when trying to use the HW+ decoder (which is working fine on any 4.2 based rom) and YT is showing a pixelated/aliased video (also compared to a 4.2 based rom). I can reproduce this bevaviour on any 4.3/4.4 based rom, but I don't know what has changed from 4.2 -> 4.3. I can supply logcats if there is an interest to fix.

Don't have this problem on my other devices (i9300, p3110 & p5110)
[Galaxy S III Mini Original Android Development] tetakpatak:
A-A and G-G, S3mini will work great with its 2core, if the patch will work on Tab 2, it will also work on S3mini

tetakpatalked from N7100
[Galaxy S III Mini Original Android Development] akkufix:
Found your thread, as i looked for a good rom for my son's mini. And this rom is really fine. :good:

So, i don't want to disturbe you, but maybe this helps you for H/W+ acceleration:

https://github.com/thicklizard/Komo...a17cd5fbc51e565b9f74553d42712bf0257954#diff-0

Add/change the diff in /fs/binfmt_elf.c

For zImage, set in .defconfig file:

I put this some times ago in cm and stock kernels for my (sold) Sony Sola and it worked. Well, nearly same chips.

Can't check it on the mini, because i haven't it in my hands atm.

To activate frandom, create a file (i.e. 81frandom with rights 755) for init.d, like this:

Maybe you have different paths and i'm not sure, if you need the red marked lines.

You see it, if you execute the script in adb shell.

Check for function with "Check Random Entrophy" from market.

Value should go up >3000

Hope this helps you to get H/W+ to life.
[Galaxy S III Mini Original Android Development] joelalmeidaptg:
Install an app called GPS test, go to the app settings and select Update AGPS. Does that work for you?
[Galaxy S III Mini Original Android Development] cmgonzalez:
YouTube has definitely quality issues from cm10.2 also Netflix is crashing.
[Galaxy S III Mini Original Android Development] dapeterle:
Hi Joelalmeidaptg,

I tried nearly everything to fix GPS in > 4.4.x roms. Downloading AGPS data with GPS Test, GPS status etc. is not fixing my problem. I have some experience with flashing. For me it seems that sensor is not started correctly. Is it possible to see this with DDMS / Logcat? I attached some logs with ddms of GPS Test and google maps in this thread:

http://xdaforums.com/galaxy-s3-mini/help/problem-gps-stock-roms-t2807788

My newest finding:

In this stock rom GPS works fine: [ROM][STOCK JB 4.1.2][I8190/N/L]★R-Mod-v3★[21/6/2014][AROMA]

For this stock rom [ROM+KERNEL][27/06][ANF6] ♪★● VIRGINITY V13 ●★♫ S5 Taste | Blazing fast | AROMA! I have the same behavior as in the kitkat roms. I totally see no satellites.

How can I analyze the differences between this roms for gps?

Greetz,

dapeterle
[Galaxy S III Mini Original Android Development] joelalmeidaptg:
Which recover are you using to install the ROMs?
[Galaxy S III Mini Original Android Development] golden-guy:
[MENTION=4845845]dapeterle[/MENTION], please take a full logcat when you have restarted your device. Toggle GPS on/off and start GMaps with sensor on and also with sensor off (and activate with GMaps running)

If related, this "sensor is null" message could mean, that no driver could be loaded (which in turn would mean there's diff hw/revision in use)

Also,

- check inside app-permissions settings menu, if location is allowed to be accessed for GMaps.

- switch to "Device only" in location so that only GPS module is being used for retrieving location (if not already done so)

Anyone else having GPS issues with an I8190N?
[Galaxy S III Mini Original Android Development] golden-guy:
Thanks for pointing this out, looks interesting - will give it a try! :good:
[Galaxy S III Mini Original Android Development] dapeterle:
Hi,

I tried everyone. TWRP, ODIN, CWM.

Will do the complete logcat today evening. For me it really seems like the sensor can't be loaded.

Thanks for your response and time! I really appreciate.
[Galaxy S III Mini Original Android Development] dapeterle:
Hi together,

I could manage to make a logcat faster. Its made with Catlog, I hope this is fine?! I started several times GPS Test and google maps, with GPS on and off. With different settings of location, device only and high resolution. From short point of analysis I see a lot of "sensor is null". Seems like I have a problem ;-(

What I do not understand is the difference for GPS in RMOD v3 and the other roms. There everything works fine for the GPS.

I now also enclosed the catlog of RMOD v3
[Galaxy S III Mini Original Android Development] joelalmeidaptg:
I remember having the exact same problem as you. At the time I bought my phone I could only have GPS when using Dmod. I'm not sure what fixed it for me, but maybe you should try and Odin flash the latest firmware available, maybe that will fix it ;)
[Galaxy S III Mini Original Android Development] dapeterle:
Hi joelalmeidaptg,

I tried this 3 weeks ago. I flashed this firmware from sammobile with Odin:

Model: GT-I8190N

Model name: GALAXY S III mini

Country: Germany (T-Mobile)

Version: Android 4.1.2

Changelist: 1546175

Build date: Fri, 23 May 2014 10:09:55 +0000

Product Code: DTM

PDA: I8190NXXANR6

CSC: I8190NDTMANE2

MODEM: I8190NXXANR6

Also I tried flashing all kitkat version via Odin, TWRP, CWM. No change @ all ;-(

I really don't know whats the problem with my device... I also tried to analyse the sensor vendors, but this are just the normal ones...

My about device (RMODv3) says:

Baseband version I8190NXXANR6

Kernel: 3.031-1549853

dpi@DELL148 #2

SMP PREEMPT Thu Jun 12 11:22:11

KST 2014

Build Number:

JZO54K.I8190NXXANF2

My about device (omni_4.4.4-20140801-golden-homemade):

Model Number: GT-I8190

Baseband I8190NXXANR6

Kernel: 3.0.44+

stefan@octo-bot #1

Fri Aug 1 23:49:11 CEST 2014

Build number: omni_golden-userdebug 4.4.4 KTU84P

eng.stefan.20140801.234215 test-keys

Here you find my device in android-analyzer with omni_golden-userdebug 4.4.4 KTU84P:

http://androidfragmentation.com/database/v/dr/657475/oem/Samsung/dm/GT-I8190/carrier/o2 - de

Interestingly under location it says: AGPS not supported....

Here is the analysis with RMOD v3

http://androidfragmentation.com/database/v/dr/657476/oem/samsung/dm/GT-I8190N/carrier/o2 - de

AGPS supported
[Galaxy S III Mini Original Android Development] herries:
"OK Google bar not showing / working"

@ Goldenguy

I found a bug , or maybe my mistake - In otherwise a flawless omni build i found that the "ok google bar microfone icon dissapears , the bar is there but no mic icon " no longer works by saying "ok google" and i tried to disable/enable it in the settings next to widgets , but it won't work.

If you touch the bar then google search by voice works fine, but still no microphone icon in the bar or responding to "ok google " not working just white bar at top of screen.

Thanks for a otherwise near flawless Omni rom build @ Golden-guy. :)
[Galaxy S III Mini Original Android Development] M@t-MC:
Golden i have the i8190N and gps works and worked like a charm in every your update and roms;) i'm not an expert,but im completelly sure that is not caused of your rom..but cannot understand why with stocks work..

Anyway im very satisfied with your and android andi rom..good job thank you:)

P.s.i never been so long time with a rom like you:)
[Galaxy S III Mini Original Android Development] golden-guy:
Not much to find in your logs, apart from those "sensor is null" messages. You might try with wiping /data and as last resort, try if changing baseband would help. AMG4 and AMJ3 both work fine for me. I cannot think of anything else atm, mate. Hope that one of these work out.
[Galaxy S III Mini Original Android Development] golden-guy:
This opaque search bar gets apparently introduced by the KitKat White Theme Mod that I have applied to the ROM. Will see if that can be amended. For the "OK Google" to work, you need to have recent GApps and the Google Now launcher active. Launcher3 has its own Custom Hotwords feature, which works somewhat differently.
[Galaxy S III Mini Original Android Development] Fred6681:
Hello,

There is a commit that works "Ok Google" in the search bar with launcher3 -> https://github.com/Team-Exhibit/bea...mmit/0c1919b031d60f2498a5bf0f4de6d8f9177ff802

I use it works very well
[Galaxy S III Mini Original Android Development] herries:
New Kernel

[MENTION=5473651]golden-guy[/MENTION]

Coming from novafusion to your omnirom ver is just a pleasure , every thing works fine, however just for interest sake Novafusion managed to get a

new Kernel for S3 mini from samsung and they published it and Nova is using it now in there roms.

Maybe if you can test this Kernel we can get better performance/battery life ect from the new kernel. Everything is nearly 100% with your rom but

Maybe we can test the benifit of it if you decide to include it in a future release.

Thanks for a near perfect rom.

http://novafusion.pl/2014/07/22/great-success/
[Galaxy S III Mini Original Android Development] Android-Andi:
[MENTION=5972779]herries[/MENTION] incl. Allready, applyed the changes myself https://github.com/andi34/android_kernel_samsung_golden/commits/android-4.4

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Original Android Development] golden-guy:
Thanks mate :) Chances are high that you are running the latest kernel already, since release 20140801 has been built using Andi's sources with JB_Update2 commit applied. Which already contains the latest Samsung kernel sources.
[Galaxy S III Mini Original Android Development] joelalmeidaptg:
I just got my first time freeze in forever! I should have been sleeping for hours '-'
[Galaxy S III Mini Original Android Development] M@t-MC:
is this happened only with the last update or before too? (onlyt to know if i should go back to the previous version)