[JB+][3.0.8/2.6.32 kernel] CM10.1 Android 4.2.2 for the Defy(+)

[KairosDev]

I've been getting the same problem. Occasionally however, it works fine.

Sent from my MB526 using xda premium

 

[bharaththeunique]

Defy cm10.1 gets some Portal love..
http://www.xda-developers.com/android/unofficial-cm10-1-lands-on-the-defy-defy/

sent from my awesome DEFY+
current ROM: cm10 JB4.1.2
Kernel: latest Blechdose kernel

 

[ppero196]

Defy cm10.1 gets some Portal love..
http://www.xda-developers.com/android/unofficial-cm10-1-lands-on-the-defy-defy/

sent from my awesome DEFY+
current ROM: cm10 JB4.1.2
Kernel: latest Blechdose kernel

I might have some influence in that as I was getting on nerves of one of the writers cause post isn't out yet

Sent from my Balls of Steel

 

[neonod]

Somebody know how to fix problem with SD card ?

 

[Quarx]

It's a bad fix... 4.2 has multiuser support which made problems with sdcard(apps doesn't have permissions to read sdcard).
Android 4.2 use new mount system which require fuse fs, but we have old driver and it cause segfolts at mount fs(invalid argument)....
I think we need backport new fuse fs driver (fs/fuse) from 3.0 kernel. (Or find another way)
But not sure help it or not.

 

[thekguy]

@Quarx thanks for your amazing work on our beloved phones. I just wanted to ask about the problems faced in booting the newer kernel. I think it was a display issue. Because I feel that perhaps we should focus our efforts on the newer kernel because many things are requiring back porting for the older kernel. Thanks very much for your work once again

Sent from my MB526 using xda premium

 

[YZ]

This thread has been cleaned several times by TeeJay3800, but it seems like some people still don't understand.
The threads in the fora "Android Development" are for obviously; development. Other users trying the development are supposed to rather post bugs, or contribute for fixes. You can of course show your appreciation or recommendation, but posting "+1" and such is just cluttering the boards.
Please use the "thanks button" for that.

Thanks for reporting guys.

Cheers,
YZ.

 

[Deonix]

Can multiuser be fully disabled? I find it more useful on a tablet, let's say. Do others agree on this?
Maybe it will make it easier for quarx to develop

 

[ppero196]

Can multiuser be fully disabled? I find it more useful on a tablet, let's say. Do others agree on this?
Maybe it will make it easier for quarx to develop

Google disabled it automatically on Nexus 4 and Gnex.
Its enabled only for tablets.

Unless Cyanogenmod team wants to do somehing with it

 

[swapnil360]

I am 100% agree on this.
IMO, multiuser is practically useless on phone because a phone is usually a private device.
So, if it will also make it easier for Quarx to port 4.2.1 to our Defy, it would be great.

It wouldn't make it easier. The problem is the mounting. Until now, we used Mass Storage. Now it's MTP (fuse is the Linux MTP driver). That's the only option in 4.2 and it was implemented for multiuser Disabling multiuser won't make it easier for development. We still need that driver as Quarx said.

@Quarx
Does fuse and MTP mean that mounting Defy on a Linux machine will require setting up mtpfs (a huge pain IMO)? Does that mean we can't use Mass Storage just for mounting SD? I remember you said yourself that you use ArchLinux

Sent from my MB526 using xda premium

 

[ansontyl96]

Then is that means we need a3.0 kernel under to use a stable cm10.1?

Sent from my MB526 using xda app-developers app

 

[swapnil360]

Then is that means we need a3.0 kernel under to use a stable cm10.1?

Sent from my MB526 using xda app-developers app

Quarx said that we can
1) Use 3.0 kernel
2) Backport 3.0 kernel drivers to the current kernel
3) Something else

Sent from my MB526 using xda premium

 

[sebx_g1]

Quarx said that we can
1) Use 3.0 kernel
2) Backport 3.0 kernel drivers to the current kernel
3) Something else

Sent from my MB526 using xda premium

Do type of formating sdcard make any difference - far32 vs ext4 for example? Shouldn't be easier mount sdcard formated in native Linux format?

 

[swapnil360]

Do type of formating sdcard make any difference - far32 vs ext4 for example? Shouldn't be easier mount sdcard formated in native Linux format?

