[Q] - HD2 Android Q&A, Help & Troubleshooting and Genera

Hi all!
Recently I flashed tytung rom:
[2.Jun.2012] NexusHD2-ICS-4.0.4-CM9-HWA V2.2 (Kernel: tytung_HWA_r3)
It's a good one, no random resets since flashing, it's quite stable.
2 issues i encountered:
1. no way to remove google search from main screen
2. FuelLog Pro v2.2.1 doesn't work, crush right away
Did anyone experience it and can help solving it up?
Thanks!

ehud83 said:
Hi all!
Recently I flashed tytung rom:
[2.Jun.2012] NexusHD2-ICS-4.0.4-CM9-HWA V2.2 (Kernel: tytung_HWA_r3)
It's a good one, no random resets since flashing, it's quite stable.
2 issues i encountered:
1. no way to remove google search from main screen
2. FuelLog Pro v2.2.1 doesn't work, crush right away
Did anyone experience it and can help solving it up?
Thanks!
Click to expand...
Click to collapse
The Google search bar can be removed in the Trebuchet settings (there's a flashable zip in the thread which enables them) and try moving that app to the internal storage (it's a weak suggestion but on occasion it works).

Thanks!
Number 1 solved.
Now I need help with number 2..

ehud83 said:
Thanks!
Number 1 solved.
Now I need help with number 2..
Click to expand...
Click to collapse
Try clearing the data for that app and then rebooting to recovery and under advanced menu option select "Fix Permissions" solves a lot of my force closes. Other than that you may need to post a logcat and/or traces.txt file

elesbb said:
Try clearing the data for that app and then rebooting to recovery and under advanced menu option select "Fix Permissions" solves a lot of my force closes. Other than that you may need to post a logcat and/or traces.txt file
Click to expand...
Click to collapse
I tried what you suggested - no success.
I'll appreciate if you tell me where can I find logcat and traces.txt
Thanks!

ehud83 said:
I tried what you suggested - no success.
I'll appreciate if you tell me where can I find logcat and traces.txt
Thanks!
Click to expand...
Click to collapse
Well logcat is an android debug tool found in ADB or a terminal emulator. Traces.txt is located
Code:
/data/anr/traces.txt
To make a logcat follow the steps below
Code:
1. Open ADB or a terminal emulator inside your phone.
PRESS ENTER after each command or after each segment of ' '
2. Type 'su'
3. followed by 'logcat -c'
4. Then go open your program that always force closes
5. Go back to your ADB or terminal emulator
6. Then type 'logcat -d > /mnt/sdcard/logcat.txt'
7. Then plug your phone into your computer and enable USB mass storage and find the file on your SD card labled "logcat.txt"
8. And post it for me to look at :)
That should help in the diagnoses

elesbb said:
Well logcat is an android debug tool found in ADB or a terminal emulator. Traces.txt is located
Code:
/data/anr/traces.txt
To make a logcat follow the steps below
Code:
1. Open ADB or a terminal emulator inside your phone.
PRESS ENTER after each command or after each segment of ' '
2. Type 'su'
3. followed by 'logcat -c'
4. Then go open your program that always force closes
5. Go back to your ADB or terminal emulator
6. Then type 'logcat -d > /mnt/sdcard/logcat.txt'
7. Then plug your phone into your computer and enable USB mass storage and find the file on your SD card labled "logcat.txt"
8. And post it for me to look at :)
That should help in the diagnoses
Click to expand...
Click to collapse
OK! I'll try to do it, but it would take a few days due to work and semester exams.
I'll post it as soon as possible.
Thank you!

ehud83 said:
OK! I'll try to do it, but it would take a few days due to work and semester exams.
I'll post it as soon as possible.
Thank you!
Click to expand...
Click to collapse
Yep not a problem! Traces.txt is auto generated by the program so thats just a matter of extracting and posting logcat is a little more complicated.

Here is logcat.txt file
Thanks a lot!

