yashsingh1/xdaforums huggingface dataset:
[Android Software Development] njarun:
how much battery does this drain? is there any mod to decrease battery drain while phone is in sleep state?
[Android Software Development] Maneth:
Hi !

Specific to my LG Optimus Black P970 (French Froyo stock) : when I reboot it, this app couldn't be open, and I must do a forced close.

Is anyone have this issue ?
[Android Software Development] SaphirX:
hi,

downloaded and used it for some time now. really useful but I have got a question regarding the duration under the summary tab...

what does duration mean? I know what the word duration mean but what does it mean in relation to the time and so on?

For example:

2-5% 44 (13h:37min) 1337 xD

what does the time behind 44 mean?
[Android Software Development] BlackRatVN:
Nice application and it works well - Thanks!

Sent from my Xperia Neo using Forum Runner
[Android Software Development] avss:
It's been a couple of day's. Maybe you missed it. So here's it again....
[Android Software Development] ihavenick:
mine is %19-13/h is that normal?
[Eee Pad Transformer Q&A, Help & Troubleshooting] Pwnography6:
Hi so im having a strange problem with my asus transformer tf101 . I rooted my tab yesterday no probs at all using the vipermod method. Then today I downloaded all the files needed to flash to the latest revolver ROM . Set everything up and put my tab in APX mode.

But every time I hit the .bat to start the flash It runs for a second then shuts down the window and disconnects my tab from APX. Im sure iv just missed a minor detail but its got me pretty frustrated.

So I turn to the forums has anyone got any idea what went wrong.?

BIT More INFO....I currently am waiting on my sd card so I cant flash that way and I am attempting this on a windows computer. Thanks!
[Eee Pad Transformer Q&A, Help & Troubleshooting] baseballfanz:
What is the serial number of your TF? Not all are able to use nvflash.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Pwnography6:
ok so i got a SD card and rom manger still cant seem to get cwm installed or revolver . NVflash seems to just disconnect the usb when I start it . I found my serial number it's BCOKAS130761.

Im assuming by the looks of it thats a B70? As I said in previous post I am successfully rooted with full superuser support just can seem to get anything else working.
[Eee Pad Transformer Q&A, Help & Troubleshooting] baseballfanz:
ROM manager doesn't really work on the tf.

To get cwm use this

http://xdaforums.com/showthread.php?p=22359727

As for your serial number, your BCO is not nvflash compatible.

You have sbk v2.
[Wildfire Q&A, Help & Troubleshooting] Scratch0805:
Pull the status bar down, there should be a option to switch on disk mode.
[Wildfire Q&A, Help & Troubleshooting] heavy_metal_man:
reply

+1 thats the way to do it;)
[Wildfire Q&A, Help & Troubleshooting] calvinhara:
Check with Titanium Back Up to see if you have an app named "Connect to PC". I did uninstall the app once and could not switch to disk mode. Have to reinstall the app. Luckily that I have the app backed up by Titanium.
[LG Optimus Black] REAPER1992:
HI all actually i wanted to know how to make costom rom for our lg ob using our pc [windows or ubuntu what ever] i just wanted to make costom rom like zues 2.2 or nova v9..... or ginger bread 20n..................

i hope any developers out there can give steps to make roms ..........................
[LG Optimus Black] N00BY0815:
Well since you dont wanna program, I think the Xda Kitchen http://xdaforums.com/showthread.php?t=633246 should be good for you ;) You can also simply unpack a Rom like Zeus, modify some things, repack, sign it (use search) and test it. Pls test your ROMs first, before you post them ;)
[LG Optimus Black] redy2006:
Have you learn to read documentation? There's hundreds of them out there. We can't just explain it to you here, as they already documented/published out there. But AFAIK there's no specific docs for P970 devices, that's why you should use your brain of knowledge and your instinct to develop it... ;)
[LG Optimus Black] REAPER1992:
hey N00BY0815 it says that LG Optimus Black (unconfirmed)

has any one tryed it before on lg ob

and yes thanks for replying fast
[LG Optimus Black] N00BY0815:
I tried it, but I wont work, since updater-script get changed and so the flashing procedure doesnt work. And I dont have time to try, since I will have a lot of tests, the following weeks... but after that, I'll try if I can make it ;)

