Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.
KrossX said:
Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.
Click to expand...
Click to collapse
Sent from my GT-I9505G using Tapatalk 2
KrossX this is the second time you have posted questions in the development forum. As I stated before these are for Q&A NOT here. Please refrain from posting your questions here and READ the XDA users guide and forum rules again. There is a reason for this. I am glad your part of the community and your questions and comments are noteworthy you just need to put them in the right place. We read those threads as well! MJ
This is for Development ONLY
Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I thought that since I was aiming this more at the devs it would've been in the Dev forums. Sorry for having you move yet another thread of mine.
Didn't mean to cause a ruckus; never really got a chance to read the post by deaffob above before it was edited by the mod so no offense from whatever name-calling was done, haha.
Thanks MJHawaii; I will search for logcat and see what I can pull up.
Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4
KrossX said:
Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.
xHausx said:
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.
Click to expand...
Click to collapse
Good news and bad news.
Bad news: I am unable to run logcat; I am unable to access my device via USB ever since the root and when I tried doing the logcat steps, yet again it couldn't connect to my device.
Good news: I believe the solution to this issue (being unable to access my device via USB) may also lie in the logs along with the bluetooth issue. The reason why is because of this error message I received while trying to reinstall the USB driver (attached pic); it points to not being able to "start" a device. I think this will all eventually tie-in with some services not running correctly on my phone.
So, is there another way for me to post a log for you kind folks to review on here via my phone directly?
If I can do that via catlog app on my device, let me know what sort of log (which options) I'd need to run and post. Thanks!
Well, did a restore to stock + root. That didn't help. It changed the Baseband, Kernel, and Build versions but did nothing to fix my issues with BT and USB connectivity.
I think I am going to start researching ways to start from scratch. Like a factory reset/wipe back to first-use condition. If anyone can point me towards some reading material on how to do that safely and wisely, it would be much appreciated!
I just ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Bluetooth issue is resolved; tested it just now and it works just fine again. As is the USB issue; as soon as the phone was connected to the same exact PC as before, it was recognized and showed up as a device that I could open and explore.
My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting too.
Thanks to all those who attempted to help!
Related
Fellow Android enthusiasts,
I seldom post on these boards because of the accurate and spot on instructions usually posted, however, this time I must ask if there is an easier explanation on ow to side load. I tried the ad push method of the settings.db file provided on here however this boot my phone into a continuous boot loop which caused me to wipe the device back to factory. I would like to know if there is a new way or different method of allowing sideloading of apps with the exception of using a program like HTC Sync, Droid Explorer, etc...I would like to enable it in the phone. Any help is much appreciated. Thank You!
fightingcrest said:
Fellow Android enthusiasts,
I seldom post on these boards because of the accurate and spot on instructions usually posted, however, this time I must ask if there is an easier explanation on ow to side load. I tried the ad push method of the settings.db file provided on here however this boot my phone into a continuous boot loop which caused me to wipe the device back to factory. I would like to know if there is a new way or different method of allowing sideloading of apps with the exception of using a program like HTC Sync, Droid Explorer, etc...I would like to enable it in the phone. Any help is much appreciated. Thank You!
Click to expand...
Click to collapse
First, this should go into the General forum, as it really a question that doesn't have much to do with development.
There is more to this than a simple adb push. What exactly did you do? And in order to use ADB to get this done, you must be rooted properly. How are you rooted?
If you go to the irc channel in my tag, someone will help as they are available.
moved to General
Understood. Sorry for incorrect post. I am rooted through liberty Rom b003. I connect through Droid explorer and utilize regularly.
Sent from my HTC Liberty using XDA Ap
Ever since the first froyo rom until now (currently running Nero 4.1), Fix Permissions in Rom Manager and ClockworkMod Recovery has been rendered useless. It simply starts for a second then ends right after, and permissions remain unfixed. Is this a problem due to lack of source from samsung or is this a bug that has not been detected by devs, either way if its solvable I think its a minor bug that should have some attention and maybe a fix.
Thank You!
I thought I had read something about having the proper busybox installed, but I have changed mine and can't seem to get it to work ether. I have also uninstalled and reinstalled RM.
No need for a think tank. There is already a solution.
Apparently the script in Clockwork is looking for a file in the wrong place. You can change the script or you can copy and move the file it's looking for. Either one will work. I am unsure if Koush has been contacted about this issue.
Check out this thread. I use the solution in post #3 and it works fine.
Also, if you feel as though someone is being rude, just ignore it and report the post. The mods act quickly as soon as something is brought to their attention.
-thanks for your suggestion...worked great.
Keslynn said:
No need for a think tank. There is already a solution.
Apparently the script in Clockwork is looking for a file in the wrong place. You can change the script or you can copy and move the file it's looking for. Either one will work. I am unsure if Koush has been contacted about this issue.
Check out this thread. I use the solution in post #3 and it works fine.
Also, if you feel as though someone is being rude, just ignore it and report the post. The mods act quickly as soon as something is brought to their attention.
Click to expand...
Click to collapse
--Thanks for keeping this thread on-point. Almost got side-tracked there with all the other posts. Follow Keslynn's attached link. The fix worked for me.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General
I'm trying to follow these directions... but I'm not sure where to get the packages.xml file.
Can someone please show me?
jnagar said:
Thank you--if it helps, I simply copied the packages.xml file into /data/system/ in order to run fix_permissions, and then just deleted the .xml file.
A temporary fix, yes, but I was just trying to fix a specific problem with ending phone calls causing an FC (see http://forum.xda-developers.com/showthread.php?p=9943863#post9943863).
Click to expand...
Click to collapse
rogue sound files
I wonder if permissions will fix the rogue sound files in my player?
Does anyone know if the fix permissions issue is limited to Rom Manager or if all other applications doing the same thing are affected? I tried using the "Root Tools" app to fix permissions, but it looks to be doing the same thing that occurs in rom manager.
- Mat
hi all,
a few hours ago i install HoneyVillain 1.2 and i have 2 problems,
1) on every boot i got a message " no sim inserted" but my tablet hasnt any working sim slot.is there any way to remove this message?
2) on every boot i got an error message the application systemupdater (process com.FD.updater) has stopper unexpectedly.please try again if i select force close i can work with no further problems.if i left it for a while my tablet rebooting and i get the same message again..any solution??
thanks in advance
android-noob said:
hi all,
a few hours ago i install HoneyVillain 1.2 and i have 2 problems,
1) on every boot i got a message " no sim inserted" but my tablet hasnt any working sim slot.is there any way to remove this message?
2) on every boot i got an error message the application systemupdater (process com.FD.updater) has stopper unexpectedly.please try again if i select force close i can work with no further problems.if i left it for a while my tablet rebooting and i get the same message again..any solution??
thanks in advance
Click to expand...
Click to collapse
You SN is aptly named
Literally two posts below yours http://forum.xda-developers.com/showthread.php?t=1230744&highlight=ro+carrier
Perhaps the response was helpful to android-noob, I'm not sure. However, I have searched for quite a while and don't see anything relating to the questions that result in actual help to fix the problems. I certainly take full credit for being an android idiot but we all start somewhere when we're trying to learn new things. I've been trying to learn from reading and this is quite honestly the best forum for everything that has to do with phones and tablets.
I would appreciate a simple link or response that might be of help to fix the problem of suddenly getting the errors listed by the first poster if you would be so kind.
Thank you for any help you can give.
docvicki said:
Perhaps the response was helpful to android-noob, I'm not sure. However, I have searched for quite a while and don't see anything relating to the questions that result in actual help to fix the problems. I certainly take full credit for being an android idiot but we all start somewhere when we're trying to learn new things. I've been trying to learn from reading and this is quite honestly the best forum for everything that has to do with phones and tablets.
I would appreciate a simple link or response that might be of help to fix the problem of suddenly getting the errors listed by the first poster if you would be so kind.
Thank you for any help you can give.
Click to expand...
Click to collapse
Let's see. I did provide a link in my response, and the last post on the page of the link I gave had the fix for the sim card message. How much more spoon feeding will you require?
first you need file manager with root access
Sim card messages:
Go to system there is a file called build.prop ,open it and add the line ro.carrier=wifi-only,you can add this line on the bottom of the file for example and les and save the file.
Reboot and the simcard message should be gone.
For the fd.updater problem:
That is because the build prop is changed so the update service doesn't recognize it.
That is no problem I delete this in my roms so you won't have that stupid message.
What you can do is go to system/app, find fd.updater.apk and fw.updater (i think that is the correct name) and rename them by putting a .bak behind the name of the apps.
Reboot and the messages should be gone.
civato said:
first you need file manager with root access
Sim card messages:
Go to system there is a file called build.prop ,open it and add the line ro.carrier=wifi-only,you can add this line on the bottom of the file for example and les and save the file.
Reboot and the simcard message should be gone.
For the fd.updater problem:
That is because the build prop is changed so the update service doesn't recognize it.
That is no problem I delete this in my roms so you won't have that stupid message.
What you can do is go to system/app, find fd.updater.apk and fw.updater (i think that is the correct name) and rename them by putting a .bak behind the name of the apps.
Reboot and the messages should be gone.
Click to expand...
Click to collapse
If he's not going to read the same answer on the link I posted, what makes you think he's going to read your post?
kjy2010 said:
Let's see. I did provide a link in my response, and the last post on the page of the link I gave had the fix for the sim card message. How much more spoon feeding will you require?
Click to expand...
Click to collapse
Woweeeeeee.spoon feeding sucks I been there for 12 weeks twice this year while recovering from shoulder surgery.then again less then a month ago.
Op I do not have this or any of the other known issues with the custom roms.thou I know they can bring some extra speed and apps.
Kjy can you go spoon shopping for me.Erica needs some new winter boots.
Giggles.
Goodluck. OP ..
BACKUP THE BUILD .prop file before you edit it.
Thanks for your reply and for being so kind in it. I was able to repair my problems right after I posted, which is why I rarely post. I have no formal computer education, self taught. I normally do pretty well but run into problems once in a while that stump me. This forum is a true Godsend to a 63 year old woman. Thanks again.
Sent from my A500 using XDA Premium App
Thanks so much.
Sent from my A500 using XDA Premium App
kjy2010 said:
If he's not going to read the same answer on the link I posted, what makes you think he's going to read your post?
Click to expand...
Click to collapse
I'm nice to old ladies,
Honeyvillain 1.2 problems
civato said:
I'm nice to old ladies,
Click to expand...
Click to collapse
Yes you are, your Mother would be proud. Seriously, thanks.
Hey guys!
I have spent the past 2 days getting this one error and after hours of reading up and trying to get all the facts straight, I just can't figure this one out!
I have cyanogen mod 10
I have Skrillax unlocked bootloader v8
and then I have all the files necessary for Ubuntu and Bodhi. Plus recoveries.
Mostly, I have been trying to follow
HTML:
http://forum.xda-developers.com/showpost.php?p=22201465&postcount=351
single post, which works great up until the point of booting! I seem to get an error that says:
"busybox: 'busybox' is not an absolute path Could not find /dev/mmcblk0p7! Dropping to a shell.
sh can't access tty; job control turned off"
(there's more after that but it doesn't seem to pertain to anything of importance that I can tell)
I just can't get over that error! I read about, but it seems like there is some dialog between other users that happened, and the conversation got changed way too fast that I couldn't understand what was going on!
If I am in the wrong area just let me know and I can move, or repost my question on a different thread. I just can't seem to find the direct answer through google, forum search, or even *shiver* Bing.
Thanks for the views, thanks for the help (if you can!).
:angel:
The odd one out!
Looks like you are one of the unlucky owners of A500 with a different file system than most A500. You will probably only be able to use the external card method for now. If some one compiles a new Kernel (recovery) then you will be able to use internel card method. Check the Dual Boot thread in the General section I made a more detailed explanation. Hope that helps
Thanks!
themechaniac said:
Looks like you are one of the unlucky owners of A500 with a different file system than most A500.
Click to expand...
Click to collapse
Thanks for the reply! I guess that answers all of my questions! Hopefully I can get something setup .
calebcoverdale said:
Thanks for the reply! I guess that answers all of my questions! Hopefully I can get something setup .
Click to expand...
Click to collapse
Ill try to compile a new recovery.img to point to 08 but no promises :-\
Hey guys,
I'm a new Nexus 7 user (Will be delivered today) and I'm just looking for some quick advice to get started.
I have had a good search/read of forum and found various rooting methods/kernels and some roms I will be trying out etc and shouldn't have any problem getting myself started, however to lower risk I'm just looking for some seasoned N7 users to maybe give me any recommendations or advice.
I'm not a n00b and dont expect/want any spoon feeding, Maybe just a few pointers to avoid any ****ups/bricks on N7/flashing techniques.
Advice/Links would be appreciated.
Easiest way you can possibly do it:
http://www.wugfresh.com/nrt/
Wilks3y said:
Easiest way you can possibly do it:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Thnx, This was one of the apps I was looking at in my research so will give it a go.
I know you're not a noob because i saw you in S2 Q/A section several times. I recommand you to unlock your bootloader and flash a custom recovery with fastboot and after that you can flash superSU with the custom recovery.
PM me if you want more advices/links.
Since unlocking your bootloader wipes the device - including the psuedo-SD card, you may as well do that first - as soon as it comes out of the box - and get it over with.
The custom recoveries use a different USB VID/PID pair than the normal OS boot for the ADB endpoint - so a single driver (Asus or Google) won't talk to the custom recoveries in ADB mode unless you edit their .INF files (use notepad app, not any other editor) so you can use a single driver for fastboot/adb-OS/adb-recovery. For signed drivers this breaks their signing, but you can still install them. I suppose others get around this by installing multiple drivers - including drivers off of XDA of mysterious origin which are also unsigned.
You can find documentation of relevant USB VID/PID pairs at the bottom of this post
[REF] Nexus 7 Button Combinations
You might find the top bit of that post useful, too
Some folks claim that you need the latest version of the SDK to deal with the new 4.2.2 adb security layer. IMO, I'm not convinced (I'm using Asus drivers from 6/2012, not Google, and everything seems to work fine.) But, it certainly can't hurt to update your SDK.
After that you might as well run stock for a week or two while you are doing more reading (OK, let's say rooted stock); that way when you start ROM-hopping you will have a baseline experience to compare against.
Get yourself a decent OTG cable; maybe a USB key that has storage capacity as big as your device, too. If you want to mount Mass Storage devices as "OTG" devices on a rooted-stock ROM, use chainfire's Stickmount app from the market.
And lastly - just like with any other device, make full Nandroid backups - including for your lightly-rooted stock ROM. You never know when you might want to pull bits and pieces from them later.
Also, I consider myself decently skilled at this stuff - but because I came from a device with a real external SD card, I have managed to totally wipe out my "psuedo-SD card" twice now because I got in a hurry and wasn't paying attention. Moral: at a minimum, get copies of your Nandroid backups off of the device.
Finally, don't use a toolkit - you will learn nothing, and be unable to resolve even the most trivial of problems which eventually crop up. Underneath the hood it's all fastboot and adb anyway.
$.02
bftb0 said:
Since unlocking your bootloader wipes the device - including the psuedo-SD card, you may as well do that first - as soon as it comes out of the box - and get it over with.
...
[REF] Nexus 7 Button Combinations
...
Click to expand...
Click to collapse
The link doesn't work.. Thought I'd mention it
And have fun enjoying your new Nexus. Do yourself a favor no matter what method you use to root/flash: read everything in the op before you flash anything and its better if you wait until others post feedback. I still have a $200 paperweight that says KINDLE on the back.
Sent from my Nexus 7 using XDA Premium HD app
kilometers4 said:
The link doesn't work.. Thought I'd mention it
Click to expand...
Click to collapse
Thanks - fixed it. Dropped one digit at the end.
Thnx for advice guys, will be rom hopping for a while until I find one to stay with for a while. Currently on CM10.1.
As mentioned the lack of real ext sd is a bit of a ball ache. Really wish they had have added the slot to new nexus range.