yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] xfim:
can i expect reply?! Please
[Samsung Galaxy Mini] thelastbad:
i think he stop dev in cm9
[Samsung Galaxy Mini] Accoun:
So, installed CM10 and it looks like it doesn't recognize my memory card. Is it a matter of some incompatibility between stock GB and CM or what? Is this fixable?

Someone in the dev thread said:

But I'm not sure what EXACTLY does it do. Does it make it the same as in GB? Does it make the system think memcard is the internal memory (would that mean I can't change cards?)? Or does it just make the phone recognize the memory card in the proper way?
[Samsung Galaxy Mini] thelastbad:
yeah its A big difference between stock GB(3.6) and CM10(4.1) and this mean swap memory (changing internal with external memory)

to make external memory aBasic memory to save internal memory space
[Samsung Galaxy Mini] Accoun:
So I can't use both? Well, I guess I'd be better off reverting to stock. :-/

Is it something that can be fixed somehow later in development somehow?
[Samsung Galaxy Mini] Roadmau5:
How do you expect him to solve problem/bug, that he doesn't have?

off topic- I am from Latvija too, it is so cool that this developer is from Latvija
[Samsung Galaxy Mini] hachibei:
Same here

Same here. SG - S6500 (non carrier). The white screen appears after the first unlock from sleep.

CM10 4.2.2 Build 7/7 : Good.

CM10 4.2.2 Build 7/13 : White screen

CM10 4.2.2 Build 7/18 : White screen

Reflashed back to build 7/7 since that's the only latest build working for me.

Each flash was accompanied by factory reset, data wipe and dalvik wipe. Tried that method for reverting to stock > wipe + cwm > wipe + cm > CM 7/18 build, but that white screen still appears. Changing unlocking method from slide to pattern, no unlock, or numbers doesn't remove the white screen.

Now back on build 7/7. (I had a gut feeling it all might come down to one command line changed for 7/13 :fingers-crossed:)

Edit: Just to make it clear, you can still interact with the launcher (the phone does vibrates if you remember the icon locations and opening apps does makes a sound and stuffs). It is as if it was overlayed by a white screen (like those screen filter app on play store except this one is totally white).
[Samsung Galaxy Mini] TheWhisp:
I really don't know why some people have that bug. I and a lot of people have never experienced that, maybe it's something hardware specific. You can use latest build with older kernel, it should work fine. It's very likely that people who have this "white screen" bug will also have it with the 3.0.x kernel.

I'll upload a nightly with 3.0.87 kernel later.

Not working:

Wi-Fi

NFC ( I can't fix it because I don't have NFC variant )

HW v-sync
[Samsung Galaxy Mini] ahmed mo7a:
good, but wifi is very important
[Samsung Galaxy Mini] thelastbad:
you can make backup of your rom and use your stock
[Samsung Galaxy Mini] cardinal83:
Good day to all!

Yesterday I installed cm-10-20130720-UNOFFICIAL-jena.zip and after a couple days of use I have a question:

1. When I plug headphones sound plays through them and through the speaker.

2. After setting up an access point Wi-Fi computer finds it under a different name (wl0.1) and without the selected encryption method WPA2 PSK.

Otherwise, the firmware is fully functional and stable.

Thank TheWisp for the work done!
[Samsung Galaxy Mini] Zedd247:
So the white screen bug can be fixed with older kernel? What kernel has to be installed and how to install that kernel? CWM? Odin?
[Samsung Galaxy Mini] portagira:
If i flash squadzone kernel will i fix white screen?

Inviato dal mio GT-S6500 con Tapatalk 2
[Samsung Galaxy Mini] midzan21:
No squadzone kernel is pretty old and it wouldn't work on Cm10.1/cm10
[Samsung Galaxy Mini] portagira:
So what i should flash?

