yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] pyfviperx:
I think your wrong there buddy! I thought google made 30% on the google play store ? In fact most hardware makers lose money with their hardware and make it back with software! (Check out sony and its ps3)
[Samsung Galaxy Nexus] bozzykid:
Google makes very little from the Play Store. Yes, they get a percentage but the costs are pretty high. They make more from people using Google branded services like Gmail, Search, etc. And having Android keeps people using those services since most Android phones pay to license Android (giving access to the Play Store, Gmail, Maps, etc). It is no different than Apple. Apple makes nothing from selling music/video on their app store. They make theirs from the hardware they sell.
[Samsung Galaxy Nexus] kklijer:
voted till 6.x.x.x

but i hope beyond 7:cyclops:
[Samsung Galaxy Nexus] zhuqiusong:
也许要到所有人手中的GN都坏了谷歌估计就不会更新了
[Samsung Galaxy Nexus] Dri94:
Its not goin to be a version number to base on. Once the phone standard for a phone surpasses 2cores and 1gb ram then the phone will be unsupoorted. I could see that haooening in two years as quadcore is now in the high end and som with 2gb. Once it reaches mid-low end itll become standard and OS wilk be built ti use that power
[Samsung Galaxy Nexus] incredulous:
Bottom line is that the N1 doesn't have the hardware needed for ICS or JB to run smoothly. Hardware changes and sometimes you have to drop older devices to make bigger jumps. What you're saying is that you'd rather all Galaxy Nexus owners had slightly inferior devices just so that ICS might not be as hardware intense as it is.

No thanks.
[Samsung Galaxy Nexus] MikeyMike01:
I predict the Nexus S will stay on 4.x and the Galaxy Nexus will stop on 5.x.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] scarcry:
My bet is that the Nexus will get at least 5.x. Even if we're going to get a new nexus come December, I still don't believe that will stop Google from supporting the current Nexus.
[Samsung Galaxy Nexus] lesonal:
We will get the next 3 updates
[Samsung Galaxy Nexus] cwhitney24:
English please per xda rules

sent from my Galaxy Nexus while eating bacon
[Samsung Galaxy Nexus] Alton (Halo 2):
Google is going to stop updating the galaxy nexus in 20never
[Samsung Galaxy Nexus] :
Will be a while yet. Before it completely goes
[Samsung Galaxy Nexus] vetvito:
Nope, the Nexus S will continue getting updates. Google will keep updating it as a reference device for entry level/cheap devices.

⚡sent from my Nexus S ?
[Samsung Galaxy Nexus] blackhand1001:
I have played around with android 4.0 and 4.1 on the sister phone of the nexus one, the incredible. Its pretty obvious why it never recieved ice cream sandwich. Its really slow in ICS because the GPU is really slow. The system partition is also really tiny as well. The nexus s and the galaxy nexus both have massively faster GPUs and CPUs. The galaxy nexus should be supported for quite a long time. Much longer than the original nexus one.
[Samsung Galaxy Nexus] i n f a m o u s:
If the Desire C is capable of running ICS with Sense 4, why shouldn't the Nexus One be capable of running just stock ICS? If single core smartphones are capable of running ICS, quad core at the moment seems really unnecessary.
[Samsung Galaxy Nexus] vetvito:
Check the internals http://m.gsmarena.com/htc_google_nexus_one-3069.php

That's why the N1 isn't running ICS.

⚡sent from my Nexus S ?
[Samsung Galaxy Nexus] i n f a m o u s:
I don't see much of a difference. In fact, the Nexus One has a slight edge over the Desire C with 400MHz.
[Samsung Galaxy Nexus] withbloodskies:
Are you referring to OTA or just root ICS?

Because Nexus One resembles the Droid Incredible, we can run ICS and Jelly Bean, even Sense 4.
[Samsung Galaxy Nexus] vetvito:
512mb ROM vs 4gb of ROM

