yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] fenomen0:
Please help me! I had a boot loop into recovery when i have installed CM10. I saw to reflash stock ROM and recovery and to install CM10 on clean. Everything was fine until i made wipe data and wipe dalvik cash. I had again boot loop into recovery. I start again reflashing but after the installation of the stock ROM i had a new problem: boot loop to the animation logo samsung (the third i think). I disconnected the cable and ... the phone is not starting anymore. Odin recognize it but can't establish connection for transfer.
[Samsung Galaxy Mini] Uizz.UW:
Okay so just to sum up all the bugs I've encountered :

Most important thing :

The incoming call problem that was in the CM9 build is now present here as well , but it's worse . On the CM9 build after the caller ended the call , you could still use your phone , whereas now the phone freezes completely even after that and you have to remove the battery .

Other Bugs :

- The SD card isn't mounted where it should be - this can make some apps malfunction . Also , I forgot to test its copy / move / delete functionality (I flashed back to stock because of the incoming call problem) .

- APN bug is still in , but can be fixed by turning on & off airplane mode .

- Does WiFi Direct work ? On stock GB it did fine but on CM10 I saw no option for it (maybe I didn't look around very well) .

- After flashing Gapps , Maps won't work . I keep getting the error "Unfortunately Maps has stopped." until I completely kill its process , and when I enter it , it keeps telling me that it needs a data connection , even though I tried both WiFi and 3G .

- When Apollo is playing , when turning on the lockscreen , the widget pops up on it , but the lockscreen wallpaper goes all black (a small thing but still a bug :p )

This is all that comes into my mind right now . If I encounter anything else , I'll keep you updated . I may try reflashing it once more today for some more testing .

______________________________________________________________

Some tips for those having bootloops and stuff :

-Make sure you are using Squadzone's CWM . mb-14's has some more bugs you may not want to encounter .

-Don't use Reboot - Recovery . Manually boot into recovery yourself .

-If you do get into a recovery bootloop , just flash the CWM again , no need to flash back to stock .

-If you get into a normal bootloop , don't forget that after flashing the stock again , at the first boot you have to let the phone unpack the files for about 5 minutes . If it still won't start after that , reflash the firmware , or try another one .
[Samsung Galaxy Mini] sembre:
If you stuck in MIBIB on odin

Try

Rename file .pit

To

CALLISTO

or

TASS

Tell me if work on your device

This trick sucsesed on my device
[Samsung Galaxy Mini] TheWhisp:
APNs are working fine for me. Maps also work fine for me. External sdcard is in correct place. In Jellybean+ it's in /storage
[Samsung Galaxy Mini] bwn:
OK,

- calling bug

- APN bug (airplane on/off)

- some graphic bug in lock screen settings (see screenshot)

Maps are working fine for me.
[Samsung Galaxy Mini] tekkenl0rd13:
sir what stock ROM do you used before you flashed your CM10 in CWM 5.0.2.8?
[Samsung Galaxy Mini] fenomen0:
Odin recognize the phone, but i have to remove the battery. Now everything seems going well but whitout change: bootloop on last logo Samsung, the phone vibrate 2 times like some force close and restart from the animated color loro (not from the begining). I can't enter on Recovery (stock or CWM). When i try to enter on recovery seems that something is working but the screen is black and i can't see what's happens, but in Odin the phone is "Added". Please give me some advice. I'm not noob for android. Its my second phone with this OS.
[Samsung Galaxy Mini] Fallen_Knight:
cant aplly cm10 themes from playstore.

slight lag

more..ofcourse its on early dev stage...thanks thewhisp
[Samsung Galaxy Mini] CoX26:
I have the same baseband as thewhisp (the one from the first post screenshot) I don't have any problems with SD card ..

TheWhisp can you solve that call bug ? This ROM can be used daily if you are to solve that problem
[Samsung Galaxy Mini] TheWhisp:
Yes, I'm trying to find out what's wrong
[Samsung Galaxy Mini] Porobu:
u can partiali fix it by activating home key and power for calls in accesibility setting
[Samsung Galaxy Mini] sembre:
Home button not function

Please fix that's
[Samsung Galaxy Mini] Porobu:
Home button works perfectly on s6500d

Do u have a 6500? the one with NFC
[Samsung Galaxy Mini] CoX26:
Yes, i did that ...and after you press it like 5 times on a call..it answers, and with lock ley you silence the call.

If the phone is not locked you see the call and you can answer so...the temporary solution is : set screen always on and dont lock your phone :)) or use home key to answer but you can't see who's calling ..
[Samsung Galaxy Mini] TheWhisp:
That's why you must remember why this release is called "preview".
[Samsung Galaxy Mini] CoX26:
So, this call problem is it SOD ? is it from the kernel ? ...

