I have what I needed, thanks!
Hi, I'm wondering if someone with a Le Pro3, either the CN or US model (or both) could please provide me with the output for dmesg and logcat.
Pre-requisites:
have adb installed and working for your device
Make sure adb debugging is on for your device, and your computer recognizes your device, and is authenticated for your device. (I don't know EUI, I've only ever dealt with western AOSP/CAF style roms, you'll have to understand and manage this all yourself).
PLEASE don't type the commands from memory, they have case sensitive options. Please copy and paste them. Thank you.
The following commands need to be executed shortly after reboots. Please don't run them if the device has been on longer than a minute. In fact, please don't stray far from the procedure, please.
Reboot device
Once booted run "adb shell dmesg > dmesg.txt"
Run "adb shell cat /proc/partitions > partitions.txt"
Run "adb shell df > df.txt"
Run "adb shell df -P > df-P.txt"
Run "adb shell mount > mount.txt"
Reboot the device and perform the next adb step once it's started to boot
run "adb logcat > logcat.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Reboot the device and run the following once it's started booting back up
run "adb logcat -b radio > logcat-radio.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Now, for some root-required tidbits (these commands could actually be dangerous!!! they will be running as root, please be very careful, you've been warned): You have two ways you can do this:
Run "adb root" to put adb in an automatic root mode (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name > by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num > by-num.txt"
Please check the files to verify that the contents are not an error. The other method, if switching adb to root mode doesn't work, would be to:
Run "adb shell"
Run "su" to put your shell into root mode, NOTE: BE VERY CAREFUL HERE (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name" and then copy/paste the output into a file named "by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num" and then copy/paste the output into a file named "by-num.txt"
Finally, if you are simply not able to achieve root on your device (either in general, or just for ADB), both of these tasks SHOULD be possible when you're booted into the TWRP recovery. If you don't have TWRP installed, then don't worry about it. I'm just assuming you do.
Note: None of these commands will produce empty files. If you get empty files, something went wrong. If only a few are empty and you can't seem to get them working properly, just send me what you do get.
Once you've done these things, zip up the files and send them to me in a private message. You don't want these posted here unless you want people knowing your phone number. The text files, especially for the logcat and radio output will be large, but they should compress down to something quite reasonable. Also, please make sure to include your model number so I know which I'm working with. Thanks much.
Thanks.
I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.
secXces_debaki said:
I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.
Click to expand...
Click to collapse
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.
dr4stic said:
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.
Click to expand...
Click to collapse
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.
secXces_debaki said:
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.
Click to expand...
Click to collapse
Well, don't get yourself into any trouble. I'm not in the business of ending relationships None of the commands modify anything, they just read information and dump it into a file. Other than rebooting, your device won't need to go offline. Also, if you HAVE modified your device in terms of ROM or whatever, please include a list of your mods or whatever in the message you send me with the text files zip.
PS> I've visited your area, or at least the one listed with your profile on XDA. It's a beautiful place. If I could get a visa worked out, it's on my list of places in europe I'd love to move to, possibly in retirement
U are planing to get one x720/7?
There are some way beautiful places around in Germany.
Can u maybe help me with my meta-inf?
secXces_debaki said:
U are planing to get one x720/7?
Click to expand...
Click to collapse
I'm giving it some very serious thought. I'm in the US and the x727 will be on sale on wednesday at US$300, which is very compelling for a device with an msm8996pro, even if the camera is average at best, the screen is less than impressive, and it's missing a headphone jack. My G2 is starting to act up and I need something cheap for the short term.
In any case, I'm doing my research now. I've downloaded the ROMs for 17s (both the stock CN version and the modified IT version). The kernel sources are released for x727, and I imagine the x720 kernel can likely be built from the same sources, in fact I wouldn't be surprised if everything about the kernel was the same. So I wanna see if I can get a kernel and rom building. I may attempt a TWRP build first, since I'd want that anyway, and it's simple enough to boot from fastboot and see if things work. But, I need help understanding the system. And that's where the information gathering in this post comes in.
secXces_debaki said:
Can u maybe help me with my meta-inf?
Click to expand...
Click to collapse
I have no idea what you're referring to with the meta-inf.
I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^
U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?
secXces_debaki said:
U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?
Click to expand...
Click to collapse
I would really like the logcat and logcat-radio to be running from the moment just after the hardware logos on the screen start showing up, once EUI starts to boot. The logcat is circular and has a limited buffer. Once it reaches the end of it's buffer, it starts overwriting itself, therefore it only keeps a certain amount of the logs in memory before they're gone. Your logcats were therefore incomplete. In more basic terms, I don't see where the system started booting up, that part of the log had already been overwritten when you took the log.
I also sent you a response requesting additional information, and for you to re-run one of the other commands that also errored out.
I do appreciate the help, I really do, thank you
Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.
secXces_debaki said:
I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
Click to expand...
Click to collapse
Yeah, that doesn't help at all. Meta-inf to me is a file included in a flashable zip. It isn't even a main file, and it isn't even particularly important. It certainly wouldn't damage the baseband. The baseband, otherwise known as the modem or radio, controls your phone. It's like the brain stem, it controls the most basic automatic responses. Generally if your radio was broken, your phone would be hard bricked, there would almost certainly be no recovering from that.
Did you flash a modified radio/firmware to your device?
secXces_debaki said:
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^
Click to expand...
Click to collapse
Heh, thanks
That actually lines up similarly to other things I've head about the device. Your assessment of the screen seems more positive than some, but then that sorta thing is a bit of personal preference. Frankly I don't game (much) to the point where I want a QHD or 4K display, and I don't intend to do VR. The reason I wanted a msm8996 is for the other advanced capabilities. The thing I'm looking forward to most is getting WiFi Calling working for T-Mobile, my reception isn't always great and that would be fantastic for me
As for the sound, I learned a long time ago to accept disappointment there. And I'm OK with that. I really wanted a headphone jack. Adapters tend to be bulky and/or break, and I don't like to be restricted to a single pair of headphones just because they have the right connector. You also can't easily share headphones with a CDLA connection. I have heard that the speaker output is nice, and I'm looking forward to that.
Mostly I'm excited that the kernel is not much modified from the CAF sources. Once I've verified that whatever it is I'm working on will actually boot, I will be able to upgrade to a newer revision of the kernel (with security fixes) and possibly even jump to the UM branch for the kernel, which is unifying for the Nougat release. I'm using the op3 as a template for my cm device and at the moment just gathering information. I don't even know if I'll buy the device yet or even make a rom. But it's what I'm looking into. This is a side project for me, and I desperately need to find a job, that takes priority.
secXces_debaki said:
Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.
Click to expand...
Click to collapse
I don't know how fast the phone boots, but usually I have the command already typed into the window, then I reboot and as soon as the first logo appears on the screen I hit enter. The command may not see the device immediately, and it'll say "awaiting device" and that's fine, it'll start logging as soon as the device appears. Then do CTRL+C 30 seconds after all the final connections to the cellular network are done
Managed to fix my standby drain..
U got a pm with the last logs. Hope it's good
Related
Well, this is frustrating...
Sitting in church with my family on Easter Sunday, I felt a short vibrate from my phone. Figured it was just an email coming in, so I didn't pay it much attention. But by the fourth time, I started wondering why I was getting such a flood of email, especially on a Sunday morning.... That's not a typical pattern for that email account.
So I discreetly slid my phone out of my pocket to take a peek, and it was on the boot screen. Since then, my phone has been periodically rebooting itself for no reason that I can think of.
Unfortunately, it never does it with the USB cable connected, so I haven't been able to capture a logcat of what's going on when it reboots. It also doesn't seem to every do it while I'm using the phone, only while it's sleeping.
Searches haven't been much help. A few promising leads, but they all seem to end up getting blamed on apps that I've never had installed.
It also seems to be getting slowly less frequent. Only happened twice yesterday, and my phone made it through the night with no reboot.
I've uninstalled most of the apps I had on the phone. The only ones left are things I've been running since my first day with the phone, so I have a high degree of confidence that they're not the problem.
For completeness, I'm running DC v2.05, PRI 1.70_003, PRL 60663. I have no reason to think it's the specific rom causing a problem, but it's always good to include information that could be relevant... I'm also running radio version 2.42.00.03.10. (Doubt that's the culprit since I flashed it after this problem began.)
Are there any likely causes that my searches aren't turning up that would be worth looking at? More to the point, is there a way to view the logcat from before the phone rebooted? From what I can tell, it only shows me the log from the point where the phone booted up.
And as a last resort, aside from an RUU are there any steps I should take before having the Sprint store replace the phone?
I had my phone reboot on its own the other day as well, also unplugged. It's only happened once so far that i've noticed. I'm running the new fresh 2.0d.
subliminalurge said:
And as a last resort, aside from an RUU are there any steps I should take before having the Sprint store replace the phone?
Click to expand...
Click to collapse
I would take your battery into consideration here, it might possibly be shorting out? That's one thing to look at.
Also, if you wouldn't mind, do post your logcat -- it'll help us diagnose a possible problem you haven't caught.
Also, try this comand: adb bugreport > errorlog.txt and also look at these sets of commands:
Filtering Log Output
Every Android log message has a tag and a priority associated with it.
* The tag of a log message is a short string indicating the system component from which the message originates (for example, "View" for the view system).
* The priority is one of the following character values, ordered from lowest to highest priority:
o V — Verbose (lowest priority)
o D — Debug
o I — Info
o W — Warning
o E — Error
o F — Fatal
o S — Silent (highest priority, on which nothing is ever printed)
So try to run a command like this: adb logcat *:W -- This will show any messages that have a level of "warning" or higher.
More info HERE
Same thing happened to me yesterday. Had the phone sitting on the counter for a few hours. Didn't get a call that I was expecting. Hit the power button and the phone booted. The battery was not low and I don't know why it was off. I'm on Fresh 2.0d
Ive got two heros on fresh 2.0d. Happened on one while I was exiting camera. Thats the one and only time though.
pseudoremora said:
I would take your battery into consideration here, it might possibly be shorting out? That's one thing to look at.
Also, if you wouldn't mind, do post your logcat -- it'll help us diagnose a possible problem you haven't caught.
Also, try this comand: adb bugreport > errorlog.txt and also look at these sets of commands:
Filtering Log Output
Every Android log message has a tag and a priority associated with it.
* The tag of a log message is a short string indicating the system component from which the message originates (for example, "View" for the view system).
* The priority is one of the following character values, ordered from lowest to highest priority:
o V — Verbose (lowest priority)
o D — Debug
o I — Info
o W — Warning
o E — Error
o F — Fatal
o S — Silent (highest priority, on which nothing is ever printed)
So try to run a command like this: adb logcat *:W -- This will show any messages that have a level of "warning" or higher.
More info HERE
Click to expand...
Click to collapse
+1 on the battery suggestion. Ordered a battery from Ebay and that's what happened to me. Stopped using the battery, problem ended
USB is a sign...
pipskicks said:
+1 on the battery suggestion. Ordered a battery from Ebay and that's what happened to me. Stopped using the battery, problem ended
USB is a sign...
Click to expand...
Click to collapse
Good thought. I'm still using the stock battery, so it wouldn't be anything to do with an aftermarket, but...
A few weeks ago I flashed a beta rom to test it out, and when I woke up in the morning my phone was too hot to comfortably hold in my hand.
Wondering if the battery got radically overcharged and is finally starting to flake out... Might have to swap my battery with my wife's tonight and see if the problem follows the battery or stays with the phone.
(Be cool if that's the problem, been wanting a higher capacity battery and this would be just the nudge I've needed to pull the trigger on one....)
Maybe its because you brought it into church. its needs to be exercised.
j/k
It has happened to me as well
tyrnight said:
Maybe its because you brought it into church. its needs to be exercised.
Click to expand...
Click to collapse
Well, I did comment to my wife on the way out that "Wow, I didn't even melt when he splashed the holy water on us...."
The battery idea sounds good. Plus, the battery on EBay for $10 is a good deal...that's what I'm currently using and I haven't had any problems so far. YMMV.
My wife just told me she has the same problem. It's a battery from ebay, oem. She went back to her regular stock battery - no problems. She's on fresh 1.5 rom v1.1.
Well, I swapped the batteries between my and my wife's phones last night, and so far neither one has rebooted itself. So the results are still inconclusive.
But, as I said, the problem was fairly intermittent, so I guess I'll just have to keep an eye on them for the next day or two....
I get random reboots every so often myself and I only use the stock battery. Currently running Damage Control v2.05 based off the Sprint leak. Does logcat need to be done immediately once the reboot happens? Because it's been about two days since it last happened.
I haven't had a chance to fully read up on how logcat work. It's at the top of my todo list, but the past few days have been crazy busy....
As far as I've been able to tell from a little poking around, the log gets cleared when the phone is rebooted. I'm strongly hoping I'm wrong about that, but as I said, it might be a day or two before I get a chance to educate myself more in depth on how logging is done on Android.... (the normal linux log directory doesn't seem to be present, either in the normal location, or a few obvious alternatives I've looked at....)
I noticed my phone reboot after I picked it up the other day as well. I'm running Fresh Rom 2.0d with a ebay battery. This was before I installed the new radio though so I don't know if that makes any difference.
Any one else notice that after a random reboot, the phone constantly stays awake 100% of the time and eats away at battery life?
Austin3600 said:
Any one else notice that after a random reboot, the phone constantly stays awake 100% of the time and eats away at battery life?
Click to expand...
Click to collapse
Actually, I hadn't noticed that, but I'll be sure to keep an eye on it from here on out....
Hey guys, my EVO rebooted on me during a marathon I was running over the weekend. Really sucked because I was using a run-tracking app to keep track of my pace. My EVO is completely stock (running the latest update), and it has historically been extremely stable. In fact, this is the first time it's ever spontaneously rebooted on me post-Froyo.
So... I'd love to look at some system logs and see if I can find any clues as to why it happened. I plugged my EVO into my mac last night and tried to look at /system/kmsg using ADB to see the kernel output. However, I got a permission denied error. Are there any logs I can look at (without rooting) that might help me out? Does anyone have any other ideas to try and troubleshoot this one?
Thanks!!
I haven't used it personally, but there's a program on the market called alogcat that should work for you.
As my $0.02...the reboot could have been caused by the constant jostling while running. There are a lot of variables at play...could have been the accelerometers going over their threshold, etc. I don't know. A marathon would be just as taxing on an electronic device as would a human body.
Let us know your log results =).
topdawgn8 said:
I haven't used it personally, but there's a program on the market called alogcat that should work for you.
As my $0.02...the reboot could have been caused by the constant jostling while running. There are a lot of variables at play...could have been the accelerometers going over their threshold, etc. I don't know. A marathon would be just as taxing on an electronic device as would a human body.
Let us know your log results =).
Click to expand...
Click to collapse
Thanks for the idea, I downloaded alogcat and tried it out. Seems like a really handy app, but unless I'm missing something it only displays the current logs. In other words, I can't go back in time and look at the logs from 18 hours ago for example. So if I had had this app running yesterday (while I was running), then it probably would have spit out something useful. Maybe I'm out of luck, unless there's a way to access historical logs...
I got my Geeksphone Peak a few days ago, and have already ran into some problems, that I believe some others may experience at some point in the future as well, when the device gets out to the public. I have therefore decided to make this thread to report issues and solutions, along with answering peoples questions about the phone.
First off, be aware of that the phone uses a standard size sim card, so if you plan to use it with a SIM card, you will have to get one of those old big SIM cards.
Second, you will without doubt want to debug your apps on the phone. The easiest way to do this, is by using the Firefox OS simulator v3, that allows you to push apps to the phone. To do this you will have to enable remote debugging on the phone, which was recently changed from enabled to disabled by default. Enable remote debugging by going to Settings -> Device information -> More information -> Developer. If you are using Linux, you will now have to add a value to the file /etc/udev/rules.d/51-android.rules: 'SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev"'. The idVendor ID is found using lsusb.
I do not know how to use remote debugging on Windows or Mac, and would be glad if someone would be able to contribute with this information. I will update this post when I discover more flaws and fixes
Hi, I wanted to know how the overall build quality is. I am thinking of ordering one myself.
chozyn said:
Hi, I wanted to know how the overall build quality is. I am thinking of ordering one myself.
Click to expand...
Click to collapse
I received mine yesterday. To me, the build quality is mediocre. The back is quite hard to remove to insert the battery and SIM card. When the back is removed, I saw "Engineered in Spain", "Made in P.R.C". The screen is average. Perhaps I'm pixel peeping, but I can feel the grid of pixels when viewing images on it. It's a developer phone, but I did expect a better build.
Certainly order one if you are a developer.
I got my Peak two days ago.
Materials and assembly is more or less what I expected. Clearly not a Sony but it is not so bad, in my view.
So far I have only connected via wifi, do not use the SIM yet. Once connected the first thing to do is upgrade. The process of downloading a 100MB and install the update was fast enough.
However, after using it for a couple of days I've noticed a lot of problems with connectivity. The worst is that sometimes fails to reconnect to wifi after unlock.
It is always very quick to complain lack of connection: is unable to access the sites for Mobile Twitter or Facebook, for example, as does access to regular Google. It's as if only Google respond fast enough to keep active navigation.
Well, this is a beta edition and it will sure get better, but today is all that I can bring on the Peak.
Regards!
Thanks songuke, Rackam el Roig. I appreciate the follow up!
t-mobile connectivity?
Either of you know how well this works on t-mobile? I see that t-mobile supports the 1900 band in my area, but I'm still not sure about how well tmo will work in general (as I do leave this city on occasion). I'd love to know. Also, it's a pity that it doesn't do HSPA+ so I'd like to know about the speed as well if possible. Thanks and you guys are lucky to have the phones. I've been watching the site like a hawk since day 1 and haven't managed to grab one.
Push to Device on Windows/Mac
I know on Windows, push to device is not supported in the simulator as of now, I am not 100% sure if it supported on Mac, but it is supported on Linux.
the simulator was just updated to version 3 and should have push to device for every OS now.
Impressed
I think that the hardware is pretty nice. It's super lightweight, almost too much so. The software is definitely beta quality - the email app doesn't automatically refresh, wifi turns off when the display turns off (to save power), no adjustable settings for still or video recording, etc.
I'm really enjoying it. No crashes or reboots in the day I've had it.
glystar said:
I think that the hardware is pretty nice. It's super lightweight, almost too much so. The software is definitely beta quality - the email app doesn't automatically refresh, wifi turns off when the display turns off (to save power), no adjustable settings for still or video recording, etc.
I'm really enjoying it. No crashes or reboots in the day I've had it.
Click to expand...
Click to collapse
And even when we need to reboot, it's fast enough on that.
I've been thinking of buying one, but it's always sold out.
Do you think it's usable as a lightweight daily driver? I was thinking of getting one for my parents, I could experiment a bit, and they just use phone calls / contacts / sms.
Hello, I have order the Geekshone Peak and it got the day also delivered. Unfortunately, I discovered that the Rear camera does not work. The Front Camera is working without problems.
Although it can be switched in the menu from the front camera to the rear camera, but the lens is then this is not activated.
Is this normal fault at the moment? If the Rear Camera not currently supported by the OS?
Thanks for answers und sorry for my bad english.
Best regards
not that mozilla is not a project to support, but i was wondering if there are some alternative os for this device ? gnu/linux or aosp based ?
Regards
rad30n said:
I've been thinking of buying one, but it's always sold out.
Do you think it's usable as a lightweight daily driver? I was thinking of getting one for my parents, I could experiment a bit, and they just use phone calls / contacts / sms.
Click to expand...
Click to collapse
I only own a Keon, but: These devices are for developers and geeks that don't get mad when something breaks, not your parents. Wait for a consumer device.
I have a Keon too, where I can find basic documentation to start hacking/upgrading my devices?
I am not a developer, only curious (maybe a bit geek too)... and I LOVE the Firefox OS paradigm!
android for peak ?
I was trying to find an android version that would run on it, but seems like the MSM8225 chip is not something you can get binaries for.
Any idea if its possible to compile an AOSP version that will run ?
:good::fingers-crossed:UPS just arrived with my new Geeksphone Peak :victory::victory::victory::victory:
_stefans_ said:
I was trying to find an android version that would run on it, but seems like the MSM8225 chip is not something you can get binaries for.
Any idea if its possible to compile an AOSP version that will run ?
Click to expand...
Click to collapse
It looks like the Peak is using the same chipset with HTC Desire X, which seems to have an alpha version of CM9:
http://forum.xda-developers.com/showthread.php?t=2265338
Can anyone enlighten me how to proceed from here?
That would be great to see CM9 or CM10 running on Peak as an alternative to the current Firefox OS build.
songuke said:
I received mine yesterday. To me, the build quality is mediocre. The back is quite hard to remove to insert the battery and SIM card. When the back is removed, I saw "Engineered in Spain", "Made in P.R.C". The screen is average. Perhaps I'm pixel peeping, but I can feel the grid of pixels when viewing images on it. It's a developer phone, but I did expect a better build.
Certainly order one if you are a developer.
Click to expand...
Click to collapse
Have you started working on an app yet? David Walsh (Mozilla) has written a really handy guide to runing any existing website into a Firefox Web App in just five minutes.
FYI, here are instructions on setting up the GeeksPhone for push to device on Windows/Linux/OSX: github.com/comoyo/Firefox-OS-training/blob/master/setup.md#pushing-to-geeksphone
I posted a while ago about the GPS failing to find even a single satellite. I got no responses, just a redirect to this forum. Since then I have searched and searched but no one has a solution to this common problem. I watched a video about cleaning the antenna contacts and performed this cleaning - no help. I have tried numerous apps that are supposed to help - no help. I took the tablet out of its case - no help. I even set the tablet out in the backyard for 45 minutes with a GPS app running as was suggested by someone - no help. I can't find anything at all about updating or re-installing GPS drivers or firmware so i don't know if that is even an option, but if there is a way to do this I would sure like help trying that. I have Titanium backups from before the GPS outage but I don't know which ones control the GPS.
It is as though this is a taboo subject and no one wants to even talk about it, but I did see that LOTS of people are having the same problem. Doesn't anyone have a solid solution short of just buying a new tablet? The GPS worked on a flight from TX to TN last March but never worked again after that. Could something on that flight have jammed or disabled my GPS?
If anyone has a solid solution based on actual resolution of this same problem, a lot of people would appreciate knowing about it.
Thank you.
Oooh i luv a good conspiracy! xD
Although i don't think taboo has any thing to do with it, now, if we were talking about dwarf elephants,sodomy and juggling then that would be troubling! But i think the empire is too busy tripping over the trump disaster to jam your gps. xD
okay, start by cycling through your back ups and find the one that worked, though i don't know much about titanium backup. It would have been smarter to use an actual recovery to make you backups.
The reason most common for not finding an answer or even a lead to one is insufficient data.
I have a tab4 and gps doesn't work, is literally nothing to go on.
What OS and/or firmware were/are you running? Did you install a custom kernel? Did you modify your OS with questionable applications or modifications that came at a cost or broke something?
What tab 4 is your tab 4? there are about 11-16 of them. Specifying the 8.0 is still not good enough.
It is interesting that you got some function on a flight. That's definitely worth a ? . I don't think a "jamming device" would fry your gps though.
I would say that you should first restore your tab back to cherry, meaning the original state you purchased/recieved it in and walk your mod process forward. Take notes and get logs.
m
Moonbutt74, thanks for responding.
My Tab 4 8.0 is model SM-T330NU
It's rooted & has several of the nice apps that can be used on rooted devices. Nothing was added between the time the GPS worked and when I noticed it not working. I am ALMOST certain of that. If there were a way to check logs for changes maybe I could get a clue - hadn't thought of that 'till now. Do you know how to do that? I suppose restoration to original state may end up being necessary, but I would sure like to avoid that. Everything else works just as I like it except for the fact that Google is still spying on me. There's no stable custom ROM yet as far as I can tell.
Yes, GPS worked fine on several commercial flights. It's fun seeing things on the ground and seeing what they are on the map + knowing speed and ETA.
O,
okay that's the main question, in -flight i guess your "line of sight" to gps satellites is unhindered, if it's anything like satellite tv service, then what's you situation on ground? Meaning canopy, and cloud cover. Back up your full current rom through recovery to external sd card. And then revert your tab to it's factory state. If you haven't modified the contents of your system directory after rooting then after doing factory reset while in recovery should put you back to your initial state.
Logging,
if you don't know how to set up adb there are plenty of threads dedicated to the subject, get that set up.
once your tab is cherry, get it connected to your pc abd run adb shell
once in adb shell run logcat -c to clear your log
start a gps related function or app
run logcat without any arguments for a "live" logcat
You have a huge log to go through , but go through every line.
You'll get the idea of how to read the log as you go.
We know that as of the LP 5.1.1 update to the sm-t330nu that samsung tried to disable ir blaster, so who knows?
I didn't know the wifi variants had gps.
m
moonbutt74 said:
O,
okay that's the main question, in -flight i guess your "line of sight" to gps satellites is unhindered, if it's anything like satellite tv service, then what's you situation on ground? Meaning canopy, and cloud cover. Back up your full current rom through recovery to external sd card. And then revert your tab to it's factory state. If you haven't modified the contents of your system directory after rooting then after doing factory reset while in recovery should put you back to your initial state.
Logging,
if you don't know how to set up adb there are plenty of threads dedicated to the subject, get that set up.
once your tab is cherry, get it connected to your pc abd run adb shell
once in adb shell run logcat -c to clear your log
start a gps related function or app
run logcat without any arguments for a "live" logcat
You have a huge log to go through , but go through every line.
You'll get the idea of how to read the log as you go.
We know that as of the LP 5.1.1 update to the sm-t330nu that samsung tried to disable ir blaster, so who knows?
I didn't know the wifi variants had gps.
m
Click to expand...
Click to collapse
I have posted this in a new thread, but I'll tell you the short version: My Allow Mock Locations was disabled in Settings/General/Developer options/Allow mock locations...). When I enabled this my GPS started working. Such a simple thing but a total odyssey to find out about it. OB
I have not seen a lot about this tablet other than it is Walmart's brand name, it is cheap, and it is based upon the MT8163. (The OEM is actually Chunghsin Technology Group CO according to FCC documents.) Anyway, I needed a cheap Android development platform, and this seemed to fit the bill since it appears less locked down than the Amazon Fire 7 I have -- however, I have already rooted the Fire 7.
What I am ultimately trying to do is connect a BeagleBone to an Android tablet using rndis over USB. On the Fire, this required running a script to set sys.usb.config as well as set up the networking details for the virtual ethernet port. I was hoping the Onn would be more standard, and I could just enable tethering and not have to deal with custom shell scripts. That is not quite the case. I cannot enable tethering with a BeagleBone (the option is greyed out), but I do appear to be able to enable tethering with a Windows 10 PC.
I can connect via ADB and get a shell, but I cannot get root access where I can query sys.usb.config or dmesg or anything else particularly useful that I know how to use. I can however, unlock the boot loader (via developer options), but that is where I am stuck. If I boot the tablet and hold the volume down key, I get a menu in Chinese or I get a factory test also in Chinese. Since the bootloader is unlocked, I should be able to load something else, but I'm enough of a newbie to have no idea what version of what I should load. I really just want a simple generic Android tablet to use as a UI and a platform as I learn Android development. Can anyone give some assistance on a direction? I've used Linux for years, but I'm taking the crash course in Android.
Update: For reasons I cannot explain, I can now get to an English menu. Volume up and power on gives me some options to Fastboot, Recovery, or Normal. So, I just need a recommendation on what to load.
I'm going to answer my own question. Most of the answers can be found in this thread that addresses rooting MTK based devices:
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Running mtk-su does indeed work on these Walmart tablets. (Shame searching for "Walmart" does not turn up the results I needed.)
What type of modifications have you been able to make?
Were you able to find a solution for permanent root? (edit: saw your answer in the MTK thread).
creeve4 said:
What type of modifications have you been able to make?
Were you able to find a solution for permanent root? (edit: saw your answer in the MTK thread).
Click to expand...
Click to collapse
I dont know what OP has but I have Magisk running EdXposed with gravitybox. Only a few minor tweaks so far, like navbar colors and power menu. Reboot recovery and screenshot works so far thats all I've really tried. I used sm commands to partition sdcard and still testing that. Screen gets a little confused at times, not really lag just weird and erratic. Overall its been fun about as expected on performance. Don't open the tablet or you will be disappointed by just how cheap it actually looks inside. Crimped and creased wires and cables with crooked poor looking connections. If anybody starts anything with project treble on this let me know, I at least want to test.
Personally, I stopped working on rooting when I was able to connect without it. It looks like others are having success, and I expect someone will publish (if it has not already been done) a step by step process.
Well... there's this: https://forum.xda-developers.com/general/help/how-to-unlock-root-xposed-onn-8-walmart-t3945284
I truly appreciate the work an effort made to do this, unfortunately I'm lost. Would it be possible for a tutorial by chance. I'm sorry for the inconveniences I truly am, I just don't know how to start this. My goal is to dual boot Kali Linux and Android Pie. I've got experience with Odin etc but for some reason no luck with this. thank you so much for your time and patience.
Honestly I just wanna take one of these and set it up with stock (vanilla) android 9 and exclusively use F-Droid only on it.
Unfortunately, the specs are weak and it makes even mundane pdf reading an arduous task at best (so I hear...I do not own it yet.)
3drinks said:
Honestly I just wanna take one of these and set it up with stock (vanilla) android 9 and exclusively use F-Droid only on it.
Unfortunately, the specs are weak and it makes even mundane pdf reading an arduous task at best (so I hear...I do not own it yet.)
Click to expand...
Click to collapse
If you buy one you can unlock, root and install numerous gsi's without gapps and run a foss device. I'm using the 8" version that way. You can also run microG to use any google apps you may want. If you want any.