[HACK][HOW-TO] Fix lags w/ ext3 sd partition on STOCK firmware. 6 Aug 2010

[HACK][HOW-TO] Fix lags w/ ext3 sd partition on STOCK firmware. 6 Aug 2010 - Captivate Android Development

DISCLAIMER
DO IT ON YOUR OWN RISK.
ME OR ANYONE ELSE ON THIS FORUM IS NOT RESPONSIBLE FOR BRICKED/DEAD DEVICES AND/OR DEAD SD CARDS.
YOU SHOULD UNDERSTAND EVERY STEP IN THIS HOW-TO BEFORE ATTEMPTING TO FOLLOW.
INFO
This fix/hack mounts second ext3 partition of your EXTERNAL SD card at startup and binds /data/data and /data/dalvik-cache to it. This will give you ~1400 Quadrant score on the stock ROM with AT&T bloatware.
This fix/hack is based on the anomalous3 info posted here
anomalous3 said:
An explanation of how this was done:
When looking through the init.rc, I realized that there was only one thing running as root that could safely be replaced; the boot logo player. So, all this does is replace the boot logo player with a script that calls userinit.sh from /data/local and then calls the (now renamed) bootlogo player for those of you who want that nifty startup screen
A super simple (and slightly dirty) hack but I figured it might come in handy for those of us who are impatient and would like to do our own tweaks.
Click to expand...
Click to collapse
PREREQUISITES
1. This guide was tested on complete STOCK ROM. If you need to revert use Odin3 One-Click Downloader
2. You will need root on your device. [How To] Root
3. Make sure you have latest busybox (I have v1.17.1), search market for "busybox" or use this qrcode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. You should have adb working until someone will help me figuring out how to pack in handy update.zip
5. You need sdcard with first partition fat32 and second partition ext3. I use 6.5Gb fat and 1.5Gb ext3 (I never tested, but it was mentioned in Mimocan thread DO NOT CREATE BIGGER THAN 1.9Gb EXT PARTITION)
HOW-TO
Step -1. I strongly advise to Backup your ROM (Use Rom Manager)
Step 1. Download and Unpack attached lagfix.zip
Step 2. Copy into root of Internal sdcard or push files using adb:
Code:
adb push playlogos1 /sdcard
adb push userinit.sh /sdcard
Step 3. Backup stock boot logo using adb:
Code:
adb pull /system/bin/playlogos1 playlogos1.bak
Step 4. ADB shell to device and became a root
Code:
adb shell
$ su
#
Step 5. Remount root filesystem as rw
Code:
busybox mount -o remount,rw -t rootfs /
Someone please advise if this step is necessary
Step 6. Rename stock boot logo:
Code:
mv /system/bin/playlogos1 /system/bin/playlogosnow
Step 7. Copy playlogos1 and userinit.sh and fix permissions:
Code:
cp /sdcard/playlogos1 /system/bin/playlogos1
cp /sdcard/userinit.sh /system/bin/userinit.sh
chmod 755 /system/bin/playlogos1
chmod 755 /system/bin/userinit.sh
Step 8. Remount root filesystem as ro
Code:
busybox mount -o remount,ro -t rootfs /
Step 9. Reboot and verify fix:
Code:
$ su
# ls /sd-ext
data
dalvik-cache
TROUBLESHOOTING
- If you do not have /sd-ext after reboot - script is not working
- If content of /sd-ext is empty I bet you are using old busybox
REVERT FIX
Note: Due to userinit script, I have to play with it in order to revert script changes. Will do it this weekend.
Code:
adb shell
$ su
busybox mount -o remount,rw -t rootfs /
cd /system/bin/
rm playlogos1
mv /system/bin/playlogosnow /system/bin/playlogos1
busybox mount -o remount,ro -t rootfs /
Thanks to everyone involved including, but not limited to: designgears, Koush, anomalous3 and NukaCola

Change log:
06/08/2010 Added revert step
06/08/2010 Initial release

Okay, am i the only person having problems creating partitions for sd on ubuntu everytime i try it says card damaged error.

Gparted boot disk works for me....
Does this script have shutdown scripts in it or no? I guess it is just like the Vibrant script?
Is there also a 130MB limit for apps like in the other fix?
Any other gotchas?

mykenyc said:
Okay, am i the only person having problems creating partitions for sd on ubuntu everytime i try it says card damaged error.
Click to expand...
Click to collapse
Hm... I never did this way but it should work.
Try to do so with ROM Manager:
Choose Partition SD card.
Choose your ext size (I suggest 512Mb)
Choose swap as 0.
Let me know if it works for you.
I used parted to create fat and ext2 and then upgraded to ext3 under ubuntu.

alphadog00 said:
Does this script have shutdown scripts in it or no? I guess it is just like the Vibrant script?
Is there also a 130MB limit for apps like in the other fix?
Any other gotchas?
Click to expand...
Click to collapse
All the script do is injects call to userinit and then call usual boot logo player.
userinit provided is from justanothercrowd work or even from app2sd earlier.
It is completely uncanged from the vibrant version and it looks great.
This script is:
1. /sd-ext if needed
2. mounts mmcblk1p2 to it
3. if not here binds /data/data as /sd-ext/data
4. if not here binds /data/dalvik-cacheas /sd-ext/dalvik-cache
magic done.
Also, there is only possible 2gb limit (mentioned in mimocan thread at modaco, I never tried to create more then 2Gb)

XorZone said:
All the script do is injects call to userinit and then call usual boot logo player.
userinit provided is from justanothercrowd work or even from app2sd earlier.
It is completely uncanged from the vibrant version and it looks great.
This script is:
1. /sd-ext if needed
2. mounts mmcblk1p2 to it
3. if not here binds /data/data as /sd-ext/data
4. if not here binds /data/dalvik-cacheas /sd-ext/dalvik-cache
magic done.
Also, there is only possible 2gb limit (mentioned in mimocan thread at modaco, I never tried to create more then 2Gb)
Click to expand...
Click to collapse
I was reading the last page of the vibrant thread, and he mentioned still wanting to add unmount commands and such for shutdown.
I am assuming that there is not mic issue as in the other version?
Has anyone tested yet with real DB IO? The other fix had boosted Quadrant scores, but still had terrible.
Just curious if anyone did any real world tests yet.

Thanks i appreciate everyone work but i give up on this lag fix stuff/gps fix/or antenna issues that's not working for me. I'm just going to get the blackberry torch, and when Samsung update everything or we get more development i will be back. And i will use my second line to buy another captivate. So be back soon my android brothers happy hacking!

alphadog00 said:
I was reading the last page of the vibrant thread, and he mentioned still wanting to add unmount commands and such for shutdown.
I am assuming that there is not mic issue as in the other version?
Has anyone tested yet with real DB IO? The other fix had boosted Quadrant scores, but still had terrible.
Just curious if anyone did any real world tests yet.
Click to expand...
Click to collapse
I will update it as soon as they will add more info or update a script.
I didn't and probably will not do any "realworld" testing as I fill it is boosted and better.
It's up to you if to use it.
No mic problems because kernel is stock.