Inviato dal mio GT-S6500 con Tapatalk 2
[Samsung Galaxy Mini] xfim:
Could it work on cm9 without danger of bricking device? :D
[Samsung Galaxy Mini] midzan21:
No xfim no... squadzone kernel is made only for stock gb ROMs not for ics+
[Samsung Galaxy Mini] TheWhisp:
just stop asking. CM10,CM10.1 kernels doesn't work on CM9.
[Samsung Galaxy Mini] midzan21:
Cm10.1 18/07/2013

So yeah guys here is mine review of this ROM which I used for last 2 weeks (after upgrade from 13/07 build without wipes because I need to have stable ROM with working WiFi and Bluetooth for my summer job where I use some app for Fiskalizacija - Fiskal blagajna (some new Croaitan laws need to use that stuff which we bought from one Croatian Android dev and it's not availiable on Google Play because it cost about 100€ per month)). Only problem I got is white screen after being outside on 35°C for about 3 hours (yeah restaurant job on seaside) with phone but this got away in next 5 minutes in colder room.

Everybody should expect to upload an CM10.1 working TW5 launcher with Waether widget in my thread for CM10 TW5 launcher (they are pretty same so I don't need separate threads). For now on I'm going to use CM10 because I need to test that app with older Android versions (everybody on my work was using Nexus 4 with stock 4.2.2 and only I was using old but very fast and smooth Mini2 and I was so proud for that)
[Samsung Galaxy Mini] luxyuz:
I tried the CM10.1 for the last month and loved it. Didn't used the much better and faster CM10 because I could not get wifi to connect.

Now I try to update CM10.1 and no wifi :crying:

Well, back to 236 because I'm tired of charging my phone every day.

Please make wifi work with CM10, its my fav and thanks for the hard work.
[Samsung Galaxy Mini] CoX26:
Will OTG work on our phone with kernel 3.x ? Does SGM2 have the hardware needed for OTG ?
[Samsung Galaxy Mini] midzan21:
I hope that OTG should work in 3.x kernel. I got OTG cable from my friend and I hope that should work on our phone with 3.x kernel
[Samsung Galaxy Mini] TheWhisp:
Yes, msm7x27a supports OTG (USB host). You should be able to use flash drives, USB keyboards/mice etc.
[Samsung Galaxy Mini] thelastbad:
wow thats fantastic
[Samsung Galaxy Mini] xfim:
Does cm10.2 boot? Can i safely try it?
[Samsung Galaxy Mini] midzan21:
try it for yourself. you can't lost anything except time to make nandroid backup and restore to it if it doesn't work.
[Samsung Galaxy Mini] cardinal83:
Questions

Good day to all!

I installed cm-10-20130720-UNOFFICIAL-jena.zip and after a couple days of use I have a question:

1. When I plug headphones sound plays through them and through the speaker.

2. After setting up an access point Wi-Fi computer finds it under a different name (wl0.1) and without the selected encryption method WPA2 PSK.

Otherwise, the firmware is fully functional and stable.

Thank TheWisp for the work done!
[Samsung Galaxy Mini] Zedd247:
I want the white screen bug fixed soooo bad :'( I just need to have Blue A2DP.
[Samsung Galaxy Mini] triplex92:
CM10.2 not play, restart recovery?
[Samsung Galaxy Mini] mat_yan:
Since Mini 2 has quite a small RAM for Jelly Bean, can somebody suggest how to manage RAM for best user experience in CM10?
[Samsung Galaxy Mini] xfim:
You can go to developer options and at bottom you will se background process limit at standard. Put it to 1 or 0
[Samsung Galaxy Mini] nelmini:
The Dreaded White Screen

anyone have any solution for the white screen after flashing the new build?

Here is my details:

I downloaded the latest build from thewhisp goo account.

transferred the zip file via usb cable into my sdcard.

power off the phone and reboot into recovery (cwm6)

selected the "install zip from sdcard" and chose the zip file fore mentioned.

after waiting for a few minutes, the installation is complete.

reboot.

screen says "updating file"

after updated, the dreaded white screen appears.

ohya, I've tried wiping dalvik cache, cache partition too. but white screen still appeared. hmm
[Samsung Galaxy Mini] injola:
Until 3 days ago, I only used unrooted, stock android. I installed cm-10.1-20130718. I saw a mix of what everyone else saw. Lots of very nice stuff. Some corruption sometimes in Google maps. Stock vidcam records, but on playback it is garbled. Plays back older video fine. Other vidcam programs work a little bit or not at all. Quality is always bad, even worse than stock vidcam on stock ROM. FM radio works fine, sound through headphones. Other audio apps always route through speaker, ignore headphones.

Wiped system/cache/dalvik, installed cm-10.1.2-20130713l. Now headphones work in audio apps. Did not try FM radio. Video behavior same. Tried illusion videocam, it works, but don't know how it works in stock. But quality is much worse than stock ROM stock vidcam. Tried messing with light levels, bright, low, on CM 10.1 and stock ROM. Stock is much better. Restored nandroid backup of rooted stock ROM. Video is better. Not great, but it's all I have.

One concern is that 10.1 mounts external SD at /storage/sdcard, so several apps restored via TB from stock ROM can't find their data. Don't know best way to handle it. Make a sym link ? I was doing each one in the UI by hand.

Tried mtp to a linux box. Didn't really work. Fault probably on linux side. Tried adb from debian with android-tools-adb. Could see device over usb, but could not run shell or logcat. Never did it before so I don't know what was wrong.

Edit: I did not see any white screen bug, but I didn't ever use it very much. Didn't seem hot.

I have S6500DXXLK2.
[Samsung Galaxy Mini] c.kyriakoulis:
Hi,I have a question & I hope somebody can help me.First I have installed 18/07/2013 built and my problems are: I can't send mms,it keeps saying sending (till the end of time :banghead: )sms are working fine I have Cosmote network provider (Greece) someone told me that something has to do with my "csc" which I can't change it,I even tried to replace "mms.apk" with root explorer and changed permissions and still the same,I even tried another app from googleplay and changed some stuff and still nothing,Does anyone have an idea about that? :confused: :banghead:
[Samsung Galaxy Mini] darkmanz:
[MENTION=4148720]TheWhisp[/MENTION] will the 3.x kernel be integrated in the next build
[Samsung Galaxy Mini] TheWhisp:
yes, the only major issue left that prevents me from releasing new CM10.1 build is that Wi-Fi AP cannot be enabled via settings. But it works if manually enabled via terminal/adb shell

btw., for those who did try the latest cm-10.2 development build: did the device hang on Samsung logo, or did it boot into recovery mode?
[Samsung Galaxy Mini] Yuri_PL:
So does this build (newest 10.1, ofcourse) will have support for USB On-The-Go?
[Samsung Galaxy Mini] iceblow1:
What mean bug "offline charge" ? The phone will not charge when is offline ? If i have no battery i can't charge my phone ?

Where i can fiind to make cm 10.1 to look like touchwiz ?
[Samsung Galaxy Mini] Yuri_PL:
TouchWiz for CM10.1@GT-S6500: http://xdaforums.com/showthread.php?t=2166058&page=8

Offline charge mean, that You can't charge phone when he is turned off.

How do You want charge battery by phone, when its not connected with phone?
[Samsung Galaxy Mini] scheibenwischer:
Barcoo Scan Quits

Hi,

has anyone else the Problem that the Barcoo-Scanfunction Quits unexcpected if Scan Button is clicked?
[Samsung Galaxy Mini] c.kyriakoulis:
Doesn't anybody know to help me with my mms problem??? :eek::eek::eek::eek:

:banghead::banghead::banghead::banghead::banghead::confused::confused::confused::confused:
[Samsung Galaxy Mini] portagira:
Someone who fixed white screen in latest build of cyano 10?

Inviato dal mio GT-S6500 con Tapatalk 2
[Samsung Galaxy Mini] larissamafia:
I try now for the 1st time to send mms and the app f.c.

Sms some times is sending something like (&#%$&@$%&&)
[Samsung Galaxy Mini] c.kyriakoulis:
Thanks for your efford but I've sent like five or six none was sent..
[Samsung Galaxy Mini] blinqipa:
Is the camera working on AOKP?
[Samsung Galaxy Mini] Daks32:
Overclock

Dear Dev:

i have a question, is that if our mini 2 does not support overclock up to 1267mhz why your kernel have that frequencies, I know that it can support up to 1126.4mhz that is what squadzone kernel have but I mean that if you can add 1126.4 frequency to cyanogenmod kernel cause that little MHz(13.4) can give us a little boost, why don't you try. cause when I go up to 1152mhz it gives me blue screen and the high frequency that I can use is 1113mhz.

Thanks for your attention

---------- Post added at 02:58 PM ---------- Previous post was at 02:50 PM ----------

hi, another thing that I want to discuses is that yesterday when I was doing a benchmark checking I saw that one person gets like 4800 points and I can only get like 4600 so I look the cpu frequency and it says 1190mhz but my mini 2 not supports that frequency cause when I get to that one it gives me blue screen and I want to know if maybe yours mini 2 supports that frequency cause I don't know how that person do to get so high
[Samsung Galaxy Mini] xenas:
Mine is working 100% @ 1190mhz !! I guess its a matter of luck with the hardware.

Enviado do meu GT-S6500 utilizando Tapatalk 4
[Samsung Galaxy Mini] Daks32:
mine not

really, mine if I get to 1190mhz it gives me blue screen and reboots, xenas what scalling governor you use and what scheduler cause I use smartassv2 and sio that ones people tell me that are the most stable ones but I really want to get to 1190mhz so if you can help me
[Samsung Galaxy Mini] xenas:
I use Noop on the I/O. The other settings are just stock.

Enviado do meu GT-S6500 utilizando Tapatalk 4
[Samsung Galaxy Mini] Daks32:
thanks

thanks, I will try this config, when I come back to cm10.1 cause now im on stock
[Samsung Galaxy Mini] scheibenwischer:
Headset wont work

has jb a headset detection?

if i plug one in, the only effect is that volume changes but output goes allways to the internal speaker with apps like vlc, tunein or apollo.

just the fmradio app has a inapp toggle between speaker and headset, this works fine.

i could not find any headset configuration menues in the os nor an app who can toogle between headset and the internal speaker.

my extended volume control has no property icon for an headset device (see attachement).

(phone and build info screenshots see post above).

need help

thanks
[Samsung Galaxy Mini] TheWhisp:
@ above: wait for the next build

edit: I have uploaded CM-10.2 development build. It would nice if someone could test and report to me if the device 1) boots 2) hangs on samsung logo 3) reboots into recovery

if it hangs on samsung logo. do: adb pull /proc/kmsg
[Samsung Galaxy Mini] scheibenwischer:
Dev Build 17.08.2013

update without clearing caches:

1) boots fine