⚡sent from my Nexus S ?
[Samsung Galaxy Nexus] i n f a m o u s:
The 4GB of memory they're referring to is for storage use. The Nexus has 4GB of storage too.
[Samsung Galaxy Nexus] blankit:
Honestly since this phone is a dual core and a pretty capable phone it should support anything they throw at it so I'm hoping they will continue to give us upgrades
[Samsung Galaxy Nexus] nhizzat:
After 18 months is when they'll stop, so mid-2013.
[Samsung Galaxy Nexus] vetvito:
No, its for the actual ROM and internal phone storage.

⚡sent from my Nexus S ?
[Samsung Galaxy Nexus] msavic6:
The nexus s has support for how many months now? Has to be getting close to 18 months
[Samsung Galaxy Nexus] Lesicnik1:
Unless I fail at basic math, August 22nd was its 20th month.
[Samsung Galaxy Nexus] blackhand1001:
The desire c only has to render 480x320. The GPU is more more than capable of that in ICS/jellybean. It also has a much larger ROM partition. The GPU in the nexus one chokes when doing 2d rendering in ICS. I have used it, the old cm7 software rendering was much better on this device. It also has a very small ROM partition. Combine that with the fact that the desire c has a newer snapdragon even if the cpu is clocked lower.

The Gpu in the nexus s and galaxy nexus is just so much faster than the one in the nexus one. Its not even funny how much of a difference there is.
[Samsung Galaxy Nexus] :
Just accept it. It will get dropped in mid to late 2013
[Samsung Galaxy Nexus] kc_exactly:
Seems like Sprint has already dropped it.....
[Samsung Galaxy Nexus] Zeinzu:
How do you figure? Just cause they haven't gotten an update out yet?

Sent from my Stock AOSP Android 4.1.1 Galaxy Nexus.
[Samsung Galaxy Nexus] lhkjohn:
They already stopped Support for the VZW Nexus, no? Shameful that we haven't even received official JB, but the GS3 is already set to get it

Tapatalkin' from my Eclipsed jelly bean GNEX
[Samsung Galaxy Nexus] donsh00tmesanta:
nexus s got JB if that happened I see GNEX getting the L android as well
[Samsung Galaxy Nexus] Zeinzu:
Ok, where are people getting this? Didn't an official leak just surface within the last week? And isn't the Verizon Nexus showing support for AOSP?

Sent from my Stock AOSP Android 4.1.1 Galaxy Nexus.
[Samsung Galaxy Nexus] oldblue910:
Yes, you're correct. People never truly understood what that whole mess was about, and it's done nothing but fuel blatant falsehoods.

The removal of support for certain CDMA devices in AOSP has absolutely nothing whatsoever to do with OTA updates and official support from Google, carriers, or the OEMs who make the devices. AOSP and OTA updates are two completely different universes. The only reason the VZW Gnex takes so much longer to get the updates than the GSM model does is because Google has to submit all OTA updates to Verizon for testing and approval before they can roll it out. You want to have a device on the best cell network in America, that's the baggage that comes with it. Sucks, yeah, but that's how it is. The Verizon Xoom has the same problem. The WiFi-only variant always gets updates first because it doesn't have to go through VZW testing and approval. Same scenario with the Sprint Nexus S 4G.

The VZW Galaxy Nexus (and the VZW Xoom and Sprint Nexus S 4G) were all removed from "official support" in AOSP only. The reason for this was that Google didn't have a license to distribute the CDMA binaries. Even though those devices weren't officially supported in AOSP, their kernel source was still there and updated with every new AOSP release. The thing was, you couldn't build it with a working radio due to no CDMA binaries. This is why they weren't "officially" supported.

Since that time, Google has secured licenses for the NS4G and VZW Gnex CDMA binaries, so those two devices are once again supported in AOSP. Having those CDMA binaries allow you to build AOSP for those devices AND have a working radio when you're done.