Just give it a try ;) But for the first, start cooking, not deving, which is mainly about changing basic stuff, like taking redy's repack, add some build.prop tweaks, maybe fix some settings, ... Then repack and sign the zip. Test it if it works, and keep on refining ;) Thats the easiest way i think :)
[LG Optimus Black] REAPER1992:
well i was thinking more like using our lg ob rom in virtual machine [vm ware software] or something...... i know it is a bit stupid thought.................. well atleast we will very carefull if we use that kinda method
[Galaxy S II Q&A, Help & Troubleshooting] marci4na:
HI!

is there a way to turn on the screen when for example arrive a whatsapp msg?

it works for sms in my s2...so the screen turn on in lock screen...

but it stays off when i receive any other notification (whatsapp, facebook, mail...)

is there a way??

thanks!
[Samsung Galaxy Nexus] josteink:
From techeye:

http://news.techeye.net/mobile/google-abandons-cdma?

CDMA is marked "archived, for reference only"

http://code.google.com/android/nexus/images.html

I guess that finally nails the Verizon Galaxy Nexus as a carrier-phone. Next time buy a truly free & open device (i.e. GSM) :p

Seriously though. This Galaxy Nexus launch and follow-up has to be the messiest thing I've ever since Google set its foot into. From launch, to providing international release-dates, to US promotion, to handling updates, to releasing buggy updates, to pulling them, to general PR.

It's all been a big ****ing mess.

Is this the sign of the start of the end of the Nexus program or what? Or is leaving closed CDMA networks and carriers behind actually a sign of a new, better start?

Discuss.
[Samsung Galaxy Nexus] matt30:
Welcome to last week.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] josteink:
Edit: Rootzwiki seems to have something more to offer than the techeye article.

http://rootzwiki.com/_/articles/ann...dma-galaxy-nexus-will-continue-to-update-r374

Still not crystal clear, and definitely falls under my definition of messy PR.

The rootzwiki even has an update, because Google has messed up its correcting response and needs to correct itself, again.
[Samsung Galaxy Nexus] masully84:
Yeah this is old news. Plus the 4.0.4 update is out for the VZW. What's it like beating a dead horse lol?

Sent from my Gummy Nexus
[Samsung Galaxy Nexus] matt30:
http://xdaforums.com/showthread.php?t=1479199

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Haesslich:
Funny thing is how the 'abandoned' device is getting more frequent updates than e officially supported device. We still don't have 4.0.3 officially yet (the last relapse is officially the Nexus S one), and 4.0.4 is CDMA only.

Welcome to last week, BTW. ;)
[Samsung Galaxy Nexus] adrynalyne:
Omg. Not only does it keep being reposted but by people who don't even understand what's going on and say things like " next time buy a truly free and open device".

Sent from my 'closed' 4.0.4 CDMA Galaxy Nexus.
[Samsung Galaxy Nexus] josteink:
Hm. Should have searched the forum better it seems. I didn't find it before posting. Anyway. The conclusion from that thread still seems to be incredibly messy.

Can anyone tell WTH it now does mean to be a "Nexus" device? Ever since the release of the Galaxy Nexus and its "evil" CDMA counter-pair, that definition seems to have been in a flux.
[Samsung Galaxy Nexus] josteink:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.

How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.

So yeah, feels good, open and free :p
[Samsung Galaxy Nexus] masully84:
http://androinica.com/2012/02/cdma-...l-dev-support-updates-still-come-from-google/

Sent from my Gummy Nexus
[Samsung Galaxy Nexus] adrynalyne:
Don't talk about what you do not comprehend. That is the most ignorant thing I have heard in a long time.

I too can build 4.0.3 for CDMA. So go get educated.
[Samsung Galaxy Nexus] josteink:
Good. Reading Google's various statements on the matters it seems like you cannot though, so excuse me for thinking otherwise.

So again. Yay for Google's handling of this :p
[Samsung Galaxy Nexus] matt30:
If my understanding is correct, you need to build 4.0.3 with the proprietary files (binaries) contained in a working cdma build of the device (what Google has called "apks"). Since those files are closed source, they cannot be included in AOSP.

Why those cdma files are closed source is a mystery. It could be for legal reasons or it could be because of the way cdma networks communicate with devices (requiring them to have a signature from the carrier embedded in them).

