Unmounting in Terminal Emulator - G1 Q&A, Help & Troubleshooting

ive done a search already and found nothing...is there a way or a file i unmount in terminal emulator to reduce the # of home screens because i only need the 3 that the stock firmware includes but i get 5..can any1 help?
ps..ive done a search already and found nothing..

search the forums for advanced launcher. it lets you configure the # of screens (and much more!)
Also, totally should go in the Q&A section, dude. For future reference.

boimarc89 said:
ive done a search already and found nothing...is there a way or a file i unmount in terminal emulator to reduce the # of home screens because i only need the 3 that the stock firmware includes but i get 5..can any1 help?
ps..ive done a search already and found nothing..
Click to expand...
Click to collapse
It's not as easy as that.
You'd need to build the Launcher.apk from source (i think) and manually edit the number of home screens.
Or you can do what biosehnsucht said, which is what i'd recommend

Related

Android app for linux 'FIND' command.

I was just wondering if there is a app for the linux find command so I can search for files, if there isn't one out there could someone please make one.
MURALEYPILLAI said:
I was just wondering if there is a app for the linux find command so I can search for files, if there isn't one out there could someone please make one.
Click to expand...
Click to collapse
Sure. Its called *open the terminal and use the find command*.
lbcoder said:
Sure. Its called *open the terminal and use the find command*.
Click to expand...
Click to collapse
While this does work it is not user friendly . It requires every android user to have terminal installed and understand linux. To clarify I would like a graphical .apk that all users can use something that shows options like search by size or extension and browse for a specific folder to search in.
Wrong forum, moving this.
And although it might be useful... it really won't be. The only reason you should be searching through the linux install for files is if you understand what you're doing, and in which case, you'd know how to use find (or at least read the man page for it).
SU File Manager & Terminal has a find gui. I don't use it much because it also has a terminal It's a payed app ($1.99) but well worth it for me.
Here's the thread in this forum: SUFBS
look for me
I posted a script like this here
http://forum.xda-developers.com/showthread.php?p=4247181
I have a terminal and a rooted droid 2, but I can not find a "find" command. I can find all the normal suspects in sys. Find would be very useful. Anyone know were this command hides on a droid 2 or do I need to download a special apk for this command?
Try busybox
After rooted, you can find "find" in busybox. Busybox is found in android market, and you can find how to be rooted in this forum.
Thanks.

Changing the LCD Density Post Install?

