[ROM] CyanogenMod 11 [OFFICIAL] [NIGHTLIES]

[PVL_93_RU]

@temasek and others

It was a pain and took me 2 days.. ( every build takes me 5 hours, every repo sync 30 minutes, and yeah.. the merging...i dont want to count the hours
did the first time an own device tree )

but finally everything works cm10.2 for tilapia.

Will upload the build shortly but my interent is so slow so it will take a few hours

YESS!!!!!

Dude, message CM team and ask them to become a 10.2 maintainer for Tilapia - WE NEED YOU!:victory:

 

[n3ocort3x]

created an own thread now so we dont get to offtopic here as its a 10.1.X thread

http://forum.xda-developers.com/showthread.php?t=2428618

@temasek

DEVICE TREE UPLOADED :
https://github.com/n3ocort3x/android_device_asus_tilapia

 

[frozst]

I must say that I updated to the 2013 version after all the hassle with the lag and performance, and I couldn't be happier now.

Sent from my Nexus 7 using Tapatalk 4

 

[temasek]

created an own thread now so we dont get to offtopic here as its a 10.1.X thread

http://forum.xda-developers.com/showthread.php?t=2428618

@temasek

DEVICE TREE UPLOADED :
https://github.com/n3ocort3x/android_device_asus_tilapia

Thanks to @n3ocort3x I've resumed my cm builds but I'm not creating a thread here since my last tilapia thread closure.

Those who knows my download sites can go ahead and try.

And many thanks again to n3ocort3x for the tilapia device tree which points out my mistake in my failure to bring tilapia up.

Regards
Temasek

 

[n3ocort3x]

Thanks to @n3ocort3x I've resumed my cm builds but I'm not creating a thread here since my last tilapia thread closure.

Those who knows my download sites can go ahead and try.

And many thanks again to n3ocort3x for the tilapia device tree which points out my mistake in my failure to bring tilapia up.

No more post from me here.

Regards
Temasek

Why no more posts? Stay here feel free to post ur builds here. (if u want to) That's community nothing to thank I provide help where I can and also learned a lot from it

noNeedForAsig

 

[temasek]

Why no more posts? Stay here feel free to post ur builds here. (if u want to) That's community nothing to thank I provide help where I can and also learned a lot from it

noNeedForAsig

Btw u probably need a fix on mms if not it will FC, at least it's fixed at my end when I replaced basicsmsreceiver with mms and added a fix to overlay config

 

[kenkiller]

Hehe....one of the reasons for someone to be a maintainer is to be able to do delta updates. It's not always easy to download the whole package to flash often.

Yeah I'm lazy.

 

[temasek]

Thanks to @n3ocort3x I've resumed my cm builds but I'm not creating a thread here since my last tilapia thread closure.

Those who knows my download sites can go ahead and try.

And many thanks again to n3ocort3x for the tilapia device tree which points out my mistake in my failure to bring tilapia up.

Regards
Temasek

My download sites are.

temasek.hopto.org
http://d-h.st/users/temasek

Currently in Build V5

 

[gben1783]

Mount network share (nfs/cifs)

So this finally is my very first noob-post... I'm quite afraid of what's gonna happen with me after that even though I really tried my best to find a solution myself and to post to the right thread I'm quite familiar with Linux, but not (yet?) android.

Flashed official CM 10.1.2 to my Nexus 7 (it's grouper, but didn't find a 10.1 official thread over there and can't imagine it matters). I'm unable to mount a network share (either nfs or cifs) while the config looks promising to me:

In /proc/config.gz I see this:

# CONFIG_USB_FUNCTIONFS is not set
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_V4 is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFSD is not set
CONFIG_NFS_COMMON=y

and this:

CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set

/proc/filesystems is this (amongst others of course):

nodev	nfs
nodev	cifs

After modprobe cifs I get this from lsmod:

cifs 235109 0 - Live 0x00000000

For NFS the best I can get is this:

# busybox mount -o nolock -t nfs 192.168.2.25:/path/to/share /mnt/cifs
mount: mounting ... on ... failed: Protocol not supported

For CIFS it's this:

# busybox mount -o user=foo,password=bar -t cifs //192.168.2.25 /mnt/cifs
mount: mounting ... on ... failed

/mnt/cifs is root:root 777.

CIFSmanager seems to use a different mount command and yields "mount: invalid argument" (I also get this if omitting busybox on the above commands)

I'd really appreciate if anybody was able to help me on this issue or direct me somwhere else.
Thank you!

 

[jkkk88]

Only for logging: bl. 4.18, twrp recovery 2.6.0.0, update 10.1.2 -> 10.1.3 (cache and dalvik cache wiped after update)- no issues
Hopping to find free time to boot unofficial higher version from n3ocort3x...

 

[eak1080]

Majorly update OP. lots of old links fixed and new ones added because we now have OFFICIAL nightlies of CM 10.2

 

[b4b4.4l1]

Finally! \(^o^)/

 

[BeEmEroff]

here the google play won't work. is there anyone with the same prob?

 

[Exterminatus]

here the google play won't work. is there anyone with the same prob?

If it even doesn't show, and after every boot the tablet shows message like "format your data patrition", I had same problem. You should install TWRP recovery and press "Fix permissions" in advanced settings.

 

[Sengir]

Finally!
Downloading right now,thank you!

 

[gben1783]

CIFS finally working for me

For CIFS it's this:

# busybox mount -o user=foo,password=bar -t cifs //192.168.2.25 /mnt/cifs
mount: mounting ... on ... failed

Just in case it helps anybody out there... I wasn't able to get NFS up and running, but finally got CIFS working. The crucial part making the above command fail is that there's no "path" after the share's address. To make it clear, this works:

busybox mount -o user=foo,password=bar -t cifs //192.168.2.25/name_of_some_folder_on_the_share /mnt/cifs

This doesn't work:

busybox mount -o user=foo,password=bar -t cifs //192.168.2.25 /mnt/cifs

I don't see the reason for this (the //192.168.2.25 without path works for TotalCommander and ES explorer, for example) and, because of this, I need to mount every top folder of my share separately, but hey it's better than nothing

 

[bedtime_with_the_bear]

Just in case it helps anybody out there... I wasn't able to get NFS up and running, but finally got CIFS working. The crucial part making the above command fail is that there's no "path" after the share's address. To make it clear, this works:

busybox mount -o user=foo,password=bar -t cifs //192.168.2.25/name_of_some_folder_on_the_share /mnt/cifs

This doesn't work:

busybox mount -o user=foo,password=bar -t cifs //192.168.2.25 /mnt/cifs

I don't see the reason for this (the //192.168.2.25 without path works for TotalCommander and ES explorer, for example) and, because of this, I need to mount every top folder of my share separately, but hey it's better than nothing

The reason is the //192.168.2.25 only specifies the server, and gives the mount command no information whatsoever about what you want to mount, whereas TotalCommander and ES Explorer are browsing the shares presented by the server.

TL; DR: there's a difference between mounting a CIFS share and browsing the server.

Sent from my Nexus 4 using Tapatalk now Free

 

[Feenfleisch]

i have the same problem (Google play have no connection, system not mount). anyone a idea for fix this. THX.

 

[bamboocha]

No Problem here,

GooglePlay works with

cm-10.2-20131011-NIGHTLY-tilapia

 

[mathsga]

No issues so far using 20131011. Battery maybe draining too fast or need a few cycles to calibrate...