Sent via Galaxy Nexus
[Samsung Galaxy Nexus] adrynalyne:
The proprietaries are all closed source. GSM included. Looks like Google couldn't obtain a license to distribute is the whole problem. Hence they also axed the factory images, because it was a form of redistribution of them as well.
[Samsung Galaxy Nexus] matt30:
And cmda (and I guess the proprietary software) is owned by a working group of several different telecom companies.

Sent via Galaxy Nexus
[Samsung Galaxy Nexus] sahakiap:
how does what feel? unless you are just into foreign flags you will never use a cdma phone from verizon. looking at this logically you are either seeking attention or trolling. either way its sort of pathetic but i guess its winter over there and you havent much to do.
[Samsung Galaxy Nexus] josteink:
At first I was trying to get some news out. And discussion about Google's general handling of the Nexus-line this time around and how it hasn't exactly been "optimal".

But I guess that got lost in everyone picking up on the snide remark rather than the rest of the comment.
[Samsung Galaxy Nexus] efrant:
Thanks for posting josteink. I hadn't seen it before either. Not sure why everyone is getting their feathers ruffled when you clearly put a smiley face beside the comment. And besides, those that are posting saying it is old news keep bumping the thread... :)
[Samsung Galaxy Nexus] mutelight:
There is no source release of 4.0.4 yet but I have been on 4.0.3 since the day I got my phone.

How does it feel? It feels great to have 32GB of space on my phone and get an average 20Mbps downstream. (At times reaching 40Mbps+) :cool:
[Samsung Galaxy Nexus] sirkirby:
This isn't old news at all and it is a big deal. A lot of people got screwed here by both Google and Verizon. Not having official AOSP support for developer nexus phone is unacceptable. If there were code distribution issues, then Google should have worked that out way before the official launch. I'm still holding out hope that this will be resolved, but at this point i'd settle for just getting out of my contract and moving over to the GSM variant.

On a related note, I wish CDMA would just fade away into a bad memory.
[Samsung Galaxy Nexus] mutelight:
http://www.droid-life.com/2012/02/03/google-issues-statement-regarding-cdma-nexus-devices/

Why people are getting all "the sky is falling" over this is beyond me.

Does it suck that if you are getting OTA updates, it can be held up by the carrier? Sure but like almost everyone on these boards, we have a plethora of ROMs to choose from and devs will continue to support CDMA.
[Samsung Galaxy Nexus] adrynalyne:
They are being that way because they understand the implications and their own explanation is not technically sound.
[Samsung Galaxy Nexus] AllGamer:
CDMA has always been a bad technogoly for cell phones to begin with, i'm surprised CDMA survived that long

it was never popular outside USA, some carriers & conutries only uses it as a last resort to get a foot hold into a countries comm market

but that was only back then when carriers were not allowed to use something that another carrier had, that's a thing of the past now in days
[Samsung Galaxy Nexus] masully84:
This is easily my favorite post in this thread lol. Thanks for the laugh.

Sent from my Gummy Nexus
[Samsung Galaxy Nexus] efrant:
Really? I was under the impression that CDMA is the better technology and the reason that GSM is more widespread is that it had "first mover advantage". Is HSPA not based on the same principles as CDMA?
[Samsung Galaxy Nexus] adrynalyne:
How many times has GSM been hacked? Anyone?

;)
[Samsung Galaxy Nexus] LionAR10:
CDMA has really strict licensing requirements (Qualcomm) and GSM is an open standard. Newer GSM modes (like UMTS and up) have some CDMA style tech in them, but pure CDMA is expensive. It's technically better, but for reasons that often don't matter.
[Samsung Galaxy Nexus] Bruce lee roy:
I think this is still a valid topic for discussion. The fact that there are so many different interpretations of the released information, proves that paying customers are unclear as to on the consequences of this most recent change.

To my understanding, which may be incorrect, the most recent change indicate that it will before difficult for developers to dev from the source. This is because the release of source for select devices (non GSM), will be more dependant on the carriers and not Google. This means that the previous process of Google releasing sending out the ota source immediately after the ota will likely change. What will happen instead is something more akin to what happens with non nexus phones - devs wait for an update which may never happen and if it does, source drops at a time determined by the carrier (within a required time frame) with the possibility that the carrier decide not include portions of the source.

