yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] WhiteGorilla:
Calculator & Converter Pro

UPDATE v4.3.7

(May 29, 2013)

In the last two months we have added the following features:

1) Added select all button for easier user selection of currencies

2) Get Pro Version for free by unlocking reward: http://goo.gl/ogDF7

3) Nexus 10 layout bug

4) Fixed all crashes! (No reported crashes in last 30 days

UPDATE v4.3.1

(March 3, 2013)

1) Added "Themes" option for users who don't like new theme.

UPDATE v4.3 (February 28, 2013)

Thank you to everybody for the feedback, and suggestions! We’ve completely revamped the app and included almost everything you guys asked for. Changes are as follows:

1) Brand New Graphics and UI

2) New Graphing Calculator

3) Added new advanced functions

4) Added new measurement types including Cooking, Energy, PC Memory, Speed, and more.

5) Convert as many currencies as you like at once

6) Revamped tipping calculator with sales tax setting

7) Add/remove calculators from app

8) Enable/Disable Haptic Vibration

9) Calculator History

10) Copy equations & results to clipboard

Google Play Download:

Pro Version ($2.99) | Free Version

Reviews:

TalkAndroid Article | Androinica Article | Droid Dog Video Review

Screenshots:
[Paid Software Announcement and Discussion] thermax04:
UPDATE v4.3.7 (May 29, 2013)

Not available any more!!!
[Nexus 4 Q&A, Help & Troubleshooting] JohnCarrot:
As I continue to read new about the upcoming google device, I cannot help but wonder if it will manifest. Many people are pointing to a Motorola x phone. However, I have waited my time for this new device and more importantly a newer version of Android OS. I would like to know all of your opinions on this topic. I really want a Nexus 5 made by HTC, but that is just a wish. Please let me know what you believe will happen along with your dream phone.

Enjoy,

JCarrot
[Nexus 4 Q&A, Help & Troubleshooting] Gorjira:
Personally I would like to see a Sony Nexus 5. Look at the build quality of the Xperia Z Ultra, the big-a** phone. It looks great and is thin as all hell. Their too invested into the Xperia name to do so. And I'm not sure how Google feels about Phablets but I'd like to see a Nexus Phablet. A 5.5-6 inch screen running pure Android with a almost 2GHz processor, smoothly flowing thanks to (wait for it...) 3(!) GB of RAM. No, no, no I mean 2GB of RAM. I would like to see a HTC Nexus though.

How about an Apple made Nexus?... ;)

Sente from my M470BSA using xda premium
[Nexus 4 Q&A, Help & Troubleshooting] rayiskon:
Wtf did i just read? :confused: :D
[Nexus 4 Q&A, Help & Troubleshooting] IRX120:
Mabey Google will build it themselves,

Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
[Nexus 4 Q&A, Help & Troubleshooting] BobWalker:
I'm sure Steve Jobs left special instructions for that :silly:

Key Lime Pie will probably be released this fall. Nobody knows yet what the next Nexus device will be, but I expect that Google will make an official statement regarding the next Nexus phone only when Key Lime Pie is actually released.
[Nexus 4 Q&A, Help & Troubleshooting] ryaniskira:
no no no no no no NOOOOO :p:D

Nexus 4 CyanogenMod 10.1.0
[Nexus 4 Q&A, Help & Troubleshooting] simms22:
the next nexus will come out towards the end of the year, mid fall. key lime pie will probably come out about this time. thats keeping to googles history. does it matter who builds the next nexus? not to me. ive had/have every nexus phone, and ill grab the next one too. really, the important sticking point to me is that it IS a nexus :)
[Nexus 4 Q&A, Help & Troubleshooting] nd4spdbh:
If you guys just put two and two together.... in december when they have historically released their phones for the past like 3 or 4 years in a row.... we will probably see a 4.7-5inch phone made by Motorola which google just acquired, with either the sapdragon 600 or the samsung exnos 5 octa ... and at least 2 gb of ram.. Its not hard to put some pieces together.