mykenyc said:
Thanks i appreciate everyone work but i give up on this lag fix stuff/gps fix/or antenna issues that's not working for me. I'm just going to get the blackberry torch, and when Samsung update everything or we get more development i will be back. And i will use my second line to buy another captivate. So be back soon my android brothers happy hacking!
Click to expand...
Click to collapse
Well. I do not have any issues with GPS/MIC and lag now.
Pretty happy with the device. Only kernel source problem annoying, but never thought to regret the deal.
It's your decision. Farewell. Take it easy, there are more important things then cell phones

XorZone said:
Well. I do not have any issues with GPS/MIC and lag now.
Pretty happy with the device. Only kernel source problem annoying, but never thought to regret the deal.
It's your decision. Farewell. Take it easy, there are more important things then cell phones
Click to expand...
Click to collapse
No i'm not bashing this, trust me cell phones not my life. But for me this is my second captivate my antenna is my biggest problem it goes up and down like wild fire trying to be put out. My dad own a BB on ATT and his bars never go crazy in our apartment. I was trying to hold out to see if we would have a fix by now but its effecting my livelihood, and once that happens then i got to make a change. I don't get the lag but i do get times where text messages literally take (upon power on) 20 minutes to shoot in, i tried different sims and this my second captivate like i said. But i'm not going to hijack your thread just wanted to say i appreciate the attempts.
but hey if something happens before the torch come out i will def stay...
good luck bro

Has anyone confirmed voice quality still good after this mod?
Sent from my SAMSUNG-SGH-I897 using XDA App

larry996 said:
Has anyone confirmed voice quality still good after this mod?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I don't see any reason why there would be. You're still using the stock kernel. All the voice quality problems come from building a custom kernel. The kernels we were given by Samsung weren't entirely proper, so we're seeing some errors...

Fortune090 said:
I don't see any reason why there would be. You're still using the stock kernel. All the voice quality problems come from building a custom kernel. The kernels we were given by Samsung weren't entirely proper, so we're seeing some errors...
Click to expand...
Click to collapse
Thx for help with elaboration.
Btw, did you successfully applied fix through this guide?

I just applied your fix and I was using a stock rom. Everything went ok and it does feel quicker. I am getting some kernel crashes but only really when you reboot the phone. I would write what the quadrant score is but it never finishes the tests, it sticks on part 3 of the I/O tests.

Just did this and got a Quadrant score of 1439!
Thank youuu!!!!
I had a ton of trouble with apps f/c-ing, but reinstalls help.
To all attempting: Just flash to stock and save yourself the trouble.
You won't have to deal with all the trouble of your apps not working, and you can just reinstall them later. I had to do a ROM recovery to remove launcher pro's permissions so I wouldn't get stuck in a constant f/c loop...
BUT! It's working now! Many thanks!!

Nevermind I just let quadrant run for a while and it finished. Got a score of 1389! But I am still getting these kernel crashes. Specifically process com.google.process.gapps

illspyder said:
I just applied your fix and I was using a stock rom. Everything went ok and it does feel quicker. I am getting some kernel crashes but only really when you reboot the phone. I would write what the quadrant score is but it never finishes the tests, it sticks on part 3 of the I/O tests.
Click to expand...
Click to collapse
Sounds strange.
I'll do number of reboots to verify.
Could you check under linux (ubuntu or other) that you ext is ext3 and second check it with e2fsck if it's healthy

Fortune090 said:
Just did this and got a Quadrant score of 1439!
BUT! It's working now! Many thanks!!
Click to expand...
Click to collapse
Glad to hear!