Coming from a galaxy s phone (tmobile variant) I hope that I am wrong in my assessment of the information. For me, A major selling point for getting a nexus device was not the availability of otas but rather the ease in which devs could take source from scratch and build something awesome.
[Samsung Galaxy Nexus] bplewis24:
Here is the comment that has made the most sense to me thus far:

http://www.droid-life.com/2012/02/0...-in-aosp-like-the-galaxy-nexus/#disqus_thread

Whether that is technically 100% accurate or not, I'm not sure. But given the massive amounts of press releases, blog postings and reader comments that I've read today, it seems the most logical parsing of all of the information.

Brandon
[Samsung Galaxy Nexus] josteink:
CDMA (the modulation) may be technically more sophisticated than than TDMA (the modulation) which basic GSM is based on. This does in theory give CDMA-based networks the benefit of higher network utilization and better overall capacity.

But then, GSM evolved to be more than just voice. You got EDGE, GPRS, UMTS, HSPA+, LTE etc. LTE, which contrary to popular belief, does not depend on a base CDMA network and was actually deployed in GSM networks first.

The higher speeds which the CDMA/Verison Nexus owners here cite comes not from CDMA, but from LTE. So if you ignore the data-speed argument as moot (because that is LTE's doing), what you are left with is judging the practical merits of CDMA vs GSM.

GSM provides you with universal, mandated network mobility and portability and a universal standard which every phone and provider has to abide by. This gives you as a user massive network effects, local and worldwide. With both providers and equipment.

CDMA provides you with a theoretically higher network utilization for last generation data networks. The only benefit this provides is for carriers using CDMA technology where they may save some money with regard to deployment and maintenance of cellphone-towers.

How CDMA is deployed in the US, this comes at the cost of no end-user network mobility, no network effects and a complete carrier-controlled ecosystem where the carrier controls all access and equipment. CDMA leaves carriers free to **** both phone vendors and end-users.

Does the theoretical network-capacity benefits of last-generation data-network traffic on CDMA-networks make it better than the practical benefits provided by all generations of GSM?

I really don't think that is hard to answer at all. CDMA is a dinosaur. It really needs to die.
[Samsung Galaxy Nexus] efrant:
@josteink I was actually getting more at what you talked about in the first three paragraphs of your post: that the modulation is better, and because of that, the data side of GSM has evolved to use it. UMTS and HSPA (i.e., data for GSM) are also based on a modulation similar to CDMA, no? (Although I believe LTE is different.) While WCDMA is not CDMA, it is similar modulation, no? It is certainty not TDMA. I am not saying that UMTS and HSPA depend on a base CDMA network - that is untrue - they are deployed on GSM networks, not CDMA networks. But the underlying modulation is based on code-division, not time-division, no?
[Samsung Galaxy Nexus] zerozoneice:
https://groups.google.com/group/android-contrib/msg/c8152d677f05e3e1

"For various technical reasons, recent CDMA Android devices implement core telephony functionality in .apk files provided in binary form by the

carriers."

Go screw your carriers, not Google on this one folks...
[Samsung Galaxy Nexus] josteink:
Indeed. Hence why I mentioned that a pure CDMA network only provided theoretical benefits for a last-generation (GSM era EDGE/GPRS) data-network.
[Samsung Galaxy Nexus] tannor:
I think what I am pisst off with google is the deception, if they had known this was an issue to begin with and it sounds like they did know but was hoping to fix it, they should never have advertised on their developer page to begin with.

I only bought my phone at beginning of Jan and they had it listed at the time.

I still probably would have bought it, but I am worried that cdma custom AOSP roms are going to get a lot harder down the road as updates come out.
[Samsung Galaxy Nexus] matt30:
Can we get some thread merging? People are going around in circles.

Sent via Galaxy Nexus
[Samsung Galaxy Nexus] Character Zero:
I will ask this question here also. How did they not run into this 10 months ago when they released the Sprint Nexus S? Does that not have the same issue since they also took it off the page? But its been out for a while and had at least 1 update to GB right? So did they just provide the proprietaries but now for some reason its an issue to have them on the site, is LTE really the issue? I wonder since the 4.0.4 LTE radio update was only a patch in the OTA, as opposed to the CDMA radio being the full radio, maybe the carriers only provided a LTE patch to Google and they decided they can't put a patch on the site for a radio. While we can patch the radio and pull the full file, maybe Google isn't allowed to do that. So I am pointing to LTE and whoever controls the releasing of that radio and I guess even the apks that interface with that radio, as the problem here, but I could be wrong.
[Samsung Galaxy Nexus] zerozoneice:
i think the US carriers are worried about not being able to bundle stuff like CarrierIQ anymore :) Opensource my ass....
[Samsung Galaxy Nexus] adrynalyne:
Stupid comment is stupid.
[Samsung Galaxy Nexus] k.electron:
firstly this seems to be blowing out of proportion. im pretty sure what they mean here is that the carriers get a chance to merge in their apks if any. not that google has "abandoned" it.