The VZW Xoom still does not have binary licenses, thus its support is still "unofficial". The kernel source is still there, still updated, but you just can't build it and have a working radio. If they ever manage to secure the CDMA license for it, it too will go back to having "official" support.
[Samsung Galaxy Nexus] lhkjohn:
Ok well obviously many people are running leaks, myself included, but it still doesn't change the fact that people who don't root or unlock bootloaders like my wife, among others are still stuck on ICS along with crappy radios, while GSM versions and even non-Nexus devices have had official and leaked JB versions long before VZW GN.

Tapatalkin' from my Eclipsed jelly bean GNEX
[Samsung Galaxy Nexus] Zeinzu:
You said Verizon dropped support. The fact that you're running an official test leak means an update is in process and nearing completion. That kinda blows a huge hole in "Verizon dropped support".

They didn't drop it. They just aren't timely enough for your taste.

Sent from my Stock AOSP Android 4.1.1 Galaxy Nexus.
[Samsung Galaxy Nexus] lhkjohn:
I was being facetious. I'm pretty positive that most people who own these don't actually believe that support is no longer available for their devices, but rather are frustrated that a device that was supposed to "receive updates before anyone else" really doesn't. Not even close.

Tapatalkin' from my Eclipsed jelly bean GNEX
[Samsung Galaxy Nexus] vetvito:
You CDMA guys are funny.

⚡sent from my Nexus S ?
[Android Q&A, Help & Troubleshooting] julioromano:
Hello everyone,

This is a question I've tried to search for an answer since quite some time but never found any so far.

It is happening on a stock HSPA+ Galaxy Nexus with JRO03C 4.1.1 Jelly Bean (bought from US play store).

Please note this behaviour was happening with Ice Cream Sandwich as well.

This happens with more than one app, but this time I'll focus on play.google.com/store/apps/details?id=com.merriamwebster

because it's free and I was able to reproduce this behaviour quickly.

Steps to reproduce:

-Open up Merriam Webster's app

-Write any word in the search box, than tap it in the drop down list that appears (you're brought to the word's dictionary page)

-Wait a few seconds then hit Android's home button on the bottom bar

Now check in Settings -> Apps -> Running:

You will see that the app is not on the running list but is in the cached processes list.

Now go to Developer Tools and enable "Show CPU usage" and hit home to show up the desktop.

You will see that com.merriam.webster is constantly using a small but not negligible percentage of cpu (its green bar is big enough to "highlight" the 'er' in .webster )

The only way to stop this is to stop the cached process in Settings -> Apps -> Running -> Show cached processes

I think the question now comes up by itself: "Aren't cached processes supposed not to use any CPU at all?"

Any info on the matter is appreciated.

Thanks
[Android Q&A, Help & Troubleshooting] VoiD_Dweller:
I think they do but its really minimal and probably doesn't affect performance much at all..
[Android Q&A, Help & Troubleshooting] julioromano:
Such a constant CPU usage, even if small, will prevent CPU from going to its sleep state. No sleep state = battery drain.
[Android Q&A, Help & Troubleshooting] julioromano:
More on the matter...

I've been able to investigate the issue a little further:

Installing the ad-free version of the same app ( play.google.com/store/apps/details?id=com.merriamwebster.premium ) and trying to reproduce the same steps does NOT show the problem. The app is now sitting in the background without chewing CPU time.

The only difference among the 2 apps should be the fact that the paid one lacks the piece of code to retrieve and show the ads (is that made with google ads?).

This would at least point us to a culprit (the ad code).

Still I don't understand why a process which is show as cached by the system is able to use CPU cycles. This should not be possible according to Android OS Documentation.
[Android Q&A, Help & Troubleshooting] kuisma:
The app isn't cached, but running, the time it consumes CPU cycles. It's just that it's only running a fraction of a second at a time, so you don't see it. In between, the app stops itself, rendering a "cached process" until the next time it wakes up, due to an intent restarting the app for a short while again.
[Android Q&A, Help & Troubleshooting] julioromano:
This might be a possible explanation, however installing the ad-free version of the app eliminates this odd behaviour.