2) passes samsung logo

3) did not boot to recovery

4) android startup update process ok, got same desktop as before, kernel 3.x in phoneinfo

- camera didnt work, no connection to device message

- tuninpro: playing stops after selecting a radio

- app starts are extrem slow or hung

made then cache wipes and factory reset:

- android starts as before wih factory settings

- camera app error message

tried cwm restore: md5 didnt match error :(

installed gapps-jb-20130813-signed.zip:

message "Android Keyboard (AOSP) has exited"

no keyboard working.

all wipes again:

After simcode -> Unfortunately, Google Text-to-speech Engine has stopped"

Android Setup starts

Personalisation -> keyboard will not start again

Reboot

"Android Keyboard (AOSP) has stopped"

"Google+ has stopped"
[Samsung Galaxy Mini] blinqipa:
Anything really special about 4.3 (10.2)???
[Samsung Galaxy Mini] TheWhisp:
you had to wipe data and /system. Camera will not work on 4.3 since I had to enable PIE to make it boot.
[Samsung Galaxy Mini] blinqipa:
So if jena users disable arm_PIE , will the Camera work , will the device boot ?
[Samsung Galaxy Mini] scheibenwischer:
next try

- wiped data / factory reset

- wiped cache partition

- wiped dalvik cache

- installed dev build

- installed gapps 4.3

- reboot

- problems finding my wlan on setup

- i skipped wlan search

- no more gapp errors ocur, keyboard works

- wlan can not be activated, slider is ghosted

- reboot

- wlan found and active

- got a donut circle running in the upper right corner, dont know if its ok?

edit: while running wlan goes inactive (symbol on top dissapear), reboot, wlan inactive -> imho not stable
[Samsung Galaxy Mini] TheWhisp:
That's battery icon
[Samsung Galaxy Mini] scheibenwischer:
upps, i changed the symbol on 4.2.2 to a batteryicon, thought its a donut of death :)

