yashsingh1/xdaforums huggingface dataset:
[MDA II, XDA II, 2060 General] dl:
I've had my MDA in the US for a couple of weeks now. During the first week the reception was great, but now is terrible. In at least two specific places where I used to get good reception, I now get no service at all.

Hard boot has not helped.

I suspect the problem started after I plugged in an external antenna. For those who have seen the inside, is there anything I might have knocked loose?

I'm not afraid to open it up, but there might be a tradeoff in getting warranty service afterward. Mostly likely, I will open it up, void whatever warranty there is, and find nothing to fix anyway . . .

I am a long-time XDAI/AT&T user. Switched to T-Mobile about the same time as getting the XDAII. But initially, after switching, I sat in a meeting and surfed the internet with good coverage. A week later, in the same place, no service. There is a marked decrease in signal strength in every other location, also. Much too consistent to be a problem with the provider (I think).
[MDA II, XDA II, 2060 General] dadarkmcse:
I'm having the same exact problem. Does anyone know what might cause this? how it can be fixed?
[MDA II, XDA II, 2060 General] wtharp2:
Poor Reception

I seem to be having a poor reception issue, too, though I'm not sure what reception I should be getting from my XDA II -- I've only had it for a week or two, and can only compare its phone performance against an XDA 1. In that comparison, the XDA 1 received much better than the XDA II. Can anyone tell me if something is going on?

Thanks!
[MDA II, XDA II, 2060 General] Rudegar:
maybe it's because xda1 have an antenna ?

my exp is that they are the same receptionwise

and both of them are the same as my old motorola cellphone
[MDA II, XDA II, 2060 General] watchdogsdg:
Bad Reception after plugging in external antenna

had the same problem after plugging in a radio shack antenna. It was so bad I was ready to buy the new Ipaq thinking I could use the quad band for AT&T in the USA.

THe bad reception lasted about two months, thenone day it just "snapped" out of it. I have had great reception now for over a month, and have used an external antenna without a problem. plugging it in and out no longer effects the reception when it is unplugged. A hardware switch that did not reset? No idea, just reporting m experience.

Steve
[MDA II, XDA II, 2060 General] powerppc:
Could it be because of your provider? Mine has almost no reception here at work but that's how it was eversince I started working here. Even with my Nokia, my XDA II still have one or two bar the most here at work. But when I'm at home, I get full reception.

But Cingular has always had bad coverage around my work area, Verizon on the other hand has good coverage.
[Samsung Galaxy Mini] space1991:
TWRP & CWM Link --> http://goo.im/devs/thewhisp/jena-recovery

ROOT Link --> http://www.mediafire.com/?g4aoso6qoqm72o0

KERNEL Link -->

BLN Link -->

I can't found Kernel (overclockable) and Bln link, they are expired... someone could give me them??
[Samsung Galaxy Mini] MrMateczko:
Kernel - http://www43.zippyshare.com/v/24843785/file.html

BLN - http://www62.zippyshare.com/v/95476641/file.html
[Samsung Galaxy Mini] tekkenl0rd13:
OC kernel is in my thread HERE!

ALSO

read first

before making threads like this. responsibly use the search button
[Samsung Galaxy Mini] space1991:
Thank you very much... And sorry, but the link in your post redirect me to a 404 eroor page... Probably is my internet connection... Thank you again
[HTC One S] tkitk:
Hello,

Yesterday, i was on a plane and my htc ons s S3 turn off due to battery go to less than 5% and loses all power, when i came to home i try to charge it but the LED still off and when i pressing the Power key does not turn on the device, i have left more than 5h and the issue still here.

if i remove the battery and than try to charge it with an externel adaptater sector, it will be charged or not ?

Please any idea ?
[Nexus 10 Q&A, Help & Troubleshooting] knoxploration:
Hi all

Just got my Nexus 10 yesterday, and am wondering if I have faulty hardware, or Photosphere is just unusable on a stock tablet.