Does this mean that some ad library code is buggy and can actually cause CPU hogging?

It makes no sense to wake up a process via intent every fraction of a second when it's UI (and hence the ads) is not displayed at all.
[Android Q&A, Help & Troubleshooting] kuisma:
Not every fraction of a second, just once in a while, enough for the process to stay alive. Also, at a closer look, I see no reason why a cached process shouldn't be able to consume CPU cycles. Just because the Android app terminated, I see nothing that hinders the JVM (DVM) to keep threads going. Not for very long, though, since the ActivityManager loves to slay cached processes. Where in the Android OS Documentation did you find the claims this isn't possible?

Why the ad code behaves this way, you'll have to ask them about. There can me many different reasons. Checking availability of new ads, internal administration, collecting usage statistics ... just to mention a few.
[Android Q&A, Help & Troubleshooting] kuisma:
I agree that "empty process" here means "cached process", but I see no claim that this process must not contain a worker thread, and not consume CPU. "Empty" is in the context of Android app level, i.e. contains no activity or service (no context), not OS level.

But you can always test this quite easy. Create an app with an activity only starting a worker thread, then terminating. See if the worker thread still consumes CPU during its existence as a cached process. I believe it will. Of course, this is an artificial construct, not very useful since it doesn't have any context and can not interact with Android. Still, performing gc, updating singeltons etc, are still very possible tasks for such a worker thread.

Edit: But the ad software maintaining a 5% CPU usage as a background/cached process, I'm quite sure is due to low programming skills. But possible, yes indeed.
[Android Q&A, Help & Troubleshooting] julioromano:
I agree with your line of reasoning, sometime in the coming weeks I'll try to develop a test app and then I'll post my findings here.

What keeps me mumbling on this topic is the general approach to process management on Android:

Android has been thought from the ground up with mobile devices in mind: such devices must put their CPU in the highest possible of its sleep states for as much time as possible not only when the screen is off, but also during regular usage e.g. browsing a web page.

When you read an article on your browser app, you'll want only your display chewing up battery juice and your CPU as close to 0% as possible (unless you're scrolling or zooming, but let's say you're just reading a piece without touching the screen).

With this approach in mind it should be clear that the only processes that should be able to be put into execution by the OS's scheduler are those belonging to categories 1 to 4 ( developer.android.com/guide/components/processes-and-threads.html ).

From an OS perspective, cached processes (category 5) are useful to avoid wasting otherwise empty RAM so that recently used apps can be relaunched as quickly as possible.

But if cached processes are able to use CPU cycles then this is by no means useful to the OS (nor the device), because you'll have no longer needed processes causing your CPU to exit its much beloved sleep state.

In other words:

-Having processes sit in RAM without wasting CPU is ok because it speeds up the system when you reopen those apps and still, those processes will be purged when more RAM is needed (i.e. caching).

-Having processes sit in RAM wasting CPU is not ok because the benefits you gain from caching are offset by the increased battery drain.
[Android Q&A, Help & Troubleshooting] kuisma:
I agree with you. Mostly. :)

I don't really care if an app consumes CPU in the incarnation of a hidden (background) app, or as an cached app waking up by e.g. AlarmMamanger once in a while, or even as a cached app using a worker thread. If I need the app, and the app need the CPU time, so be it. But more often, those are badly written apps, and then I don't care about the details of their inner workings, I just uninstall them ...

Also, even processes sitting in RAM without consuming CPU can be a menace. Take my Xperia for example. In the last version of GB it started so much bloatware, that the limit of 15 hidden tasks was exceeded. But the tasks was sticky, i.e. required to restart in the case of termination. The result was that the phone constantly killed and restarted all the hidden tasks, draining the battery doing ... nothing! Only restarting all the bloatware, time after time after time..!
[Android Q&A, Help & Troubleshooting] julioromano:
Sure! Apps that do stuff useful to us should always be allowed to run ;)