You, TheWhisp are the best thing that happened to SGM2 :)
[Samsung Galaxy Mini] ady_seray:
Will this (eventually) work on the NFC model? I mean there aren't any hardware differences except the NFC.
[Samsung Galaxy Mini] Porobu:
Found another bug: when the phone screen is turned off and u try to wake it up sometimes screen doesnt turn on and u have to hard reboot

Edit:Deepsleep works
[Samsung Galaxy Mini] TheWhisp:
My device is kind of bricked, I cannot go into recovery mode, phone is bootlooping. While everything else works. So development is stopped. :/
[Samsung Galaxy Mini] Porobu:
Did u try download mode and repartition?
[Samsung Galaxy Mini] TheWhisp:
repartition? I didn't try that, does it work?

edit: whew, got in the recovery mode, wiped data, should boot now. (I guess I had to hold the buttons a lot longer)
[Samsung Galaxy Mini] Uizz.UW:
I never tried it either , but you can find the good .pit file along with Odin in my signature .

But try a simple stock firmware flash first if you can get it into download mode .
[Samsung Galaxy Mini] Porobu:
I had that problem wirh my galaxy y and repartition helps

BACKUP EVERYTHING BECAUE SE EVERYTHING WILL BE DELETED

Also use the correct pit because u can superbeick ur phone
[Samsung Galaxy Mini] sembre:
Hi there

You can try flash recovery only in PDA section with odin
[Samsung Galaxy Mini] tekkenl0rd13:
the ROM works great.

sir TheWhisp. will this phone receive a nightly build?
[Samsung Galaxy Mini] TheWhisp:
Yes, download mode worked, I flashed stock ROM, I just had to hold the buttons a little longer I guess. It's fine now ;)
[Samsung Galaxy Mini] TheWhisp:
If I fix everything, I can push it to CM so it's official, but that will happen only after official JB comes out. I still don't have any idea why there is that backlight bug, logcat and dmesg doesn't say anything. :/
[Samsung Galaxy Mini] sembre:
Yeahh

:D:(:D:D:D:D
[Samsung Galaxy Mini] tekkenl0rd13:
im thinking of it sir, since in a messages its fully working.

while in calling the screen wont light up but the softkeys and sounds are working fine.

maybe the proximity sensor of the phone does the problem?.
[Samsung Galaxy Mini] Porobu:
Also thewhisp, tje backlight bug when unlocking screen can be avoided by pressing power screen doesnt light up, wait 3 seconds press power again and press power again and if it doesnt light up repeat steps
[Samsung Galaxy Mini] Uizz.UW:
About that ... I don't think the proximity sensor actually works on this device , or at least doesn't fully work , so if the sensor is the one that triggers screen to light up , that may be the problem .

Also , I was thinking ... back when the screen wouldn't light up after booting the device . What caused that to happen ? Maybe it's the same thing .

Or it could be the lockscreen itself not showing up .

The thing is that incoming calls work , everything is displayed properly if the screen is still on , so I'm guessing something might not be triggered properly , thus not turning the screen on . Either the sensor , the lockscreen itself , the call event itself , I don't know which one is responsible for turning on the screen xD
[Samsung Galaxy Mini] TheWhisp:
Proximity is working. Even the dmesg shows that backlight has been set.
[Samsung Galaxy Mini] tekkenl0rd13:
sir do you try to dial this? *#*#0588#*#* then test the proximity sensors

i cant test it myself coz the phone is not here right now.

edit: wrong code

it must be *#*#0588#*#*
[Samsung Galaxy Mini] Porobu:
Tried the code but doesnt work
[Samsung Galaxy Mini] Uizz.UW:
Looks like it works o.o . I'm on stock GB now though .

Well then idk what could be the problem ... I'll reflash it & do some extra-testing & logging myself & see if I can come up with anything .
[Samsung Galaxy Mini] TheWhisp:
Samsung codes don't work on AOSP based ROMs
[Samsung Galaxy Mini] TheWhisp:
ok, data usage fixed, no reboots anymore ;)
[Samsung Galaxy Mini] marek_poland:
I've got problem with wifi. I can not connect to my wifi with MAC address filtering. I have an information connecting and then saved. Have you any solution for that?