also, who cares, the phones still have one click unlockable bootloaders. just unlock and go get a aosp built rom. done. that being said lte is way faster than gsm, so just go get ur lte device if you can.
[Samsung Galaxy Nexus] adrynalyne:
LOL, I like your no big deal attitude because you can use aosp...yet the changes they are discussing is regarding aosp. Support has been yanked for aosp. It was not just a documentation change. There were changes on the repo as well. I haven't check in the last 24 hours, but I have been told that Toro was yanked from the device repo sync. That and CDMA builds will no longer be tested with aosp.

Dcoumentation change only? No. A change we can overcome? Probably. A change that may slow down CDMA progress on aosp if proprietaries required change drastically? Definitely.
[Samsung Galaxy Nexus] miketoasty:
I have been reading a lot into this so let me clear up some things for you. First off the Developers at Google were unaware that they would not be able to get to distribute the CDMA proprietary blobs's. One of the Google Dev's came out and said that basically their legal team dropped the ball and was unable to obtain what they promised they would. So basically, blame Google's legal team.

The Nexus S also had this problem but it was not stated until now because when building the GB for the Nexus S they must not have needed to update the radio's which means that they would not have needed to push any new radio software, or new radio's were built by the correct party's and merged by Samsung to Android source and then pushed, therefor Google never needed to address the closed source crap.

Basically right now, at least how I understand it after reading a couple hours of information, and of course this could all be wrong but.... For the CDMA GNexus there are specific proprietary blobs's that host the CDMA radio files. Now these cannot be specifically distributed by Google in a open source form (Right there making our phone a non AOSP phone as it HAS to have some closed source files), so thus the images being pulled. So, for our dev's to build new source they need to take the latest source and merge our (Closed source) CDMA proprietary blobs's. Done, well sort of. When Google updates it's software our radio's may not be 100% compatible, now we have one of two options. Hope the dev's make the correct modifications to fix the proprietary blobs's or wait for our carriers to push the OTA of that OS. Also, when creating a new ROM (OTA) it takes a while to push out when you need to add sense or motoblur, with our devices all that needs to be done is new signed proprietary blobs's that work correctly with the OS just need to be merged with current source and pushed, which in my eyes "SHOULD" take a lot less time (Look's at the Galaxy S with ICS, which only took a couple weeks to release).

Initially this isn't much of a problem, I don't believe that we will have a problem until Jelly Bean comes out, if even then, depending on what changes that Google makes.

Finally, anyone coming from the Thunderbolt know's that these fixes are possible, they just take time and make some things a little wonky.

Finally, finally, so yes Google did blindside us slightly, and yes we are no longer an AOSP device, and yes that sucks, but no the sky is not falling, we are not going to be forever left out of Jelly Bean goodness, things just may take more time than GSM due to some complications.

Finally, finally, finally, everyone who seems annoyed by this check out this link: http://bit.ly/wMfcMp, which is what happens when you use open sourced radio files.
[Samsung Galaxy Nexus] adrynalyne:
Let's just call them CDMA proprietary blobs because the apks are not for CDMA at all. In fact, they aren't even for cdma functions.

Also, GSM props are closed source as well.
[Samsung Galaxy Nexus] miketoasty:
Thank's, fixed my post.
[Samsung Galaxy Nexus] reuthermonkey:
Let's not confuse CDMA2000 the standard with the CDMA radio interface. UMTS/HSPA has nothing to do with the CDMA2000 closed standard. UMTS/HSPA does use a WCDMA radio interface.

Countless. It's one of the reasons GSM operators have primarily been using UMTS for the past 5 years.

As for the reason CDMA devices are problematic for google - possibly CDMA licensing issues with Qualcomm that aren't necessary for GSM devices?