and No you will NOT get your sdcard slot.
[Nexus 4 Q&A, Help & Troubleshooting] El Daddy:
Yep if it's a nexus, I'll buy it. Hell I even have a nexus Q. :)
[Nexus 4 Q&A, Help & Troubleshooting] Tunderpimp:
Nah dog apple is making the nexus 5
[Nexus 4 Q&A, Help & Troubleshooting] Gorjira:
Ha it's funny reading everyone's reaction to my last statement. An Apple made Nexus 5... Imagine if that really happened?... But really I see either LG making one again or Motorola. To be honest I don't have any gripes with my Nexus 4.
[Nexus 4 Q&A, Help & Troubleshooting] thfreedumb:
I would just like a metal body like the HTC one that doesn't cause signal problems. All this glass makes me nervous and I can only deal with it for the Nexus 4, please not again. haha
[Nexus 4 Q&A, Help & Troubleshooting] samabenie:
5" screen

Heck, call it the Nexus 5 and throw a 1080p 5" screen on that bad boy. It better be thinner than a GS4 too!
[Nexus 4 Q&A, Help & Troubleshooting] omaga:
:laugh::laugh: yes he did...he probably said "F**k Google"
[Nexus 4 Q&A, Help & Troubleshooting] atulalvenkar:
Past experience days Google gives 2 years per OEM to build Nexus devices.

HTC - G1, Nexus One

Samsung - Nexus S, Galaxy Nexus

LG - Nexus 4

Granted G1 was not called a nexus device but it did come with stock Android and close collaboration between Google and HTC.
[Nexus 4 Q&A, Help & Troubleshooting] scream4cheese:
So kinda like what Samsung and HTC are doing right now.
[Nexus 4 Q&A, Help & Troubleshooting] simms22:
well, yes and no. id consider a g1/dream a pre-nexus. it was googles first developer phone, and first phone sold directly by google, and worked with aosp directly out of the box. no special propritary drivers like these two htc/samsung phones.
[Nexus 4 Q&A, Help & Troubleshooting] hp13:
nexusb1tch :p

---------- Post added at 01:50 PM ---------- Previous post was at 01:48 PM ----------

honestly i just want better camera and if possible have speakers at the bottom like iphone. otherwise i could care less who builds the next one. always love the surprises form google :D
[Nexus 4 Q&A, Help & Troubleshooting] napyaninja:
How about own nexus company by Google...
[Nexus 4 Q&A, Help & Troubleshooting] JohnCarrot:
I agree that it doesn't really matter who makes it. I just think that HTC has really fantastic build quality that would be phenomenal if collaborated with Google. Also, I just really want it to come out sooner because my current phone is breaking down, but I don't want to buy a Nexus 4. I'd rather buy the next Nexus phone. Hopefully, it will have a 5" screen to compensate for the software buttons.
[Nexus 4 Q&A, Help & Troubleshooting] simms22:
thats me :D
[Nexus 4 Q&A, Help & Troubleshooting] deeren:
Speaking of build quality; I agree that HTC one is awesome but so is the nexus 4.... in hand. I have seen my friend's HTC one ( few weeks old) get a cracked screen and bent case from one single fall. And the worst thing is that you cannot replace the parts. Even ifixit rated the phone as irreparable.The gnex was a piece of plastic but hell was it solid. I cannot recall how many times it fell on concrete, road, without any significant damage.
[Nexus 4 Q&A, Help & Troubleshooting] scream4cheese:
motorola
[Nexus 4 Q&A, Help & Troubleshooting] roysuryo:
As a former Sony Ericsson fan, I prefer Sony Nexus.. ;)
[One (M7) Q&A, Help & Troubleshooting] devinthomas:
I saw that iPhone users on AT&T got a hacked carrier update today that enables HD Voice in markets where it's being tested in the USA, and I can't find anything on how to enable it for our HTC One devices. I know that for the One X it was a simple build.prop tweak, but I don't see any such entry in the build.prop for the HTC One. Any ideas?
[One (M7) Q&A, Help & Troubleshooting] daclaw:
mine has the following in build.prop, i'm pretty sure it enables it...

