yashsingh1/xdaforums huggingface dataset:
[Galaxy Y GT-S5360 Android Development] gadgetroid:
Nice update Physco! Thanks for the good news!

Now on to work. :p Well, I did some digging around, and I found that you have no /datadata folder. I figured that the Gapps FC issue had something to do with the data partition, and from memory, I knew that most AOSP ROMs stored their app data to the /datadata partition. So I opened up Terminal and ran the following command:

df -h /datadata

I was actually a bit surprised with what turned up, because it said that it couldn't find the /datadata partition! Now, most AOSP and based ROMs use the /datadata partion as it's on a faster memory, as opposed to the /data partition, which is on a slower memory. TouchWiz based ROMs don't have this partition from what I could gather.

I am currently going through JT's GitHub for the partition table and I will compare this later with Physco's source. I am not completely sure if this is the path that we should follow, because the /datadata partition is very small (only 170 MB or so), and it lies in the internal memory. The /datadata partition is native to CM7 and CM9 as far as I know (maybe also for other AOSP and AOKP builds, but I can't be sure).

I would guess that the /data/data partition would be symlinked to /datadata. Cyanogen originally implemented this for a lagless experience (as the frequently used data by the app would be linked to the /datadata partition, which is essentially in a faster memory than the /data/data partition), but on devices like the Fascinate, Galaxy S, Mesmerize and certain other Samsung based devices, this seems to fill up fast and cause FC errors.

Another thing that I mentioned before was running the CM build through dsixda's kitchen and signing the zip file with the Gapps included. Sadly, this didn't work for me, but I must say that I also zipaligned the APKs during the process and the ROM eats much less RAM now! :D

But getting back on topic, I will look further into this force close matter and will try my best to provide any fixes I find for this issue. Hopefully, I will get the repos synced and start working on this one now. Can WhiteXP pitch in with some info on this? Will post my GitHub here soon. :)

Greetings,

gadgetroid

---------- Post added at 11:26 PM ---------- Previous post was at 11:22 PM ----------

Sigh! Again!? Yes! Read back a few pages and you will see Physco stating that this is in fact a problem with updating the kernel to 2.6.35.14! Happens on all ROMs running on this kernel and I don't know if a working fix has been found yet or not.
[Galaxy Y GT-S5360 Android Development] pustinjak:
Hi,...me again about data problem:p

I try to manualy set Apn but nothing help'd.So can i get tut about that.

p.s.

i cant find that file:p
[Galaxy Y GT-S5360 Android Development] gadgetroid:
Flash the provided zip file in CWM recovery. Apply "Fix Permissions" after flashing. MAKE AN NANDROID BACKUP BEFORE PROCEEDING! Reboot. Tell me if it works or not. :fingers-crossed:
[Galaxy Y GT-S5360 Android Development] pustinjak:
Thank u for great help and fast responce but,.....:p i stil got no data working

edit:

btw,till now i got no problems with this CM everithing is fine (except data nd camera) for files on SD i use airdroid and for galery-Quickpic

edit again:

i try to replace modules in system/lib/modules (r w r r) with 14 modules-stil no data
[Galaxy Y GT-S5360 Android Development] gadgetroid:
What do you mean when you say that you replaced the modules with 14 modules? :confused: If you unzip the zip I gave you, you will get a xml file. Use root explorer or some other file manager with root access and move it to system/etc. If it asks to replace the file, press yes.

Didn't you call up your customer care and ask for settings? It's the safest way and the most recommended,

And there is also no need for using a third party gallery. The 3D AOSP Gallery works fine enough for me.

BTW, just a small update: After zipaligning and optimizing the apks, the ROM doesn't seem to lag as much as the original version even after about 9 hours of usage. Not much RAM is eaten, from what I can tell. Occasional flickering occurs, but is very rare. My settings are:

CPU set to "Performance"

Just-in-time compiler enabled

Compcache disabled by default

Surface dithering disabled (Note: enabling dithering may improve the images, but you will get the glitches at every other screen. Even rotating the device won't help then)

16bit transparency enabled

Scrolling cache force diabled

Allow purging of assets enabled

VM Heap size set to 24m. (@Physco It is set to 32m by default, and the phone becomes quite laggy when it is set to this. I recommend changing it to 24m, which is default for most phones.)
[Galaxy Y GT-S5360 Android Development] PsychoGame:
Thanks gadgetroid for you're wonderfull report and the research you did:).

With the information you've provided me I'll look into this matter and see if I can come up with a solution for this problem.

Hopefully we can fix this as well before the alpha 3 build as this makes it almost perfectly stable then:).

