Alright, starting here in this thread you can see what I've tried to fix this:
http://forum.xda-developers.com/showthread.php?p=43218631#post43218631
My internal sdcard has been wiped and is no longer available in CWM or the OS. Have tried multiple ftf flashes from stock 2.1, 2.3 and CM10 but no luck. If I have an external sdcard in the phone while flashing it uses that as the internal space, but it's not seeing the flash memory that should be available in the actual device.
Everything works 'fine' without that space available, just that file explorers can't see it, camera can't take pictures, about what you may expect.
Anybody experience anything similar?
Been around Android a long time now and quite familiar with the ins-and-outs but this has me stumped.
Thanks!
Try Another Rom My Friend
Ronald G V A said:
Try Another Rom My Friend
Click to expand...
Click to collapse
It's definitely not just a ROM install issue as I've tried 3 or 4 different ones now and they don't fix the underlying issue.
Need to properly repartition my internal sdcard so it's visible to recovery/Android.
seanpr123 said:
It's definitely not just a ROM install issue as I've tried 3 or 4 different ones now and they don't fix the underlying issue.
Need to properly repartition my internal sdcard so it's visible to recovery/Android.
Click to expand...
Click to collapse
jaja ok Senior Member All as you said (Y)
I tried another ROM and kernel, no luck.
Anybody else have any thoughts/suggestions?
Please please
Please, anybody else have any input?
Stuck in the mud here... :-\
Hi there, if been wondering the same things and i almost sure how it works and that particular service is set from the services in one of the .rc files but we doesnt seem to have it.
Its about a binary and needs to be set from the kernels ramdisk.
This is what i found so far on info about it.
the /system/bin/sdcard binary, which mounts the /data/media folder at /mnt/sdcard and does some magic with the user/group ids. from one of the
/init.????.rc files.
This i saw in another devices .rc file.
# create virtual SD card at /mnt/sdcard, based on the /data/media directory
# deamon will drop to user/group system/media_rw after initializing
# underlying files in /data/media wil be created with user and group media_rw (1023)
service sdcard /system/bin/sdcard /data/media 1023 1023
class late_start
If i have some time i will try to set that services in x10i ramdisk with kernel to see if that will work.
Sent from my x10i
Danny23 said:
Hi there, if been wondering the same things and i almost sure how it works and that particular service is set from the services in one of the .rc files but we doesnt seem to have it.
Its about a binary and needs to be set from the kernels ramdisk.
If i have some time i will try to set that services in x10i ramdisk with kernel to see if that will work.
Click to expand...
Click to collapse
Not really following that, what are you suggesting I try?
Simply a new kernel or something else?
QUOTE=seanpr123;43754685]Not really following that, what are you suggesting I try?
Simply a new kernel or something else?[/QUOTE]
I am sorry it still not 100% clear to me.
But you need a new ramdisk inside the kernel.
And the framework-res.apk storage-list.xml needs also to be edited and recovery.fstab and vold.fstab.
And a file which we dont have some devices have it and i got it from Google search.
Its a file named "vold.conf".
I did these mods and cwm recovery is acting weird crying about log but some new options apeared and roms stil boots.
Here are few pictures of it with my gtn-n7000.
Sent from my x10i
Related
I need the community's help. I have never posted on XDA cause I have always been able to find the answers I was looking for by searching these forums. This time I am stumped. I am not a noob, but I'm also not a dev or programmer. I have managed, thanks to XDA, to unlock, root and flash a dozen different android devices I've owned without bricking any of them (I admit I'm a flash-a-holic and refuse to get treatment ).
I have a TFP (201) that refuses to download anything from anywhere except the Google Play Store. Cannot download via browser, Amazon app store, Goo Manager, Rom Manager or any other means. In each case it almost immediately tells me that the download was unsuccessful or download errored. I have done dozens of searches and have tried an equal number of so-called fixes with no luck. I have tried every custom rom on the forum, have switched between CWM and TWRP. I have flashed previous backups from TWRP. All to no avail.
Two other issues that may be related; 1- when i run the fix permissions script from inside Rom Manager or from Recovery screen, I get a "an error occurred while attempting to run priviliged commands!" 2- in CWM, when I try to flash older nandroid backups, it tells me that the files are not valid because it can't find the checksum (MD5) corresponding file.
I am currently running aokpcb_tf201_r2.1 with the kernel it comes with, everything else works except no downloading.
Any help would be greatly appreciated.
Can you check to see if your internal SdCard folder has the correct permissions using root explorer? I forget the details of exactly where it is, as I dont have my prime with me, however it is a folder within /data partition... something like /data/media/sdcard or something of that nature.
GooglePlay I believe uses the /cache partition for its downloads, thus I believe these are not throwing errors, whilst everything else is done into the internal sdcard folder.
Same oribkem
kokopuphz said:
Can you check to see if your internal SdCard folder has the correct permissions using root explorer? I forget the details of exactly where it is, as I dont have my prime with me, however it is a folder within /data partition... something like /data/media/sdcard or something of that nature.
GooglePlay I believe uses the /cache partition for its downloads, thus I believe these are not throwing errors, whilst everything else is done into the internal sdcard folder.
Click to expand...
Click to collapse
having the same problem , and you solution didn't work man .
kokopuphz said:
Can you check to see if your internal SdCard folder has the correct permissions using root explorer? I forget the details of exactly where it is, as I dont have my prime with me, however it is a folder within /data partition... something like /data/media/sdcard or something of that nature.
GooglePlay I believe uses the /cache partition for its downloads, thus I believe these are not throwing errors, whilst everything else is done into the internal sdcard folder.
Click to expand...
Click to collapse
This seemed to work. If you go to data/media/download and change the permissions this should fix the problem. I was unable to download anything using any browser or an email attachment.
Sent from my Transformer Prime TF201 using xda app-developers app
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
pavitar said:
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
Click to expand...
Click to collapse
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
ricky310711 said:
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
Click to expand...
Click to collapse
Can you please tell me, how to apply a file permission? I tried checking the box which is not checked in the snapshot shared, but that too gives an error.Says "Operation failed"
pavitar said:
Can you please tell me, how to apply a file permission?
Click to expand...
Click to collapse
download mobile terminal from playstore
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
pavitar said:
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
Click to expand...
Click to collapse
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
iamareebjamal said:
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Click to expand...
Click to collapse
pavitar said:
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
Click to expand...
Click to collapse
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
iamareebjamal said:
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
Click to expand...
Click to collapse
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
pavitar said:
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
Click to expand...
Click to collapse
Try this
https://play.google.com/store/apps/...&utm_medium=organic&utm_term=universal+init.d
with the massive overhaul that is kitkat, google changed alot of files, and therefore a new way must be discovered to switch internal/external storages.
The editing vold.fstab option from 4.1-4.2 no longer works as vold.fstab was removed in 4.3, and the editing build.prop method for 4.3 no longer works.
Anyone know how to do it for 4.4?
thanks in advance
No Luck So Far
Been working for hours trying to figure this one out. Things to note is that now there are two mount points.
1) /mnt/media_rw/sdcard1 / sdcard0 (this has the actual /dev/block/vold/179:1 origin
2) /dev/fuse /storage/sdcard1 / sdcard 0
I've been unsuccessful trying any of the old build.prop tweaks. Hopefully someone smarter will come along and bang this one out.
Bump..... Stuck on 4.3 till a solution arises
Sent from my GT-I9100 using XDA Premium 4 mobile app
I've asked the compiler of the NeatKernel if he would fork it and swap out the sdcards in fstab.aries, but have yet to receive a reply....
Perhaps if you two went and posted the same, it might motivate him to do so.
Me too
alkspo said:
Bump..... Stuck on 4.3 till a solution arises
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You got Company!
vivin007 said:
You got Company!
Click to expand...
Click to collapse
Same here! I upgraded to 4.4 and then realised that the build.prop 's changes made in 4.3 doesn't work for 4.4. Downgrading to 4.3 till there is a solution.
Still no "real" solution. but pretty convenient for me.
@fusionjack integrated swap option in the rom i was using which is slimsaber, so now i have swap
unfortunately, its only for this rom unless other rom makers incorporate it as well
alkspo said:
Still no "real" solution. but pretty convenient for me.
@fusionjack integrated swap option in the rom i was using which is slimsaber, so now i have swap
unfortunately, its only for this rom unless other rom makers incorporate it as well
Click to expand...
Click to collapse
Good news, so it's not impossible, it's just about time to see the swap method for 4.4 floating around.
I found an application that allows you to move the data from games to external sdcard, but you have to run the game through the application to play it though. Its called gl to sd, your phone must be rooted though.
Sent from my GT-I9100 using xda app-developers app
anatoliy0813 said:
I found an application that allows you to move the data from games to external sdcard, but you have to run the game through the application to play it though. Its called gl to sd, your phone must be rooted though.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yeah I know it, but DirectoryBind is better m8. Once it moves and link the data to external you can forget about it.
I've been trying to swap the storage on my note 2 on 4.3 can abtobetell me how to do this tried so many methods and nothing works. I would really appreciate some help guys. Thanks in advance
bigevil124 said:
I've been trying to swap the storage on my note 2 on 4.3 can abtobetell me how to do this tried so many methods and nothing works. I would really appreciate some help guys. Thanks in advance
Click to expand...
Click to collapse
Try file, called "fstab.sun6i" in / folder. I keep trying, but all the changes, I made was unstable...If I'll make some progress I'll write it down
Hi im not sure if this helps but someone released a script for cm11 to swap sdcards. Worked fine on resurection for me all I tested.the thread is somewhere in galaxy2 forum I posted to his thread so one of my last replys. I will find the link and edit
http://forum.xda-developers.com/showthread.php?t=2595756
Sent from my GT-I9100 using XDA Premium HD app
swap internal sd to external
Hello
did anyone come up to a solution for this or have any info about it?
i want to swap mine too and nothing seems to work on Kitkat
thank you
rictec said:
Hello
did anyone come up to a solution for this or have any info about it?
i want to swap mine too and nothing seems to work on Kitkat
thank you
Click to expand...
Click to collapse
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
tried that but it failed
seb_131 said:
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
Click to expand...
Click to collapse
thank you for you reply i already try that had some trouble to flash back the boot and when i manage to do it fstab got ignored
i m currently doing that with a boot script but have to run it every time the table reboots
its not a samsung is a storex A31 based device
rictec said:
thank you for you reply i already try that had some trouble to flash back the boot and when i manage to do it fstab got ignored
i m currently doing that with a boot script but have to run it every time the table reboots
its not a samsung is a storex A31 based device
Click to expand...
Click to collapse
You have to look for the dev kit dedicated to your processor. Have a look there : http://www.slatedroid.com/topic/73913-onda-kitchen-a31-a31s/
I have a mtk based device. I found the tools in this forum. I edited the 3 fstab.* files I found, and then all worked fine.
thank you
seb_131 said:
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
Click to expand...
Click to collapse
seb_131 said:
You have to look for the dev kit dedicated to your processor. Have a look there : http://www.slatedroid.com/topic/73913-onda-kitchen-a31-a31s/
I have a mtk based device. I found the tools in this forum. I edited the 3 fstab.* files I found, and then all worked fine.
Click to expand...
Click to collapse
i have those thank you did not wanted to do a entire img just to change some files on boot but it looks like i have to maybe i do some more twicks and be great
Foldermount maybe a good solution
alkspo said:
with the massive overhaul that is kitkat, google changed alot of files, and therefore a new way must be discovered to switch internal/external storages.
The editing vold.fstab option from 4.1-4.2 no longer works as vold.fstab was removed in 4.3, and the editing build.prop method for 4.3 no longer works.
Anyone know how to do it for 4.4?
thanks in advance
Click to expand...
Click to collapse
Before 4.4 I could do it by "Android Internal to External sdcard" app, but this app couldn't do the trick on 4.4 KitKat OS, so "Foldermount" could be a good solution for you. All this app does is make a image of your apps (that you want to) to sdcard. The real files are located in external sdcard and only the clone file ( of max few KB) will residue at internal sdcard. If you are a gamer, this will help you until the real solution arrives.
Good Luck.
There is real solution! Or at least it works for me.
biopsin said:
Since Android 4.2 and the intro of multiusers there is a problem with bind folders across sdcards, making any attempt on mount bind folders as root would result in visible to root only.
Solution is to fool Android with temporary hijack debuggerd to create the mount binds for us. Thanks Chainfire for this workaround!
* Download both files and rename without .txt
* edit debuggerd.mnt to suit your needs (using any other dir then /emulated/legacy/ will result in read only if browsing folders from sdcard0)
* move debuggerd.mnt to /system/bin
* move mount.sh to any place with execute permissions
* execute mount.sh with any preferred method.
cheers!
Click to expand...
Click to collapse
Quoted from http://forum.xda-developers.com/showthread.php?t=2718760.
Thank You biopsin! Thank You Chainfire!
I'm including my files, but 'mount.sh' was not really changed in practical sense.
In case of 'debugger.mnt' it all depends on Your device. You need to check which block for You is internal and which external storage. Just 'mount' command should help.
You can also use it to mount only one folder - like 'obb', which will let You keep applications data on external card.
Just use "mount -o bind /storage/sdcard1/Android /obb /storage/sdcard0/Android/obb" command in debuggerd.mnt file.
You can also have different 'debuggerd.mnt' files (of course called somehow different - like 'debuggerd02.mnt') and different 'mount.sh' files which will let You mount different things whenever You like.
Enjoy!
-----
And for easier usage You can try $cripter - https://play.google.com/store/apps/details?id=sites.mjwhitta.scripter&hl=en .
It's the best I found.
Hello XDA community for the GPs,
some of you may heard about my project to port CyanogenMod 7.2 to the Galaxy Player 3.6.
The thing is.. I got it successfully compiled and installed on my player but it won't boot (it is stuck at zygote).
So I thin here are some really good CM porters and experts which could may help ... so...
Please be a community and help me a bit
The poor thing is that I'm the only dev for this device.
Here are some files...
If you need more information or files.. LET ME KNOW!
Here's the init.rc which I'm using to boot (I used the stock one as a base to write a new init.rc)
http://pastebin.com/nbkubMyx
That's the init.<devicename>.rc (devicename: aalto) (I fixed some things on the kernel so it gets executed)
http://pastebin.com/g0FxQUja
That's the logcat which gets made via init.rc (service: logcat)
http://pastebin.com/bN4yfPiq
Here's the logcat which gets made via ADB
https://www.dropbox.com/s/j1zbganc8whowly/log
Device tree
https://github.com/androthan/android_device_samsung_aalto
Thanks for any help in advance
If the 3.6 is anything like 5.0, the stock gingerbread had much more in it's initramfs than CM puts in there. Alot of the paths in the stock init.rc and init.(device).rc may point to locations expected to be there in the initramfs which cm has moved to the /system dir. You might want to try looking at the init.rc and init.(device).rc for a device that has a similar partition layout( and CM7 working). Maybe use that as a base instead of stock init.rc???
I've never built CM7. I'm actually pretty new to building CM but it looks like you've got mount point problems....
Hope this helps
Meticulus said:
If the 3.6 is anything like 5.0, the stock gingerbread had much more in it's initramfs than CM puts in there. Alot of the paths in the stock init.rc and init.(device).rc may point to locations expected to be there in the initramfs which cm has moved to the /system dir. You might want to try looking at the init.rc and init.(device).rc for a device that has a similar partition layout( and CM7 working). Maybe use that as a base instead of stock init.rc???
I've never built CM7. I'm actually pretty new to building CM but it looks like you've got mount point problems....
Hope this helps
Click to expand...
Click to collapse
Yeah that's what I've seen. Though here's a beginning for what you can do @Androthan
1. Make a cleaner vold.fstab (yours look like stock samsung crap, even vold can't read it as per your logcat says ), you can base yourself here: https://github.com/dhiru1602/android_device_samsung_galaxysl/blob/gingerbread/etc/vold.fstab
Also you can remove that sdcard mounting in your init.rc as it is already supposed to be mounted with vold.
2. Looks like from the log that your device can't access dalvik cache needed for the apps. Here's a commit I've found that will replace the path location from /cache to /dbdata. Though perhaps it would be better if it could be /cache. For this I would need to check dmesg as well to see if something haven't broke during the process. Here's the commit for the path change in case you need it:
https://github.com/dhiru1602/android_device_samsung_galaxysl/commit/5c2a2a54541448565a8d2418cfd75a1a4882342d
My guess would be that maybe cache doesn't get mounted right but it's not only logcat that can tell me this.
Hope it helps!
EDIT: Looks like it's better to use /data for dalvik-cache instead of /cache then make a symlink to it as per the commit says...
This commit shows how mounting was done in for the 5.0 in CM7 : https://github.com/ambrice/android_...mmit/891c1f59058d4d7e082d44ca40f9fcf3addd6188 . Not exactly sure how far @ambrice got with CM7 though...
I know that the partition table is different for 3.6 but I thought it might give you an idea of how it's should be.
EDIT: I should mention that in the 5.0, we try to mount ext4 first but we fail back to rfs if we can't mount ext4....
Another thing I noticed is that you are trying to mount mmcblk0p1. I don't know how it is on the 3.6 but on the 5.0 that partition represents the entire extended partition and I don't think it can actually be mounted....
Meticulus said:
This commit shows how mounting was done in for the 5.0 in CM7 : https://github.com/ambrice/android_...mmit/891c1f59058d4d7e082d44ca40f9fcf3addd6188 . Not exactly sure how far @ambrice got with CM7 though...
I know that the partition table is different for 3.6 but I thought it might give you an idea of how it's should be.
EDIT: I should mention that in the 5.0, we try to mount ext4 first but we fail back to rfs if we can't mount ext4....
Another thing I noticed is that you are trying to mount mmcblk0p1. I don't know how it is on the 3.6 but on the 5.0 that partition represents the entire extended partition and I don't think it can actually be mounted....
Click to expand...
Click to collapse
The mmcblk0p1 is the efs partition which is why it is needed to be mounted as reperesented here:
https://github.com/zaclimon/initramfs-ypgs1/blob/master/init.aalto.rc#L68
However he looks like he doesn't put the mounting flags to his partition so that to be done as well. Also those devices mounts as ext4 by default as well.
Meticulus said:
If the 3.6 is anything like 5.0, the stock gingerbread had much more in it's initramfs than CM puts in there. Alot of the paths in the stock init.rc and init.(device).rc may point to locations expected to be there in the initramfs which cm has moved to the /system dir. You might want to try looking at the init.rc and init.(device).rc for a device that has a similar partition layout( and CM7 working). Maybe use that as a base instead of stock init.rc???
I've never built CM7. I'm actually pretty new to building CM but it looks like you've got mount point problems....
Hope this helps
Click to expand...
Click to collapse
zaclimon said:
Yeah that's what I've seen. Though here's a beginning for what you can do @Androthan
1. Make a cleaner vold.fstab (yours look like stock samsung crap, even vold can't read it as per your logcat says ), you can base yourself here: https://github.com/dhiru1602/android_device_samsung_galaxysl/blob/gingerbread/etc/vold.fstab
Also you can remove that sdcard mounting in your init.rc as it is already supposed to be mounted with vold.
2. Looks like from the log that your device can't access dalvik cache needed for the apps. Here's a commit I've found that will replace the path location from /cache to /dbdata. Though perhaps it would be better if it could be /cache. For this I would need to check dmesg as well to see if something haven't broke during the process. Here's the commit for the path change in case you need it:
https://github.com/dhiru1602/androi...mmit/5c2a2a54541448565a8d2418cfd75a1a4882342d
My guess would be that maybe cache doesn't get mounted right but it's not only logcat that can tell me this.
Hope it helps!
EDIT: Looks like it's better to use /data for dalvik-cache instead of /cache then make a symlink to it as per the commit says...
Click to expand...
Click to collapse
Thank you both for answering my thread
I used the init.rc from <cmsource>/system/core/rootdir and added the things from the stock init.rc. I also cleaned up init.aalto.rc and modified it to work with CM.
I already tried to symlink /cache/dalvik-cache and /data/dalvik-cache
but this doesn't fixed my issue that it can't create the DEX caches.
I think I'll have to fix...
... the vold.fstab (like you said)
... Add some folders to ramdisk
... libaudio.so (libaudio doesn't get located but its needed to start the system server
... Figure why it doesn't mount cache
... Figurebwhy dbus can't find etc/dbus.conf (even when /system/etc is symlinked to /etc)
BTW, zaclimon you said you need a 'dmesg'. What is it and how can I get it?
Thanks, Androthan
Sent from my Nexus 7 using xda app-developers app
Androthan said:
Thank you both for answering my thread
I used the init.rc from <cmsource>/system/core/rootdir and added the things from the stock init.rc. I also cleaned up init.aalto.rc and modified it to work with CM.
I already tried to symlink /cache/dalvik-cache and /data/dalvik-cache
but this doesn't fixed my issue that it can't create the DEX caches.
I think I'll have to fix...
... the vold.fstab (like you said)
... Add some folders to ramdisk
... libaudio.so (libaudio doesn't get located but its needed to start the system server
... Figure why it doesn't mount cache
... Figurebwhy dbus can't find etc/dbus.conf (even when /system/etc is symlinked to /etc)
BTW, zaclimon you said you need a 'dmesg'. What is it and how can I get it?
Thanks, Androthan
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thing is the approach for the dalvik cache is different from the one you maybe made. This one implies that you make a dalvik-cache folder inside /dbdata which is in /data, then symlink it to make it /cache/dalvik-cache as well. For the moment these are the most important. Also as for cache, I didn't say that it won't mount it, I said that maybe it won't mount it because of some issues unless the dalvik-cache isn't made here.
Also the dmesg is the kernel log (it's basically a logcat but from a kernel side instead, here you can see how the kernel make it's initialization. You can have it either with this:
adb shell dmesg > dmesg.log
A proc/last_ksmg is a dmesg too but from the previous boot.
It's better to do one at a time then fix the other things after (this way you could get other problems than the one you have already)
Androthan said:
Thank you both for answering my thread
I used the init.rc from <cmsource>/system/core/rootdir and added the things from the stock init.rc. I also cleaned up init.aalto.rc and modified it to work with CM.
I already tried to symlink /cache/dalvik-cache and /data/dalvik-cache
but this doesn't fixed my issue that it can't create the DEX caches.
I think I'll have to fix...
... the vold.fstab (like you said)
... Add some folders to ramdisk
... libaudio.so (libaudio doesn't get located but its needed to start the system server
... Figure why it doesn't mount cache
... Figurebwhy dbus can't find etc/dbus.conf (even when /system/etc is symlinked to /etc)
BTW, zaclimon you said you need a 'dmesg'. What is it and how can I get it?
Thanks, Androthan
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Here is the dmesg man:
http://unixhelp.ed.ac.uk/CGI/man-cgi?dmesg+8
Normally you could get a dmesg by being root and typing dmesg > nameoffile.log but you'd need to be in a directory that you can write to for that. You can type dmesg as root in the shell and it will output to the screen...
I normally just
adb root
adb shell
dmesg
EDIT: Sorry @zaclimon, I didn't think you were going to answer
Meticulus said:
Here is the dmesg man:
http://unixhelp.ed.ac.uk/CGI/man-cgi?dmesg+8
Normally you could get a dmesg by being root and typing dmesg > nameoffile.log but you'd need to be in a directory that you can write to for that. You can type dmesg as root in the shell and it will output to the screen...
I normally just
adb root
adb shell
dmesg
EDIT: Sorry @zaclimon, I didn't think you were going to answer
Click to expand...
Click to collapse
Haha ya well perhaps it wouldn't have worked if he didn't made adb root so I guess this is a team work after all.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
zaclimon said:
Haha ya well perhaps it wouldn't have worked if he didn't made adb root so I guess this is a team work after all.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Click to expand...
Click to collapse
Meticulus said:
Here is the dmesg man:
http://unixhelp.ed.ac.uk/CGI/man-cgi?dmesg+8
Normally you could get a dmesg by being root and typing dmesg > nameoffile.log but you'd need to be in a directory that you can write to for that. You can type dmesg as root in the shell and it will output to the screen...
I normally just
adb root
adb shell
dmesg
EDIT: Sorry @zaclimon, I didn't think you were going to answer
Click to expand...
Click to collapse
Thanks for the tip and the explanation of dmsg.
I'm now testing a new build with the following changes :
- added lines to init.rc "export ANDROID_CACHE /cache and export DOWNLOD_CACHE /cache/download"
- Added mounting flags (for example: nodev,noexec,wait...)
- symlinked /dbdata/dalvik-cache /cache/dalvik-cache
Another question... Do I have to use the libaudio.so library (and libasound.so) from the device (proprietary way) or can I use the libaudio which gets compiled with CM7 (ALSA sound) ?
Greetings, Androthan
Sent from my Nexus 7 using xda app-developers app
Androthan said:
...
Another question... Do I have to use the libaudio.so library (and libasound.so) from the device (proprietary way) or can I use the libaudio which gets compiled with CM7 (ALSA sound) ?
...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I honestly don't know but If I were you, I'd do which ever one worked and if they both worked, then I'd do which ever one worked better...:cyclops:
Androthan said:
Thanks for the tip and the explanation of dmsg.
I'm now testing a new build with the following changes :
- added lines to init.rc "export ANDROID_CACHE /cache and export DOWNLOD_CACHE /cache/download"
- Added mounting flags (for example: nodev,noexec,wait...)
- symlinked /dbdata/dalvik-cache /cache/dalvik-cache
Another question... Do I have to use the libaudio.so library (and libasound.so) from the device (proprietary way) or can I use the libaudio which gets compiled with CM7 (ALSA sound) ?
Greetings, Androthan
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
As meticulus said, I'd probably test which one sound better but it would be better to use the open source variant. Though it would be better as I said earlier to make the thing booting first.
As for the dalvik cache, be sure to make a directory in dbdata before symlink it to /cache.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Androthan said:
Thank you both for answering my thread
I used the init.rc from <cmsource>/system/core/rootdir and added the things from the stock init.rc. I also cleaned up init.aalto.rc and modified it to work with CM.
I already tried to symlink /cache/dalvik-cache and /data/dalvik-cache
but this doesn't fixed my issue that it can't create the DEX caches.
I think I'll have to fix...
... the vold.fstab (like you said)
... Add some folders to ramdisk
... libaudio.so (libaudio doesn't get located but its needed to start the system server
... Figure why it doesn't mount cache
... Figurebwhy dbus can't find etc/dbus.conf (even when /system/etc is symlinked to /etc)
BTW, zaclimon you said you need a 'dmesg'. What is it and how can I get it?
Thanks, Androthan
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So, I reworked some things and fixed...
... vold.fstab (rewrote it)
... dbus.conf (deleted etc in the ramdisk)
... dalvik-cache (the rootfilesystem '/' system was mounted as 'read only' so we hadn't the right permissions // symlinked /cache/dalvik-cache and /dbdata/dalvik-cache )
My/Our problem is now the libaudio.so:
It is needed to load the SystemServer.
I'm actually using the stock libaudio files (libaudiopolicy.so, libaudioflinger.so, libasound.so, libsoundpool.so,...) but theres an error in libaudio.so , something doesn't get located.
Some websites are saying that libaudio.so contains the proprietary code (HAL implementation) for the audio device (like libcamera.so for the camera).
How to fix that? Did I missed a proprietary file?
Greetings, Androthan
Androthan said:
So, I reworked some things and fixed...
... vold.fstab (rewrote it)
... dbus.conf (deleted etc in the ramdisk)
... dalvik-cache (the rootfilesystem '/' system was mounted as 'read only' so we hadn't the right permissions // symlinked /cache/dalvik-cache and /dbdata/dalvik-cache )
My/Our problem is now the libaudio.so:
It is needed to load the SystemServer.
I'm actually using the stock libaudio files (libaudiopolicy.so, libaudioflinger.so, libasound.so, libsoundpool.so,...) but theres an error in libaudio.so , something doesn't get located.
Some websites are saying that libaudio.so contains the proprietary code (HAL implementation) for the audio device (like libcamera.so for the camera).
How to fix that? Did I missed a proprietary file?
Greetings, Androthan
Click to expand...
Click to collapse
Logs?
Androthan said:
So, I reworked some things and fixed...
... vold.fstab (rewrote it)
... dbus.conf (deleted etc in the ramdisk)
... dalvik-cache (the rootfilesystem '/' system was mounted as 'read only' so we hadn't the right permissions // symlinked /cache/dalvik-cache and /dbdata/dalvik-cache )
My/Our problem is now the libaudio.so:
It is needed to load the SystemServer.
I'm actually using the stock libaudio files (libaudiopolicy.so, libaudioflinger.so, libasound.so, libsoundpool.so,...) but theres an error in libaudio.so , something doesn't get located.
Some websites are saying that libaudio.so contains the proprietary code (HAL implementation) for the audio device (like libcamera.so for the camera).
How to fix that? Did I missed a proprietary file?
Greetings, Androthan
Click to expand...
Click to collapse
Well as a temporary solution you could use the one found in the stock rom and then copy it to your vendor files so it can be copied into your lib folder. This way it'll work no problem. Also as @Meticulus said, a bunch of logs is always appreciated.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Good afternoon. As the 8 GB aren't enough for me, I've been looking for a solution. While doing so, I found the INT2EXT4 script, which mounts /data on the second partition of the SD card. The first time I flashed it (after enabling init.d support with an app) it didn't work at all. Then, I realised this script is written assuming that the second partition of the card is mmcblk0p2. But on the M4, it's mmcblk1p2 (found it out with another app).
I changed those lines on the script, but it didn't work either. I analyzed all the lines, and I can't see where the problem could be. Has anyone tried this, or could somebody help me with this issue? I think it could be really useful for a lot of users.
Another thing: flashing the file through TWRP gave me an error, so I copied the file directly to /system/etc/init.d and set the permissions manually. I hope this is not a problem, but let me know if it could be...
sounds interesting... ill take a look at it soon!
Have you checked the "adress" of internal sd? In the script there is a connection between internal and external storage so i would assume that both "adresses" need to be correct in order for the script to work. Just an opinion....
Sent from my SM-G901F using XDA Free mobile app
vader20 said:
Have you checked the "adress" of internal sd? In the script there is a connection between internal and external storage so i would assume that both "adresses" need to be correct in order for the script to work. Just an opinion....
Sent from my SM-G901F using XDA Free mobile app
Click to expand...
Click to collapse
several1989 said:
sounds interesting... ill take a look at it soon!
Click to expand...
Click to collapse
I think there's a problem with the commands that the script uses. If I try to do umount from the terminal, nothing happens. So maybe the script doesn't work in this phone, but if any of you are able to make it do so, let me know. So I think it's better to build the kernel from source, but before that make changes in the fstab file. With that, /data will be mounted at the second partition of the sdcard directly at boot time. Trying to do this now, but I'm facing some difficulties building the kernel. If I make it work, I'll post it
Testé folder Mouth playstore