mykenyc said:
No i'm not bashing this, trust me cell phones not my life. But for me this is my second captivate my antenna is my biggest problem it goes up and down like wild fire trying to be put out. My dad own a BB on ATT and his bars never go crazy in our apartment. I was trying to hold out to see if we would have a fix by now but its effecting my livelihood, and once that happens then i got to make a change. I don't get the lag but i do get times where text messages literally take (upon power on) 20 minutes to shoot in, i tried different sims and this my second captivate like i said. But i'm not going to hijack your thread just wanted to say i appreciate the attempts.
but hey if something happens before the torch come out i will def stay...
good luck bro
Click to expand...
Click to collapse
bars mean nothing. I could have 0 bars on my captivate and still hold a call better than when I had an iPhone 4. If you are constantly dropping calls on your captivate and not on your dad's Blackberry, then you should be worried, otherwise, you should not.
Either follow this lag fix or the NAND lag fix (http://forum.xda-developers.com/showthread.php?t=737829), and it will solve most of your problems

Related

GPS fixed on Captivate. Combination of 2 methods + detailed steps

This is how I fixed my GPS issue on Captivate. It would not lock on, not even after 5 minutes of me standing still.
Found this thread - http://forum.xda-developers.com/showthread.php?t=786486
Was trying to follow the steps and realized I wished it was spelled out more. So this is what I am doing in this thread, to make it easier for everyone else, if they decide to try. After an hour of googling commands and trial and error - its done, and my phone's GPS locks on under 10 seconds.
I downloaded that zip file. Then installed Droid Explorer on my PC. I already had USB drivers installed for the Galaxy S, so during install I unchecked it. When I opened Droid Explorer I realized I cant write to the /system/bin and the other two. The Write permissions for the system folder were not set, so when I dragged files over - they wouldnt copy over to my phone. It would kinda "refresh" but files wouldnt show up in there.
Easy way seemed to be to buy and install Root Explorer on my phone from the market. And click on Mount R/W for the system folder. However I am waiting for credit card replacement in the mail and was so fed up with GPS that I wanted to do it NOW, and was not gonna stop until its done. Today.
So the other way to make /system/bin , /system/etc and /system/lib folders writable was thru command prompt.
First off my phone has Cog 5.5 on it so it is rooted.
1. set phone in usb debugging mode and connect to pc
2. navigated to my sdk/tools directory on my hard drive. In my case it looked like this
Code:
cd c:\sdk\tools
<hit enter> but it depends on where you downloaded and unzipped your android SDK folder
3. typed
Code:
adb shell
<hit enter> then
Code:
su
<hit enter> to give me root access to the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone will ask if you want to grant permissions to unknown, hit Yes.
4. Now we need to set system as writable. While googling commands it seemed that the command should be
Code:
mount -o rw,remount /system
But in my case that didnt work, telling me location was invalid. I obviously was missing something. Duh! correct location! So -
type
Code:
mount
<hit enter> It will list the root directory. We need t locate exactly where system is on the phone. In my case it was /dev/block/st19 /system
So the command should be then
Code:
mount -o rw,remount /dev/block/st19 /system
<enter>
then
Code:
chmod 777 /system
<enter>
Code:
chmod 777 /system/bin
<enter>
Code:
chmod 777 /system/etc
<enter>
Code:
chmod 777 /system/lib
<enter>
Code:
exit
<enter>
and one more time
Code:
exit
<enter>
The folders are now writable.
5. Opened Droid Explorer, copied files over, lbstestmode launch app was already installed on my phone. So it didnt have to do that step, as it was in j101399j's thread
6. Rebooted the phone, opened lbstestmode, deleted GPS data.
Started testing. It wouldnt lock. Went to Get Position Test in lbstestmode app. It would see the sattellites, 8 of them but wouldnt give me my lat/long! So I remembered this post - http://forum.xda-developers.com/showpost.php?p=9150551&postcount=7862 by cnewsgrp
and changed
3. In the LBSTestMode menu change “Operation Mode” to MS Based
4. In the LBSTestMode menu, find “SUPL/CP Settings” and change the SERVER & PORT to supl.google.com and port 7276 (DO NOT use www. in front of supl)
Click to expand...
Click to collapse
Didnt even have to reboot. Went to Get Position Test again and it saw like 8 or 9 satellites and had * next to 4 of them in 10 seconds. Give me my lat/long with precision. Wanted to mention that I tried cnewsgrp 's method a week ago, just by itself, and it gave me no results.
So to summarize. Combination of those 2 fixes worked wonders for me. And the Captivates GPS issue is definitely not hardware based.
I do have a question however,lol, how do I revoke write settings for my system folder, and go back to how it was? Would that be
Code:
chmod 755
?
I hope these detailed instructions help someone.

And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.

chmod 777???
NO THANK YOU!!

zerojay said:
And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.
Click to expand...
Click to collapse
it didnt change file settings inside folders, just folder setting

also this is where I got chmod 777 from - http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html and http://karuppuswamy.com/wordpress/2009/04/25/mounting-system-partition-in-read-write-mode-in-android/
was obviously for android.

There's a reason why 777 permissions weren't there to begin with
also I love how there are currently 7 views and 6 replies. which means almost everyone is going - Aaah!!!!! NOOO!!! Must post and warn her!!!

my phone's GPS locks on under 10 seconds
Click to expand...
Click to collapse
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads

sinoth said:
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads
Click to expand...
Click to collapse
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
Yes there is a
"a reason why 777 permissions weren't there to begin with"
Click to expand...
Click to collapse
It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.

bmvik said:
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.
Click to expand...
Click to collapse
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...

kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
I agree. I'll let you know regarding tracking as I test. Before however, not only it would take 5 min to lock on, but would lose me while I was driving, constantly. Accuracy was jumping to 200 meters or so. So instant lock was a good sign to me.

bmvik said:
Yes there is a It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
Wow, the cluelessness.

kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
For me it does. I have been using GPS with any issues for past few days. And to give credit what ever steps I have posted have been around for a long time just search for "Vibrant GPS fix". The only reason I needed to do that was my GPS stopped working after applying Cog 2.4 ROM with is Vibrant ROM. I applied Vibrant GPS fix and voila GPS now works!!
I must stress here that I have had no GPS issues with any of the Captivate ROMS or Stock ROMS. I usually get lock in 10 - 30 seconds and it tracks well for me. I used GPS test and I an see around 8-9 satellites with S/N ratio of 35 and accuracy of 16.5 regularly.

Oh the boogeyman
I also would like to add, had anything went wrong during these steps - I would've just reflashed my phone to another Cognition ROM and started from scratch. Voila!

bmvik said:
Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
bmvik said:
Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Click to expand...
Click to collapse
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.

installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant

DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.

DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
Thank you. I mean, really.
fatttire said:
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.
Click to expand...
Click to collapse
Let me spell it out for you. In this thread http://forum.xda-developers.com/showthread.php?t=786486 OP suggests
2. Using root explorer or droid explorer, copy the files from each folder.
Click to expand...
Click to collapse
For root explorer to be able to write to system folder it would HAVE to change that folders permissions. I didnt have the app, so changed them manually, then used droid explorer. Then changed permissions right back to 755.
cnewsgrp said:
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.
Click to expand...
Click to collapse
Well I just copied the files from the zip file I linked to in the OP, over to the system/bin, /etc and /lib I dont know how screenshot would help

aaaand uhhhhhh can you non-haters vote the thread up, plz? some 5 haters hit 1 star

OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App

skinien said:
OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Lol stop using the samsung keyboard the period is in the wrong spot.
btw op can you plz post some tracking results with mytracks or something. Locking on is not the problem, tracking is.
If you do ill vote this thread up

[Linux] [DEV] [WIP]Backtrack 5 on the gtablet HYBRID. 7/18/11 1.2 BL kernel

6/13/12 update
updated links and some instructions.
I currently do not have time to do any work on this currently as i have been working 18+ hours a day. Hopefully if i ever get some time again I will continue it.
Jaybob413 built the kernel for 1.2 Bootloader. Link is posted below
Thanks jaybob413
*PLEASE READ AND UNDERSTAND EVERYTHING HERE BEFORE ATTEMPTING THIS*
BACKTRACK 5 IS running on the GTABLET in Hybrid mode!
http://www.youtube.com/watch?v=kJb3mwBhMik video up now =)
http://www.youtube.com/watch?v=be-9F_VzbHY Dual boot video
working
boots natively into backtrack
X11 desktop works
wifi
TOUCHSCREEN!!!!!
4 buttons. Search opens firefox, home opens users home dir, settings toggles the Onscreen keyboard, and back switches through virtual desktops.
Not Working
sound
bluetooth
battery stats
------------------------------------------------
I currently have this set up for windows. It can be done from linux but will link everything for windows in this post.
you must have ADB installed on windows working with the gtablet. see http://forum.xda-developers.com/showthread.php?t=902860
required files:
bt5.tar.xz http://d-h.st/YZ4
restore_droid-kern.zip http://dev-host.org/qsbz1s7xbebt/restore_droid-kern.zip
droid-kern_backup.zip http://dev-host.org/evmqb1yrd0tn/droid-kern_backup.zip
1.1 bootloader:
bt5kern-01-20110525.zip http://dev-host.org/s4d4pp1wvxx4/bt5kern-01-20110525.zip
1.2 bootloader: thanks jaybob413 for the 1.2 kernel.
http://forum.xda-developers.com/showpost.php?p=15703493&postcount=137
optional files:
nvidia_windows.zip http://dl.dropbox.com/u/4917587/nvflash_windows.zip
kernel config file http://dl.dropbox.com/u/4917587/config this file is only for reference. you do not have to download it or install it
the root password is "toor"
THIS MAY ERASE EVERYTHING ON YOUR TABLET!!!!
Do this at your own risk!! I take no responsibility for anything that happens to your tablet.
Start by installing your favorite ROM and kernel.
Make sure you have adb working and CWM installed
turn off the device then boot into recovery. (vol+ and power).
once in recovery you must format the EXTERNAL sdcard into ext3.
Code:
adb shell
parted /dev/block/mmcblk2
mkfs 1 ext2
confirm
exit
tune2fs -j /dev/block/mmcblk2p1 to format the external SDcard to ext3
mkdir /tmp/ext-sd
mount /dev/block/mmcblk2p1 /tmp/ext-sd/
exit adb and run
* this will take a long time *
Code:
on a linux box unxz bt5.tar.xz
adb push c:\path\to\bt5.tar /tmp/ext-sd/bt5.tar
adb shell
# cd /tmp/ext-sd/
tar xvf bt5.tar
rm bt5.tar
cd /
umount /tmp/ext-sd/
reboot the device into android and connect the INTERNAL sdcard to the computer to place files on to the sdcard.
make a directory called kernels on the sdcard and put the 3 zips from above in that folder.
bt5kern-01-20110525.zip
droid-kern_backup.zip
restore_droid-kern.zip
reboot into recovery and flash the
droid-kern_backup.zip this will create a backup of the android kernel. This will ONLY need to be done any time that you UPGRADE or CHANGE your android kernel.
once this is done you switch back and forth between android and backtrack with:
bt5kern-{date}.zip to boot into backtrack
restore_droid-kern.zip to boot into android
******* You do NOT have to wipe cache or anything when switching back and forth. Just flash whichever you want to boot into and you are done************
http://forum.xda-developers.com/showpost.php?p=16223052&postcount=139 WICD fix

Linux touchscreen drivers and settings
xf86-input-multitouch https://launchpad.net/debian/+archi...ut-multitouch_1.0~rc2+git20110312.orig.tar.gz
libmtdev1 http://ftp.de.debian.org/debian/pool/main/m/mtdev/mtdev_1.1.0.orig.tar.gz
************OLD WAY******************
How to install backtrack 5 to run on the gtablet with out gtab filesystem modification.
You must recreate the img file to be less then 4Gb. The img file is currently 4.6Gb. The new image created will be 2.9Gb. this is a vfat limitation
this has been tested on vegan 5.1 with the gtab/zpad 1.4 OC kernel. Its still a little buggy with random reboots depending on what your are doing but it is a WIP
The kernel must have loop devices support. Also looks like the kernel needs swap functionality to be enabled.
I could release the img file that has already been created but backtrack would prefer that people not release other images so this will allow you to create your own after downloading it from them so it remains trusted.
you either need:
linux with ADB working on the gtab
OR
windows with ADB and access to a linux box with about 10gb of free space.
Backup your sdcard because it needs to be repartitioned with CWM.
In CWM under advanced > Partition SD Card > 2048 > 128
download the arm version of backtrack from www.backtrack-linux.org/downloads/
and extract the files. you need to copy the bt5.img.gz to the linux box and do all the following steps.
make a working directory for all the files, copy and gunzip the img file
Code:
mkdir bt5
cp /root/bt5.img.gz bt5
cd bt5
gunzip bt5.img.gz
rename the old bt5.img to something else and create a new image that fits onto the gtabs vfat filesystem.
then create 2 directory to mount each image and copy the files over to the new img file.
Code:
mv bt5.img bt5.old.img
dd if=/dev/zero of=bt5.img bs=4k count=900000
mke2fs -F -i 8192 bt5.img
mkdir bt5old bt5new
mount -o loop bt5.old.img bt5old
mount -o loop bt5.img bt5new
cd bt5old
cp -rp * ../bt5new
*****************************************
since the system does not go through the full startup scripts once you run "sh bootbt" you must run /etc/rc.local from the chroot to start the vnc server if you add these lines otherwise you must type them each time.
Code:
cd ../bt5new/
vi etc/rc.local and add the following 2 lines before the exit 0 line
export USER=root
/usr/bin/startvnc
save the file and then continue on.
also you can edit /usr/bin/startvnc and modify the screensize to fit the tablet
the gtablet is 1024x600
Code:
vncserver -geometry 1024x600
*****************************************
after all files have been copied over you just unmount the 2 directories and gzip the new image.
Code:
cd ..
(you should now be in the directory with the 2 img files and 2 directories)
umount bt5old
umount bt5new
gzip bt5.img
edit the bootbt file and change the line
Code:
mount -o remount,rw /dev/block/mmcblk0p5 /system
with
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
*** this needs to be changed to whatever your /system is on your tablet or phone if it is something other then the gtablet.
now copy this new bt5.img.gz file over to the directory where you got the original image from and then follow the instructions that are included with the download in the README file.
a good VNC viewer is located
http://code.google.com/p/android-vnc-viewer/downloads/list
and also install a terminal emulator so you can start Backtrack 5 from the device.
---BUGS---
running from a terminal emulator everything runs fine but running VNC gnome takes up way to much RAM currently. Looking at fluxbox and/or swap as a fix. causes the tablet to lock up and must be powered off by holding the power button.
---Thanks---
The Backtrack Team -- for coming up with an amazing security distro
The G-TabDevs Team -- for the vegan 5.1 Rom
Pershoot -- for maintaining the 1.4 kernel for the gtab and hopefully adding support for needed features =)
Sorry for the flash in the pictures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sorry for the noob question.....
where we need to run all the commands you have stated????