I need to change my LCD density on my phone (NAND / Warm Donut), but I do not want to reinstall the whole system...is there a way to change the LCD density without formatting/reinstalling Android?
Also what is the best NBH resolution and density combination to use?...I tried 120 density on 240x320 NBH file, but it is 'too big'...I have to scroll down to see stuff. 110 was perfect it seemed for 240x320 except that it left some black space on the edges at times.
Thanks,
-C
su
mount /system -o rw,remount
edit ro.sf.lcd_density in /system/build.prop
mount /system -o ro,remount
then reboot
I am a Windows user. How do I do it in Windows or in the phone. Also my phone is not "rooted" (whatever that means)
crobs808 said:
I am a Windows user. How do I do it in Windows or in the phone. Also my phone is not "rooted" (whatever that means)
Click to expand...
Click to collapse
Our phones are rooted, period.
You have to use adb to do it from windows or linux, or be comfy using vi on the phone (ha.)
so you'd do the remount stuff mentioned above, then
Code:
adb pull /system/build.prop/ro.sf.lcd_density c:\mydata\ro.sf.lcd_density
*edit the pulled file*
adb push c:\mydata\ro.sf.lcd_density /system/build.prop/
mrkite38 said:
Our phones are rooted, period.
You have to use adb to do it from windows or linux, or be comfy using vi on the phone (ha.)
so you'd do the remount stuff mentioned above, then
Code:
adb pull /system/build.prop/ro.sf.lcd_density c:\mydata\ro.sf.lcd_density
*edit the pulled file*
adb push c:\mydata\ro.sf.lcd_density /system/build.prop/
Click to expand...
Click to collapse
Ok thanks...now, what is the best NBH resolution and density value combination to use for the Vogue?
open a terminal "better terminal emulator" on your phone
type
su
mount /system -o rw,remount
Click to expand...
Click to collapse
use astro to browse and edit /system/build.prop
look for the line ro.sf.lcd_density=120
change it to whatever you like save changes.
makes filesystem read only
Code:
mount /system -o ro,remount
restart phone
seriously read Tatnai's FAQ (apparently yours isn't the easiest if it didn't work on your own Vogue) and stop making these useless threads.
berardi said:
seriously read Tatnai's FAQ (apparently yours isn't the easiest if it didn't work on your own Vogue) and stop making these useless threads.
Click to expand...
Click to collapse
Huh? I didn't incorporate anything about LCD density into my tutorial on purpose...my tutorial is about how to install Android via the NAND method...has nothing to do with density tweaking, and I never intended it to.
Also "stop making threads"...? What is this forum for then, because I only post a thread when the search or FAQs do not cover something. Isn't that the point of a forum?
myn said:
Change LCD Density to 110
Change LCD Density to 160
Click to expand...
Click to collapse
If you want any other density edit the build.prop within these files - look for lcd density and change it to what you want. Go into your boot up menu and do "install update"
Do a little reading like everyone else does, studies show it is good for your brain.
if using 320x480, you should use lcd.density of 160.
if using 240x320, most people use something between 110 and 120. I like 110, things are a little smaller, easier to see in messaging, and the eclair dialer and wysie's dialer fit the screen. others like 120, because supposedly it is a little "crisper"; try for yourself. I've played around with 113, 115, -> basically everything between 120 and 110.
if using 320x428 (does anyone use this anymore???) use 160 (I think, I can't even remember anymore).
there is a full discussion of other benefits of different resolutions in the FAQ thread. also, you might want to take a look at the market FAQ post, as it applies.
berardi said:
If you want any other density edit the build.prop within these files - look for lcd density and change it to what you want. Go into your boot up menu and do "install update"
Do a little reading like everyone else does, studies show it is good for your brain.
Click to expand...
Click to collapse
ha...you like following me around the board and insulting me. you have done this now on three threads where i simply ask a question on how to do something, then you state that my post is 'useless'. that really lends itself to good discussion. please re-evaluate why you post things because you are definitely not doing it to help me or answer the original question.
p.s. - i did read the forum and search before i posted. all the instructions so far were how to do it on Linux or how to do it using ADB, neither of which I have at my disposal. The other posters in this thread helped, which I had already stated (post #5 on pg.1) before you even posted, so there was no reason for you to post all all, except to get your insult in I guess. Stop following me around the forum. Now.
crobs808 said:
ha...you like following me around the board and insulting me. you have done this now on three threads where i simply ask a question on how to do something, then you state that my post is 'useless'. that really lends itself to good discussion. please re-evaluate why you post things because you are definitely not doing it to help me or answer the original question.
p.s. - i did read the forum and search before i posted. all the instructions so far were how to do it on Linux or how to do it using ADB, neither of which I have at my disposal. The other posters in this thread helped, which I had already stated (post #5 on pg.1) before you even posted, so there was no reason for you to post all all, except to get your insult in I guess. Stop following me around the forum. Now.
Click to expand...
Click to collapse
It is my opinion man, can't we all post our own opinions wherever we want? these were your words afterall..
As for you reading the forum and not finding the answers, well apparently you can't read very well. Trust me I am FAR from a coder / developer / hacker - I learned how to do it simply by reading other posts. If you do a little reading you can get far.
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
tmcfarland said:
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
Click to expand...
Click to collapse
Are you using one of those files I linked to? I found it easiest to do it in windows on a pc. If so, open up the .tar file and look for build.prop - open that and make the change. Close the file and it should allow you to save changes. Put that on an sd card in your phone reboot and install update and you should be good.
berardi said:
Are you using one of those files I linked to? I found it easiest to do it in windows on a pc. If so, open up the .tar file and look for build.prop - open that and make the change. Close the file and it should allow you to save changes. Put that on an sd card in your phone reboot and install update and you should be good.
Click to expand...
Click to collapse
That did the trick ... many thanks!
crobs808 said:
I need to change my LCD density on my phone (NAND / Warm Donut), but I do not want to reinstall the whole system...is there a way to change the LCD density without formatting/reinstalling Android?
Also what is the best NBH resolution and density combination to use?...I tried 120 density on 240x320 NBH file, but it is 'too big'...I have to scroll down to see stuff. 110 was perfect it seemed for 240x320 except that it left some black space on the edges at times.
Thanks,
-C
Click to expand...
Click to collapse
Either use an androidupdate.tar, or, if you need to do it on your phone:
Open BetterTerminal.
1. Type 'su', enter.
2. Type 'mount -o remount,rw /system', enter.
3. Type 'vi /system/build.prop'.
4. Scroll down to the build.prop section. Put the cursor where you want to modify.
5. Hit 'i' to go into edit/insert mode.
6. Hit backspace to delete the comment "#" of the line you want..
7. Add a # to the old density line. You can safely use the dpad to move in edit mode.
8. Hit escape (Hold Center Button and type '1'), to leave edit/insert mode.
9. Type ':wq', then enter, to write and quit.
10. Power down (the proper way, hold red button, hit power off....).
You can always hit escape (Center-1), then ':q<enter>' to quit without saving if you mess up. Then start over.
I just did this, so it works.
Vi has two modes, edit mode, and command mode. If you don't know what mode you're in, always just hit ESC (Hold center button, type the number '1') to return you to command mode.
BetterTerminal is kinda screwy, the cursor covers the letter before it, so you have to keep that in mind.
Personally, I prefer 120, it's nice and clear. It originally was changed from 120 to 110 because Google Maps would freeze on the 3.4.0? update and a density of 120, however 4.0.0+ seems to fix that. I don't know why Myn doesn't go back.... Google maps works perfectly fine for me now on 120.
jnadke said:
Either use an androidupdate.tar, or, if you need to do it on your phone:
Open BetterTerminal.
1. Type 'su', enter.
2. Type 'remount -o remount,rw /system', enter.
3. Type 'vi /system/build.prop'.
4. Scroll down to the build.prop section. Put the cursor where you want to modify.
5. Hit 'i' to go into edit/insert mode.
6. Hit backspace to delete the comment "#" of the line you want..
7. Add a # to the old density line. You can safely use the dpad to move in edit mode.
8. Hit escape (Hold Center Button and type '1'), to leave edit/insert mode.
9. Type ':wq', then enter, to write and quit.
You can always hit escape (Center-1), then ':q<enter>' to quit without saving if you mess up. Then start over.
I just did this, so it works.
Vi has two modes, edit mode, and command mode. If you don't know what mode you're in, always just hit ESC (Hold center button, type the number '1') to return you to command mode.
BetterTerminal is kinda screwy, the cursor covers the letter before it, so you have to keep that in mind.
Personally, I prefer 120, it's nice and clear. It originally was changed from 120 to 110 because Google Maps would freeze on the 3.4.0 update and a density of 120, however 3.4.1+ seems to fix that. I don't know why Myn doesn't go back....
Click to expand...
Click to collapse
Man you are a vi hacker!!
The only reason I am using 110 (soon to be 113) is because the eclair dialers cut off the top of the numbers with 120. Some themes however don't have the eclair dialer so 120 is completely perfect for it.
This process of changing density will become inherently easier come the next release of Warm Donut . More to come as I make more progress.. I will leave it at that.
myn said:
Man you are a vi hacker!!
The only reason I am using 110 (soon to be 113) is because the eclair dialers cut off the top of the numbers with 120. Some themes however don't have the eclair dialer so 120 is completely perfect for it.
This process of changing density will become inherently easier come the next release of Warm Donut . More to come as I make more progress.. I will leave it at that.
Click to expand...
Click to collapse
Astro wouldn't save the changes to build.prop Even after su/remount (That's because only BetterTerminal gets su privileges, not Astro)
Yeah, I've learned to love vi, mainly because searching is similar to sed, unlike that stupid emacs.
I actually use 123, I'm greedy
the 1, 2, 3 don't bother me in the least, you can still press them and I rarely dial numbers manually
tmcfarland said:
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
Click to expand...
Click to collapse
Ditto - I tried doing it this way after reading a post on page like 153 (or there abouts) on the main Myn Warm Donut thread to no avail. Definitely doesn't work.

Need Help From The pros

So I'm fairly new to android about three months now, and need help.....
1) How do you modify system files and apk's? (tried Estrongs but it won't let me use root access even when i click the always allow prompt)
2) Can someone explain exactly how i partition for Apps2SD ( PM me if possible)
3) Can you change bootscreens with a .zip flash? if so does anyone have a link for the cynanogen mod nexus boot as used in Darchvanilla??
Thank you and any help is deeply appreciated.....
did you just make 2 threads of the exact same thing???
That search feature has been breaking all damn day!! I swear we need a HUGE Search icon in the middle of the freakin forum.
not purposely i'm on a slow connection and clicked it twice???
abov3dis said:
not purposely i'm on a slow connection and clicked it twice???
Click to expand...
Click to collapse
Then why are some of the questions different on the two threads?
abov3dis said:
So I'm fairly new to android about three months now, and need help.....
1) How do you modify system files and apk's? (tried Estrongs but it won't let me use root access even when i click the always allow prompt)
2) Can someone explain exactly how i partition for Apps2SD ( PM me if possible)
3) Can you change bootscreens with a .zip flash? if so does anyone have a link for the cynanogen mod nexus boot as used in Darchvanilla??
Thank you and any help is deeply appreciated.....
Click to expand...
Click to collapse
1) mount to your pc pull the apk you wish then use "7 zip" to extract it
2) boot into recovery(home + end call) go to partition...partition swap + file + ext
3) yes you can flash a boot screen using a zip file
For the bootscreens use Fresh's new kitchen. It has the nexus one bootscreen and a couple others. Then you just hit a couple of buttons and its on your phone without having to manually edit or even boot into recovery.