I'm not talking about stitching issues with nearby objects; I know about parallax. What I'm experiencing seems to be an issue with the accelerometer / tilt sensor, compass, or both.

So far, out of three Photosphere panos I tried, only the first worked. On the second, after I'd completed only one row of photos, the blue dot for the first picture in the second row suddenly drifted away across the sphere, while I was holding the tablet perfectly still.

I stopped the pano, and tried to start a new one, but when I centered the blue dot, the three circles above the frame flickered wildly and the camera wouldn't capture even the first shot of the pano. I completely cold-booted the tablet, and the exact same thing happened on reopening the camera; it just wouldn't take a photo with the blue dot centered, no matter how I held the tablet or tilted it. That first pano row did stitch correctly, although not a full 360 degrees, probably more like 270 degrees or so.

I did some Googling and downloaded the GPS Status & Toolbox app, then ran both the Compass Calibration and Calibrate Pitch & Roll tools. When I reopened the camera app and tried another Photosphere, it took photos correctly again, and I completed the full first row without problem. I almost completed the second row of photos, but then the same problem occurred again -- right before I reached it, the blue dot drifted away from the correct location. I stopped without that shot, and checked the pano that stitched, but it was completely nonsensical -- shots from the first row appear up in the second row instead, random pieces of house floating in a cloud-free blue sky. (So it's not that a texture tricked the app into thinking the shot belonged there.)

If I leave the GPS Status & Toolbox app sitting, it only seems to show around one degree of compass drift with the tablet sitting perfectly still, although immediately after I started the app it did show the compass jump around by 90 degrees 3-4 times.

I'm baffled by whether this is a hardware or software problem. The tablet is brand-new with little software installed, and isn't even rooted, let alone anything else. It's as stock as stock can be.

Anybody else have similar issues, or any suggestions?
[Nexus 10 Q&A, Help & Troubleshooting] knoxploration:
Apologies, I thought I posted this on Q&A, I'm not sure how it ended up in general. If a mod would like to move it, please do!
[Nexus 10 Q&A, Help & Troubleshooting] stamatis:
Done;).

Next time please use the report button in order to bring something to our attention instaid of posts like the above.

You can imagine the difference in efficacy:D.
[Nexus 10 Q&A, Help & Troubleshooting] knoxploration:
Thanks very much!
[Nexus 10 Q&A, Help & Troubleshooting] knoxploration:
I just tried this again in bright mid-afternoon sunlight, and the results were comically awful. This time I successfully captured the first row of the Photosphere panorama, although it seemed that the compass might have drifted a little bit in one 360 degree rotation, because the first and last shots were off from overlapping by about half a shot-width.

However, when I started the second row of the Photosphere (this time I went for the row beneath, rather than the row above as I had been doing), it went absolutely insane. I continued turning at the same rate with which I did the first row, but in the time I did less than a half-turn, Photosphere acted as if I'd done closer to a three-quarter turn; the second row's shots were off by more than 90 degrees from the correct direction. I stopped moving at this point and stayed absolutely still, but the blue dot continued to track around as if I was still moving, capturing multiple identical photos and using them to fill in the next 90 degrees or so to complete the second row.

Nobody has answered me yet, sadly. I cannot believe that it is like this for anybody else, or Google would be being lambasted for the hopelessly, absolutely unusably-bad performance of Photosphere.

That leads me to believe it is a problem limited to my tablet -- but how? Looking at GPS Status and Toolbox, both of my tilt sensors report accurately, and the accelerometer *seems* to do so as well. (It shows a zero value when the tablet is stationary.)

The compass is another matter. 99% of the time, it is perfect -- even with sensor filtering disabled, it reads a rock-steady value that changes instantly when I move the tablet. Just occasionally after I move it, it will drift by 2-4 degrees while the tablet is stationary though -- and just one time it changed radically without warning. Having been showing values that stayed steady when the tablet was still, and returned to the same value after the tablet was moved back to the same position, the value suddenly drifted by more like 30-40 degrees without the tablet being moved, and if I moved the tablet around and put it back in the same place, it returned to this new value instead.