If an app registers for a intent or alarm and then goes to cached processes and we kill it (by removing it form the cached processes list via the settings app), it will be relaunched by the OS whenever an intent or alarm goes off.

Back to the case of our Ad-supported version of the Merriam Webster dictionary app:

When the app is cached (but still using around 5% of cpu) killing its cached process stops the strange behaviour: the app never gets relaunched by the OS (unless I tap again on its icon of course...)!

This means that it's not using CPU because it's been woken up via alarm or intents...

I still don't get it :laugh:
[Android Q&A, Help & Troubleshooting] kuisma:
Ah, but this is another mechanism. When a service in Android initialise, it tells Android whatever it's sticky or not. Android may always terminate any app/service to preserve resources, but the sticky ones, must always be restarted once the starvation ends. This is why some app's can't be killed. They (the processes) get restarted even before an alarm or other intent wakes them (in the sticky case).
[HTC One X] glukosio:
**RUMORS**

HTC One Tab

******************************************************************

3 different versions with 10″, 12″ and 15″

Display Full HD IPS

CPU quad-core 1.7 GHz (Tegra 3 or Snapdragon S4 Pro)

4 GB of RAM and 32 GB of ROM

Main camera 13.1 megapixel with Xenon flash

Front camera 3 megapixel FullHD video

WiFI, 3G, NFC

microSD slot

Beats Audio and PlayStation certificate

10 hours autonomy of battery

policarbonate cover

Android 4.1 Jelly Bean with Sense 4.1

*******************************************************************

it's just a rumor, but who knows, maybe at IFA in Berlin we'll see some tablets from taiwan company :D

would you buy it?:D

**********************

(source: hdblog.it)
[HTC One X] kryptoner:
So how is this related to one x general? :D:D

Sent from my HTC One X
[HTC One X] sumeshd:
It's a concept and not real..

Those specs are just mediocre..

No tab today and not even in next year will have or want or need 4gb of ram..even computers today work just fine with 2gb..

So its just a concept and its not happening..
[HTC One X] *elmo*:
Looks great :D:thumbup:
[HTC One X] glukosio:
windows 8 can have needing this hardware, so maybe we'll se something with win8?
[HTC One X] Maximus78:
Now that's a tab I'd carry around. :good:
[HTC One X] PhoenixFx:
This is NOT a rumor (change the title), it is JUST a concept. People come up with imaginary concept designs and specs all the time. This is just one of them. Go to their Facebook page and you’ll see plenty of such designs for phones and tablets.
[HTC One X] Diamondback:
It's a concept and not some leaked rumour. Apart from that, this is the HOX section so please use the proper forum next time.

Closed.
[Samsung Galaxy Mini] tio12:
[ROM] [GALAXY MINI] [SCORPIOSZ ALPHA 0.1]

For user, sorry if my works is not perfect and have many missbehave inside thid ROM, but i guess i'll make it better from this later, im JUST NEWBIE not NOOBS..

PLEASE APPRECIATE MY WORKS, AND IF LIKE THAT, DONT FORGET TO SAY 'THANKS :)

SCORPIOSZ alpha 0.1 For Galaxy Mini

Changelog :

base on stock rom gingerbread XXKS1 (2.3.5)

zipalign

rooted

busybox

init/d script and tweaks

bravia engine (im not guarantee if it works)

gallery 3d to prevent fc the first galerry app

LauncherPro

ESfile explorer

CWM manager,

dand other things inside this ROM :)

thanks to:

Tuhan Yesus (JESUS CHRIST)

Forum XDA Developers for tips build custom ROm

All people support me,

and YOU

LINK:

For link and screenshot see attachment :)

I added an Update app, check it out...

install method

push zip file into directory of sd card