fauz33 said:
sorry for the noob question.....
where we need to run all the commands you have stated????
Click to expand...
Click to collapse
They must be run on a linux box. I bolded it just now in the first post. I would do it all and just release the gzip file but backtrack does not want that.

slimm609 said:
They must be run on a linux box. I bolded it just now in the first post. I would do it all and just release the gzip file but backtrack does not want that.
Click to expand...
Click to collapse
sorry....
i have googled it for hours.....
what is mean by linux box??

fauz33 said:
sorry....
i have googled it for hours.....
what is mean by linux box??
Click to expand...
Click to collapse
_almost_ any version of linux installed on a computer (laptop or desktop).
you need about 8-10gb of free space after linux is installed.
like fedora, centOS, ubuntu, suse, slackware, etc.
90+% of the versions on this site would work www.distrowatch.com

I'll talk to Muts and see if he will allow the gzip. Maybe if it is maintained by you but released by them they might consider it.
These instructions are for running BT5 in a shell, not actually installing it as the working OS on the gtablet - right?
Similar to:
http://www.backtrack-linux.org/forums/backtrack-5-how-tos/40376-%5Bhow-%5D-backtrack-5-motorola-xoom-gnome-ui-via-tightvncserver.html

runner989 said:
I'll talk to Muts and see if he will allow the gzip. Maybe if it is maintained by you but released by them they might consider it.
These instructions are for running BT5 in a shell, not actually installing it as the working OS on the gtablet - right?
Similar to:
http://www.backtrack-linux.org/forums/backtrack-5-how-tos/40376-%5Bhow-%5D-backtrack-5-motorola-xoom-gnome-ui-via-tightvncserver.html
Click to expand...
Click to collapse
This runs the same way that it does on the Xoom. Just making it fit onto the gtab and Evo 4g
here is CHS (runner989)

Is packet injection working with the wireless adapter?

kdj67f said:
Is packet injection working with the wireless adapter?
Click to expand...
Click to collapse
most of the tools for wireless were removed when they created the arm version.
I am going to try and compile them and see if they work when i get a chance (hopefully soon)

Ugh! That sucks! I did not know they did that. Since the gtablet has a USB port the USB wireless adapters (like the Alfa adapter) should work just as they do in the regular Backtrack builds.
slimm609 said:
most of the tools for wireless were removed when they created the arm version.
I am going to try and compile them and see if they work when i get a chance (hopefully soon)
Click to expand...
Click to collapse

runner989 said:
Ugh! That sucks! I did not know they did that. Since the gtablet has a USB port the USB wireless adapters (like the Alfa adapter) should work just as they do in the regular Backtrack builds.
Click to expand...
Click to collapse
The internal card is a broadcom 4329 so it should support everything also. have to wait and see.

Major progress made on booting native backtrack linux. Kernel boots but it missing a driver so it drops into a ramfs but getting close.
off to bed

I was so excited I forgot we run an arm processor! Good work to the devs on this. And although it was probably an ethical thing to remove all the wireless functions for ARM builds, It would be much handier than lugging around my old laptop with it's ancient battery that barely last 45 minutes under load.
Many thanks, I am subscribing. Just wish I could help

This is pretty awesome. Might want to check the debian or ubuntu ARM community to find out how the wireless drivers work there. I'm assuming our ARM runs in it's normal little indian, not ARMEB mode, right?

muqali said:
This is pretty awesome. Might want to check the debian or ubuntu ARM community to find out how the wireless drivers work there. I'm assuming our ARM runs in it's normal little indian, not ARMEB mode, right?
Click to expand...
Click to collapse
the wireless card is a broadcom 4329