think the wlan device on the new build is not stable.

wlan worked only once, now its deactivated again on my phone.

tried build 18.07 again, my wlan would found after seconds in the setup procedure.

greets and thanks for the cool os, i love it
[Samsung Galaxy Mini] Yuri_PL:
There are available new Gapps for CM10.1 (20130812), someone tested it on our phone?

I asking, because in CM10.1 thread is still link for older version.

And where disappeared NFC patch?

I see that this build has OTA update, does this will work for us unofficial builds, or this is relict from official release code?
[Samsung Galaxy Mini] midzan21:
I'm using this new gapps and it works good just like other versions.
[Samsung Galaxy Mini] injola:
Wrong link for bug reports for CM 10.1 on Galaxy Mini 2

I think the link given in post http://xdaforums.com/showpost.php?p=44689962&postcount=1962

is not correct. It is for the wrong platform.

I believe the correct link for bugs for CM 10.1 on Galaxy Mini II is

https://github.com/TheWhisp/android_device_samsung_jena/issues. This is for the repository android_device_samsung_jena.

Edit: I am not allowed to post on the original thread. Maybe someone with permission can post a correction there.
[Samsung Galaxy Mini] Yuri_PL:
I installed new Gapss & they work. :D

But on new CM10.1 build WiFi constantly reconnecting. :/
[Samsung Galaxy Mini] TheWhisp:
the link is correct. The main repo is msm7x27a-common. jena, jenad and trebon are just minor repos to set device specific stuff like choosing correct defconfig for kernel building, setting device name etc.
[Samsung Galaxy Mini] bleached:
Has anyone who had white screen problems with previous builds tried latest 18/8 build? Is whitescreen problem still there as theWhisp predicted?
[Samsung Galaxy Mini] MisMisMis:
Yes, the problem persists. I just finished downgrading back to the 20130707 build on my device. :(

Additionally there was heavy color banding present on todays release and association times for WIFI were significantly longer than pre-ath.

BTW I am just trying to build the tun.ko for that old build's kernel - I want to try out IPSEC with strongswan.

EDIT: I see tun/tap is already built into the kernel. Hmmm. I wonder why strongswan can't set up the tun device then...

EDIT2: Ok, was a permission problem. Setting permissions to 0666 for /dev/tun fixes vpn access. :)
[Samsung Galaxy Mini] TheWhisp:
well, then 07/07 build is the last one for people who have white screen problem. At least for a while. There has to be slight difference in HW, but there is no way to detect this change :/ I guess on 2.6.38 kernel drivers/video/msm worked fine for both display revisions, so Samsung didn't need add anything in order to make it work. I have on thing in mind, but I am not sure it's related.

