yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] kissingmylove:
Can we ask mod to give us a section for pop plus??
[Samsung Galaxy Mini] Miche1asso:
Sure we can, I just don't know how! :D

Actually I've read that the forum should change. They are testing the beta. Maybe they are postponing the new less popular phones waiting for the new site. It's still a bit of a shame, though. This is generating quite some confusion.
[Samsung Galaxy Mini] Messi10:
yes, u can here
[Samsung Galaxy Mini] Miche1asso:
Oh, that's great. Ive already added a request. I think it would be good if more will join.
[Samsung Galaxy Mini] kissingmylove:
please vote for our devide
[Samsung Galaxy Mini] mkajkut123:
So, should this work with mini plus? I have tried to flash this CWM on my mini plus, and I got CWM recovery, but when I rebooted into recovery again, it was normal recovery. :confused:
[Samsung Galaxy Mini] :
I got that problem too but everytime I flash a custom rom , I have to flash CWM first.
[Samsung Galaxy Mini] Miche1asso:
The CWM we've got for the Mini Plus is not flashable, And IMO it is better it isn't. I hard bricked a Mini because something went wrong with the CWM. Just apply the CWM before doing any installation. It just takes few seconds.
[Samsung Galaxy Mini] kissingmylove:
it's not the error,everyone uses cwm by that way
[Samsung Galaxy Mini] kissingmylove:
here the cmw sir,i use it everyday

http://www.mediafire.com/?sll5ddcqrxlni3f
[Samsung Galaxy Mini] phiexz:
i just develop a kernel for this device

please check it out:

http://android.phiexz.com/device/galaxy-pop-plus/px-kernel/item/67-px-kernel-20120728-gt-s5770i.html
[Samsung Galaxy Mini] Miche1asso:
Never mind. It seems had to push the upper right button.

Anyway, I flashed it with CWM over the Repencis ROM. But it didn't stick. Do we have to flash it with Odin? If so, as a PDA?
[Samsung Galaxy Mini] iHero96:
No, it is a flashable zip from recovery not for odin
[Samsung Galaxy Mini] Miche1asso:
Yeah, I think I know why the kernel didn't work on my phone. It seems my /system partition is formatted as ext4 (which is bugged in this kernel). I used the CWM format utility in the past. Also after flashing it with CWM the /system was just corrupted, so I reformatted it again with CWM, Any idea how to format /system back to rfs fast? I am going to reinstall the stock ROM for it, but it is a PITA.
[Samsung Galaxy Mini] draiyan:
do anyone here have a odin flashable stock rom? i dont know how to make a odin flashable rom, i have downloaded from samfirmware but i dont know how to use splitFUS
[Samsung Galaxy Mini] phiexz:
Next released project: px-recovery with permanent clockworkmod

more info:

Here

its easy to use splitFUS, just follow its instruction.
[Samsung Galaxy Mini] :
hey how do i flash this?

through stock? or through cwm?

EDIT:

flashed this on stock recovery and everything works fine!!!

great work.
[Samsung Galaxy Mini] Miche1asso:
Has the ext4 bug been fixed in this last release?
[Samsung Galaxy Mini] draiyan:
i really would like to, but im no good at it, i tried it once, installed cygin, and other stuffs, but getting error. perhaps you could provide me the 3 files? please? the pda,csc and modem tars? i really like to try your kernel.
[Samsung Galaxy Mini] phiexz:
not yet, i dont know where's the bug from. is there any kernel with fully ext4 support for this device??

what firmware?
[Samsung Galaxy Mini] draiyan:
i got error, i forgot the exact error message but it was something like no zip installed, or something about zip, its in cygwin. then i give up on it. i really need the files, coz im on a boot loop after flashing your kernel on my bro's mini plus. i flash simply young custom rom, then it booted, and i flashed your kernel, and im stuck now.

EDIT:

oh yeah!! i got it working!! simply young rom + your kernel!! thanks!!

---------- Post added at 07:35 AM ---------- Previous post was at 07:12 AM ----------

but i have a problem, i cant sideload an app????... i already tick/check the unknown sources but it keeps reverting back. do i need a google account first?
[Samsung Galaxy Mini] kissingmylove:
anyone want new kernel can try this,i tried and worked

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

---------- Post added at 01:59 AM ---------- Previous post was at 01:58 AM ----------

and the rom for us: http://xdaforums.com/showthread.php?p=29340182#post29340182
[Samsung Galaxy Mini] :
I am using phiexz kernel with permanent clockworkmod recovery.

Its working fine for me . ( and has boot animation too , COOL!!! )