Btw TheWhisp you've made great work, thanks:)

Wysyłane z mojego GT-S6500D za pomocą Tapatalk 2
[Samsung Galaxy Mini] max5800:
Camera and bluetooth make problems on every device while porting CM.

Does mini2 shares any camera or bluetooth libs with other phones?

What is kernel 3.0 status? Are you going to work on it?
[Samsung Galaxy Mini] Uizz.UW:
I think the WiFi MAC address has changed . Check it and add it to the list .
[Samsung Galaxy Mini] TheWhisp:
Don't worry, it will be fixed, I was just focusing on other things. :)

I will not port 3.x, it's better to wait for official Samsung kernel.
[Samsung Galaxy Mini] max5800:
I guess it is. If it ever comes...

I don't have any worries. I can see you're talented and skillful. Keep up the good work!

P.S. I'd help, but my knowledge on porting is really basic.
[Samsung Galaxy Mini] TheWhisp:
It should be fixed now. Appears I have accidentally removed a service from ramdisk.
[Samsung Galaxy Mini] Uizz.UW:
Okay so I flashed back to CM10 and started doing some tests .

First of all , just to get it out of the way , the Maps bug I was having is gone . It was because I restored the GB TB backup . I thought it was installed by the gapps but actually I restored it with TB . Now I clean-installed it from the Play Store and it works okay .

Second , about the brightness problem ... this line keeps popping up when it happens :

E/CM PowerHAL( 357): Error opening /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate: Permission denied

Also I think there's something wrong with the accelerometer , because it keeps doing this :

D/AccelerometerListener( 494): enable(false)

but it's never making it true again .

The lockscreen itself is not the problem , as the problem still occours if you deactivate it . Also , you can still do screenshots by holding down the Vol.DOWN + Power buttons . Looks like everything works fine under the black screen - the answer screen is showing up , and I've even somehow managed to get a screenshot of the Power menu .

One time I even made it turn back on after the call had ended , but I have no idea how , I just spammed all the buttons xD Only the first time though , it wouldn't turn on anymore during the next ... 7 attempts .

So as a conclusion , I think there might be something wrong with the Power HAL . If I recall right , the Power HAL was the thing that fixed this bug on CM9 as well .
[Samsung Galaxy Mini] Porobu:
Thewhisp found another bug: if u change governor, max or min processoer speed the proccesor will lock itself to the highest avaiable frecuency
[Samsung Galaxy Mini] TheWhisp:
Probably because you set the governor to "performance"
[Samsung Galaxy Mini] Porobu:
I used interactive governor

Edit:changed default governor to interactive rebooted waited to everyrhing to finish loading and cpu is still on 800Mhz

Edit2: Also if i set max 245 when this is happening and then return to 800 freq qill lock in 245 and phone lags
[Samsung Galaxy Mini] TheWhisp:
I haven't experienced that kind of problem.

@ Uizz.UW: that permission error should be fixed.
[Samsung Galaxy Mini] gabrielking9:
On Cm7 on galaxy we was having this same call problem but instead of black it was white. I think when the lockscreen is activated for sometime and deep sleeps begins works when you receive a call maybe it is not waking up the processor task which on deep sleep it just stop working and keep memory on to save battery.
[Samsung Galaxy Mini] Uizz.UW:
Nah it's not deep sleep . The phone still works . I was able to screenshot while the phone was ringing & even afterwards .