slimm609 said:
the wireless card is a broadcom 4329
Click to expand...
Click to collapse
The driver source thread is http://forum.xda-developers.com/showthread.php?t=906628

wifi is working now. tested with wpa-psk
New files coming tomorrow with wifi included.
the touchscreen is seen by the system and xorg just need to find the right configuration for it to work
now trying to compile as a single touch device because Xorg does not support multi-touch displays

touchscreen is working. just working on calibration of it now. only single touch currently

This is awesome...
Sent from my Droid using XDA App

[DEV] Tutorial for installing ubuntu on Iconia

For those who want a tutorial, here's my experience in installing the system:
(PS: FOR those who want a really simple command-by-command tutorial, please see #26 post. That's part 1 of the tutorial on how to boot ubuntu up without wireless. If you need wireless working and want a command-by-command tutorial on that, just reply and I'll make it. )
I mainly referred to sp3dev's thread: http://forum.xda-developers.com/showthread.php?t=1158260
I've make ubuntu run on my iconia, but I cannot let bluetooth run so you'd better have a usb keyboard and (if you could find the trick to use the touch screen, no need of) a usb mouse.
Tools to prepare:
1. Ubuntu OS on PC with adb tool.
2. A >=4GB microSD card and make sure iconia can identify it.
3. USB keyboard and USB mouse
4. rooted iconia with acer recovery installer, busybox, terminal emulator.
5. Perhaps more that I didn't listed
Files to download:
1. rootfs: http://www.dmmhosting.co.uk/tegra-rootfs.tar from Digitaldaz;
2. precompiled header: http://www.mediafire.com/?ucvk6x66129igzc from sp3dev;
3. itsmagic: http://forum.xda-developers.com/showthread.php?t=1121543&highlight=itsmagic from sc2k;
4. source code: https://github.com/astarasikov/iconia-gnu-kernel from sp3dev;
5. Perhaps more that I didn't listed
Procedure to install ubuntu:
1. Use your computer to format your microSD card into two partitions: one is in FAT32, to be used as normal external storage. Suggested minimum size is 1GB, to store backup file in step 2. The other is ext4, to store root filesystem of ubuntu. Suggested minimum size is 3GB. Tools: fdisk, mkfs.vfat, mkfs.ext4. Using sudo when making filesystem. Refer to rkaszala's post for further information: http://forum.xda-developers.com/showthread.php?t=1158260&highlight=itsmagic&page=12
(Comment: I use computer to format while he/she uses iconia to format.)
Make sure the formatted sdcard can be recognized by iconia as /dev/block/mmcblk1p1 and /dev/block/mmcblk1p2 .
2. Backup all data using itsmagic link above. Be familiar with usage of itsmagic, esp. use it to recalculate the checksum.
3. use tools here: http://forum.xda-developers.com/showthread.php?t=1126364 to flash the newrec.img file onto the /dev/block/mmcblk0p1, and use itsmagic to recalculate checksum.
3.1. on android system, use terminal emulator to copy /system/etc/nvram.txt out as bcm4329-fullmac-4.txt .
4. USING SUDO to unzip the rootfs tarball referred in Files:1 into the ext4 fs mentioned in step 1. If you do not use sudo, some device nodes will not be able to be created.
5. SUDO EDIT the etc/fstab IN YOUR UNZIPPED ROOT FILESYSTEM NOT IN YOUR OWN UBUNTU SYSTEM to one line:
proc /proc proc defaults 0 0
6. compile source code using instructions by sp3dev here: http://forum.xda-developers.com/showthread.php?t=1158260&highlight=itsmagic&page=9 in the middle part of the page.
7. copy the compiled bcm4329-fullmac-4.bin firmware (should be at lib/firmware/brcm/) to sdcard's root filesystem's location: /lib/firmware/brcm/ folder and copy the previous bcm4329-fullmac-4.txt here.
8. copy the compiled modules into sdcard's root filesystem's /lib/modules/ (I forget the name of the folder so be sure to name it correctly. )
9. insert the sdcard into iconia and reboot with wolume down key pressed (the way to boot into recovery img.)
and now, you should have reached what I have reached.
If you failed on some step please tell me. All I summarized is what I have done, so please refer to their original post for more information.

impressive...

Can you make more detailed tutorial?

can you make video tutorial, because some people don't understand how to do this things. Sorry for bad english

Tautvaldas said:
can you make video tutorial, because some people don't understand how to do this things. Sorry for bad english
Click to expand...
Click to collapse
My opinion: tutorial in first post is good enough. If someone don't understand is better not to try!

PhilipZ said:
My opinion: tutorial in first post is good enough. If someone don't understand is better not to try!
Click to expand...
Click to collapse
Sorry if I've missed something here but I didn't realize your comprehension ability was the benchmark for tutorials being "good enough"
Troll or not, I hate attitudes like this. If everybody followed this line of thought we'd still be in the stone ages.
The whole purpose of a tutorial is to show people how to do something that is outside of there general knowledge. If adding more details to a tutorial will allow it to be useful a wider audience then surely that can only be a good thing for knowledge sharing and the author.
A video tutorial, if somebody can spare the time of course, would be great.

Hi guys:
Sorry I'm really busy these days so I didn't have time to give more detail on that. This weekend I will reinstall the ubuntu on my Iconia and will post a more detailed command by command tutorial here. I don't have a camera nor a phone with good camera so I'm afraid I cannot make a video, but if u have any question pls just reply here and I will get an email notification and I'll reach back asap.
The installation is tough yet exciting so I understand your feeling of getting ubuntu running on your iconia, but my word now is don't expect too much, it's just running yet still slow and I didn't patch some drivers on (At least now I cannot get bluetooth and nvidia drivers work but wifi works!).
Anyway, even if you're new here, I recommend you to read the links I posted above as they're good place to learn stuff.

sirzen said:
Hi guys:
This weekend I will reinstall the ubuntu on my Iconia and will post a more detailed command by command tutorial here.
Click to expand...
Click to collapse
Thank you! We are waiting
You used rootfs from Digitaldaz or from rkaszala ?
(Sorry for my english)

I'm planning a video tutorial once I work the bugs out, right now still having wifi (it loads firmware but I'm not offered any networks, it statys "disabled") issues, and I'm working it out on Ubuntu 10.10 which doesn't have unity, unity is a POS, requires far too much of the gpu, and for our tab we can live without.
wish me luck!

Nice thread i am still working thru the wireless card issues
You cleaned up most of thenative linux thread nicely. I am still struggling with wifi. I made a 250mb rootfs trying for minimalize size
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rkaszala said:
Nice thread i am still working thru the wireless card issues
You cleaned up most of thenative linux thread nicely. I am still struggling with wifi. I made a 250mb rootfs trying for minimalize size
Click to expand...
Click to collapse
Noob question!
Can I use all 2gb SD Card to ext partition,and will linux fit in >2gb ?

Currently I'm using the one from Digitaldaz since I have not get a usable rootfs, but I strongly suggest u to use something built by yourself if you could.
ZeRo_samdroid said:
Thank you! We are waiting
You used rootfs from Digitaldaz or from rkaszala ?
(Sorry for my english)
Click to expand...
Click to collapse