Sent from my GT-S5570I
[Samsung Galaxy Mini] Miche1asso:
Yup. The Repencis kernel from the Repencis V3.5 (for Pop Plus - not Galaxy Y) ROM! You may ask Repencis how he achieved that. It's kind of important because it messed up badly my first installation of your kernel. Now it is fine. Here is a little report of what I've done and discovered using your kernel:

First install (bad):

- I had Repencis v3.5 installed

- for some reason my /system was in ext4. Probably due to a bad installation of a CM9 wannabe ROM (don't ask. I still feel like killing that pretentious boy)

- Installed PX kernel via stock recovery

- adb logcat reported that /system/bin/sh wasn't present.

- The CWM was very messed up and didn't recognized the SD card.

- Reinstalled stock ROM to fix it

- Since I was there I backed up /sd-ext and reformatted it in ext3

- /system was back to rfs as well

Second install (the good one):

- I had Repencis v3.5 restored

- I tried installing PX kernel with CWM 5.0.2.6 (the one not flashable, the only we had available until now)

- The The installation process run but nothing was flashed

- Reinstalled PX kernel with stock recovery

- It worked and booted! No FCs at al

Now I have few questions:

- CWM 5.0.28 is flashed. I couldn't installed PX kernel with CWM, only with stock recovery. Am I going to be stuck at next PX update??

- The CPU governors seem to behave differently from the Repencis ROM. Actualy better, more governors have parameters we can set up. But why is that so? Aren't they all part of the same Linux kernel source code (I don't know. Just asking).

- SmartassV2 seems to stay stuck at the highest frequency. I switched to ondemand or conservative, depending on my mood. And then I already made the script to set them up in Repencis.. :D

- Monitoring the CPU frequencies I see that a value of 156MHz appears. Is it defined in the kernel but not in the list of user settable frequencies?

- I see that you "manipulated" a lot the system by use of scripts in /sbin. I am personally not very happy with it. These are a few reasons:

we are now forced to use only your busybox. Which has all applets linked at boot time. Busybox app from Google Play has a much smarter way of organizing the links to the applets

we can't updated busybox executable via application. Must be done via terminal.

Directories I was making use of in my scripts, like /sd-ext disappeared and they are deleted at boot time.

I thought (but I may be wrong) that /etc/init.d was a characteristic of the Linux kernel when enabled. You are using a busybox applet to enable/run the scripts in it

Changes made to /sbin automagically get reverted after reboot (very annoying)

swap is enabled by default. I can't disable it. Read above.

all together it doesn't feel very standard.

Said that I must also say that the performances seem impressive!! i had a gain of 20-30MB or so in RAM and even at 104MHz the phone feels smooth just sliding around. Great work!

PS: one last question: but at this point one can take ANY ROM for any phone, install it, apply the PX kernel and it will work? That would be impressive. Otherwise what would be the reason for this not to work?
[Samsung Galaxy Mini] phiexz:
repencis rom use Galpop+ kernel build2 by Fedy right??

i've already try that kernel. its also cant mount ext4 partition. its like samsung messed something in kernel source. i'll try to figure it.

adb logcat reported that /system/bin/sh wasn't present -> its because kernel cant mount system partition, maybe your system partition is on ext4.

i also know, galaxy pop has flashable cwm 5.0.2.6, but its not good. i dont know its actually for what device, and some feature are not working.

i only add some cpu governor, why?? i dont want mess kernel with useless feature. because most of 17 governor are never used by user. user usually use ondemand, conservative, interactive/x, lagfree and smartassV2.

156MHz freq appears? are you sure? what application do you use? CPU Spy???

i'll check it later.

for busybox, i'll make user choose what they want in next release. so user can use their busybox or use embedded busybox on kernel.

why you need /sd-ext directory?? its directory should be use only for cyanogenmod.

a2sd use /system/sd and link2sd use /data/sdext (correct me if im wrong).

no, init.d on android is executed with busybox. or sysinit script.

for swap, try to disable it with command "swapoff" on terminal.

for /sd-ext and disable swap, you can easily write script on init.d, so you dont need to doing swapoff everytime you restarted.

yes, i think this kernel can use for ANY ROM. but make sure your rom not use ext4 for internal partition (/system, /data, /cache). i hope i can fix ext4 bug ASAP

btw, thankyou for the very good opinions :D
[Samsung Galaxy Mini] :
Hey can someone recommend me a good theme for repencis 3.5 rom?

Sent from my GT-S5570I
[Samsung Galaxy Mini] Miche1asso:
Hi Phiexz, thanks for answering!

Let me reply one by one:

- Repencis ROM reported it was using a Repencis/Fedy kernel. I can't check anymore now, but I can assure you ext4 on it works great. I was running the Repencis ROM when my /system (and /sd-ext for link2SD) were in ext4 format before installing your kernel over.

- The CWM I (we?) was using was not flashable. I am glad your is, but it doesn't fully work (I'll report later about it)

- No, I meant that your kernel have more governors which can actually use parameters. Which is a good thing. As far as I checked Repencis "lagfree" for example didn't have any configurable one.

- Yup. 156Mhz. And 104Mhz. Reported by SetCPU and Antutu CPU Master. I am very positive.

- Also SmartassV2 after boot gets stuck at 832MHz. Changing it from SetCPU it moves on. Another user in the italian forum saw the same.

- Thanks about busybox! :)

- I needed /sd-ext because I am using it for a script I made to get a rid of Link2SD just mounting /data/app and /data/dalvik-cache into the sd partition (it actually works!! Not sure why people don't implement it). But I fixed it anyway. It just took me 2 hours to find out what was going on.

- I tried that already. swapoff doesn't seem to work. I really believe that you should leave to us user the option to enable the swap. And yes, I already had a script to enable the swap, so I changed swapon to swapoff. The kernel keeps using the swap, I see the swap used changing,

- So I was correct? I can install any ROM I like, now? That's great!! Good job sir!!

Now, about the CWM. Few things I checked:

- flash of zip files works fine

- backup works with /system, reads all /data and then fails saying "error while making a backup image of /data!". Too bad because the file data.rfs.tar is there in the CWM backup folder.

- I didn't test the restore at this point

- I can't mount/umount /sd-ext. So I suppose no operations are possible with it.

- Mount/umount of all other partitions work fine (at least they didn't report any error)

- So does mount USB storage (the SD card gets mounted on my Mac). But it doesn't get unmounted leaving the menu.

- Format of /cache worked

I can't check much more because I couldn't make the first backup. I'd just would like to know if/how one can revert back to Stock Recovery without flashing a stock ROM with Odin if needed. Any idea?

Anyway, thanks to you to answer!! I hope this helps as well. :)

EDIT: I could catch the 156MHz frequency. I attach a screenshot. Actually I am checking with other tools now and they report 104MHz. I am staring to believe that setCPU is a piece of junk. But I was pretty sure I saw it with other applications.

Nope, it is 156MHz. I read the value directy from /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq,
[Samsung Galaxy Mini] draiyan:
@phiexz is it just me or the kernel? cpu spy says that your kernel dont have deep sleep. please take a look at it.
[Samsung Galaxy Mini] Miche1asso:
Does it show the 832Mhz at 100% usage? Because my deep sleep is fine. But I set the ondemand governor at boot time with a /etc/init.d script.

It seems the first governor (SmartassV2) gets stuck at the highest frequency until one modifies something (governor, frequency range, whatever),
[Samsung Galaxy Mini] draiyan:
i used set cpu, conservative governor clocked at 105-832 mhz and sio. so far battery is better than stock kernel, i only got around 5% at 832mhz abd 70+% at 105mhz and remaining goes to the two other freq.

maybe il try to change my governor to ondemand. will it save more juice?
[Samsung Galaxy Mini] Miche1asso:
To be honest? I am starting to doubt that low frequencies give any benefit at all. I am experimenting now with 624-832MHz (any balanced governor would do). Let me put in this way:

We set up a governor that is supposed to save battery staying more at low frequencies. This means that the tasks will take longer to execute with an higher (although at a lower frequency) CPU usage. Also if the screen is on that implies more time on the display ==> Battery drain!! Not to mention the frustration.

On deep sleep it shouldn't matter. No matter the frequencies the CPU should go into an idle power saving state. But I am not sure about it.

Maybe the best solution is to be aggressive with ondemand, using a low up_threshold (60 or even less) and a 312-832MHz frequency range. Which is considered to be a battery drain but for the considerations above it shouldn't.
[Samsung Galaxy Mini] phiexz:
i know howto fix ext4 problem.

is there any major bug in this kernel??? because i only hold galaxy pop sometime. if itsnt i think i'll try to start build cyanogenmod 7.

@Miche1asso if you want to disable swap, try to swapoff /dev/block/mmcblk0p3

i forgot to add "/dev/block/mmcblk0p3" yesterday.
[Samsung Galaxy Mini] Miche1asso:
Yeah, stupid me not to think about it, I just used "swapoff -a". Ok, "swapoff /dev/block/mmcblk0p3" works!! Thanks!

Regarding other bugs, I just remind you the minor ones:

- Frequencies stuck at 832MHz until one changes the governor settings (reported by more people, I could check it personally)

- The kernel switching to frequency 156MHz without being defined/available

- Well, the busybox which is mandatory set by you, cleaning all previous user settings and installation

Also bugs with CWM, but I suppose they will be fixed for CM7.2 as well (how do you do it? Amazing!! ;)):