ehud83 said:
Here is logcat.txt file
Thanks a lot!
Click to expand...
Click to collapse
good job creating that logcat not much garbage was inlcuded thank you so much!!!
But after looking at it, its a developer error on terms of the person who created it, not your HD2 or anything on your part.
Code:
W/dalvikvm(12012): Verifier rejected class Lt7iscAj4/UDOaYxz;
and
Code:
W/dalvikvm(12012): threadid=1: thread exiting with uncaught exception (group=0x40a571f8)
E/AndroidRuntime(12012): FATAL EXCEPTION: main
E/AndroidRuntime(12012): java.lang.VerifyError: t7iscAj4/UDOaYxz
E/AndroidRuntime(12012): at ch.simonmorgenthaler.fuellog.FuelLog.onCreate(FuelLog.java:41)
E/AndroidRuntime(12012): at android.app.Activity.performCreate(Activity.java:4465)
E/AndroidRuntime(12012): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1049)
E/AndroidRuntime(12012): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2033)
E/AndroidRuntime(12012): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2104)
E/AndroidRuntime(12012): at android.app.ActivityThread.access$600(ActivityThread.java:132)
E/AndroidRuntime(12012): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1157)
E/AndroidRuntime(12012): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(12012): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(12012): at android.app.ActivityThread.main(ActivityThread.java:4575)
E/AndroidRuntime(12012): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(12012): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(12012): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
E/AndroidRuntime(12012): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
E/AndroidRuntime(12012): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager(10213): Force finishing activity ch.simonmorgenthaler.fuellog/.FuelLog
are all common errors developers get when something doesnt work. (Ive seen lots of these in my programs xD) It almost seems like its due to it being androd 4.0 from what i read in the logcat. email the developer and give them the logcat, and the traces.txt (if there was one) they should be able to fix it. Also firstly check for an updated version.

I tried to access traces file, but my Data directory is empty..

ehud83 said:
I tried to access traces file, but my Data directory is empty..
Click to expand...
Click to collapse
Are you using data2ext? Plus what file browser did you use?
Sent from my GT-I9100 using Tapatalk

elesbb said:
Are you using data2ext? Plus what file browser did you use?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I'm not using data2ext.
I'm using File Manager comes with rom

ehud83 said:
I'm not using data2ext.
I'm using File Manager comes with rom
Click to expand...
Click to collapse
And your entire data directory is empty? -scratches head- that's kind of impossible xP
Sent from my GT-I9100 using Tapatalk

elesbb said:
And your entire data directory is empty? -scratches head- that's kind of impossible xP
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I know. I'll try to upload a screenshot, to prove it.. My \Data was always empty, don't know why.
By the why: I'm using HTC HD2, if it's help..

ehud83 said:
I know. I'll try to upload a screenshot, to prove it.. My \Data was always empty, don't know why.
By the why: I'm using HTC HD2, if it's help..
Click to expand...
Click to collapse
Try doing this
Open a terminal emulator
Enter following:
Again pressing enter after each line:
Su
Cd /data
Ls
Then make a screen shot of that. It might be the file browser you're using. Ls will let us know if your data directory is truly empty
Sent from my GT-I9100 using Tapatalk

elesbb said:
Try doing this
Open a terminal emulator
Enter following:
Again pressing enter after each line:
Su
Cd /data
Ls
Then make a screen shot of that. It might be the file browser you're using. Ls will let us know if your data directory is truly empty
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Here you go
By picture I guess it's not..

ehud83 said:
Here you go
By picture I guess it's not..
Click to expand...
Click to collapse
yep its not empty, your file browser is just not working i guess. under settings, is there a "show hidden files" option? i use root browser and never had an issue, plus ive never used file manager so i know nothing about it. but you are correct it is not empty, also, if you look at that, you will see a "anr" in the list, that is where your traces.txt file will be