[Request] Virtual Device Emulator

thats it... im taying to make a virtual emulator of the nexus one.... and i need help... i want an AVD emulator that looks exactly as the nexus one system..
i have the system.img of my fist nandroid backup, i dont know if i can do it with that.
please, i need help
Yeaaah. I also wanted to know how to do this.
wrong section, also there are multiple different sites with tutorials including xda that show you how to set up an emulator.
jmotyka said:
wrong section, also there are multiple different sites with tutorials including xda that show you how to set up an emulator.
Click to expand...
Click to collapse
i know. i can set up an emulator, i didnt found any tutorial to set up an emulator with a custom system
Budske said:
i know. i can set up an emulator, i didnt found any tutorial to set up an emulator with a custom system
Click to expand...
Click to collapse
here this might help you http://android.modaco.com/content/g...p-and-running-a-full-rom-with-the-market-etc/
im trying it.... again.. i hope it works
it only shows a black screen with a text that says "Android"... 7 minutes waiting
its loading ive sat there forever and if finally loads

Enabling sideloading on Captivate with mac

Hi guys, I know some of you are just going to tell me to do a search on this, but I've already tried. So, my problem is, I'm very new to android and am trying to learn all this stuff and quickly and possible but it still feel like a giant noob because even when I've followed directions on what to do in Terminal it never works and I need some help. I've already rooted it and have removed At&T's bloatware and am running 2.1. Does anyone have, or have a link to relatively n00b related instructions for how to do this on a Mac thru terminal or something? Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
You can install a rom if you want, thats what I did.
Jsmallsawe said:
Hi guys, I know some of you are just going to tell me to do a search on this, but I've already tried. So, my problem is, I'm very new to android and am trying to learn all this stuff and quickly and possible but it still feel like a giant noob because even when I've followed directions on what to do in Terminal it never works and I need some help. I've already rooted it and have removed At&T's bloatware and am running 2.1. Does anyone have, or have a link to relatively n00b related instructions for how to do this on a Mac thru terminal or something? Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Here's a link to how I did it. (and there are probably other ways like just simply flashing custom ROM).
1) Root'ed using one of the update.zip methods floating around. I think I used this one.
2) Downloaded Root Explorer and SQLite Editor. Both of these are paid apps but look like they are worth owning. For instance, you can also use Root Explorer to rename and disable the AT&T bloatware, as an alternative to this method.
3) Using Root Explorer, mount the filesystem R/W and copy /dbdata/databases/com.android.providers.settings/settings.db to /sdcard/settings.db
4) Open /sdcard/settings.db in SQLite Editor
5) Open the 'secure' table
6) Long-hold on record 6, "install_non_market_apps" and select "Edit Record"
7) Change the value from 0 to 1 and save
8) Back in Root Explorer, copy /sdcard/settings.db back to /dbdata/databases/com.android.providers.settings/settings.db
9) I don't remember if I had to reboot or not, but you may as well.
Click to expand...
Click to collapse
Couple of notes, instead of downloading SQLite Editor, you can download an add-on for firefox called SQLite Manager. Load up your settings.db and select secure, then I believe the numbering is different from SQLite Editor. Just find "install_non_market_apps", edit the value from 0 to 1, then copy and paste the new settings.db to the original location. You might also want to re-name the original settings.db to something so that the phone doesn't recognize it but it's there. Also you need to reboot.

Categories

Resources