ro.ril.enable.amr.wideband=1
[One (M7) Q&A, Help & Troubleshooting] Shane_pcs:
In addition the carrier has to white list the handset model as a whole.
[One (M7) Q&A, Help & Troubleshooting] devinthomas:
AOSP or Sense?
[Upgrading, Modifying and Unlocking] doncal:
I downloaded "xdaII_upgrade_16044eng" from site myxda

when executing thru usb crdle "activesync" from laptop to xda, process halted with message ERROR 100: MODEL ID ERROR

my laptop now does not find & connect to xda

xda screen remains at display of USB V 1.06

What is wrong & how can I fix?

I was sold this device without motherboard cd & without companion cd

Can anyone send me copies of these please?

I am dejected, frustrated, impatient, but optimistic

Don :cry:
[Upgrading, Modifying and Unlocking] Rudegar:
the only thing on the cd is activesync and outlook

you can just download activesync it's the only software the pc needs
[Upgrading, Modifying and Unlocking] willie_xda:
Don,

I have exactly the same problem with my XDA IIs. I am not sure there is a solution. My understanding is that one can only communicate with the XDA through ActivSync. If the XDA has dumped its operating system one cannot sync with it and therefore not resolve the problem.

I hope somebody will tell me that I am wrong.

Willie :?:
[Upgrading, Modifying and Unlocking] AdmiralAK:
Not sure if this applies, but when I had an iPaq I loaded linux on it. I did not need activesync to talk to it, I needed to have it cradled and accessed it using a terminal application. It's been a while since I did this so I dont remember exactly what I had done :-) (I am pretty sure I did something to the bootloader before I started messing around with the terminal :) )
[Samsung Galaxy S Relay 4G] :
We are now officially on CyanogenMod, this thread is old.
[Samsung Galaxy S Relay 4G] :
Bug list:

Minor glitch switching from video recording on FFC (switch to back camera before switching back to still images)

Flash while video recording

Pandora while using Bluetooth/wifi at the same time

MMS sizes set too big?

You tell me.

Wontfix:

Chargers that do not send any signals on D+/D-

Enhancements needed:

Panel colors/gamma correction code needs porting from d2 (Galaxy S III)
[Samsung Galaxy S Relay 4G] wedg11383:
Seems great so far. WIFI speed is much better.

I am having no luck toggling NFC though. A small request as well: Can the default Bluetooth name be changed back to Relay instead of Galaxy S 3.
[Samsung Galaxy S Relay 4G] stephenclower:
I'm finding that if I have headphones plugged in at boot, there's no sound until I unplug them and then reconnect. GPS also seemed to drop a lot on the way to work this morning, but that might be coincidence. Other than that, the new ROM seems to be working very well.
[Samsung Galaxy S Relay 4G] John5788:
Regarding the bootloader and modem from that post, can the zip files be flashed via CWM? Also, what versions should it report?
[Samsung Galaxy S Relay 4G] wedg11383:
I was able to flash them in CWM yes. Just mind the GPS toggle as stated in the previous post.
[Samsung Galaxy S Relay 4G] :
Going to add one more bug here, I'm having problems with certain chargers, especially if they're plugged in during boot. Looks like I need to spelunk into the kernel a bit more.
[Samsung Galaxy S Relay 4G] :
lbcoder fixed wifi mac addresses. Here's mine, just for fun

https://www.dropbox.com/s/qpte7lv0ijencic/2013-06-29 10.39.56.png
[Samsung Galaxy S Relay 4G] Jason78729:
The wallpaper isn't covering the far left screen on my desktop (5 screens). It happens with trebuchet, nova and apex launchers so it might be something that needs to be adjusted from the d2 settings.
[Samsung Galaxy S Relay 4G] terminal addict:
Miracast

I understand that you don't have an adapter, but can you confirm that you see the Wireless Display option?

Settings > Display > Wireless Display