reboot cwm

wipe data/cache

install zip from sd card

done !!

enjoy it !!
[Samsung Galaxy Mini] YudhiezChitilieaz:
Dont forget Screenshot

CustomRom now jarang use version 2.3.5

NICE WORK :)
[Samsung Galaxy Mini] tio12:
sip om,

btw, how to add shortcut to power menu om?, i dont know?

pliss bimbingannya om :D
[Samsung Galaxy Mini] astrosp4c3:
Sorry man....but why 2.3.5?

2.3.6 is more powerful...;)

For add other trick/function searching you can found more Discussion.......simple search :D
[Samsung Galaxy Mini] MAD_psycho_Zz:
for screenshots just download ux screenshot from playstore :)
[Samsung Galaxy Mini] yackovsky:
Newbie, n00b... same thing...
[Samsung Galaxy Mini] YudhiezChitilieaz:
Do not ignoble or degrading her friend

respect him because he has managed to create a custom rom and not as user who only criticize and just download :)

AMAZING ROMs
[Samsung Galaxy Mini] mustatir:
I agree with u..why the people who juz critize another people work build his rom n post it here..juz critize and download u can do?? Sorry for my english
[Samsung Galaxy Mini] astrosp4c3:
Yes respect...but i'm waiting for reply....why 2.3.5?

2.3.6 work very good and battery problem is fixed and drain is minor....only asking, because i like that in this section there are new developer :)
[Samsung Galaxy Mini] yackovsky:
...and who was criticizing this rom? If you two talking about me, i was just clarifying that noob and newbie is the same thing, no matter how hard you try.
[Samsung Galaxy Mini] tio12:
i wanna make some difference guys, ok thx for answer
[Samsung Galaxy Mini] tio12:
ok, i'll try, thx before
[Samsung Galaxy Mini] YudhiezChitilieaz:
maybe he like 2.3.5
[Samsung Galaxy Mini] hamxxa:
M not neww.....but certanly m noob .....not same... ;P
[Samsung Galaxy Mini] blakmazk:
Novice would be a rather suitable word, since every professional beings his/her journey as a novice :D

peace:)
[Samsung Galaxy Mini] YudhiezChitilieaz:
Squadzone says

Nubie is someone who is not very reliable or smart, but he would seek to know and does not bother anyone else

but

Noob is someone who is not too powerful or too smart and would not seek to know and just made ​​the other person
[Samsung Galaxy Mini] yackovsky:
That's his definition (taken from urban dictionary) for me there's no difference, after all everyone can learn something.
[Samsung Galaxy Mini] tio12:
okay, but please this is how about we would to go up, just not stay on our line and not have a moving,..

I already post the Screenshot guys ...
[Samsung Galaxy Mini] tio12:
correct om :)
[Samsung Galaxy Fit GT 5670] pranesh.rkz:
Is there any way i can change the file system to EXT-4 so that i can get the clockwork mod or can i do something else?

Now mine is RFS file system.... :(

Tried installing some custom roms still my fs is RFS only

Can't able to install CYANOGEN MOD :( It stuck on the boot screen for approx 1 and half hour which is a black screen written "android" on it. bcoz of RFS file system i think

I JUST WANT THE CYANOGEN MOD.

PLEASE HELP ME OUT :( Is thr any other method for converting RFS to EXT 4 file system
[Samsung Galaxy Fit GT 5670] samo_gf:
U should flash cwm by tj_style via Odin , then u can flash any custom rom all of them are ext4
[Samsung Galaxy Fit GT 5670] pranesh.rkz:
I tried all CWM it wont work out :( Getting dis error ''Can't Mount System'' with CWM 5
[Samsung Galaxy Fit GT 5670] samo_gf:
Flash another stock rom
[Samsung Galaxy Fit GT 5670] dheeraj (dhlalit11):
flash cwm boot into it

wipe data and cache

install rom

wipe data and cache

reboot