I originally couldnt get the rootfs posted by Digitaldaz to untar tons of symlink errors. So i installed Ubuntu 11 on a desktop , built rootfs using rootstock.

Cool......
rkaszala said:
I originally couldnt get the rootfs posted by Digitaldaz to untar tons of symlink errors. So i installed Ubuntu 11 on a desktop , built rootfs using rootstock.
Click to expand...
Click to collapse

Still havent been able to get the wireless to work, found out that the brcm-bcm4399 had to remove the brcm- from the front. No more firmware errors. just not getting any wlan0 , when i dmesg | gregp brcm no errors there. Any ideas what to try now?

Get your wifi working? I did the bcm4329-fullmac-4.bin and nvram > bcm4329-fullmac-4.txt and then copied the 2 .fw files from the github. I am still not having any luck with wifi.
Wifi Update,
rfkill listall showed the wifi blocked , odd. So i did a rkfill unblock wifi and now i can get the wlan0 to ifup. But using wicd both wext and nl80211 i cant get it to do anything. thoughts?

rkaszala said:
Get your wifi working? I did the bcm4329-fullmac-4.bin and nvram > bcm4329-fullmac-4.txt and then copied the 2 .fw files from the github. I am still not having any luck with wifi.
Wifi Update,
rfkill listall showed the wifi blocked , odd. So i did a rkfill unblock wifi and now i can get the wlan0 to ifup. But using wicd both wext and nl80211 i cant get it to do anything. thoughts?
Click to expand...
Click to collapse
That's how I get my wifi work. I don't know more about the detail. I think Digitaldaz add something in his rootfs as his rootfs tarball is ~400MB while the rootstock stuff is less than 300MB.

same root fs? cause last time i tried his was 1.5 gig

rkaszala said:
same root fs? cause last time i tried his was 1.5 gig
Click to expand...
Click to collapse
I mean his tarball. After untar it should be about 1.5gig. I installed some updates and it grows up to 2.0gig on my one. Should be same?

what about the touch screen ... any prograsess ???

[Q] cifs mounting problem with android 4.3

Hi guys,
Do any of you have successful solution to mount cifs shares with ANY kernel available? I've tried to do it with Project Flaming Monkey kernel, but had no luck. Most of the time I got "device not authorized" error when tried to mount via adb shell. But even if I could overcome this error (didn't figure out exact sequence of steps) it always says that mounting failed or even gets segfault.
With KTmanta kernel device is always authorized, I get root credentials immediately, but mounting also fails. Later I discovered that mounting actually happens and I can see it via adb shell, but it's invisible for all other users including root. Does it mean that 'mount using adb shell' trick doesn't work anymore?
Anyway I'll be very grateful for any kind of working solution or direction where to get it. Thanks in advance.
P.S. interesting but StickMount just works even on stock kernel that is said to have module loading disabled.
Sent from my Nexus 10 using xda app-developers app

uentity said:
Hi guys,
Do any of you have successful solution to mount cifs shares with ANY kernel available? I've tried to do it with Project Flaming Monkey kernel, but had no luck. Most of the time I got "device not authorized" error when tried to mount via adb shell. But even if I could overcome this error (didn't figure out exact sequence of steps) it always says that mounting failed or even gets segfault.
With KTmanta kernel device is always authorized, I get root credentials immediately, but mounting also fails. Later I discovered that mounting actually happens and I can see it via adb shell, but it's invisible for all other users including root. Does it mean that 'mount using adb shell' trick doesn't work anymore?
Anyway I'll be very grateful for any kind of working solution or direction where to get it. Thanks in advance.
P.S. interesting but StickMount just works even on stock kernel that is said to have module loading disabled.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
CM 10.2 plus Trinity Kernel plus Mount Manager works

I didn't yet tried trinity kernel
Thanks for the reply!
I think that kernel actually affects mounting process and not the ROM. Didn't tried trinity kernel yet, because author said that it's not feature complete for 4.3.
Do you have any issues with it? Everything works fine?
Sent from my Nexus 10 using xda app-developers app

uentity said:
I didn't yet tried trinity kernel
Thanks for the reply!
I think that kernel actually affects mounting process and not the ROM. Didn't tried trinity kernel yet, because author said that it's not feature complete for 4.3.
Do you have any issues with it? Everything works fine?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Running the kernel version TX10, I have had some rare forced close issues, but i have no idea if it is kernel- or rom-related, propably the latter. Other than that it works just as well as any 4.2 combo I had before. Some kinks here and there, but perfectly usable.

I use Trinity with any 4.3 ROM and a script to mount my home file share. Works great.

I'm running 4.3 and Trinity kernel (tx17), I'm able to mount the cifs share from adb shell, I see the data there, but it's not available for the apps on the tablet. I also tried mounting the share using mount manager but it didn't help. I see it as a mounted, but no apps can see the data.
Where (mountpoint) and how should you mount the cifs share so it's visible for the rest of apps as well? Thx.

slano said:
I'm running 4.3 and Trinity kernel (tx17), I'm able to mount the cifs share from adb shell, I see the data there, but it's not available for the apps on the tablet. I also tried mounting the share using mount manager but it didn't help. I see it as a mounted, but no apps can see the data.
Where (mountpoint) and how should you mount the cifs share so it's visible for the rest of apps as well? Thx.
Click to expand...
Click to collapse
I remember having this problem, but I don't remember how I fixed it. Here's my script, compare it to yours to see if there's any difference. The below is all one line;
busybox mount -t cifs -o username=tv,password=<your_password>,rw,file_mode=0777,dir_mode=0777,uid=1000,gid=1000,unc=\\\\192.168.1.101\\files //192.168.1.101/files /data/media/0/TV-PC
I seem to remember it having something to do with mounting to /data/media/(whatever) or the uid/gid.

sttovo said:
I remember having this problem, but I don't remember how I fixed it. Here's my script, compare it to yours to see if there's any difference. The below is all one line;
busybox mount -t cifs -o username=tv,password=<your_password>,rw,file_mode=0777,dir_mode=0777,uid=1000,gid=1000,unc=\\\\192.168.1.101\\files //192.168.1.101/files /data/media/0/TV-PC
I seem to remember it having something to do with mounting to /data/media/(whatever) or the uid/gid.
Click to expand...
Click to collapse
Did try all possible combinations but still no luck. I've changed rom to Flaming Monkey and everything works like a charm there, so I'll probably stick with it for a while.

slano said:
Did try all possible combinations but still no luck. I've changed rom to Flaming Monkey and everything works like a charm there, so I'll probably stick with it for a while.
Click to expand...
Click to collapse
So to confirm, you did get cifs working with project flaming monkey rom or that's just the Rom you settled with since cifs never worked anyway? Did you use trinity kernel tx17? That's currently the combo I have and for the life of me cannot get it to work..... I am just learning about this so I'm sure it's me but if I know I have the same combo as someone who got it working, I will keep trying.

c683 said:
So to confirm, you did get cifs working with project flaming monkey rom or that's just the Rom you settled with since cifs never worked anyway? Did you use trinity kernel tx17? That's currently the combo I have and for the life of me cannot get it to work..... I am just learning about this so I'm sure it's me but if I know I have the same combo as someone who got it working, I will keep trying.
Click to expand...
Click to collapse
I've tried stock ROM with the Trinity kernel but no luck. I was able to mount the cifs filesystem, but it was not accessible for other apps. I've switched to Flaming monkey and everything mounted and was available just fine.
What is your problem with the current set-up? Will the share mount ok but it's not accessible from other apps or are you not able to perform the mount at all?