That is different. fat32 and ext4 are file systems. Mass Storage and MTP are mounting methods. Here's an example, my father's Galaxy S II mounts with MTP by default (for now). Linux requires extra steps for mounting MTP. I always have to enable Mass Storage before connecting to my PC with Linux.

Sent from my MB526 using xda premium

 

[walter79]

on early-init
    export EXTERNAL_STORAGE /storage/sdcard0
    mkdir /storage 0050 system sdcard_r
    mkdir /storage/sdcard0 0000 system system
    symlink /storage/sdcard0 /sdcard
    symlink /storage/sdcard0 /mnt/sdcard

init.rc

# See storage config details at http://source.android.com/tech/storage/
    mkdir /mnt/shell 0700 shell shell
    mkdir /storage 0050 root sdcard_r

SDCARD: This works for HTC HD2

 

[Quarx]

SDCARD: This works for HTC HD2

Yes, on RAZR it work too, but on defy it doesn't work. I have no idea why it happens.

    export EXTERNAL_STORAGE /storage/sdcard1
    export SECONDARY_STORAGE /storage/sdcard0

    mkdir /storage/sdcard0 0000 system system
    mkdir /storage/sdcard1 0000 system system

    symlink /storage/sdcard1 /sdcard-ext
    symlink /storage/sdcard1 /mnt/sdcard-ext
    symlink /storage/sdcard0 /mnt/sdcard

 

[Boss442]

Yes, on RAZR it work too, but on defy it doesn't work. I have no idea why it happens.

    export EXTERNAL_STORAGE /storage/sdcard1
    export SECONDARY_STORAGE /storage/sdcard0

    mkdir /storage/sdcard0 0000 system system
    mkdir /storage/sdcard1 0000 system system

    symlink /storage/sdcard1 /sdcard-ext
    symlink /storage/sdcard1 /mnt/sdcard-ext
    symlink /storage/sdcard0 /mnt/sdcard

why /storage/sdcard0 or sdcard1? never heard about that... why don't use /mnt/sdcard o /mnt/sdcard-ext without symlink?

like:

export SECONDARY_STORAGE /mnt/sdcard

    mkdir /mnt/sdcard 0000 system system
    mkdir /mnt/sdcard-ext 0000 system system

    symlink /mnt/sdcard-ext /sdcard-ext
    symlink /mnt/sdcard /sdcard

 

[Kayant]

Yes, on RAZR it work too, but on defy it doesn't work. I have no idea why it happens.

    export EXTERNAL_STORAGE /storage/sdcard1
    export SECONDARY_STORAGE /storage/sdcard0

    mkdir /storage/sdcard0 0000 system system
    mkdir /storage/sdcard1 0000 system system

    symlink /storage/sdcard1 /sdcard-ext
    symlink /storage/sdcard1 /mnt/sdcard-ext
    symlink /storage/sdcard0 /mnt/sdcard

Could something like this help instead??

on init
# for backwards compatibility
    # for backwards compatibility
    mkdir /mnt/shell/emulated 0700 shell shell
    mkdir /storage/emulated 0555 root root
    mkdir /storage 0550 system sdcard_r
    export EXTERNAL_STORAGE /storage/emulated/legacy
    export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
    export EMULATED_STORAGE_TARGET /storage/emulated

    # Support legacy paths
    symlink /storage/emulated/legacy /sdcard
    symlink /storage/emulated/legacy /mnt/sdcard
    symlink /storage/emulated/legacy /storage/sdcard0
    symlink /mnt/shell/emulated/0 /storage/emulated/legacy

    # Enable secondary storage
    export SECONDARY_STORAGE /storage/sdcard1

    # make the pathes for the external media mounts
    mkdir /storage/sdcard1 0000 system system
    mkdir /storage/sdcard2 0000 system system
    mkdir /storage/usbdisk0 0000 system system
    mkdir /storage/usbdisk1 0000 system system

Found it here

 

[Quarx]

Emulated storage will not work with old fuse driver.

 

[nostupidthing]

to re-say, the existing custom kernel is too outdated to support JB4.2/CM10.1, either we need backporting some new features back to 2.6.32 or update the kernel... neither one is an easy task, so it seems...

anybody can lend a hand...? (can we kang from other models that use the same CPU? like the optimus black?)