Wi-Fi is indeed not as good as with previous driver (probably because it lacks Samsung specific code), but we cannot use the old driver with 3.0 kernel. I'll see what I can do. I don't have Wi-Fi network at home so Wi-Fi testing is limited for me :/
[Samsung Galaxy Mini] MisMisMis:
[MENTION=4148720]TheWhisp[/MENTION]: Just out of interest I flashed build 20130818 again and obtained a dmesg copy at kernel log level 7 aka. KERN_DEBUG while I cycled the screen on and off several times. I also did this on the working 20130707 build. If you are interested in the logs I could PM them to you. There is MSM-related output in both of them - though my kernel hacking skills are not up to scratch to interpret it. ;)
[Samsung Galaxy Mini] pcgaldo:
Hi!

I'm new here. It is the first time I installed a custom rom and I have to say I am very satisfied.

Greetings to all and thank you very much, especially [MENTION=4148720]TheWhisp[/MENTION], for all the work done. Thanks to your efforts, we can extend the life of low-end terminals, making them almost as functional as other more powerful devices, which have official updates to the latest versions of Android.

I recently installed cm-10.1-20130818-UNOFFICIAL-jena and gapps-jb-20130301-signed on a previous rooted device, using CWM Jena 6.0.3.5 wipe all "wipeable" things. Baseband is S6500DXXLD3.

