yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] blueskidder:
(this is my first post so im sorry if i posted in the wrong place or asked in the wrong area)

A couple nights ago i flashed a 4.2.2 P.A.C man ROM ( dont get me wrong i love this ROM thanks to the devs ) but ever since i installed this ROM my phone has been heating up to temperatures like 96 degrees Fahrenheit this kills my battery really fast, i just use basic apps like stock messaging app or apollo music player :'(

(today i unplugged my phone from the charger at around 7:25 AM and by 10:00 AM i was down to about 23% battery life) along with this sometimes my phone crashes ( i believe its from the heat) and i have to pull my battery pack out and reinsert it to boot up the phone.

I love this ROM but this is irritating me :( i cant get 5 hours out of my battery :( i already tried a new SIII battery and the same thing happened.

If someone could please help me or atleast guide me somewhere that would help me i would appreciate it i used to love listening to music on my way home but now i cant :/
[T-Mobile, Samsung Galaxy SIII] KingKostas:
try to reflash the rom with full wipe . if that doesnt work use another rom in the meantime. i would of said use another battery, but you stated the problem continued. i think its the rom
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Sounds like something may be keeping the CPU at 100%. Let's see some stats?
[T-Mobile, Samsung Galaxy SIII] mt3g:
Wouldn't go as far as the rom is the issue as the person using the rom (not a shot at you op) we need more details on what you did to install and what you came from and stuff. Might be your boot loader needs to be updated. Might be a kernel issue. Like I said can't immediately run and blame roms, even though its possible. Download betterbatterystats and report battery life with detailed info.

T-Mobile SGS III
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: roms

The pacman rom is an CM10/AOSP/AOKP or a ported rom.

It is an excellent rom for developers and for those people who like to do a lot of experimentation with their phones.

What I would suggest is to flash a custom rom like "Wicked V10", "Darthstalker X2" or the "STOCKORAMA" V2 rom.

Any custom roms based on Samsung Touchwiz Jellybean 4.1.1 or 4.1.2 would be a very excellent choice.

These custom roms are feature packed with themes, addons, mods and other extras. - Check em out!

Here are the links to those roms in case you decide to flash one of them.

STOCKORAMA | VERSION 2 | Aroma | Multi-Carrier | Multi-Window

WICKED™ v10 | AROMA | Rom Control | Full Customization

DARTHSTALKER ☆ | VERSION X2 | Aroma | Multi-Carrier | Customizable

Good luck!
[T-Mobile, Samsung Galaxy SIII] mt3g:
Please stop posting that its only a good rom for developers... I used aosp type builds steady for 5 months except for when I worked in a certain job site and had to have WiFi calling, I restored right away as soon as possible. It might not be 100% stable but its good for a very very large community including some friends of mine who know close to nothing about phones or modding and devving. Those other ROMs are just opinion (not bad ones at all) and you aren't helping the op at all with his question that he asked.

T-Mobile SGS III
[T-Mobile, Samsung Galaxy SIII] blueskidder:
I came from Jedi invasion 3.0 i flashed everything back to stock jellybean for tmobile then i re-rooted and flashed P.A.C man (4.2.2) using clockwork also flashed Gapps 20130301 as well.

what did you need me to screenshot on betterbatterystats ?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Start with everything. We will go from there. Let it idle for as long as possible so the stats are accurate.
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: posting

I would think that posting our own opinions or suggestions in these forums can be helpful and are within the policies and

guidelines in these xda forums. (your opinions or suggestions are just as welcome and valid as mine or anyone elses) LOL
[T-Mobile, Samsung Galaxy SIII] chrisram88:
Let us see those Better battery stats bro
[T-Mobile, Samsung Galaxy SIII] blueskidder:
This attachment right? or is it something else? it usually uses 15-30% battery power per hour depending what i use, i dont usually use applications a whole lot. Like today all i used was stock texting apollo and snapped a couple of pictures my phone was dead before my 4th period class :(
[T-Mobile, Samsung Galaxy SIII] chrisram88:
Now screenshot the cpu states. Your deep sleep slot should be the biggest one. If not a rogue app is keeping your phone awake.
[T-Mobile, Samsung Galaxy SIII] blueskidder:
this one right?
[T-Mobile, Samsung Galaxy SIII] blueskidder:
yeah my phone just burned me at 102 Fahrenheit anyone have any roms similair to pac man?
[T-Mobile, Samsung Galaxy SIII] chrisram88:
Select other then select cpu states. From unplugged or boot.
[T-Mobile, Samsung Galaxy SIII] blueskidder:
:( this sucks a minute ago it jumped to 102 degrees i could barely hold the back
[T-Mobile, Samsung Galaxy SIII] mt3g:
Mine gets to 106 its not rare lol, you have a rouge app some where eating battery I'm guessing. Cant tell much with the screens you provided. I suggest a factory reset and don't restore apps.
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: Too hot

I was going to say the same thing but you beat me to it! LOL
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Let me see partial and kernel wakelocks.
[T-Mobile, Samsung Galaxy SIII] chrisram88:
Yea like the rest say the temp is no biggie but that 38x mhz slot shows an app constantly running. It's 50% of your on time.
[Nook Touch General] theronkinator:
Basically the nook has seen a big price cut in the UK, and has subsequently sold a lot, it looks like US stock has leaked into the UK and are been shipped out by major retailers, it's just happened in the last few days so not much atm.

Any ideas how to change it? Even when I log in with my Nook UK account it still brings up the US store, whilst this is fine for me, I got it as a gift and need the UK store for them.

So far I've tried getting the UK firmware and putting it on the nook, the nook does nothing visibly but it is deleting the firmware file so it's seeing it, but won't install it.

Any ideas?
[Nook Touch General] theronkinator:
I sorted it from this thread:

http://xdaforums.com/showthread.php?t=2273758

I imagine an official fix will be released as it seems fairly widespread.
[Nook Touch General] theronkinator:
I've created my own guide that lets you switch between UK And USA software, it's here:

https://sites.google.com/site/xcdguides/nook/nookregion

Credits to the original sources at the bottom.
[Nook Touch General] borzowsky:
this is very interesting, and if I have a US account, will I be able to activate my nook in UK? What does it change in the UK version?

My nook is US but i read that with UK I can have Italian, is it true? :laugh:
[Nook Touch General] theronkinator:
My Nook UK account worked when my nook was running on the US software so I imagine it will work the other way round.

I've compared the two regions software.

There's very little difference, just the store region, build.prop (with region settings), and the screensavers as the UK ones are multilingual.

And yes the UK nook includes Italian as a language option.
[Nook Touch General] borzowsky:
ok so it's worth the upgrade to have italian ;)

thank you very much!
[Nook Touch General] borzowsky:
for your info i just changed my nook from US to UK and now it's all in italian, thank you very much! :)
[Nook Touch General] jakalman:
@ theronkinator thanks a bunch mate and very simple process

cheers :highfive:
[Nook Touch General] WAIFWAIF:
It is still possible to change from US to UK? I read that B&N is no longer available.

I want to change it just to have some dictionaries
[Nook Touch General] nmyshkin:
Here's what you want: https://sites.google.com/site/xcdguides/nook/nookregion

But be aware that it has been reported (long ago) that by-passing registration (or Oobe) results in rapid battery drain during normal use.
[Samsung Galaxy Nexus] sogrady:
Those of you have been waiting for the Galaxy Nexus to gain support for Bluetooth Low Energy - to enable syncing with devices like the Fitbit Flex or Polar heart monitor - can stop. While BLE support will arrive in the next drop of Android, it will - according to one of the folks on the Android team - apparently not be making its way to the Nexus. See the comment here:

https://plus.google.com/116110604589325140832/posts/VsF1BcaFY1g

Looks like the best bet, then, is either custom ROMs or upgrading to a Nexus 4 or later.
[Samsung Galaxy Nexus] msavic6:
Great... Another nail in the coffin against the galaxy nexus, time to start looking for a suitable replacement.
[Samsung Galaxy Nexus] fireknuckles:
This question is fairly general as I'm considering the remaining life of my device. Does anyone have an idea, once API level 18 is released, is it possible or probable that we will get BLE ported over in a ROM? Should I hold out hope for my Nexus or move on? BLE is something I've been looking forward to for a while.
[Samsung Galaxy Nexus] madd0g:
Lol, that's just ****ing weak.
[Samsung Galaxy Nexus] Mach3.2:
I don't think it's that simple, it will require some work to port it over, I remember that a google employee mentioned in the keynote that BLE requires a new stack. Correct me if i'm wrong, i'm kinda sleepy when i watched the keynote..
[Samsung Galaxy Nexus] madd0g:
Yeah, which will come with next Android release. They just don't want to bother with the drivers for GN, which is bull****.
[Samsung Galaxy Nexus] beekay201:
And we're still missing camera and GPS binaries.

Sent from my Nexus
[Samsung Galaxy Nexus] madd0g:
Missing where?
[Samsung Galaxy Nexus] Ashtrix:
Nexus Prime's hardware has become old now...dual core TI A9 and the BT3 ,with the TI gone there would be no proper binaries :p

N4 or Next nexus would be better upgrade option :good: !
[Samsung Galaxy Nexus] beekay201:
Official AOSP license

https://developers.google.com/android/nexus/drivers

Sent from my Nexus
[Samsung Galaxy Nexus] madd0g:
No one cares, since they get them from the stock build.
[Samsung Galaxy Nexus] CommanderROR:
So, now that Android 4.3 is out, what are the chances of getting BLE ported from another device with the same BT chip?
[Samsung Galaxy Nexus] joedeveloper:
I hope so. It's disappointing that Google is already starting to abandon what was their flagship phone just a year ago.
[Samsung Galaxy Nexus] beekay201:
If someone were to track down the people who are providing ROMs with the all binaries included, even the ones that are not licensed to us by Google and manufacturers, there would be no 100% complete ROMs.
[Samsung Galaxy Nexus] Gbcue:
So no 100% confirmation yet of people who have gotten the update today?
[Samsung Galaxy Nexus] 7Bit:
I already got 4.3 on my GNex, I can confirm that nothing changed in the Bluetooth settings screen. But I don't know if you can see BLE support in the interface somewhere or is it only under the hood?
[Samsung Galaxy Nexus] Ashutos1997:
http://www.androidauthority.com/galaxy-nexus-passes-bluetooth-android-4-3-224336/
[Samsung Galaxy Nexus] joedeveloper:
I'm unsure if you're saying it will get it or won't.

They just recertified BT 3.0 for it. If you go to https://www.bluetooth.org/tpg/listings.cfm and top in GT-I9250 in the search box you'll notice that it says it as for 3.0 not 4.0.

If you put in the model LG-E960 (nexus 4) and search you'll notice that it was for 4.0.
[Samsung Galaxy Nexus] Ashutos1997:
so will gnex support BLE ?
[Samsung Galaxy Nexus] madd0g:
It doesn't have it, they would certify for 4.0 if it would. Only way (unofficial at least) would be to work with with similar binaries from a 4.0 certified device, if it's possible.

It sucks ass, but I guess it was more of a business decision then a engineering one. Personally I don't see much point in having a Nexus anyway, so this decision kinda sealed that I'll look around for the next phone.
[Samsung Galaxy Nexus] andQlimax:
I think 4.3.x is the latest major version of android that we will get..I don't see any possibility that google will spend resources to make 5.0 work for our gnex
[Samsung Galaxy Nexus] Judge584:
I think Google is going nuts regarding Nexus updates.

Nexus are normally the most supported regarding rom update but they fail to compete with Apple on this area which is a shame.

Galaxy Nexus is only 21 months old... so what is the problem ?

Bluetooth 4.0 not on Nexus even if Bluetooth chip have support for it ? This is bad, this is nuts,this is evil ;)
[Samsung Galaxy Nexus] andQlimax:
the problem is that they don't want to continue to support old hardwares (GPU mainly) spending lot of development resources for a 21 months old phone, which is a lot in modern technology..
[Samsung Galaxy Nexus] Judge584:
Again, while i will certainly never buying an Iphone, we have to be honest : Apple is fully supporting devices older than just 21 months... so they do have no excuses : they just fail.
[Samsung Galaxy Nexus] andQlimax:
they just have 1 phone for each year..and don't have to think to other hardwares...

android its a big projects, it have to work on a lot of gpu, cpu, etc....you don't have idea how that is complex, every single line of code you add to support a 21 months old gpu, can break all other things in some particular conditions impossible to always be reproducible
[Samsung Galaxy Nexus] Mach3.2:
This is just being self centered, Google is not a charity organisation, every decision is for profit, directly or indirectly, it's just not economical to support a old device, look at the big picture.

Apple have a different way of doing business which enables them to update the software of older device, and so to speak, Google and Apple are different type of organisation, you can't do a comparison between them, Google make most of it's revenue off ads, Apple don't.

And I would love to have the latest updates, but that's just unlikely.

Beamed from my Grouper
[Samsung Galaxy Nexus] Judge584:
I see your point but still think you're wrong.

IOS 6 is supported on 4 smartphone devices, Android 4.3 on only 2 smartphone devices : doesn't sound more complicated.

And for other cpu, gpu that we can find in oem smartphones, most of the work is done by OEM themselves, not Google.
[Samsung Galaxy Nexus] AntonyStark:
Apple update devices and leave out features on older ones, which is just What Google just did and its the point of the thread.....
[Samsung Galaxy Nexus] Judge584:
Your comparison is not fair : Apple is leaving out new features for old devices because they do not have enough processing power for them and because implementing them on too old devices could ruin user experience.

This is exactly what Google have done with the Nexus S when they decided that photosphere would be to slow on it, and i think they were right.

I have no problem with that, this is normal.

Now about bluetooth 4.0 it is certainly not the same case : there is no problem about processing power, and the internal chip is already 4.0 compatible so... do you see my point ?

EDIT : and i want to add that of course devices cannot be supported forever in such dynamic market, but a full 24 months support on all Nexus devices should not be a dream.
[Samsung Galaxy Nexus] msavic6:
Exactly, while apple supports older devices, they remove practically all the new features and in the case od the 3GS and the iPhone 4, they destroyed the user exerperience.

I would rather not have the latest update and have a working device than be given the latest and greatest and have it completely destroy the usability of the device.

Personally, if you ask me, Google should have never released 4.2.2 as it did more harm than good to the Galaxy Nexus, I cant speak for 4.3 since im on vacation and the nexus is at home.
[Samsung Galaxy Nexus] madd0g:
As I was thinking a bit, the only thing that seems kinda logical for not including the BT 4.0 from engineering perspective would be, that it needs 3.4 kernel. Why I think this ? N7 is on 3.1.* kernel and also didn't get BT 4.0 support, while newer devices on 3.4 have. It could take them more work to bring the all the drivers work with 3.4 just for BT sake.
[Samsung Galaxy Nexus] 7Bit:
I think you are right with this theory. It makes sense...
[Samsung Galaxy Nexus] Judge584:
You will like it, project butter is back ;) It is verry noticeable on the application launcher, and when using web browser.
[Samsung Galaxy Nexus] HTF:
Has anyone actually tested a GNex running 4.3 to see if BLE works or not? I would but not really sure how to check if BLE is supported or not as I don't have any BLE devices.
[Samsung Galaxy Nexus] CommanderROR:
Same here. No BT4.0 test devices. Would be silly to buy them and then find oit they don't work.

But google qctually saod Gnex won't get it back in May...
[Samsung Galaxy Nexus] Judge584:
See the link in my first post : 4.3 only bring Bluetooth 3.0 to galaxy nexus.

Low energy support require Bluetooth 4.0.

---------- Post added at 02:41 PM ---------- Previous post was at 01:57 PM ----------

I doubt it, but not sure : ubuntu 11.04 was build with bluetooth ble support, and this was with 2.6.38 kernel.
[Samsung Galaxy Nexus] meghjagad007:
i also heard opengl es 3.0 is not for our phone..is that true?
[Samsung Galaxy Nexus] matteventu:
Yes, PowerVR SGX540 doesn't support them.
[Samsung Galaxy Nexus] talz13:
I'd be happy if I stop getting bluetooth disconnects with my heart rate monitor when running. That would make it worthwhile to me!
[Samsung Galaxy Nexus] Rufufu:
It is maybe a little off topic, but if we haven't BT LE and open GL 3.0, do the memory leaks issue has been solved? And what about the wifi drops?
[Samsung Galaxy Nexus] Judge584:
Never had any WiFi disconnection at home, but a lot at work with 4.2.2

Starting today with 4.3 : no more problems at work!!!

But this is still too early to be sure, I have to do further tests to be sure problem has been solved.
[Samsung Galaxy Nexus] zmattmanz:
This sucks. It's a big pain to not be able to sync my Fitbit Flex with my Nexus.
[Samsung Galaxy Nexus] Prasad:
Really disheartened on the part of us not receiving openGL 3.0
[Samsung Galaxy Nexus] GldRush98:
It is getting a little tiresome buying Nexus devices and STILL getting **cked over.

Nexus One: "Oh sorry, we screwed up the design and there isn't enough internal memory. You're stuck on 2.3.3"

Galaxy Nexus: "Oh sorry, we screwed up the bluetooth certification and picked a ****ty processory, You can't use any of the cool 4.3 features"

Nexus 7: "Oh sorry, we screwed up the internal memory and it bogs down to unusable levels after 70% is used"

Seriously Google? I was looking forward to a refreshed Nexus 10, but at this point I just don't know if I trust the Nexus line.
[Samsung Galaxy Nexus] Mach3.2:
There are at least 30 instance related to memory leak in the change log, so you can assume they are fixed, or at least partially fixed..

Beamed from my Maguro.

---------- Post added at 11:35 PM ---------- Previous post was at 11:35 PM ----------

Our hardware doesn't support it.. Nothing to do with Google.

Beamed from my Maguro.
[Samsung Galaxy Nexus] AntonyStark:
When Did Nexus mean future proof?
[Samsung Galaxy Nexus] Mach3.2:
OMAP flash is awesome.

Not sure if there is any similar tools out there for other devices.

Beamed from my Maguro.
[Samsung Galaxy Nexus] GldRush98:
None of those are future proof problems.

They're design problems.

Nexus One: Give it more than 256mb internal storage (this phone came out when 16gb and 32gb iPhones were common-place). Seriously. Not hard.

Galaxy Nexus: It has BT 4.0 hardware, why on earth would you not certify it as such?

Nexus 7: Did anyone even run ANY tests on the memory on this thing? It is atrocious.

All of these issues could have been handled/corrected BEFORE the devices hit the mass market.
[Samsung Galaxy Nexus] zmattmanz:
I had the N10 and it was constantly rebooting, freezing and had white screen flashes. IMO that product was terrible. Generally speaking, the Gnex and Nexus 7 were great products.
[Samsung Galaxy Nexus] joedeveloper:
I'm right there with you. The GNex isn't even 2 years old. And it's receiving watered down updates. I can understand hardware limitations but that isn't the case for BT 4.0 coming to it... which is annoying
[Samsung Galaxy Nexus] GldRush98:
I'm starting to think Google is a big believer in: http://en.wikipedia.org/wiki/Planned_obsolescence
[Samsung Galaxy Nexus] matteventu:
Sincerly I don't care about Bluetooth 4.0 LE, OpenGL ES 3.0, and others... Galaxy Nexus come out with BT 3.0 so for me is ok.

What bothers me is that they no more work for optimizing what they yet have! Not introducing new features (of course is better, but not needed), but simply make perfect AS BEFORE (with 4.1.2) the system!

Why do CRT animation lags? Why panning a zoomed photo in the Gallery is laggy? Why the UI is incoerent (Honeycomb was a lot more beautiful from this point of view) ?
[Samsung Galaxy Nexus] Judge584:
I do not experience this problem since 4.3, but I flash it with factory image, no upgrade or backup.

Perhaps you should try this way... Of course it's more time consuming, but bad things often appears when upgrading an os regardless of platform used ( PC, Apple smartphones and android smartphones.)
[Samsung Galaxy Nexus] matteventu:
I yet installed 4.3 with factory image.

I mean not the panning, but when you "throw" a photo while zoomed, and the photo goes to the side of the display, the "bounce" animation is not smooth.
[Samsung Galaxy Nexus] Judge584:
Ah yes I can see it now, you're right.
[Samsung Galaxy Nexus] AntonyStark:
The devices would not have been out when they wanted them to be. Your future proof devices are in an alternate universe.
[Samsung Galaxy Nexus] mrgnex:
Well maybe a dev can make bt 4.0 happen for our phone in the future?
[Samsung Galaxy Nexus] CWalkop:
I'd like to bring out a point:

The Galaxy Nexus was built on outdated hardware, power-wise. The GPU was already relatively weak at the time of release. The screen was sharp, the experience was fast and smooth; but the device itself simply didn't have much room for expansion.

Fast forward to the Nexus 4, and we have a class-leading device at a low price point, with an extremely powerful GPU, a great screen (although the same resolution as the Galaxy Nexus), a powerful CPU, and a class-leading 2GB of RAM.

I can see the Nexus 4 getting updates for at least 2 years; maybe even considerably longer. As for the Galaxy Nexus? I'm impressed our device has made it this far. They even IMPROVED performance with 4.3, which is great. If we get KLP with even remotely good performance, I'll be super-happy.

So be glad such a poorly-specced device performs so well, and provides a relatively good experience! The software is fast and the experience is good even with sub-par processing power.
[Samsung Galaxy Nexus] joedeveloper:
I'll probably skip the Nexus 4 though and go for whatever they come out with next. Not a huge fan of LG. The N4 isn't bad spec wise but I don't like the body of the phone. Kind of always been a Samsung and HTC fan...
[Samsung Galaxy Nexus] Plutonium0587:
The AVRCP update is weak too. Only adds track information with no additional controls. Bluetooth quality sucks again too like it did with 4.2.2. Why can we not get descent quality Bluetooth audio
[Samsung Galaxy Nexus] Judge584:
You'll probably be disappointed then, because it is very likely lg who will make the nexus 5, based on the new lg g2:

http://au.ibtimes.com/articles/494748/20130726/lg-exec-leaks-nearing-nexus-5-release.htm
[Samsung Galaxy Nexus] joedeveloper:
I certainly hope not. They usually rotate between manufacturers, so HTC, Samsung, LG... leaves Motorola next or perhaps they will repeat with LG like they did with Samsung... I hope it falls back to HTC or Samsung though.