So, every time I need to use the terminal emulator I type and the line stays blank till I press enter. I can't read what I type in real time. This causes command errors. Also I have to remember to clear the whole line if I mess up and it won't show back spacing if the letters haven't been manifested yet so that also leads to errors. I'm using Multirom now but have had this problem in many ROMs. It also happens in all forms of terminal emulators I try. From all apps. ROM toolbox pro, terminal emulator pro, etc.
Anyone else have that happen?
Supermatt01 said:
So, every time I need to use the terminal emulator I type and the line stays blank till I press enter. I can't read what I type in real time. This causes command errors. Also I have to remember to clear the whole line if I mess up and it won't show back spacing if the letters haven't been manifested yet so that also leads to errors. I'm using Multirom now but have had this problem in many ROMs. It also happens in all forms of terminal emulators I try. From all apps. ROM toolbox pro, terminal emulator pro, etc.
Anyone else have that happen?
Click to expand...
Click to collapse
first: how about screenshots?
and WHICH errors?
Terminal Emulator need some time after the boot .. so 10-15 secs ..
diedmaster said:
first: how about screenshots?
and WHICH errors?
Terminal Emulator need some time after the boot .. so 10-15 secs ..
Click to expand...
Click to collapse
Thanks for a reply but screen shots won't really show you anything because it wouldn't be a distinct error you'd be able to pick out from a pic. You'd just have to have the same issue and you'd understand. I'm not talking about running a command at boot so that's not related to the issue.
Supermatt01 said:
Thanks for a reply but screen shots won't really show you anything because it wouldn't be a distinct error you'd be able to pick out from a pic. You'd just have to have the same issue and you'd understand. I'm not talking about running a command at boot so that's not related to the issue.
Click to expand...
Click to collapse
yea. I think I know what you mean .. but there must have been some errors .. does terminal emulator not having all needed permission? e. g. file permission? And I wasn't talking about the boot from the phone, I talked about the boot of the APP. I should more clearify that sorry
Related
Hey gang,
I am trying to create a script (using GScript Lite) that will preview the boot animation currently loaded. I am running 2.1 leak v3 and don't have root yet. I made a script with only one line like this: "adb shell bootanimation" and saved it. When I try to run the script I get the "permission denied" error. I guess I need root to run the command locally on the phone. Odd though.... because I can run the command from my computer connected via USB and it works just fine. Can anyone explain why its not working locally when I run the script? Surely it does not trigger root access when running this command from a computer.... does it?
Curious....
Also, is there another way around this so I can accomplish previewing the boot animation on my phone without external input? I searched the market and installed the app called "Boot Animation Preview Lite". It required AndExplorer to be installed to work.... but it never did actually work. Only Force Closes on every attempt.
synaptyc said:
Hey gang,
I am trying to create a script (using GScript Lite) that will preview the boot animation currently loaded. I am running 2.1 leak v3 and don't have root yet. I made a script with only one line like this: "adb shell bootanimation" and saved it. When I try to run the script I get the "permission denied" error. I guess I need root to run the command locally on the phone. Odd though.... because I can run the command from my computer connected via USB and it works just fine. Can anyone explain why its not working locally when I run the script? Surely it does not trigger root access when running this command from a computer.... does it?
Curious....
Also, is there another way around this so I can accomplish previewing the boot animation on my phone without external input? I searched the market and installed the app called "Boot Animation Preview Lite". It required AndExplorer to be installed to work.... but it never did actually work. Only Force Closes on every attempt.
Click to expand...
Click to collapse
Have you tried
Code:
adb shell bootanimation
I doubt it needs root to be run but that will show you the boot animation and it will keep looping until you stop the command which on windows is control C
lol.... did you even read my post?
rofl
synaptyc said:
lol.... did you even read my post?
rofl
Click to expand...
Click to collapse
Lol probably not...
when running it from the phone where is it running from?
also if you are running it from phone it doesn't need the adb shell part
it should be
Code:
bootanimation
^^ I tried this from a terminal but it doesn't work unless I give the terminal su privilages.
so there might not be a way to do this on the phone without root privilages.
Sorry I couldn't be any help.
Its all good t2noob. Thnx for the info... food for thought.
Time to write an app for that =)
results so far:
I created a GScript called "bootscreen" (because I am using a bootscreen with sound and not a "bootanimation.zip"
I checked 'Needs SU?' because I now have root
Then I added the line: bootanimation
All goes well, and I can see/hear my bootscreen BUT I can't end it.
It continually loops like it is supposed to.
Can anyone tell me how to kill the bootanimation once it has been called via GScript Lite?
Things I have tried:
hitting the BACK, HOME, MENU, END/OFF buttons. really every button on the phone.
tapping the place on the screen where I have a "QuitIt" widget that will kill all running apps
The phone will accept screen input because I can tap where certain apps are and tell that they are launching. IE: phone, music player, etc.
I was even able to reboot the phone using Quick Boot just because I knew where the on-screen buttons were to make it reboot.
There seems to be no way to kill the bootanimation except to pull the battery.
Maybe I could create a GScrpit that will kill it, then just know where it is on the screen behind the animation?
Any tips?
EDIT: I created a script like this but it still didn't kill the bootanimation (it did run correctly with the sleep thing though)
Code:
bootanimation
sleep 10
pkill bootanimation
pkill boot1.gif
pkill boot2.gif
This is how I've done it through gscrip:
Code:
TIMEOUT=20
( bootanimation & sleep
$TIMEOUT; kill $! 2>/dev/null )
you can change the timeout duration to suit your liking (it's in seconds).
Regards,
Yahya
........ 10 chars.
Can you be more specific? That does not help us at all. Which ROM are you running and what is your error message?
Sent from my Eris using XDA App
Hello, my names Alex and I've been trying to install this battery tweak as well, but I can't. I follow the instructions. It says to run the terminal emulator and type "su" to grant superuser. Ok. That part works fine. BUt when it says to type "batt-cfg, then 1 and then press enter. It says batt-cfg1 not found.. Ans I can't get passed that part... What am I doing wrong?
Palexo said:
Hello, my names Alex and I've been trying to install this battery tweak as well, but I can't. I follow the instructions. It says to run the terminal emulator and type "su" to grant superuser. Ok. That part works fine. BUt when it says to type "batt-cfg, then 1 and then press enter. It says batt-cfg1 not found.. Ans I can't get passed that part... What am I doing wrong?
Click to expand...
Click to collapse
The instructions assumed a level of familiarity with the command line. You need to put a space between "batt-cfg" and "1".
i have been experiencing some force closes and random restarted, is there a program that can tell me what caused it or what app caused the error.
Not really a simple way to troubleshoot that. Did you do a full wipe prior to flashing whatever ROM you're running? Trying booting into recovery and wiping dalvik/cache, that can fix plenty of small issues.
bluephi1914 said:
i have been experiencing some force closes and random restarted, is there a program that can tell me what caused it or what app caused the error.
Click to expand...
Click to collapse
yes, logcat will show you, but you have to kinda know what you're looking for. There are some logcat apps on the market or you can logcat through ADB.
Also, random app FCs aren't all that weird, BUT if you are getting them consistently you could very likely fix it by fixing permissions in recovery.
If you fix perms and the issues persist, feel free to pull a logcat of the app crash, and either PM me the .txt file or link it here via pastebin.com. I am no expert but I could try to help. But again, fix perms first, that'll probably work.
bluephi1914 said:
i have been experiencing some force closes and random restarted, is there a program that can tell me what caused it or what app caused the error.
Click to expand...
Click to collapse
Yes, there is a way but it requires a bit of technical knowledge. Assuming you have the motivation, acquiring the knowledge shouldn't be an issue.
If you're familiar with how to use ADB (Android Debug Bridge), this program allows you to access a log Android creates on the device where all applications output errors, debug, warning and verbose information.
From the command line, you'd run, adb logcat or adb shell logcat. If you prefer to have a bit of a GUI, run ddms which is also packaged inside the Android SDK.
There is an Android application called aLogCat for free in the Android Market which offers a GUI on the device for viewing this information. Feel free to also try this method and see which works best for you.
Essentially, this log will contain a lot of information. HTC coders seem to lean on the side of outputing a lot of information.
This log is real time, it will scroll as the applications output information. The best way to find the FC is to trigger the FC and immediately look in logcat for the details. They should be flagged by E, for error, followed by some type of name convention for the application. There will generally be anywhere from 5-15 lines of output in logcat when an application force closes.
Once you're able to locate the FC error output in logcat, feel free to post back up here and we can attempt to give some feedback.
Understand, sometimes the issue is the result of the application developer's poor coding or not being able to forsee a potential error. Other times, the solution is as simple as wiping dalvik-cache or wiping the application's settings causing it to start again from scratch.
Hope that helps! Good luck!
joeykrim said:
Yes, there is a way but it requires a bit of technical knowledge. Assuming you have the motivation, acquiring the knowledge shouldn't be an issue.
If you're familiar with how to use ADB (Android Debug Bridge), this program allows you to access a log Android creates on the device where all applications output errors, debug, warning and verbose information.
From the command line, you'd run, adb logcat or adb shell logcat. If you prefer to have a bit of a GUI, run ddms which is also packaged inside the Android SDK.
There is an Android application called aLogCat for free in the Android Market which offers a GUI on the device for viewing this information. Feel free to also try this method and see which works best for you.
Essentially, this log will contain a lot of information. HTC coders seem to lean on the side of outputing a lot of information.
This log is real time, it will scroll as the applications output information. The best way to find the FC is to trigger the FC and immediately look in logcat for the details. They should be flagged by E, for error, followed by some type of name convention for the application. There will generally be anywhere from 5-15 lines of output in logcat when an application force closes.
Once you're able to locate the FC error output in logcat, feel free to post back up here and we can attempt to give some feedback.
Understand, sometimes the issue is the result of the application developer's poor coding or not being able to forsee a potential error. Other times, the solution is as simple as wiping dalvik-cache or wiping the application's settings causing it to start again from scratch.
Hope that helps! Good luck!
Click to expand...
Click to collapse
YOU HAVE GOT TO BE KIDDING ME... LOL as soon as i typed "adb logcat" at the command prompt in windows, the screen immediately fills up... and like you said its real time so it doesn't stop.
When "ADB logcat" is typed how far does this log go back. I think i typed it about 5-10 minutes after the restart....or random hot reboot. was this to long ???
Most of the lines begin with D/ or I/ or or V/ didn't see any E .... but im currently scrolling back through all of the output in the CMD screen, i had to unplug the phone to get it to stop scrolling.
il Duce said:
yes, logcat will show you, but you have to kinda know what you're looking for. There are some logcat apps on the market or you can logcat through ADB.
Also, random app FCs aren't all that weird, BUT if you are getting them consistently you could very likely fix it by fixing permissions in recovery.
If you fix perms and the issues persist, feel free to pull a logcat of the app crash, and either PM me the .txt file or link it here via pastebin.com. I am no expert but I could try to help. But again, fix perms first, that'll probably work.
Click to expand...
Click to collapse
typing "ADB logcat" from the command prompt in windows doesn't give me a .txt file does it?
bluephi1914 said:
typing "ADB logcat" from the command prompt in windows doesn't give me a .txt file does it?
Click to expand...
Click to collapse
Try to use the Fix Permissions Opinion in the Rom Manager App! That May Help...
Here's a Screenshot...
PMGRANDS said:
Here's a Screenshot...
Click to expand...
Click to collapse
Ok.. downloaded ROM Manager and ran Fix Permissions. Hopefully that will fix any issues that I had.
bluephi1914 said:
YOU HAVE GOT TO BE KIDDING ME... LOL as soon as i typed "adb logcat" at the command prompt in windows, the screen immediately fills up... and like you said its real time so it doesn't stop.
When "ADB logcat" is typed how far does this log go back. I think i typed it about 5-10 minutes after the restart....or random hot reboot. was this to long ???
Most of the lines begin with D/ or I/ or or V/ didn't see any E .... but im currently scrolling back through all of the output in the CMD screen, i had to unplug the phone to get it to stop scrolling.
Click to expand...
Click to collapse
D is debug, I is Information, V is verbose and E is Error. All FC messages will start with E although, sometimes other logcat information will help make the FC easier to understand. I usually gather them all around a specific FC and narrow it down as I go.
I don't recall the buffer limit size to logcat, but it is generally best to grab the logcat as soon as the FC issue occurs, that way the issue will be closest to the end of the buffer. This makes it easier to locate and less likely to be pushed out of the buffer.
bluephi1914 said:
typing "ADB logcat" from the command prompt in windows doesn't give me a .txt file does it?
Click to expand...
Click to collapse
no, by default it updates the screen in real time, to have it dump to a text file, adb logcat > logcat.txt . you might need to hit cntrl+c to stop it as it will continue to write in real time to the log file until you exit. the exit command is cntrl + c to kill the process, same as exiting.
Hope that helps arm you with another skill!
edit: in the last month since i originally posted my first answer, i found an application on the market, which is essentially a GUI for logcat called aLogCat. the developer open sourced his code and the application started in 2009. seems to work very well.
source code: http://code.google.com/p/alogcat
Hi, I was wanting to root my legend 2.2 froyo. I came across a simple guide:
[Guide] Hboot 1.0.1 root, made easy
The guide was easy to understand but on one of the steps, it stated
open crackin.bat (your phone will reboot 5 times)
Click to expand...
Click to collapse
I opened it but it doesn't work! My phone doesn't reboot 5 times like what it was supposed to. Am I doing something wrong? Any helps appreciated. Tks!
EDIT: Ok I got it to work but the problem is it gives me an error code!
Code
error: more than one device and emulator
Click to expand...
Click to collapse
and the phone only reboots twice.
After that, temproot the device, typed
adb shell
error: more than one device and emulator
Click to expand...
Click to collapse
May I know what's the issue here? Sry new to this. Really appreciate any helps.
Maybe try unplugging all other usb-related stuff, mouse keyboard, etc.. so it can't confuse them as other devices?
ahhh, I had this issue when rooting, if you do a "adb devices" you might find you have 2 devices listed, in my case i had 1 "(my device serial) offline" and 2 "(my device serial) recovery"
you have to issue an adb command to kill the server, but I can't remember the command,
oh guess what the command is "adb kill-server" i think thats all you need?
Then it should work.
If not, then you might have to do a search for the exact problem your having, 100's if not 1000's have had simular problems one way or another, so your not alone and the solution should be out there, key word "search"
Ah! Tks for ur generous replies. I actually restarted my pc and then when I typed adb shell, it automaticallies kills the server by itself tks for ur help! Another thing is that when I make my goldcard using goldcard tool 0.07, everything was fine but when I checked my removable disk drive, it doesn't show anything except 3 folders (Android.secure, LOST.DIR and whatsapp) is it supposed to be like that?
Sent from my HTC Legend using XDA App
https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
most time we solve this by deleting recreating data.img
I hope that helps you
ecksdeeay said:
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
Click to expand...
Click to collapse
I did that. But this is all I could take a picture of. http://i.imgur.com/7rseNNe.jpg I have no clue what any of it means.
I opened it in guest mode.
imadlatch said:
most time we solve this by deleting recreating data.img
I hope that helps you
Click to expand...
Click to collapse
I dont know how to do that. I cant seem to be able to open the ISO that was in the zip file I downloaded. However, I formatted my flashdrive and used the included tool to reinstall Remix OS. It didnt help.
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
ecksdeeay said:
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
Click to expand...
Click to collapse
Here's what I got doing that. http://imgur.com/a/SL1rQ
I never got the second exit prompt. I just got the errors in this https://i.imgur.com/sGo2EQ5.jpg image over and over.
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
ecksdeeay said:
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
Click to expand...
Click to collapse
androidboot.selinux=permissive is present there by default. Im using a lenovo ideapad y510P with core i7 4700MQ, 8 Gigs of RAM and dual Nvidia GT 755M.
incognitonk said:
Nvidia GT 755M.
Click to expand...
Click to collapse
Nvidia is the problem then. ...
ecksdeeay said:
Nvidia is the problem then. ...
Click to expand...
Click to collapse
Really? Oh well, guess Im gonna be playing the waiting game then.
Thanks for everything up until now.
Search as I think there are work arounds @incognitonk
incognitonk said:
https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
Click to expand...
Click to collapse
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Hit thanks if it help
mdezazrock said:
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Click to expand...
Click to collapse
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
incognitonk said:
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
Click to expand...
Click to collapse
I don't know the blinking error solution , my friend also have that same problem , but there is a easy solution for resolution -
Root remix os , open any rooted browser , go to system folder , then open build.prop , edit the file , just add a line at the end
"ro.sf.lcd_density=150"
Write that line without quote , save build.prop , and change the number between 140 to 210 , see which one looks better on your monitor , have fun exploring remix ☺