Because I have to be honest the workaround we have right now is not very friendly :P.

On the zipaligning I know this provides the system with more free ram:).

At the moment I haven't done this yet because it's not my top priority yet at the moment.

In the latter build I will zipalign the .apk packages as well because of our valuable recourses which shouldn't be wasted.

Again thank you for you're hard work also.

Greetings PsychoGame
[Galaxy Y GT-S5360 Android Development] gadgetroid:
Hello Physco.

I have a question. I was going through the OP again, and I came across your initial updates. Samsung have their own proprietary partition map called BML, and you were working on changing it to MTD, right? Then, you said you encountered issues with removing FSR and you couldn't give us the promised EXT4, right? You said that you would be using the YAFFS2 file system instead of the EXT4. In a later update, you said that the kernel is completely EXT4 and I was wondering just what file system the entire CM is now on?

I'm asking because the force close issues are related to the MTD partition map. On MTD ROMs, the /data/data partition is symlinked to /datadata for performance reasons, like I already stated before.

If as you stated, the ROM is now on MTD, I will try the general Linux command ln -sf and symlink the /data/data folder to /datadata. I will post shortly if I have any success with this.

Greetings

gadgetroid
[Galaxy Y GT-S5360 Android Development] gadgetroid:
No problem! :good: Open source is definitely the place I want to be at any day! :D Love Linux and what it stands for, and that is the primary reason I started getting into Android. :p

BTW, that workaround does not work for me on Alpha 2.1. It works on the Alpha 1 though. ;)
[Galaxy Y GT-S5360 Android Development] pustinjak:
I will not spam here any more and i will flash again 2.1 or 2.2

Thank u for all help,....see u soon :highfive::good::good::good::good:

edit:

Back again,....data working :)
[Galaxy Y GT-S5360 Android Development] Reynaldi:
Feel like gonna thanks op hundred time
[Galaxy Y GT-S5360 Android Development] Soul reaper:
well!! this is a very good going... :thumbup:

the best development and on topic i have seen so far (in case of cm )

i do have a opinion:-

how about fixing media scanning first

1 this will help in file managemnt

2 this will solve half bt problem

by this i mean if i send a file through bt on my sgy(when bt starts wrking ,which i beleive it will) and the device recognises but does not locate any extrnal storage for storing the file than how will it wrk??

3 this will help us wid camera too and video recording ...hence limiting bugs etc.

nothing more this is just my opinion

i urge u too take a little heed on it

thank you a lot ,sir :)
[Galaxy Y GT-S5360 Android Development] gadgetroid:
This is awesome, Physco! :D Great work! Bluetooth partially working! The phone is almost the same as what I had when I was working on ICS for the Android-x86 project!

Any progress on the Force Close issue? I'll test this build and see if there are any significant changes in the FC department. The fix that you had didn't work for the Alpha 2.1 release. But it did work on the Alpha 1 build. So I will take a look and see if I can work on it. :good:

---------- Post added at 09:40 PM ---------- Previous post was at 09:35 PM ----------

Umm... Media scanning already works. All the files show up on the OI File Explorer and in Gallery as well as in the various Music Players. ;) Only get a few crashes (but that was on my MIUI port) while selecting files to upload through Tapatalk, but everything else works fine! :D

I was wondering what media_profiles.xml did and I will take a look now. I think Physco just forgot to update that bit of line. :D
[Galaxy Y GT-S5360 Android Development] Kamijou:
Nice PsychoGame!,

I am now downloading your Alpha 3 Build where bluetooth is now partially working thanks to you, you made CM development on this community fast and possible with your experience in Linux programming though I'm still starting how to compile libraries and learning android's core

But you make everything fast and possible with your development which makes Galaxy Y owners proudly on CM builds you made.

From my opinion you should be "Recognize Developer" since you fixed everything that other dev couldn't although the problems we are facing is the GPU but best of luck thanks for helping us! :)

Regards, Kamijou
[Galaxy Y GT-S5360 Android Development] brianmorales:
GT-S5360L

Hello, I want to thank you for your work.

Unfortunately GT-S5360L devices, installing stays in the logo, as with previous versions.

Thank you very much for your work and dedication, I hope you can solve this problem.