At first I had a problem with white screen (sometimes gray screen) when trying to get out of the lock screen. This only happened to me while the charger or USB cable was connected. When attempting to unlock, the screen was white or gray, which does not allow me to interact with the terminal and forced me to remove the battery to restart.

To solve this white screen problem while charging, I tried to disable Daydream, in the display settings. So far, this solution is working for me. Edit: Re-enabling Daydream and I have NOT white screen issue. If I have problems again and suspect of their origin, I will comment on this thread.

I have also had problems connecting to a wireless network with dhcp protocol. Configuring the settings manually, the device connects and remains stable.

When the screen is locked, the wifi is turned off, as if entering power-saving mode. Do you know any option to keep wifi always connected?

Other things seem to work. The most important: calls work fine. Camera takes photos, car handsfree seamlessly connects via bluetooth and the battery life is acceptable (somewhat less than with the official rom).

So far this is what I need and I've tried. Coming soon I will try other functions, such as GPS.

Once again: thank you very much.
[Samsung Galaxy Mini] c.kyriakoulis:
Can anybody send me a flashable csc for greece?
[Samsung Galaxy Mini] MisMisMis:
I can NOT confirm this on my device. Toggling daydreams does NOT fix the white screen issue. And it really seems to be either heat or battery charging related. After initially flashing the image I get no white screens. If I happen to start charging the phone, the trouble starts...
[Samsung Galaxy Mini] pcgaldo:
Admittedly, I've re-enabled Daydream and now I haven't white screen when I leave lockscreen. It is so strange.

Forgive me for not verifying it before posting.

Now I verify it and I have more info, based in my experience with my device:

The issue occurs when I try to unlock my device "in a hurry". It seems that if I wait less than 8 or 10 seconds after the screen locks, white screen appears when I press the button. If I wait more than 10 seconds, there is no problem. It happens always, regardless of whether it is charging or not.

To get rid of the white screen, I push the button to lock the screen again, wait more than 10 seconds and, voila, everything works fine.

I tried to capture it in a screencast, but the screencast app didn't capture the white screen issue! It occurs between 0:10 and 0:14 in the attached video. View attachment Screencast_Aug_20_2013_2.mp4.tar.bz2

From 0:14 to the end, I waited around 10 seconds to see the unlock screen.

The display does not show the unlock screen and goes blank. However, the system is showing the unlock screen properly, which is what screencast app captures.

The screencast app that I am using is Screencast Video Recorder by Media Solutions (com.ms.screencast).
[Samsung Galaxy Mini] pcgaldo:
Hi again.

It is inconceivable: at this time, some minutes later, it does NOT appear blank screen if I press the button immediately after lock.

Then, if I put the device on a warm surface (about 40ºC) and wait a little, till the device is also warm, the white screen appears again, with the same behavior I described in the previous message.

Someone had mentioned that the problem could depend on the temperature. Is this possible?