OK. I got access to \data\anr\traces.txt, but accidentally i deleted the file, but phone refuse to create it again!
Tried reboot, create it on my own (if so, it doesn't write anything in file), nothing works.
Any ideas?
Thanks!

ehud83 said:
OK. I got access to \data\anr\traces.txt, but accidentally i deleted the file, but phone refuse to create it again!
Tried reboot, create it on my own (if so, it doesn't write anything in file), nothing works.
Any ideas?
Thanks!
Click to expand...
Click to collapse
well the program that FCs all the time is the program that creates it. you just have to keep running that fuel log program a bunch of times to generate it.

Related

[Solved] Deleted System Apps Still Showing Under Manage Applications

Im using the Root Explorer v2.10.2(which is the latest) to delete some unwanted system apks in system/apk folder, and im pretty sure i have already deleted those apks, but when i go into Settings->applications->manage applications, i still can find those deleted apks. Altho they are like 0 bite in memory, but still looks very annoying to me. Is there any way to get rid of those things in 'manage applications'? I have tried to search keywords in RootExplorer, and deleted the apk folders under data/data, and reboot my phone, and they are still there..
Also, if i click on any of those apks, "settings" will FC.
tzf123 said:
Im using the Root Explorer v2.10.2(which is the latest) to delete some unwanted system apks in system/apk folder, and im pretty sure i have already deleted those apks, but when i go into Settings->applications->manage applications, i still can find those deleted apks. Altho they are like 0 bite in memory, but still looks very annoying to me. Is there any way to get rid of those things in 'manage applications'? I have tried to search keywords in RootExplorer, and deleted the apk folders under data/data, and reboot my phone, and they are still there..
Also, if i click on any of those apks, "settings" will FC.
Click to expand...
Click to collapse
Did you try running fix_permissions?
Binary100100 said:
Did you try running fix_permissions?
Click to expand...
Click to collapse
hmm.. what is fix_permissions?
i searched on google and it says:
From a running ROM
To execute the fix_permissions script on your phone:
Open the "Terminal" app from the application drawer.
Type
su
fix_permissions
when i type fix_permissions in terminal, it indicates fix_permissions not found, i also tried fix_permissions.sh, still not found
tzf123 said:
hmm.. what is fix_permissions?
i searched on google and it says:
From a running ROM
To execute the fix_permissions script on your phone:
Open the "Terminal" app from the application drawer.
Type
su
fix_permissions
when i type fix_permissions in terminal, it indicates fix_permissions not found, i also tried fix_permissions.sh, still not found
Click to expand...
Click to collapse
what rom and recovery are you using?
Binary100100 said:
what rom and recovery are you using?
Click to expand...
Click to collapse
SMOKI 0.6.3, RA-hero-v1.6.2
it seems like the fix_permissions command can be used in CM ROMS..
tzf123 said:
SMOKI 0.6.3, RA-hero-v1.6.2
it seems like the fix_permissions command can be used in CM ROMS..
Click to expand...
Click to collapse
Try running fix_permissions from recovery.
its not working... those apks still stay in 'manage applications'.. altho recovery said its successful
Binary100100 said:
Try running fix_permissions from recovery.
Click to expand...
Click to collapse
LOL, problem solved, by editing the packages.xml under data/system, somehow the apk details are recorded in that file, so i just delete the corresponding codes and reboot my phone, walllllaaaaaaaaaa
AND, thanks a lot for your guide, LOL
tzf123 said:
LOL, problem solved, by editing the packages.xml under data/system, somehow the apk details are recorded in that file, so i just delete the corresponding codes and reboot my phone, walllllaaaaaaaaaa
AND, thanks a lot for your guide, LOL
Click to expand...
Click to collapse
Glad that you got it solved.
Also I hope that you don't mind by I edited your title because your problem wasn't specifically related to the Root Explorer app. This problem would occur if you had used any other means of removing the system app. By editing the title it'll make it easier for those that need assistance with a similar issue post their problems and find solutions. Adding [Solved] is effective to let them know that a resolution is available within the thread.
And it's not my guide, it's a reference for others that can't find the answer with the apparently evasive search feature.

CM7 / AOSP Boot sound [working]

Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
Credit to barnacles10 and lithid-cm
*NOTE: Anything in brackets is either description of what is happening or an action you need to perform; don't type in anything in brackets*
What you need to do to get a boot sound on CM7/AOSP is the following.
1. http://dl.dropbox.com/u/19699565/bootsnd.sh Apparently some people had issues with the first link, so I uploaded it again. Download that file, place on your sdcard.
2. Take whatever sound you want and rename it to: android_audio.mp3 [needs to be mp3 format] and then place in your adb tools folder.
3. On your phone, open terminal emulator, and type in the following:
su [enter]
cd /sdcard [enter]
ls [to list all files, you should see bootsnd.sh]
sh bootsnd.sh [enter]
You won't see a confirmation, or message, it just runs, and returns you to a # sign.
From your computer, adb push the android_audio.mp3 to the /system/media folder, reboot, and you'll have a sound.
If you don't like / know how to use adb, using root explorer and placing the android_audio.mp3 in the system/media folder works just as well. Reboot, and enjoy your boot sound.
*NOTE*
If you flash / change roms, you'll have to re-run the process to enable the boot sound again. If you get tired of it / don't want it, you can use root explorer and delete the file.
Alternate method:
For those that don't like using the terminal emulator, you can do it via adb:
navigate to your adb folder via commanda prompt, then issue the following commands:
adb remount
adb shell
cd /sdcard
ls [will list files, you should see bootsnd.sh]
sh bootsnd.sh
Like in the emulator, you will be returned with a # sign. Then place the audio file in the folder I specified. Just decided like posting an alt method. Enjoy.
Nice post I'm going to do this now!
Sent from my PC36100 using XDA Premium App
Well I do hope you enjoy it.
Excellent, trying this now!
Edit: Works great on CM7 7.0.2.1!!! Nice find!
.........at 8 am today someone poisons the coffee....do not drink the coffee. More instructions will follow.
Cordially,
Future Dwight
teh roxxorz said:
Well I do hope you enjoy it.
Click to expand...
Click to collapse
And I must say it has worked flawlessly.. I maintain a small network off friends rooted phones and this is one off the "hit" fixed so far everybody loves it. Thanks again for the help with this the other day..
Sent from my PC36100 using XDA Premium App
I really want this.. I just found this thread after searching and searching for an answer.. I just about gave up but I think I still my have a problem. My hboot version is 2.10 and dont think this will allow me to use pushboot.... any ideas
opps.. guess I should have read the whole post..... I am bout to give it a try
frikin awesome thanks a bunch.. I dont know what that little file did but it worked .. wooohoooooooooooo
teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. Download that file, place on your sdcard.
that download just shows up as a text file... am i doin it wrong?
Click to expand...
Click to collapse
@teh roxxorz: Thanks a lot man. I had to search a longtime to find this. You're the man. Seems like CM7.02.1 doesn't have that bootsnd.sh file embedded. Maybe the latest stable has it. If I wasn't new to the forum I'd know how to hit you with a "Thank You"...
youdoofus said:
teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. Download that file, place on your sdcard.
that download just shows up as a text file... am i doin it wrong?
Click to expand...
Click to collapse
The file should save as a .sh. If it doesn't show up as .sh when you are saving it, save it as all file types, and that should work as well.
If you double click it, it should prompt you with the "no program found...do you want to...blah blah" And it should show bootsound.sh
Click to expand...
Click to collapse
gReeNzZz said:
@teh roxxorz: Thanks a lot man. I had to search a longtime to find this. You're the man. Seems like CM7.02.1 doesn't have that bootsnd.sh file embedded. Maybe the latest stable has it. If I wasn't new to the forum I'd know how to hit you with a "Thank You"...
Click to expand...
Click to collapse
Well AOSP roms [i.e CM7] wasn't designed to have boot souns, so it probably won't be integrated [my speculation].
And if you ever want to "thank" anyone, at the bottom of every post, you'll see a "thanks" button, and then you have "thanked" them, and the user can see it.
Can't get this flashed. I tried to rename what I had downloaded from cyan's web site, Droid eye audio.zip, even tried to just flash it. A little help please
Sent from my ERIS ADR6200 using XDA App
chefrjd33 said:
Can't get this flashed. I tried to rename what I had downloaded from cyan's web site, Droid eye audio.zip, even tried to just flash it. A little help please
Sent from my ERIS ADR6200 using XDA App
Click to expand...
Click to collapse
Well if its a zip file. Extract the file, it should be an mp3 inside. Rename that file to android_auido [should have .mp3 extension already].
It launches rom manager and tells me its a operating system. Did I get the wrong file.
Sent from my ERIS ADR6200 using XDA App
chefrjd33 said:
It launches rom manager and tells me its a operating system. Did I get the wrong file.
Sent from my ERIS ADR6200 using XDA App
Click to expand...
Click to collapse
Where are you opening the file that its making it open from rom manager?
teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. http://dl.dropbox.com/u/19699565/bootsnd.sh Download that file, place on your sdcard.
2. Take whatever sound you want and rename it to: android_audio.mp3 [needs to be mp3 format] and then place in your adb tools folder.
3. On your phone, open terminal emulator, and type in the following:
su [enter]
cd /sdcard [enter]
ls [to list all files, you should see bootsnd.sh]
sh bootsnd.sh [enter]
You won't see a confirmation, or message, it just runs, and returns you to a # sign.
From your computer, adb push the android_audio.mp3 to the /system/media folder, reboot, and you'll have a sound.
If you don't like / know how to use adb, using root explorer and placing the android_audio.mp3 in the system/media folder works just as well. Reboot, and enjoy your boot sound.
*NOTE*
If you flash / change roms, you'll have to re-run the process to enable the boot sound again. If you get tired of it / don't want it, you can use root explorer and delete the file.
Click to expand...
Click to collapse
Ok just tried this without using adb as I think its million times better to just use a ftp app and get this done in seconds. But I dont know why its not working. I check the name to make sure I wasnt putting in the .mp3 twice and for some reason it wont play the file. And its in MP3 format.
I had some that wouldn't play for some reason too. Try a different mp3 file and see id it work. If not did u get the bootsnd file placed on the root of sd card and pushed the file with adb. Or my preferred method terminal emulator.
Kings GB Destroyed EVO
Or tell me what steps udid do.
Kings GB Destroyed EVO
cmurray77 said:
I had some that wouldn't play for some reason too. Try a different mp3 file and see id it work. If not did u get the bootsnd file placed on the root of sd card and pushed the file with adb. Or my preferred method terminal emulator.
Kings GB Destroyed EVO
Click to expand...
Click to collapse
Really well I actually tried the audio from the driod just to see but I try a couple more. Yeah the problem with using those they are more timely and both USB ports are beyond ****ed right lol. But I should just be able to do this over FTP. Was there anything similar to the ones that worked to the ones that did.

[Guide] How to have write protection disabled on boot with stock rom

For this to work you will need to be rooted with twrp installed.
This is for people who are on the stock rom or a rom without init.d support.
1. Download the wp_mod.ko file from @flar2's thread http://forum.xda-developers.com/showthread.php?t=2701816
and copy it over to your SD card (either internal or external)
2. Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time
13. profit
I don't have my hands on mine yet (ordered a Dev edition from Amazon), but I greatly appreciate your work here! R/W was a massive pain for me on my M7, and this seems much more simple and easy. Thanks again!
Hi graffixnyc,
Thanks for the explanation, but the link to the file is not working ....
link
flaxjef said:
Hi graffixnyc,
Thanks for the explanation, but the link to the file is not working ....
Click to expand...
Click to collapse
+1
CC
Should be fixed now.. I don't know why it cut off some of it
http://forum.xda-developers.com/showthread.php?t=2701816
Thanks for the turorial, but this isn't working for me
The file can't be executed (even after chmod) - and if i try to execute this file in an other directory, my terminal says that this file can't be found..
Any ideas?
So my device simply ignores Step 7 .... :crying:
graffixnyc said:
For this to work you will need to be rooted with twrp installed.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
Click to expand...
Click to collapse
I know I am being a grammar nazi, but I am fairly certain you mean "ensure". I tried to just leave it alone, but I can't not say something. It's a curse.
Fenny said:
I know I am being a grammar nazi, but I am fairly certain you mean "ensure". I tried to just leave it alone, but I can't not say something. It's a curse.
Click to expand...
Click to collapse
It is ironic that a "grammar nazi" would use a double negative while pointing out a grammatical error...
noimjosh said:
It is ironic that a "grammar nazi" would use a double negative while pointing out a grammatical error...
Click to expand...
Click to collapse
lol... yeah, would have been better to say: "but I'm compelled to say something"
Oh well, no biggie though.
Don't know how I missed this thread though, thanks graffixnyc.
noimjosh said:
It is ironic that a "grammar nazi" would use a double negative while pointing out a grammatical error...
Click to expand...
Click to collapse
Indeed, it is ironic.
thank you
412070391 said:
thank you
Click to expand...
Click to collapse
Does this work if the phone is still s-on? (unlocked/rooted but no s-off)
Sorry, but will this fix my little niggling issue with MX player? I keep my Stewart/Colbert files on the extSD card, but I can't delete them when done watching them using MX Player's delete command. I have to remember which files are watched and then use ES File Explorer to delete them. A silly second step in my opinion. Yes I am rooted, s-on, with TWRP.
I'm staying stock hoping a firewater solves my s-on issue, but yes I should probably do a custom ROM to solve this and a few other things.
Will this make SD card writeable to all apps?
Will this make external micro SD card writeable to all apps?
Sn8kbordin said:
Will this make external micro SD card writeable to all apps?
Click to expand...
Click to collapse
MAN, NO DOUBLE POSTS. but yea it should do it...if not there is another way
In Terminal Emulator it says "Failed Exec Format Error". Any ideas?
I followed the 1st post directions without errors for Sense 6.0, Andoid 4.4.3. When I tried to:
1. When I tried editing and saving system/customize/ACC/default.xml in ES File Explorer phone rebooted on save and default.xml went back to stock
2. When I copied default.xml to extSD card, edited it, and tried overwriting system/customize/ACC/default.xml with edited default.xml in TWRP recovery phone also rebooted
I want to do this mod http://forum.xda-developers.com/htc-one-m8/general/enable-built-music-channelroot-t2818128

Diagnosing Crashing Apps

So I have an app that I use and quite often and it crashes for seemingly no reason quite often. I have contacted the dev on these apps and they claim it's always on my end and the app is coded properly.
In order to validate these claims I need to be able to see why they are crashing. Is there any app or tool I can use to get a quick read out as to why the app crashed?
Thanks.
PieOfJustice said:
So I have an app that I use and quite often and it crashes for seemingly no reason quite often. I have contacted the dev on these apps and they claim it's always on my end and the app is coded properly.
In order to validate these claims I need to be able to see why they are crashing. Is there any app or tool I can use to get a quick read out as to why the app crashed?
Thanks.
Click to expand...
Click to collapse
The app developer can tell you how to log a crash and submit it to them
Sent from my Nexus 6P using Tapatalk
clsA said:
The app developer can tell you how to log a crash and submit it to them
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
They won't. That's why I'm asking here.
@PieOfJustice
Well if the developer is not willing to help how do you plan on fixing it?
in your fastboot / adb folder
create a new txt and name it Runlogcat.bat
open the empty file and paste
Code:
ECHO @
adb logcat -d > logcat.txt
I also use another bat file called clearlogcat.bat so the log is not so long
create it the same way
Code:
ECHO @
adb logcat -c
the idea is to clear the log and then crash the app then take the log to see what the errors were
Sent from my Nexus 6P using Tapatalk
clsA said:
@PieOfJustice
Well if the developer is not willing to help how do you plan on fixing it?
in your fastboot / adb folder
create a new txt and name it Runlogcat.bat
open the empty file and paste
Code:
ECHO @
adb logcat -d > logcat.txt
I also use another bat file called clearlogcat.bat so the log is not so long
create it the same way
Code:
ECHO @
adb logcat -c
the idea is to clear the log and then crash the app then take the log to see what the errors were
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks. It's more so I can see if its truly on my end (system) or if its related to the app .
PieOfJustice said:
@PieOfJustice
Well if the developer is not willing to help how do you plan on fixing it?
in your fastboot / adb folder
create a new txt and name it Runlogcat.bat
open the empty file and paste
I also use another bat file called clearlogcat.bat so the log is not so long
create it the same way
Thanks. It's more so I can see if its truly on my end (system) or if its related to the app .
Click to expand...
Click to collapse
Just out of curiosity are you running a custom rom or stock? I had some apps crash when I was on Pure Nexus. When I changed roms the apps didn't crash anymore.
jhs39 said:
Just out of curiosity are you running a custom rom or stock? I had some apps crash when I was on Pure Nexus. When I changed roms the apps didn't crash anymore.
Click to expand...
Click to collapse
Tried both stock and custom. Same thing. I am back to using AOSiP.

It's been a while. HELP!!

Okay guys first off sorry if there's a thread for this but XDA has become so over crowded and full of comments it's just to much to read through and try to remember. But anyway
Can anyone point me in the right direction or simply explain real quick how to properly root the T-Mobile variant. I'm running full stock (Obviously) I'm on H91810j and would like to debloat a little and use greenify. Any help is appreciated.
StonerSteve420 said:
Okay guys first off sorry if there's a thread for this but XDA has become so over crowded and full of comments it's just to much to read through and try to remember. But anyway
Can anyone point me in the right direction or simply explain real quick how to properly root the T-Mobile variant. I'm running full stock (Obviously) I'm on H91810j and would like to debloat a little and use greenify. Any help is appreciated.
Click to expand...
Click to collapse
There is literally speaking a thread dedicated just for the sake of rooting and twrp lol. Here:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
It should take about 3 to 5 minutes to complete the whole process if you know what you are doing. If you are a noob it might take sometime to figure out were to go from one step to another
Also, just remember, there is a search function on the v20 section's main screen. You can always use keywords and the function will search what you are looking for (if someone has posted something related to That). As French prople says... "Bon chance|"
P.s: yes. The rooting method by jcadduono works for 10j
jinkerz9430 said:
There is literally speaking a thread dedicated just for the sake of rooting and twrp lol. Here:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
It should take about 3 to 5 minutes to complete the whole process if you know what you are doing. If you are a noob it might take sometime to figure out were to go from one step to another
Also, just remember, there is a search function on the v20 section's main screen. You can always use keywords and the function will search what you are looking for (if someone has posted something related to That). As French prople says... "Bon chance|"
P.s: yes. The rooting method by jcadduono works for 10j
Click to expand...
Click to collapse
ive downloaded everything and when i extract the adb fastboot it extracts just fine but when i go to run it as administrator a box opens then closes immediately. what am i doing wrong
StonerSteve420 said:
ive downloaded everything and when i extract the adb fastboot it extracts just fine but when i go to run it as administrator a box opens then closes immediately. what am i doing wrong
Click to expand...
Click to collapse
Oh. The adb i used was from a pixel thread... The one posted in the rooting thread seems to either be missing a file called lib.... Something i forgot the name lol; or they did open and close immediately like it happened to you.
jinkerz9430 said:
Oh. The adb i used was from a pixel thread... The one posted in the rooting thread seems to either be missing a file called lib.... Something i forgot the name lol; or they did open and close immediately like it happened to you.
Click to expand...
Click to collapse
Can you link me to the adb you used. It just keeps opening and closing.
StonerSteve420 said:
Can you link me to the adb you used. It just keeps opening and closing.
Click to expand...
Click to collapse
Let me see if i can find it. If not i will zip it and send it to you
jinkerz9430 said:
Let me see if i can find it. If not i will zip it and send it to you
Click to expand...
Click to collapse
Thank you
StonerSteve420 said:
Thank you
Click to expand...
Click to collapse
Well. I couldnt find it. Anyway, i made a zip with all the files. Here:
View attachment 4070081
jinkerz9430 said:
Well. I couldnt find it. Anyway, i made a zip with all the files. Here:
View attachment 4070081
Click to expand...
Click to collapse
Still doing it. I must be the one person who's screwed lol
StonerSteve420 said:
Still doing it. I must be the one person who's screwed lol
Click to expand...
Click to collapse
Have you tried to run it in administrative mode?
jinkerz9430 said:
Have you tried to run it in administrative mode?
Click to expand...
Click to collapse
Right click run as administrator? Yes I have. Still can't get this to work. I'm using WinRar idk if that's the culprit or not. It's always been reliable.
Here, use this.
https://forum.xda-developers.com/showthread.php?t=2588979
Best for noobs.
It it asks about system wide say yes.
Then hit Windows key and R and type cmd. Then run your commands. The installer should also work.
StonerSteve420 said:
Right click run as administrator? Yes I have. Still can't get this to work. I'm using WinRar idk if that's the culprit or not. It's always been reliable.
Click to expand...
Click to collapse
Wait. I forgot to tell you. You cant double click the files. The files can be accessed only by using cmd. (command promt). So, extract the files into a folder, and use cd or pushd in dorect it to the directory where the files are. That is the proper way.
jinkerz9430 said:
Wait. I forgot to tell you. You cant double click the files. The files can be accessed only by using cmd. (command promt). So, extract the files into a folder, and use cd or pushd in dorect it to the directory where the files are. That is the proper way.
Click to expand...
Click to collapse
I know what you mean but how does the command go. I know I have to type something then add the file name sorry like I said I'm used to the old way maybe use adb for one step then the rest does it itself lol trying to catch up
StonerSteve420 said:
I know what you mean but how does the command go. I know I have to type something then add the file name sorry like I said I'm used to the old way maybe use adb for one step then the rest does it itself lol trying to catch up
Click to expand...
Click to collapse
For starter... Whats the directory where you downloaded and extracted adb fastboot? Assuming you are using the file i sent you. Was it on the downloads directory? If so open cmd (not in administratibe mode) and type pushd Downloads . Then ise all the start the adb server by using adb start-server to recognize your device. Or if you want to even see if your device is even present type adb devices
jinkerz9430 said:
For starter... Whats the directory where you downloaded and extracted adb fastboot? Assuming you are using the file i sent you. Was it on the downloads directory? If so open cmd (not in administratibe mode) and type pushd Downloads . Then ise all the start the adb server by using adb start-server to recognize your device. Or if you want to even see if your device is even present type adb devices
Click to expand...
Click to collapse
I have it in a folder on the desktop. So I type pushed Desktop/(folder name)? Or can it not be in a desktop folder. Sorry your spelling is confusing me with the second part how do I start adb server? Do I type adb start-server? Thanks for helping it's greatly appreciated
StonerSteve420 said:
I have it in a folder on the desktop. So I type pushed Desktop/(folder name)? Or can it not be in a desktop folder. Sorry your spelling is confusing me with the second part how do I start adb server? Do I type adb start-server? Thanks for helping it's greatly appreciated
Click to expand...
Click to collapse
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
jinkerz9430 said:
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
Click to expand...
Click to collapse
Thank you. I'll try that when I get home.
jinkerz9430 said:
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
Click to expand...
Click to collapse
Okay I got into the download folder using cmd (pushd download) i tried doing adb and hitting enter after and it brought up a bunch of lines after that. I did adb devices and it shows my phone but when I do fastboot oem unlock it just hangs at waiting for devices. USB debugging is on and so is OEM unlock.
StonerSteve420 said:
Okay I got into the download folder using cmd (pushd download) i tried doing adb and hitting enter after and it brought up a bunch of lines after that. I did adb devices and it shows my phone but when I do fastboot oem unlock it just hangs at waiting for devices. USB debugging is on and so is OEM unlock.
Click to expand...
Click to collapse
but are you in fastboot mode now? because after you have done the OEM unlock and then after that use usb debbugging then accept the prompt it shows about giving authorization to your computer, then after that you must go to fastboot mode to start the process of root

Categories

Resources