At the moment I do not have much time, but maybe after this Tuesday, you can see how to fix this, and maybe see what white screen on camera
[Galaxy Y GT-S5360 Android Development] kael2404:
Headphones again doesn't work cause the bad file name ("brm..." should be "bcm... ")
[Galaxy Y GT-S5360 Android Development] xHinne:
Media scanning is already working. ive install ES File Explorer File Manager on the market and its working and scanning after reboot :)
[Galaxy Y GT-S5360 Android Development] kaustubh.rockstar:
Nice work Psychogame (:

Feeling gr8 to have a developer like you.. :)
[Galaxy Y GT-S5360 Android Development] gadgetroid:
Hello Physco.

I was going through your source code, and I came across the recovery.fstab.

I think that changing the file systems of the /system and /cache partitions from EXT4 to YAFFS2 will benefit us more.

Also adding this line would be better too:

And also, I noticed that you have still kept the the boot and recovery partitions in the BML partition table. :confused: I thought you told us you changed it? Or is it where the FSR modules lay too? :confused: Hope you can clear up this doubt. :)

If you are adding that above line to the recover.fstab, then you also need to add these lines to the recovery.rc.

# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 /dev/block/stl9 /system
#mount yaffs2 /dev/block/stl10 /cache
#mount ext4 /dev/block/stl11 /data nosuid nodev noatime nodiratime noauto_da_alloc
#mount yaffs2 mtd@datadata /datadata

Since the current /system and /cache partition are on the EXT4 file system,

# mount mtd partitions

# Mount /system rw first to give the filesystem a chance to save a checkpoint

mount ext4 /dev/block/stl9 /system

#mount ext4 /dev/block/stl10 /cache

#mount ext4 /dev/block/stl11 /data nosuid nodev noatime nodiratime noauto_da_alloc

#mount ext4 mtd@datadata /datadata

Also changing the device names of /system and /cache in the recovery.fstab to system and cache respectively can make mounting stuff easier in the above script. Like I can just type in

mount ext4 mtd@system /system

Hope this will somehow help with the FC bug. If you want to look at a few of the sources I referred to for this, PM me or just ask on Gtalk. ;)

Also, can I implement a few changes to system.prop over at your GitHub? :fingers-crossed:

Note: You might also need to create mountpoints before you add those lines to the recovery.fstab. :)

Enjoy your weekend. :good:

Greetings

gadgetroid

EDIT: Physco, you have two files for the headset config named "bcm_headsetsw.ko" and "brcm_headsetsw.ko". I think that when you compile your build, both the files are included, and headset support conflicts as a result. Just thought I should let you know. :) :good:
[Galaxy Y GT-S5360 Android Development] Yash98:
I love you bro! No homo!

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

For me, media scanning is working.

and BTW, if media scanning is not working that doesn't mean external storage is not detected. (Correct me, if wrong)

---------- Post added at 08:20 PM ---------- Previous post was at 08:15 PM ----------

Bro, the headset module in latest build is named brm_headsetsw.ko shouldn't it be bcm_headsetsw.ko? ;)

Just helping.
[Galaxy Y GT-S5360 Android Development] GermainZ:
PsychoGame, did you have to modify the ramdisk in order to get your kernel booting (it's not even initializing ADB for me, can't get a logcat/dmesg)? I've noticed you uploaded a ramdisk to github as well, but I'm not sure about the modifications you made.

I've also sent you a few PMs, not sure if you got them.

Any hints would be appreciated,

Thanks :)
[Galaxy Y GT-S5360 Android Development] gadgetroid:
Yes yes. :) He did edit the ramdisk to get kernel booting. ;) Standard procedure if you're not compiling a stock based kernel. ;) Or porting a closed source ROM like the Sense or TouchWiz. ;)

He's especially edited the parts where it says mount so & so partition and the fs (since he has converted it to EXT4). Look at the source code; it's well documented. ;)
[Galaxy Y GT-S5360 Android Development] GermainZ:
I get that, but the kernel isn't getting to that stage.

Normally, if what you're saying is right, and if I understand correctly, the ROM would fail to boot with the kernel - but the kernel would still start initializing normally (and ADB is one of the first things to be initialized).

Am I wrong?
[Galaxy Y GT-S5360 Android Development] :
I got this weird situation!