Thanks!
[Samsung Galaxy S Relay 4G] jonahly:
Total Reserve.
[Samsung Galaxy S Relay 4G] misteropinion:
I flashed 196 yesterday and everything seems to be working, except that it would not boot (stayed in the boot logo) until I started the boot with my character unplugged. GPS took a long time to sync up right until I did a cold start, and then it took about as long as that normally does. There are still possibly some charger issues which I will report as I find them. BT works (had to repair everything), Wifi works, haven't used headphones yet, am using a 4100mAh w/o the NFC, so I can't test that.
[Samsung Galaxy S Relay 4G] dillalade:
Seems to work well.

1)

However BetterBatteryStats tell me the phone is not achieving deep sleep at all, rather in 'Awake' state 100% of time (under Other) & CPU States illustrates no info for 'Deep sleep'... :D

2)

Just tested 'wifi direct' with a friend running cm10.1 Stable on his Nexus 4... he can see my device yet the relay cannot see any devices when scanning. Progress but not yet functional :thumbup:
[Samsung Galaxy S Relay 4G] misteropinion:
And, interestingly enough, it now says that it is charging (led and spinning meter) when it is completely unplugged. Can we have discovered a way tap into the cosmic background energy pool? Untold wealth awaits!
[Samsung Galaxy S Relay 4G] John5788:
I am noticing that screen on takes a while once the phone has been locked and screen off for a while. It almost feels like sleep death, but after a while, the screen comes back by itself.
[Samsung Galaxy S Relay 4G] misteropinion:
Flashing up to 198 fixes this. I think that fixes all of my "daily drive" features. I'll try it with a bunch of chargers today and see if any of them don't work.
[Samsung Galaxy S Relay 4G] chuckiev79:
Runnning on198 and everything is smooth, even underclocked. Using conservative and very little if any slowdown, and I have 142 apps!
[Samsung Galaxy S Relay 4G] dillalade:
No matter how I try to install the latest 3.4 nightlies I cannot achieve 'deep sleep' ever (100% awake.)

Before installing the 3.4 rom, I installed the MC5 modem & Bootloader & rebooted (as per original post here.)

Back into recovery & I initially tried full system/data/cache/dalvik wipes (and also for the first time on this device I also wiped "/data &/data/media" in the mount menu) before installing the 3.4 rom & gapps.

No deep sleep.

I revert back to my 3.0 nand backup and deep sleep is restored.

Then attempt a flash over the 3.0 restore with the latest 3.4 nightly... same dillema - no 'deep sleep.'

Am I alone or Is anyone else experiencing this?

For anyone who is on 3.4 and achieving 'deep sleep' (I know lbcoder & nard have confirmed they achieve deep sleep via IRC chat) can you please share your exact method in migrating from 3.0 to 3.4 (including when & how you exactly flashed the modem &/or bootloader.)

For what it's worth the recovery I have been on for a while now is CWM Version 6.0.2.8.

Baseband under settings/other shows " T699UBVMC5."

I'm using BetterBatteryStats to determine 'deep sleep' status.

Using 'Android Root Toolkit' (the only method I could find to detail bootloader version) to tell me my bootloader version as "T699UBVMC5."

I can't see that I'm doing anything out of turn.

I'm a well seasoned CWM flasher (well atleast I thought I was:rolleyes: ), tried builds 197,8 & 9, same effect for me.

Any thoughts, ideas, cures, methods would be greatly appreciated.

Thanks in advance
[Samsung Galaxy S Relay 4G] chuckiev79:
Here is a related thread that may help http://forums.androidcentral.com/sp...keeping-my-phone-awake-eating-my-battery.html. also there is a deep sleep app on playstore. I had it but I usually toggle everything on and off from pulldown menu as a need it, which saves enough battery for me.
[Samsung Galaxy S Relay 4G] misteropinion:
My in-car charger still makes my phone stupid, where after I unplug it still says that it's charging. Power consumption is definitely up, my 4100mAh battery is behaving like the 1800 used to.
[Samsung Galaxy S Relay 4G] chuckiev79:
Just recently realized I am also not getting deep sleep. I think this may be the culprit
[Samsung Galaxy S Relay 4G] misteropinion:
Interesting. I use System Panel, and it's telling me that kswapd0 is using 3% of my CPU. That's new since 3.4. I knew I was tight on RAM (Srsly, Sammy, how much more would this phone have cost with 2GB instead of the 1?), perhaps that's what's going on.