It seems like the compass has an intermittent fault, although how I persuade Staples of this I don't know. I guess I can try to show them its complete inability to stitch a panorama, because it took significant effort to get it to show a major issue in the GPS Status app.

Or is there something I'm overlooking, a setting I could change or something that needs wiping or recalibrating somewhere? There's no magnets near the device, btw.
[Nexus 10 Q&A, Help & Troubleshooting] knoxploration:
Figured I'd drop a status update here, even though I never got any answers.

The result: Yes, my tablet had a hardware fault. I swapped it out, and the second tablet is rock-solid stable when making Photospheres.

Now, if only there was a way to lock exposure and white balance from the first frame. :-/
[Nexus 10 Q&A, Help & Troubleshooting] supertaco:
I have the same problem. Can you help me descripting your call to Google?

Enviado desde mi Nexus 10 usando Tapatalk 4
[Nexus 10 Q&A, Help & Troubleshooting] knoxploration:
I didn't need to call Google. I took the tablet back to the store and they swapped it, after a very brief description of the problem.
[Nexus 10 Q&A, Help & Troubleshooting] supertaco:
That's muy problem. I live un mexico and a friend of mine send it to me... And i don't have the warranty booklet and i don't unos where or who to call

Enviado desde mi Nexus 10 usando Tapatalk 4

---------- Post added at 06:00 PM ---------- Previous post was at 05:59 PM ----------

Enviado desde mi Nexus 10 usando Tapatalk 4
[Verizon Samsung Galaxy S III] decimalman:
Welcome to decimalman's kernel playground!​

As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.

Features:

Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)

Underclocking down to 54 MHz, with stability improvements

Undervolting compatible with most apps

Fast charge without unplugging first

Glorious animations for the notification and softkey LEDs

Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)

freelunch and tierservative governors for optimal battery life without sacrificing responsiveness

Automatic mpdecision and auto-hotplug are only enabled when needed

Adjustable minimum voltage for stability on finicky processors

Optimized UKSM to free up some extra memory

Code optimizations for size and speed

Compiler optimizations (-O3, LTO, and more) because faster is better

Donors: Thanks, everyone! Your generosity is much appreciated. :good:

drpenguino, 0xScott, vmancini3 (twice! :good:), Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict

Remember:

Nandroid!

last_kmsg and/or logcat or it didn't happen.

Other kernels have their own threads or forums. Discuss them there.

Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.

Be silly. We're here to have fun.

Installation:

Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called. :p

Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).

Reboot.

Undervolting:

Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).

Downloads:

MediaFire:

All Downloads

dkp-vmin-XXX.zip

Solidfiles (Make sure you have an adblocker!):

All Downloads

dkp-vmin-XXX.zip

Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.
[Verizon Samsung Galaxy S III] decimalman:
Bugs:

Let me know.

Stable changelog:

3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.

4/8/13 (3.0):

FauxSound support

Strip more useless stuff

A few bonus optimizations

4/8/13 (3.4):

Port everything except erandom from 3.0

Enhance cpufreq for easier configuration

4/24/13 (3.4):

Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.

Lots of CM/CAF/Linux updates

Working AssWax governor

Trinity colors support

sio, zen I/O schedulers

erandom is back!

Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness :p

Probably lots more, but there's hundreds of commits to sort through...

5/29/13 (3.4):

Bugfixes: better overclocking support, better hwrng support, etc.

Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface

Automatic auto-hotplug

New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain

6/14/13 (3.4):

Bugfixes: fix several critical bugs in the 5/29 release.

9/7/13 (3.4):

Fixes for OC, UV, auto-hotplug.

A few new optimizations.

Synced up with CM.

9/20/13 (TW):

Ported everything from AOSP to TW.

9/20/13 (4.3):

Merged 4.3 from CM into the existing 4.2 code.

Current experimental branches:

Nothing interesting at the moment.
[Verizon Samsung Galaxy S III] PsiPhiDan:
This looks great - especially excited about your custom governor! Thanks!!
[Verizon Samsung Galaxy S III] aypeeootrek:
Glad we have another kernel dev. But do you plan on releasing a tw kernel? I run tw 98% of the time and would love to try it out. Thanks for your work regardless
[Verizon Samsung Galaxy S III] decimalman:
freelunch is absurdly simple, but does its job well. Let me know what you think. Happy flashing!

I don't run TW, so I don't have any plans to release a TW kernel. If there's enough interest, I suppose I could get to work on one though.
[Verizon Samsung Galaxy S III] aj8600:
Interesting. Looks cool man, will check it out
[Verizon Samsung Galaxy S III] Josolanes:
I'm excited to give this a shot!
[Verizon Samsung Galaxy S III] Chitala383:
flashaholic commencing flash!
[Verizon Samsung Galaxy S III] masri1987:
Anyone using trickster mod with this kernel?
[Verizon Samsung Galaxy S III] killerT721:
Love this kernel! Freelunch is amazing
[Verizon Samsung Galaxy S III] juancaperez2000:
This kernel run pretty good!!
[Verizon Samsung Galaxy S III] decimalman:
It's the recommended tuner app, and plenty of people are using it (mostly on Sprint and AT&T). It shows some options that are completely bogus (like GPU governor), but I've added a few extras that only Trickster supports.

Thanks for the encouraging feedback, everyone! It's much appreciated. :good:
[Verizon Samsung Galaxy S III] TheBurgh:
Kudos on this kernel. It has been perfect for me so far.
[Verizon Samsung Galaxy S III] trvbone:
Running good on my d2usc! What scheduler do you recommend?
[Verizon Samsung Galaxy S III] decimalman:
New 3.4 experimental builds are going up!

governors is building now, and has sio and zen. It'll eventually have a few new governors, but I haven't gotten everything ported yet.

gcc480 is up now, and is a test to make sure GCC 4.8.0 isn't causing any crazy bugs. It's also got sio and zen.

Edit: I forgot about you, trvbone. I don't have a preferred scheduler. I usually just use sio. I've never had a positive experience with ROW, but that might just be bad luck on my part.

More edit: I'm building a 3.0 kernel with trinity colors support and GCC 4.8.0 now. It should be up shortly.
[Verizon Samsung Galaxy S III] trvbone:
I'm no noob when it comes to kernel lingo, but I'm not sure what the dif is here between the kernels listed as governors and gcc480. Are these two different kernels? I'm not aware of what gcc480 is I guess. Sorry until recently I was a dedicated lean kernel user and don't know all of the terminology since lk was pretty plain Jane.

I'm not a huge fan of row, but that's what I'm using right now cause it's quick just a little sketchy sometimes.
[Verizon Samsung Galaxy S III] decimalman:
I have a tendency to describe things in the least understandable way possible. Sorry about that.

Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.

The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.