I'm also having a wierd idea that it might be an accelerometer problem . Seeing as the accelerometer isn't listening , maybe the OS doesn't know whether it should show the image in portrait / landscape . Just a thought .
[Samsung Galaxy Mini] CoX26:
yep, everything works under there..i set home key to answer from accesibility and when i called i was able to answer, when the call ended i heard a sound and after i restarted i could see the call information(date, how long the call was etc)
[Samsung Galaxy Mini] Uizz.UW:
It's so wierd , both the accelerometer & power hal errors show up at any lockscreen on / off , so I guess neither is the problem .

Still looking for differences .
[Samsung Galaxy Mini] TheWhisp:
because accelerometer is turning off when screen is off. Power HAL is changing sample rate when srceen is turning on/off.

edit: you can also debug kernel. (adb shell dmesg or adb shell; dmesg > /sdcard/dmesg.txt)

edit 2:

3>[ 675.726536] Prevent infinite loop(wait for 5s)
<3>[ 675.726592] LCD can't initialize with in 5100 ms
<6>[ 675.726644] late_resume: abort, state 3
<7>[ 675.726687] LCD [BACKLIGHT] : 8
<3>[ 681.336537] Prevent infinite loop(wait for 5s)
<3>[ 681.336600] LCD can't initialize with in 5100 ms
<7>[ 681.336658] LCD [BACKLIGHT] : 9
<3>[ 686.946539] Prevent infinite loop(wait for 5s)
<3>[ 686.946596] LCD can't initialize with in 5100 ms
<7>[ 686.946664] LCD [BACKLIGHT] : 10
<3>[ 692.556518] Prevent infinite loop(wait for 5s)
<3>[ 692.556578] LCD can't initialize with in 5100 ms
<7>[ 692.556633] LCD [BACKLIGHT] : 11
<3>[ 698.166528] Prevent infinite loop(wait for 5s)
<3>[ 698.166583] LCD can't initialize with in 5100 ms
<7>[ 698.166643] LCD [BACKLIGHT] : 12

Not sure what's causing this
[Samsung Galaxy Mini] FcukBloat:
sorry I don't want to be sarcastic it is just that i don't understand exactly ;) it is you who is making the port/builds or someone else or a team or i don't know? thanks! :confused:
[Samsung Galaxy Mini] gabrielking9:
Just thewhisp of the team have this device so he is working alone
[Samsung Galaxy Mini] zalukajonet:
;]

im waiting too for thsi port. love cm9!! do it fast and good luck for all
[Samsung Galaxy Mini] Mdetring:
thnx dude best news for the galaxy mini 2 GTS6500D until now but I won't root and install custom rom in my phone it's better to wait for jelly bean original update;)

edit: I rooted ma phone cause normal user is so boring but when offical jb is out it will help creating better roms and I was noob when I wrote it before editing it ;)
[Samsung Galaxy Mini] gabrielking9:
I don't think samsung will release a jelly bean for galaxy mini 2 in this year
[Samsung Galaxy Mini] FcukBloat:
I think it will never be released actually.. :D

and by the way, what's the point in waiting official JB if it will be released in two years when maybe official android 5 will be out? :p

also, I don't like at all official roms, too much sh*t in them, unused apps etc and, additionally, I want to be able to control MY phone 100%, so root is a must! :)..byeeeee
[Samsung Galaxy Mini] gabrielking9:
And Cm9 is ics ui not touchwiz ui like in Galaxy S3 and you can customize Cm9 with a lot things.
[Samsung Galaxy Mini] k3lcior:
It's not about using official software, official soft is important for devs to create custom ROM's easier (like official libs, kernel sources etc. which means less bugs / everything working)

It will be extremally usefull for TheWhisp and other devs if they decide to work with this device.
[Samsung Galaxy Mini] FcukBloat:
yes of course.. but I was just responding to this:

"but I won't root and install custom rom in my phone it's better to wait for jelly bean original update"

;)