Most of the apps are showing of 0 Bytes and are giving FC :(

Plus, Gapps also give FC (Most of them)

Most of the System Apps give FC!

Phone, Browser, Contacts etc.
[Galaxy Y GT-S5360 Android Development] ronnieryan:
[MENTION=225651]op[/MENTION] : i would just like to ask the ff bro

1. Is kernel for CM only? or will it work for stock?

2. is it stable?

3. are the new modules good for everyday use?

thanks
[Galaxy Y GT-S5360 Android Development] PREMOLIKES:
That's Ryan again :) Stability huh ?
[Galaxy Y GT-S5360 Android Development] rio.:
i tried it on stock and custom rom bro :) works fine but init.d for me didnt function.. also the modules i currently using it on savie kernel just to test :P
[Galaxy Y GT-S5360 Android Development] gadgetroid:
Here is a nice update for you guys!

I SOLVED THE FORCE CLOSE BUG!!! :victory::victory::victory:

And unlike my previous updates, I didn't create mountpoints and mess with the partitions, Will update post later with what I exactly did to neuter the FCs. ;)

Right now, I've tested on Alpha 3 and a private MIUI v3 build, and have had no FCs for over 5 hours of usage! :D No need to go into recovery and clear stuff anymore! :D

Will update after the weekend.

Greetings

gadgetroid

---------- Post added at 01:08 AM ---------- Previous post was at 01:05 AM ----------

Even system apps on stock ROM show 0 bytes. Like the Android core. ;) Not a bug. And the FC bug is a known issue... Which I have finally fixed for now! :D
[Galaxy Y GT-S5360 Android Development] ronnieryan:
CM is near :good:
[Galaxy Y GT-S5360 Android Development] PsychoGame:
Hello everybody,

Thanks for the time everybody is taking to test my builds and the other ports like MIUI and other ports which are based on my build.

I heard that the headphone bug reappeared, this was due to a small error in my source.

The solution for this bug is to rename the file: brm_headsetsw.ko in /system/lib/modules to bcm_headsetsw.ko.

In my next build those small errors will not slip in again.

This week I continue to see if I can get Bluetooth fully working, as everyone could see in my latest build the first step has been set:).

Also I'll wait for gadgetroid to contact me on the FC bugs.

Those will be implemented in my next build as well so the stability of the next build should improve very much I hope:).

Greetings PsychoGame
[Galaxy Y GT-S5360 Android Development] :
-The 2.2 build was great but it had those graphic glitches but the build 3 has considerable improvements . Glitches now occur in only some parts of the screen like the status bar or around the corners. no great deal . (rotating the screen to get rid of them doesn't work now ...?_?)

-Bluetooth is half working it is able to scan devices and make itself is discoverable .Other devices are able to pair with it .(greatest news about cm :)).I think the problem somewhere lies in transmitting data since only other devices can be used to pair.

-The headset problem is there again but i fixed it myself (thanx for mentioning the fix in the op)

-Camera fully working (except for exposure thingy)

-Media scanning is also working

-The stock gallery app does not lag anymore.

-I don't know about the lag since i also installed adrenaline engine (cm7 is now super smooth)

-The fc close issue is irritating i tried clearing cache and dalvik cache many times and also tried fixing permissions.

-RIL and stuff completely working except when acore thingy force closes

Testing it will add more soon

Thanx for such a stable cm

Greetings

aNubhav
[Galaxy Y GT-S5360 Android Development] shree_tejas:
It isn't really important but did you see my pm? Let me know if you go ahead with it... I will help :)
[Galaxy Y GT-S5360 Android Development] gadgetroid:
The main reason why there are not many graphic glitches in the latest release was due to 16bit Transparency and surface dithering. They improve the quality, but the performance deteriorates after a few minutes of intense usage. Rotating used to work before because of the low quality of graphics (low quality means that the kernel will stick to CPU rendering, as opposed to GPU).

[MENTION=4647521]PsychoGame[/MENTION], yes I'm still working on finding the exact cause that put a stop to the FCs. ;) Will update soon. :)
[Galaxy Y GT-S5360 Android Development] lancejuson:
I want to test the rom but i get a bootloop how to fix this?
[Galaxy Y GT-S5360 Android Development] xHinne:
Download the latest Build of CM by PsychoGame and Gapps and put all of this on your Sd card. after that Download the kernel "boot.tar" Check the 1st Post :)

Now go to odin and flash Boot.tar put it on PDA.

after Flashing and bootloop, remove your battery and put it back. then go to stock recovery > cwm > Mounts and Storage > format /system, /data and /cache. go back and install zip from sd card choose cyanogenmod.zip by PsychoGame. after installation install zip again and choose gapps. Do a wipe data/factory reset from the CWM > reboot and pray :fingers-crossed:
[Galaxy Y GT-S5360 Android Development] razoraniruddh1998:
Media_profiles..