slano said:
I've tried stock ROM with the Trinity kernel but no luck. I was able to mount the cifs filesystem, but it was not accessible for other apps. I've switched to Flaming monkey and everything mounted and was available just fine.
What is your problem with the current set-up? Will the share mount ok but it's not accessible from other apps or are you not able to perform the mount at all?
Click to expand...
Click to collapse
Thanks for the reply. I have tried to use 3 different ways, below is a brief summary:
- CIFS Manager - No matter what I do, I get an "Invalid Argument" or "directory cant be found" error. Read and tried what is listed in CIFS FAQ to no avail.
- Mount Manger - Shows as connected, but there are no files; not in any apps or in the directory when using a file browser (root explorer or ES)
- Script - Yeah, just copied the script a few posts back and modified based on what I thought I needed to and used terminal emulator, gave it a go but nothing happens. Really don't know what I am doing with regard to script, over my head...
I also read that modules are needed but I thought the the trinity kernel already had them...
I am running the latest flaming monkey rom and trinity kernel on my nexus 10. So in short I really don't know exactly what I am doing but I will keep trying since I know you got it working with the same ROM and kernel setup. I can also access the files on my shared files through ES file explorer when I use the LAN or server feature so I know the PC is at least setup correctly, I think...

I haven't tried it on 4.3 yet. But the "Invalid argument" error is a problem in Linux kernels 3.4 in general. Take a look here:
How to Troubleshoot CIFS Problems on Android and Linux in General
I encountered that problem ever since JB. The problem is that mount is usually used in this way:
Code:
mount -o username=youruser,password=yourpasswd -t cifs //ipofpc/shareonpc dironphone
But that does not work in kernel 3.4. The share-directory as a device name is ignored. It has to be specified with argument unc. Like this:
Code:
mount -o unc=\\\\ipofpc\\shareonpc,username=youruser,password=yourpasswd -t cifs none dironphone
Note: since backslash is an escape character the double \\ is needed instead of \. It's also a good idea to specify noperm if you want the mounted directory to be accessible by all apps. Otherwise the mounted directory might only be accessible by root on the phone.
So a working example looks like this:
Code:
mount -o noperm,unc=\\\\10.0.0.200\\Public,username=guest,password=secret -t cifs none /sdcard/shares/nas
You have to work around that problem in CifsManager. Enter it like this:
Share Path: Enter anything. It will be ignored.
Mount Point: directory on phone: e.g. /sdcard/shares/nas
Username: enter user name
Password: leave empty
Options: e.g. noperm,unc=\\\\10.0.0.200\\Public,password=secret
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

gwodus said:
I haven't tried it on 4.3 yet. But the "Invalid argument" error is a problem in Linux kernels 3.4 in general. Take a look here:
How to Troubleshoot CIFS Problems on Android and Linux in General
I encountered that problem ever since JB. The problem is that mount is usually used in this way:
Code:
mount -o username=youruser,password=yourpasswd -t cifs //ipofpc/shareonpc dironphone
But that does not work in kernel 3.4. The share-directory as a device name is ignored. It has to be specified with argument unc. Like this:
Code:
mount -o unc=\\\\ipofpc\\shareonpc,username=youruser,password=yourpasswd -t cifs none dironphone
Note: since backslash is an escape character the double \\ is needed instead of \. It's also a good idea to specify noperm if you want the mounted directory to be accessible by all apps. Otherwise the mounted directory might only be accessible by root on the phone.
So a working example looks like this:
Code:
mount -o noperm,unc=\\\\10.0.0.200\\Public,username=guest,password=secret -t cifs none /sdcard/shares/nas
You have to work around that problem in CifsManager. Enter it like this:
Share Path: Enter anything. It will be ignored.
Mount Point: directory on phone: e.g. /sdcard/shares/nas
Username: enter user name
Password: leave empty
Options: e.g. noperm,unc=\\\\10.0.0.200\\Public,password=secret
Click to expand...
Click to collapse
Thank you for the detailed response, I will give that a try.
Sent from my Nexus 10 using xda app-developers app

c683 said:
Thank you for the detailed response, I will give that a try.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
BTW. I forgot. Before you try anything. Check if the directory /proc/fs/cifs exists. If it doesn't, then you are missing the required cifs kernel module. But more often then not, the kernel module is there and the problem is elsewhere.

gwodus said:
BTW. I forgot. Before you try anything. Check if the directory /proc/fs/cifs exists. If it doesn't, then you are missing the required cifs kernel module. But more often then not, the kernel module is there and the problem is elsewhere.
Click to expand...
Click to collapse
Thank you for your help. I thought for sure I tried what you said in your last post before as I read something similar. However, the info was wrong or I screwed up because when I followed your detailed description, it worked! The weird thing is some files open and others I'll get "the file doesn't exist error" but I am not concerned with it since I can get what I need. Thanks again.

c683 said:
Thank you for your help. I thought for sure I tried what you said in your last post before as I read something similar. However, the info was wrong or I screwed up because when I followed your detailed description, it worked! The weird thing is some files open and others I'll get "the file doesn't exist error" but I am not concerned with it since I can get what I need. Thanks again.
Click to expand...
Click to collapse
Awesome. You got it working!
I never ran across the "file doesn't exist" error. But I read around here that other people have such troubles too. It's probably a permission problem. Maybe try to play around with options like gid, forceuid, file_mode and dir_mode. A complete list of options is here: mount.cifs man page

gwodus said:
I haven't tried it on 4.3 yet. But the "Invalid argument" error is a problem in Linux kernels 3.4 in general. Take a look here:
How to Troubleshoot CIFS Problems on Android and Linux in General
I encountered that problem ever since JB. The problem is that mount is usually used in this way:
Code:
mount -o username=youruser,password=yourpasswd -t cifs //ipofpc/shareonpc dironphone
But that does not work in kernel 3.4. The share-directory as a device name is ignored. It has to be specified with argument unc. Like this:
Code:
mount -o unc=\\\\ipofpc\\shareonpc,username=youruser,password=yourpasswd -t cifs none dironphone
Note: since backslash is an escape character the double \\ is needed instead of \. It's also a good idea to specify noperm if you want the mounted directory to be accessible by all apps. Otherwise the mounted directory might only be accessible by root on the phone.
So a working example looks like this:
Code:
mount -o noperm,unc=\\\\10.0.0.200\\Public,username=guest,password=secret -t cifs none /sdcard/shares/nas
You have to work around that problem in CifsManager. Enter it like this:
Share Path: Enter anything. It will be ignored.
Mount Point: directory on phone: e.g. /sdcard/shares/nas
Username: enter user name
Password: leave empty
Options: e.g. noperm,unc=\\\\10.0.0.200\\Public,password=secret
Click to expand...
Click to collapse
I tried your solution (4.4, Nexus 5) and it actually mounts the volume correctly. The only problem is that mounted content is visibile only if you're root: i can't see the folders mounted from the applications even if the cifsmanager say it has been mounted.
I verified by mounting the volume via ADB and navigated to the mounted folder -> root can see the folder and normal user can't.
I also tried adding the parameters "rw,file_mode=0777,dir_mode=0777,nounix,iocharset=utf8", nothing.
Do you know something about this?