The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry :)). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.

Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.
[Verizon Samsung Galaxy S III] trvbone:
Thanks for the expl I'll flash tomorrow morning and give it a whirl! Great job BTW. This is now my daily driver!
[Verizon Samsung Galaxy S III] mademan420:
Giving it a go now. Do you have any test methods you use to test the stability of a kernel other than the everyday use approach? Thanks for the support, looks sweet:good::good::good:
[Verizon Samsung Galaxy S III] decimalman:
Nope. :( I don't have any BT devices to test with, and I wanted to get a build that boots out before I start working on it.
[Verizon Samsung Galaxy S III] mickskillz:
Np. I'll wait until you merge BT commits.... let me know if you ever need a tester. Thanks

Sexy gS3
[Verizon Samsung Galaxy S III] Dearborn1977:
Ah gotcha...still no luck with Bluetooth on 6/9..everything else good so far.
[Verizon Samsung Galaxy S III] decimalman:
With the information I got from you and another user, I have a pretty good idea where to start on this. I'm off to work bright and early tomorrow, but I'll be working on this over the next few days.
[Verizon Samsung Galaxy S III] pocii29:
Putting your nanolunch/zen to the test on a zero lemon! uv about 25 across the board
[Verizon Samsung Galaxy S III] mickskillz:
we won't hear back from you until the weekend then...LOL
[Verizon Samsung Galaxy S III] decimalman:
What, a guy can't be flaky and not post updates about issues? :p Honestly, it's like it hasn't clicked for me that people are actually using my kernel, so I don't even realize that I should post progress reports. Sometimes I'm dumb like that. :o

The good news is that I remembered my old Archos 5, so I have a device to test BT with. It's painful to use it (800 MHz single core, resistive touchscreen, Android 1.6), but it has bluetooth, so it'll do. That should speed up the debugging process considerably.
[Verizon Samsung Galaxy S III] Dearborn1977:
I think he was talking to the guy testing the Zerolemon..he won't run out of juice until the weekend :D. But we definitely appreciate updates!
[Verizon Samsung Galaxy S III] decimalman:
That possibility hadn't occurred to me. I should really get some sleep. :p He's probably right. Those batteries are scary.
[Verizon Samsung Galaxy S III] mickskillz:
Sorry for the confusion...... I would never expect or make a comment on time you donate. But thanks for even trying to get BT working.

Sexy gS3
[Verizon Samsung Galaxy S III] decimalman:
No worries. I'm not going to get offended by a comment that I misinterpret. ;) I've got thick skin, and development is too much fun to get offended anyway.

BT is important to lots of people, so it's definitely worth looking into. It's possible that there's a quick fix to get it working until I can actually track down the issue. Otherwise, it'll take a while to dig up the actual issue.
[Verizon Samsung Galaxy S III] pocii29:
Haha you guys won't be seeing me for a while with the way things are lookin ;)
[Verizon Samsung Galaxy S III] Dearborn1977:
I don't know if it's related but CM fixed some Bluetooth issues they had toward the end of May. I had slightly different problems with CM based kernels before they fixed it - Bluetooth would connect but only manually. On your latest build it just would not connect at all except the time I paired and unpaired the device several times. Even then once I rebooted it stopped working again.
[Verizon Samsung Galaxy S III] decimalman:
I don't think it's related. I just put together a band-aid fix until I can actually track down the real issue at hand. Without further ado:

New test builds are going up. BT should be working--I'm able to FTP to another device and transfer files, but I don't have any other BT devices to test with. Anyone who's been having issues, please let me know if you're still having issues on the new build.

Changelog:

Disabled an optimization in the dhd module. BT appears to be working.
[Verizon Samsung Galaxy S III] masri1987:
Gonna test it out for ya in a few, question, what setup should I go with?
[Verizon Samsung Galaxy S III] decimalman:
Take your pick:

The best battery life possible: turn your phone off. :p

The best battery life possible, seriously: I have no idea. freelunch or nanolunch (or maybe asswax) for governors; noop, sio, fifo, or maybe deadline for schedulers; whatever undervolt your phone can handle well; maybe even reduce your maximum frequency.

The smoothest experience possible without completely wrecking battery life: interactive governor; row scheduler; overclock to 1674 (or higher if it's stable); in trickster, disable mpdecision, open governor control, change hotplug_intpulse to 1, and increase hispeed_freq (to 1512 maybe?).

In case you're curious: when set to 1, hotplug_intpulse automatically powers core 2 on whenever you touch the screen/buttons/whatever. Awful for battery, great for smoothness. :)
[Verizon Samsung Galaxy S III] masri1987:
Thanks for advice, if I use nano or free lunch, what is the best scheduler that plays nice with them?
[Verizon Samsung Galaxy S III] Dearborn1977:
I can happily report Bluetooth is working in latest build! :thumbup:

Running latest Rootbox nightly. It has halo...all is good. :D
[Verizon Samsung Galaxy S III] masri1987:
So tried to flash the latest test you put up for d2vzw and it doesn't boot past splash screen on liquid smooth