Let's flash up to last night and see what's new!
[Samsung Galaxy S Relay 4G] stephenclower:
It appears TuneIn Radio is once again borked as of build 198.
[Samsung Galaxy S Relay 4G] :
I am unable to reproduce any of the bugs with tunein/google music or deep sleep. Try again with build 200, a few things have been tweaked.

Right now, the only bugs I know of as confirmed are charging related and switching video modes on the front camera.
[Samsung Galaxy S Relay 4G] stephenclower:
Nard,

Build 200 indeed fixes TuneIn. Just in time for my road trip to the in-laws for the 4th. Thanks!

Steve
[Samsung Galaxy S Relay 4G] Jason78729:
Try installing without adding any apps and test.
[Samsung Galaxy S Relay 4G] dillalade:
A workaround has been discovered by lbcoder who has helped diagnose this deep sleep issue - which was baffling as it seemed to only happy to my device and nobody else.

Long story short, I was probably one of verrrrrrry few here that had been testing 3.4 without ever using the USB (particularly connecting to a USB host... I.e your pc/laptop.)

A feature for when the device is connected to a USB host, is that the device naturally does not deep sleep.

Now, for whatever reason, upon each reboot (for me at least) my device believes it's connected to a USB host (hence achieving no deep sleep.)

Fix: For those not achieving deep sleep... plug into a USB host count to 10 unplug, let device sleep for a minute and then test using https://play.google.com/store/apps/details?id=com.bvalosek.cpuspy to see if you now achieve deep sleep.

So far this workaround came to my knowledge from lbcoder within the last ten minutes & I'm successfully achieving deep sleep for the first time on 3.4.

This process may need to be applied sporadically (if/when CPU Spy shows no deep sleep .) I've rebooted since performing this workaround and deep sleep once again failed. Re-performed this workaround & deep sleep returns - So I would do this upon every reboot at least.

---------- Post added at 05:25 PM ---------- Previous post was at 05:17 PM ----------

On a separate note.

The devs have asked as many of us as possible to try the new #202 build ==> http://ls.infernix.net/jenkins/job/apexq/202/

They request specific feedback on the below:

A) Graphics corruption, especially on Homescreen Background

B) Random Reboots - possibly related to screen wakeup or video display.

Good Luck :thumbup:
[Samsung Galaxy S Relay 4G] :
Charging/deep sleep has been fixed as of build 204. What I need now are logs of any random reboots/crashes you have. As long as you don't do a battery pull that information will be stored in /proc/last_kmsg

So if your system is locked/hung, instead of doing a battery pull, hold down the power key for 10 seconds and it should reset.
[Samsung Galaxy S Relay 4G] :
Bug list: wifi crashes when using bluetooth and wifi at the same time

Camera does not switch from front camera video recording to still images without crashing

You tell me
[Samsung Galaxy S Relay 4G] Jason78729:
Just got back from vacation and installed the 7-6-2013 build. No issues so far.
[Samsung Galaxy S Relay 4G] :
Here's an updated status on development:

Cyanogenmod is reviewing our application to get added to the d2 kernel. We're very close to stable and they may be waiting on that. Our code is already sitting in d2-common and noobnl is maintaining the apexq repo personally until it is added. We still have our own kernel repo for development.

Wifi and BT don't play well together with this kernel. There is a version mismatch with the WCNSS firmware. If your bluetooth audio is skipping, you can try build 99 on my test branch on our jenkins server. It has very smooth bt but still does not play well with wifi. I hope you have an unlimited data plan if you're going to stream Pandora.