cm9 or cm10 are way better then official ics and jb, at least for me! they have many extras I love :)
[Samsung Galaxy Mini] gabrielking9:
Thewhisp Can create Cm9 with everything fully working because it is armv7
[Samsung Galaxy Mini] TheWhisp:
Just because it is armv7 doesn't mean that it can fully work. It depends on drivers.
[Samsung Galaxy Mini] FcukBloat:
:( don't say that please or you will discourage us! :p and btw we all trust in you :victory:

also, pardon me a lot, I know it is not good at all to ask for ETAs.. but do you have a gross idea about when the first build could be available for testing? (I mean.. days.. weeks.. months.. not looking for something exact of course! :angel: )

thanks anyway bye!
[Samsung Galaxy Mini] gabrielking9:
Galaxy S doesn't have and it have official support with fully working
[Samsung Galaxy Mini] Uizz.UW:
Arguing about this is pointless . If you want to use it , use it . If not , use the official JB build when and if it comes out . Simple as that .

To think people were actually complaining that SGM2 doesn't get enough development attention in the past , and now people start to change their opinion lol .

I'm grateful for TheWhisp's work and I'm also looking forward to its release . Not in a hurry though . It's better to have a stable build rather than a sooner yet bug-heavy one . Keep up the good work Whisp!
[Samsung Galaxy Mini] ADrMD:
Thanks TheWhisp, i hope you will also develop cyanogenmod 10
[Samsung Galaxy Mini] TheWhisp:
I'm actually thinking of working on CM10 instead of CM9 since msm7x27a supports it just fine.
[Samsung Galaxy Mini] rhisendark:
If making cm10 is easier then it would be better :)
[Samsung Galaxy Mini] FcukBloat:
Uao cm10 would be even better of course! That's a dream thank you! :)

If we can be of any help.. just ask ;)
[Samsung Galaxy Mini] k3lcior:
+1 for CM10, it makes more sense imo. :good:

Take your time.
[Samsung Galaxy Mini] peter_baz:
whatever you think that will work out better for you

we have faith in you :)

but i think if they both have the same difficulty rate lets say,work on cm9 and just wait for the official JB as you planed from the start
[Samsung Galaxy Mini] Uizz.UW:
Maybe this would help :

<6>[ 334.931900] request_suspend_state: sleep (0->3) at 334935579876 (2013-01-13 17:10:16.394786575 UTC)
<6>[ 334.932720] early_suspend: call handlers
<6>[ 334.932764] hscd_early_suspend
<6>[ 334.933325] bma222_early_suspend
<3>[ 334.936045] release_all_fingers start.
<3>[ 334.936107] ts_power_enable off
<7>[ 334.966524] LCD start lcdc_trebon_panel_off
<4>[ 335.099495] [VIB] OFF
<3>[ 335.116475] config_lcdc_gpio_table: gpio_tlmm_config(0x41a0)=-5
<7>[ 335.116493] LCD start trebon_disp_powerdown
<6>[ 335.166333] msm_fb_blank_sub panel_power_OFF

After these lines I'm getting the same thing as you .

Also , I saw some "Failed to open libwm.so" throughout the logcat . Does that library have anything to do with this ? I've read it's used for event handling .
[Samsung Galaxy Mini] TheWhisp:
No, that's not related.
[Samsung Galaxy Mini] rianrazan:
I found that DSP manager only work for a while after turning on the phone, a few minutes/hour the sound effect is gone also the h/w+ decoder can't be used in mx player
[Samsung Galaxy Mini] max5800:
Forgot to ask before, which kernel is coming with ROM?
[Samsung Galaxy Mini] TheWhisp:
2.6.38.6 and looks like fixing bluetooth will not be as easy as I though :/
[Samsung Galaxy Mini] gbueno6:
Don't worry, we'll wait. One month ago I didn't thought I could have CM10 working in my device and it's almost perfectly working so we'll patiently wait!