- backup works with /system, reads all /data and then fails saying "error while making a backup image of /data!". Still the file data.rfs.tar is there in the CWM backup folder.

- I didn't test the restore at this point

- I can't mount/umount /sd-ext. So I suppose no operations are possible with it.

- mount USB storage works (the SD card gets mounted on my Mac). But it doesn't get unmounted leaving the menu.

Good luck with the CM7.2!

PS: any chance to know what was wrong with ext4?
[Samsung Galaxy Mini] phiexz:
- freq stuck @832MHz, i'll try to fix it

- The kernel switching to frequency 156MHz without being defined/available -> this is strange bug, i dont know howto fix it -_-

- backup error on /data -> found the problem, cwm cant backup directories in /data/misc/bluetoothd/<bluetooth mac_address> because it contains ":" on directory name. in linux you shouldn't use ":" on name files/directory. fix by remove directory before backup. (dont worry, this directory is auto created again if activated bluetooth)

- cant mount /sd-ext. its simple, i only set cwm to mount /sd-ext as ext2, but your /sd-ext on ext3. isnt it?? next release will be mount as ext4. all ext2 & ext3 also will mounted as ext4.

- in linux, mount/umount USB Storage is working perfectly

EXT4 problem because our kernel isnt support huge file (>2TB). the default ext4 paramater hase "huge file" option. so its failed to mount because kernel dont support huge file. i'm trying to activating huge file support, but kernel cant boot -___-

the other option is remove huge file option use tune2fs.

tune2fs -O ^huge_file /dev/block/<ext4_partition>
[Samsung Galaxy Mini] Miche1asso:
That sounds good, then. Anyway, yes, you are correct. My /sd-ext is ext3 because with stock and Repencis kernel ext2 has the

bcm_sdhc.3

constantly on (80-90% of total time) and the phone never went to sleep. If you have any idea how to remove that wakelock I'd be very grateful, since still now (even with your kernel) it's on 5.-6% of times. Very annoying since the battery life in this phone is anything but exceptional.

The CWM backup solution sounds good too. I know special characters in file/directory names in Unix/Linux are just a PITA. :)

I'll check better the /sd-ext umount. What I did was to unmount /sd-ext from the CWM without unmounting it first from OS X (I was expecting an OS X error). Next time I'll try to umount if first from the computer which is the clean solution anyway.

Regarding the ext4 issue, I saw that manually mounting an ext4 partition it mounted as type j4fs. Its content was the same of /mnt/.lfs. I don't know, maybe it can help. Unfortunately to remove the "huge_file" option is just half a solution. In cases like mine were /system was in ext4 format it wouldn't be possible to fix it.
[Samsung Galaxy Mini] Miche1asso:
@phiexz

Sorry if I insist. I gave a better look at your /sbin/px-kernel-init.sh script. Actually I am surprised that it works, since there are some special characters in it, like in:

(EDIT: never mind. Something corrupted my terminal. Sorry about that, it's the first time it happened)

then it would be good to check for both Superuser.apk and Supersu.apk. If neither exists then copy your Superuser.apk version. Guess what? I had Supersu.apk installed indeed and now I don't know which su version I am using anymore..

Same thing for busybox. If it isn't installed then copy your. Otherwise leave it alone. Chances are that the installed busybox is much more recent and also, as I specified before, it has been organized with stericson.busybox.apk (or any similar application if available). For example I didn't make a link to "busybox reboot" because it doesn't work.

If you like I can modify the script for you accordingly and send you a copy. Obviously after having tested it. :)
[Samsung Galaxy Mini] Miche1asso:
Hi Phiexz,

I am not sure what's going on, but after a "wipe data/factory reset" I get a bootloop:

E/ActivityThread( 1725): Failed to find provider info for settings
E/AndroidRuntime( 1725): *** FATAL EXCEPTION IN SYSTEM PROCESS: PowerManagerService
E/AndroidRuntime( 1725): java.lang.NullPointerException
E/AndroidRuntime( 1725):	at android.content.ContentQueryMap.<init>(ContentQueryMap.java:65)
E/AndroidRuntime( 1725):	at com.android.server.PowerManagerService.initInThread(PowerManagerService.java:629)
E/AndroidRuntime( 1725):	at com.android.server.PowerManagerService$2.onLooperPrepared(PowerManagerService.java:554)
E/AndroidRuntime( 1725):	at android.os.HandlerThread.run(HandlerThread.java:59)
D/BatteryService( 1725): update start
D/VoldCmdListener( 1576): asec list
D/BatteryService( 1725): update start
E/liblog ( 1725): failed to call dumpstate
E/AndroidRuntime( 1725): Error reporting crash
E/AndroidRuntime( 1725): java.lang.NullPointerException
E/AndroidRuntime( 1725):	at android.os.DropBoxManager.isTagEnabled(DropBoxManager.java:288)
E/AndroidRuntime( 1725):	at com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:6872)
E/AndroidRuntime( 1725):	at com.android.server.am.ActivityManagerService.handleApplicationCrash(ActivityManagerService.java:6586)
E/AndroidRuntime( 1725):	at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:82)
E/AndroidRuntime( 1725):	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:854)
E/AndroidRuntime( 1725):	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:851)
W/AudioSystem( 1575): AudioFlinger server died!
W/IMediaDeathNotifier( 1575): media server died
W/AudioSystem( 1575): AudioPolicyService server died!

// here the bootlopp

D/AndroidRuntime( 1901):
D/AndroidRuntime( 1901): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<

I don't know if this is related to your kernel, the Repencis ROM or both. I can't fix it restoring /data from a CWM backup (made with CWM 5.0.2.6). It can't mount/format /data
[Samsung Galaxy Mini] phiexz:
dont restore rom from cwm from my kernel. its have a serious bug with rfs formater.

try to reinstall from odin, then restore your rom with cwm 5.0.2.6

i'll upload my new kernel tommorow with fully working cwm recovery (tested) and more bug fix
[Captivate Android Development] mindphaser2k9:
Battery Mods, to be flashed from CWM.

Note: these battery mods were made for V7.1. They work on V8 but you'll get old Toggles and TaskSwitch from V7.1. To restore V8 to defaults then, use V8_NO_TOOGLES_default_battery.zip
[Captivate Android Development] Wdustin1:
This is awesome. I was under the impression that glitch could not be used because it is 4.0.3 base and not 4.0.4, does it work well? Damn I really wanna flash this I just wish I hadnt knocked my phone in the toilet last night :D
[Captivate Android Development] mindphaser2k9:
The Glitch V14 beta 6 works well for me, even with OC=1320MHz and LiveOC=110%, even more stable than it was on CM9, but when Deep Idle is switched off. I have SOD/reboots with Didle (though this is a known issue), so I don't recommend to use Didle for now.

:D
[Captivate Android Development] 305Freak:
Good morning, does this rom work as smooth on the Captivate as it does on the phone used in the Youtube video demo? Holy crap that is smooth.
[Captivate Android Development] mindphaser2k9:
Good morning, try it and tell what you think. It works very smooth for me, though I use Glitch with OC.
[Captivate Android Development] apg5031:
hows the battery life?
[Captivate Android Development] mindphaser2k9:
Battery life is better than it was on CM9 and there is no Android OS bug (it shows about 4%) on this ROM.
[Captivate Android Development] anishz:
Excellent something to do in the evening.

People atleast flash the rom before asking for battery life. Also it will take a few charge cycles for the battery to give good results.

Also it states in captivate version miui music is replaced by google music, can i replace google music with miui v4 music, as google music is useless for me in India.
[Captivate Android Development] mindphaser2k9:
Sure, you can. I've added it to the OP, so you can flash MIUI Music from CWM.
[Captivate Android Development] anishz:
Thank you very much man,

I would have pressed thanks button but the stupid thanks limit is showing up.

---------- Post added at 07:33 PM ---------- Previous post was at 07:06 PM ----------

Just flashed this and man it is smooth and fast! Just like in the video. I also installed all my apps and still there is no difference in speed.

And all this on stock kernel, excellent work by ELITEMOVILE and thank you for bringing it here.

I only found one minor problem, after i disconnect data, the arrow icon for upload stays on, even when using wifi, it shows the icon on the signal bars.
[Captivate Android Development] id_snake:
Good job, man! ;) This one better for me than DK3.

Does any one has troubles with browser FC?
[Captivate Android Development] anishz:
No browser FC's, try clearing data for the browser.
[Captivate Android Development] apg5031:
everything works besides the play store....how should i fix this?

i did flash the gapps from one of the site....it still doesn't work...
[Captivate Android Development] mindphaser2k9:
Try to clear data for google play.
[Captivate Android Development] anishz:
Google play gave me errors too, saying server timeout, but i used market enabler and it works, so no probs.