Same problem here on 4.4 N4
Sent from my Nexus 4 using Tapatalk 2

root only problem
ludalex07 said:
I tried your solution (4.4, Nexus 5) and it actually mounts the volume correctly. The only problem is that mounted content is visibile only if you're root: i can't see the folders mounted from the applications even if the cifsmanager say it has been mounted.
Click to expand...
Click to collapse
i've got the same issue on nexus 7 (new) running 4.3
here is my mount command:
mount -o noperm,unc=\\\\192.168.2.16\\Volume_2,username=guest,password=guest -t cifs musiq /sdcard/NAS
root only can see it.
from google groups, someone seems to have a workaraound, but i can not firgure out excactly what he means:
"when I mount using a shell-script (masked as a system-service like /system/bin/debuggerd) with "/system/bin/start" the mount is visible systemwide"
i tried replacing debuggerd with a script, but it is not part of the start-up services, so i am guessing /system/bin/start has to be invoked somehow?

noktilux said:
i've got the same issue on nexus 7 (new) running 4.3
here is my mount command:
mount -o noperm,unc=\\\\192.168.2.16\\Volume_2,username=guest,password=guest -t cifs musiq /sdcard/NAS
root only can see it.
from google groups, someone seems to have a workaraound, but i can not firgure out excactly what he means:
"when I mount using a shell-script (masked as a system-service like /system/bin/debuggerd) with "/system/bin/start" the mount is visible systemwide"
i tried replacing debuggerd with a script, but it is not part of the start-up services, so i am guessing /system/bin/start has to be invoked somehow?
Click to expand...
Click to collapse
The debugger method is described here: http://forum.xda-developers.com/showpost.php?p=37751808&postcount=55
Not sure it will work on 4.3, but you can give it a try.

[LINUX][POSTMARKETOS] Native Linux on the Asus Eee Pad Transformer TF101

Instructions HERE.
TO DO:
- Other things mentioned in the wiki:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
VERSION INFORMATION (CHANGELOG)
A newer MATE image is available to download. Download it here or here.
Notes about this release:
v4.0
- Please read the updated instructions.
- Vast performance improvements overall (because it's using mainline 5.12.8 grate kernel).
- It's trickier to get it working, if you cannot follow the instructions please change to v3.0.
v3.0
- Firmware has to be renamed at first boot.
Do the following command as root or using sudo:
Code:
sudo ash rename-firmware.sh
Those who are migrating from older versions or want to know what this .sh file is:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
Follow the wiki, look into Wi-Fi section.
Reboot and done.
- Bluetooth is working, but only from terminal.
Code:
sudo hciconfig hci0 up
hcitool scan
hcitool pair, etc etc
- Buttons from trackpad are working, mousepad not yet.
- Updated kernel zip. Latest release here: https://github.com/antonialoytorren...rnel_zip/PostmarketOS-kernel-3.1.10-15-r2.zip
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release

Screenshots
MATE 4.0 (mainline PostmarketOS kernel)
See HERE.
https://imgur.com/a/Sf7BbFt
XFCE 2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XFCE
MATE
JWM

Dual Booting Android and PostmarketOS
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
Note: Be sure to run the TWRP version 2.8.1.1, otherwise Android won't flash.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip (has some issues with WiFi, flashing the blob using dd and adb is more recommended, https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101))
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)

Reserved
Reserved

aat596 said:
XFCE
MATE
Click to expand...
Click to collapse
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations

be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
Having the PostmarketOS system in internal memory is harder and more difficult. You cannot install it on the bigger partition (the 30 GB one), I once tried and almost bricked my tablet because fails to boot due to media/ symlinks.
Unfortunately, you have to install it on /dev/block/mmcblk0p1 (533 MB partition).
I'm trying to make an usable small desktop image for /dev/block/mmcblk0p1 , XFCE is too big for that.
Nevertheless, you can enter recovery mode, do a Factory Reset and wipe Internal Memory to delete Android; then boot Linux from SDCard and use all available space to store your files.
If you want to make your image yourself, please look at https://wiki.postmarketos.org/wiki/Installation_guide and https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)

be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
EDIT: A mini JWM image is available for download. It has the size to fit in the Asus TF101 first partition (/dev/block/mmcblk0p1). Download here: https://downloads.sourceforge.net/project/tf101-linux-images/postmarketOS/minijwm-postmarketOS-TF101.zip
Then execute exactly the following commands:
Code:
$ unzip minijwm-postmarketOS-TF101.zip
$ cd minijwm-postmarketOS-TF101
$ adb push blob-asus-tf101 /cache
$ adb push minijwm-tf101.img /sdcard
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
# dd if=/sdcard/minijwm-tf101.img of=/dev/block/mmcblk0p1

Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?

Raphzer said:
Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?
Click to expand...
Click to collapse
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.

aat596 said:
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.
Click to expand...
Click to collapse
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.

Raphzer said:
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.
Click to expand...
Click to collapse
If it's your own working build then try these steps:
Code:
$ sudo pmbootstrap init (select asus-tf101 device, select [I]none[/I] when prompting graphical interface)
$ sudo pmbootstrap install && sudo pmbootstrap export
$ sudo dd if=/tmp/postmarketOS-export/asus-tf101.img of=/path/of/sdcard status=progress
$ adb push /tmp/postmarketOS-export/blob-asus-tf101 /cache
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
And then insert your sdcard and reboot.
Hope this helps. I have extracted it from https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101). The only difference is flashing onto internal memory or the sd card.
EDIT: Are you using a reliable SD Card (Kingston, SanDisk, ...)? It could lead to random errors or not identify it if not.

This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.

Raphzer said:
This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.
Click to expand...
Click to collapse
Yes, it could be the reason. If you run into multiple problems, try to format /system in TWRP and then try it again with only the SD Card.
Btw, what version is your TF101? SBKv1 or SBKv2? I have SBKv1, that could be another problem (but I'm not sure, as the SD Card is partition-independent, and the kernel blob file is compatible for both versions)

Very nice image !
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.

oink666 said:
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.
Click to expand...
Click to collapse
Yep, that's one of the things mentioned in the TODO list in my guide (look at nearly the end)
We have to compile xf86-mtrack-driver to get it working (there's no such driver in Alpine repos)
I lack a bit of C knowledge to get it working (because it fails when compiling), so help is appreciated

Awesome work.
Any chance of dual boot?
Thank you

riptide981 said:
Awesome work.
Any chance of dual boot?
Thank you
Click to expand...
Click to collapse
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual-boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)

XFCE 2.0
A newer XFCE image is available to download. Download it here: https://sourceforge.net/projects/tf101-linux-images/files/postmarketOS/xfce-postmarketOS-TF101-v2.0.zip
A little screenshot:
Notes about this release:
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release

Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?

gh05tface said:
Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?
Click to expand...
Click to collapse
I have just redownloaded zip file from sourceforge and I don't have this problem, so I don't know what it could be...
But there are some questions I would like to ask you:
- Does your keyboard work on Android? You can test it by flashing Timduru's Android image (https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip).
- Have you tried to do your own XFCE from scratch? https://github.com/antonialoytorrens/TF101-linux-images#doing-xfce-from-scratch. Hope this works, otherwise a patch for this kernel is needed.
- By the way, what version is your TF101? SBKv1 or SBKv2? I have SBKv1.

Database Users

welcome