Thanks!
[Samsung Galaxy Mini] RoSinner:
Hi, and thanks for the rom. After I install the rom from cwm, I rebooted and its currently sitting in that screen where it says CyanogenMod with the circle running around it. For how long does it have to stay like this cause I think its been like 10 minutes already ?
[Samsung Galaxy Mini] Unagi:
did you do a factory reset before flashing?
[Samsung Galaxy Mini] RoSinner:
Yes, I did. Its all good now. I flashed cm10 again. took less than a minute to load this time. Was hard to get into CWM though. Kept going through the boot screens for some reason. Maybe I pressed the buttons at the wrong times. Anyway, great rom so far... no bugs encountered except the known ones.

edit : btw it wont flash with earlier CWM version. think I had 5.0.2.8 instead of 5.2.0.8 and it gave some status 7 error
[Samsung Galaxy Mini] FcukBloat:
hi guys at last I can try the preveiw build by thewisp :)

sorry for the dumb question, can you let me know if the following steps are correct or if I am going to do something wrong? thanks

1. install cwm by squadzone via odin

2. wipe data/factory reset

3. flash 12.01.2013 preview rom by thewisp via cwm

4. flash gapps

5. wipe data/factory reset

6. reboot

thanks a lot in advance.

ps. the rom by thewisp comes rooted right? or should I root by myself?
[Samsung Galaxy Mini] rhisendark:
Yes. It is rooted ;)

Edit: by the way there is no fm radio on cm10 :/ why? i use that on my trips :(

GT-S6500D cihazımdan Tapatalk 2 ile gönderildi
[Samsung Galaxy Mini] RoSinner:
Might have found a temporary solution to the incoming calls bug. I installed one of those fullscreen caller id replacement apps which kick in on top of the normal caller id screen. Seems to work fine. Screen lights up with every call.

edit : nevermind, still bugs
[Samsung Galaxy Mini] bhree:
I have compiled thewhisp kernel from source using my system config. Tried with my modded GB ROM and everything's working. So I think the kernel already has everything.

Sent from s6500d with custom GB ROM and kernel.
[Samsung Galaxy Mini] ars_92:
Try spirit fm free from Mike. Google it :)
[Samsung Galaxy Mini] djfnz:
Spirit FM not working :( I test it!
[Samsung Galaxy Mini] rhisendark:
Yes. it is not working tried every option and setting.

GT-S6500D cihazımdan Tapatalk 2 ile gönderildi
[Samsung Galaxy Mini] CoX26:
TheWhisp , we are really looking foward to the call bug fix, please let us know how fixing that is going and post an update when its fixed. I really want to keep this ROM on my phone but i can't because of that call bug ...
[Samsung Galaxy Mini] FcukBloat:
installed properly first impression is great thanks thewisp for you great work! :)

I can't believe I have jb on s6500 at last you are the best! ;)
[Samsung Galaxy Mini] TheWhisp:
Of course the kernel is fine for GB.
[Samsung Galaxy Mini] tekkenl0rd13:
I've been reading about the call black screen problem on CM10 and i've read this thread

http://xdaforums.com/showthread.php?t=1835128

and found some one flashable zip that fix proximity sensor in this thread:

http://xdaforums.com/showthread.php?t=1851816

and it seems hard to generate or produce some LOGCAT of the problem

BTW

Does anyone try to put lights near the proximity sensor while theres an incoming call?

maybe we just need some calibration to it.
[Samsung Galaxy Mini] Uizz.UW:
The proximity sensor is working fine .

BUT

I was mistaking the proximity sensor for the light sensor . That's the one that isn't working on stock GB (it doesn't with the auto-brightness anyways) . But I don't think that's the problem , since the brightness mode isn't set on auto on CM10 . And besides , the logcat clearly shows that brightness is supposed to be set properly . So then I guess the LCD itself isn't turned on , not the backlight brightness leds .

The thread you posted is reffering to a different problem , specifically the screen being unable to be turned on by the proximity sensor after you answered & it turned off . I don't know if you noticed , but after you answer & put your phone at your ear , the display is turned off , but when you put it back in front of your face , it turns on again . THAT'S the thing that wasn't working there :p

// edit :

WELL IT ALL MAKES SENSE NOW XD Why the hell did I have the impression that it had one x.x