I have uploaded a media_profiles.xml. hope this works for you.. :)
[Galaxy Y GT-S5360 Android Development] gadgetroid:
You never learn, do you? Reported.
[Galaxy Y GT-S5360 Android Development] NeelDroid:
Thumbs up :)

After a long long time.. it's really good to see that It's very much close... may be it's not a dream after all!

My SGY got almost 1.5yrs old now.. I hope I get to see it running a fully functional CM7 on it before I switch it with a new phone! Cheers!:fingers-crossed:

Only if Broadcom released the drivers one yr back.. We could hv get it fully functional by now!
[Galaxy Y GT-S5360 Android Development] gadgetroid:
As an update to my FC fix, I have isolated the fix to a system.prop(?)/build.prop mod. I have been running this build for about one and a half hours, and I have had no FCs so far! :fingers-crossed: I had to restart the device before this because it started lagging like hell (this was the first boot, so I hadn't set the performance options) and that too ran for about one and a half hours too and I encountered no FCs.

If you want proof of a longer time, I initially encountered this fix when I was porting MIUI v3 based on Alpha 3 build. I ran it for over a day and never encountered a single FC!

The fix:

Add these lines below to the system.prop section. (For those who don't know where this is, the system.prop is essentially in the build.prop, and has been merged into the same file. It starts with a declaration: "system.prop for GT-S5360". Add these lines just below it.)

#deox
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.dexopt-data-only=1
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapsize=32m
dalvik.vm.checkjni=false
dalvik.vm.execution-mode=int:jit

There is much speculation about the fifth line in the above code. The heapsize is actually said to be a busted myth in the Android community. Performance does not improve or decrease, but it does solve a few FC issues. Please check if this line has already been included in the build.prop you are editing or not. If it isn't, then add it. Otherwise don't.

Search for the line:

ro.telephony.ril_class=samsung

and add this line below it:

DEVICE_PROVISIONED=1

And you're done! You can either do this yourselves, or you can wait for [MENTION=4647521]PsychoGame[/MENTION] to update his latest build with this fix. If you are doing this yourselves, then use a computer, edit the build.prop with Notepad++ (recommended) and then replace with the one in the system/ folder. Flash the build following the instructions provided in the OP. Just don't flash the Gapps yet. Clear data and reboot. Then wait for a few minutes, play around for a while and change all the performance setting that you prefer that require a reboot. After that, reboot into recovery, mount /system, /data and /cache and flash the Gapps.zip. Don't clear the data. Just reboot. And enjoy your Force Close free CyanogenMod 7. :D

Never flash files after you've just flashed CM7 in the CWM recovery. This is part of the reason that may lead to FC errors.

It seems that CyanogenMod got a wind of Psycho's project. ;)

In actuality, I added it there earlier today. :cool:
[Galaxy Y GT-S5360 Android Development] PsychoGame:
I disagree with you on the lack of importance for a 3.0 kernel version.

On our Galaxy S Plus we are still busy porting the 3.0 kernel, because it's neccesary if you want the full JB experience.

I know that ICS an JB are far away for this device yes, but if you focus on the future I think it can be important.

To change the FS of a partition is easy, that's something that I agree with you.

To change the Partition Maps from FSR to MTD is not a easy job at all.

I agree that it's more difficult to port the camera, gpu and all those other modules, but luckily the kernel modules of broadcom are opensource.

These are located in the modules folder of the Samsung opensource kernel package.

This already makes porting easier. The most difficult thing is to port the drivers within the android build itself, because ICS for example works a lot different than GB.

But on the Galaxy S Plus we also managed to overcome these difficulty's.
[Galaxy Y GT-S5360 Android Development] Apexpreadtor:
broadcom is closed source not opensource

so it is impossible to make cm 7,9,10,10.1

i have tried to compile cm 9 many times but failed to get stable they have bugs like

camera

bluetooth

hw

and wifi works but not normally
[Galaxy Y GT-S5360 Android Development] hell_lock:
had a look at kernel sources? Please dont speak anything without knowing the facts.
[Galaxy Y GT-S5360 Android Development] kentoi me:
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR

Wew.. another great dev.. even i cant relate to the topics.. but still waiting and watching u mr.OP to declaire and share ur awesome contribution..
[Galaxy Y GT-S5360 Android Development] Apexpreadtor:
broadcom gpu is still closed source