(tldr version, you can't have stable bt and wifi at the same time....yet)

If I ever get around to it I'll implement gamma correction like d2 has. All the code's there, I just have to make it work for us ;p

MHL, wifi direct, other stuff like that: very low priority, we will get to it but I'm told that stuff doesn't work very well on our stock either. The drivers may very well be broken, in which case fixing it will only be that much harder.

stevenclower: I have not forgotten about your headset on boot bug. :)

Soon we will introduce something called adaptive voltage scaling. It is very similar to undervolting, except it is automatic and is actually not considered a hack (ie we will be able to use it in official Cyanogenmod). Unfortunately it doesn't work on everyone's phone. Turns out Qualcomm does something informally called "CPU binning" which means they test CPUs after manufacture and assign them grades. The grades are slow, nominal, fast, and faster. As far as we can tell, the Relay only has slow and nominal. Once we get the code in place to properly determine which processor a phone has, we can turn AVS on. This means if you have a "slow" phone, it won't undervolt much, if at all. If you have a nominal phone, you can expect significant battery life savings.

Survey: Open a command prompt, su, and then type "cat /proc/cmdline" and post the value you get for sec_pvs. Once I get a few responses I'll post which ones are slow phones and which are nominal. And we may even discover a phone which is fast :)
[Samsung Galaxy S Relay 4G] Xenobio:
Mine = 0. Is that slow? Sigh.
[Samsung Galaxy S Relay 4G] John5788:
sec_pvs=0
[Samsung Galaxy S Relay 4G] Jason78729:
Sec_pvs=0. Getting force closes and freezes on switching between camera and video modes if I try to change flash modes on video. What logs do u need? Only happens in video. Also want to start trying to make builds, do u have a local manifest that's recommended or should I use apexq repositories. Great news whether my phone uses avs or not. I've compiled a few governors but is it beneficial to work on porting a hotplug supporting cpu such as galaxy s3 pegasusq to our kernel repository. Id like to work on little tweaks like that if u think its worthwhile. You're awesome nard and d2 devs, etc. Thanks for the great. You've earned my fave dev these past few months.
[Samsung Galaxy S Relay 4G] Kueber:
sec_pvs=0
[Samsung Galaxy S Relay 4G] gtmaster303:
sec_pvs=0

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] gee one:
sec_pvs=0xfafa
[Samsung Galaxy S Relay 4G] misteropinion:
sec_pvs=0

Also, I am still having some issues with car chargers (which mostly behave using the apple usb protocol, I think), will try and codify that further.

I'm loving how well everything works, though.
[Samsung Galaxy S Relay 4G] gtmaster303:
Didn't an xda user debunk undervolting concluding it doesn't really save battery?

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] :
Our current build manifest is at https://github.com/TeamApexQ/hudson/blob/cm-10.1/cm-10.1.xml

Used to be on our wiki but we've fallen behind in updating it.

There is much room for improvement for new kernels, governors, mpdecision replacements etc. Feel free to work on those items, don't forget to share your kernels with the rest of us (yes, you can compile your own kernel and the post it for everyone!)

I don't need logs, I can confirm the bugs with the video camera and car chargers. Seems like we just went through this lol.
[Samsung Galaxy S Relay 4G] :
Undervolting per se is terrible. User adjustable undervolting is better. Having the phone automatically undervolt itself, with official Qualcomm code is even better. We've confirmed it works wonderfully on battery life. Unfortunately it undervolts some people's phones too much and causes them to reboot.

So, if your sec_pvs is 0, your phone can be undervolted (who knows, we may even be able to push past the official numbers a bit). If your phone is 0xfafa the voltage reduction will be smaller, if any. We will release the patch once we are sure it works on everyone's phones. One of our devs unfortunately has a 0xfafa phone and it looks like a few other people do as well. We will probably ask for testers to make sure everything's stable when the time comes.
[Samsung Galaxy S Relay 4G] janejunx:
sec_pvs=0.

Yeehaw.