yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Interesting...so you think my battery life would be better with your kernel instead of KT? From an objective standpoint and not from a dev standpoint please! :P -- I'm gonna change my frequencies to 135-1350 and try using interactive as my CPU1 governer instead of PegasusQ and see how that fares for me..

But if you really think dumping KT and going to your kernel with the ROM is the best move, I can give it a shot again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I would recommend it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
By removing the underclock I meant raising your minimum to 378 or 384. Underclocking can just waste your battery and some phones can't handle it. And it's not even just my kernel, I just always saw issues with KT kernel, I used to use lean before Quantum came along, so that's what I've been used to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
Getting some random screen wakeups with 2.22 and new modem/bootloader. Never had the problem with any other version. Haven't done any troubleshooting yet, just wanted to report.

Wiped system and both caches before flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbrian27:
Just installed 2.2 yesterday, and it feels much more snappy than previous versions. Although, I'm having an issue receiving MMS and can't figure out why, and I haven't seen it mentioned in any previous pages in the thread. Anyone else having issues? I'm on ATT by the way....

Edit: I've tried deleting and re-adding APN, and was just on the phone with ATT for half an hour because originally I thought it was a network issue, although they tell me it's not
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
Me too - but old modem/bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Does 2.2 have any kernel updates? If so I wanna try flashing the latest kernel and see how battery life is, so maybe I should wait for the newest official release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
Looks like I am having the wake ups as well. Looks to be romdb causing it according to wake lock detector. I'm going to try freezing with Titanium and I'll let you know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
I never defrosted it since it started giving trouble the first time around. Really, if you pay attention here, you really don't need an app to tell you when Pwn has a new release...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aex90832:
Not sure why, but it seems as though the phone will either freeze or reboot when using google play music or youtube.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
Well, considering I clean install on most updates sometimes I forget to freeze it. It ran fine for me on the last two builds. This build (2.22) it's acting up again. Thought I'd share what may be an/the issue for me and others. I do pay attention here - thanks for you assumptions and help though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
DISABLE ROMDB IN APPS.

Since it's not officially released yet, it will keep pinging ROMdb until it finds it's version number.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Freezing ROMdB on test releases has been a consistent thing we needed to do, should really search the thread before posting cause its been said a ton of times... It's just clutter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Romdb isn't listed in apps.

Can I buy a vowel?

We need kluze
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
I apologize for cluttering up the thread. I didn't remember to freeze on test builds and I should have or I should have searched first. I was only trying to help others. Also, I would like to apologize to hytran as I wasn't too polite in response to his post above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
No apology needed. I didn't take it as such.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Man you guys are awesome. Great to see that nobody is cutthroat with eachother... like something else on this forum.

This is why I don't think we'd need a Q&A!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
I deleted Romdb w rootappdelete from the playstore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
You also don't tell people to go away the second someone needs help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Well there's nowhere for them to go cause we don't have a Q&A....but hey Pwn if you don't want it then I'll trash what I made so far, no point in posting it if you aren't gonna endorse it fully :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonv31:
I say it's a good idea.... PWN what you think? A q&a?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Can't imagine who you could possibly be referring to! It's going to be quite a task to figure it out... ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonv31:
Lol MJ!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
HAHHA I love it..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
LOL Nice... At the very least, you'll get your underwear in a knot...

To keep it on topic, just flashed the updated bootloader/modem (thanks to those that posted the link!), a day after flashing 2.22. So far so good, we'll see how it does today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
I tried to update again to v2.22 and I got up to the Round Quantum badge and then I got screen flickers and reboot cycles at the same spot a few times. The one time it did get past and boot, it started optimizing apps and then got stuck optimizing app 5, then went into a reboot frenzy. and that was it. It got stuck with some colorful horizontal lines across the screen and that was the end of the story.

PWN, if I logcat, will that help us determine why the new updates won't work on rev0 even though some say it works on their rev0 (MJ or berry if I'm not mistaken)?

Or should I just give up on the updates?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's an issue with your modem man! I'll fix it up in the next kernel release for you, which I should have out today!

Just got back from my trip and I have work in 3 hours, so I'll see what I can do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
I appreciate it !!!!

Welcome home and no worries, go get some rest :beer:

I can and will wait for you. Besides for some beer (coming your way soon), it's the least I can do for dev/person as amazing as you!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
You guys know I can never just stop working on these things...

If you keep getting hung at the boot screen, just pull out the battery and put it back in.

Like the good ol' blackberry days, right Hytran?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
LMAO I miss doing BPs all day!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
Will 1.62 still fix modem issues even if I'm using new modem that was leaked
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
something is causing the phone to wake.. i wonder if its rom db? i guess i shall delete it. im on 2.22 and quantum 1.62
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Pretty much what we've all been saying... ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Unable to use video chat on hangouts, get fc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I just used it to talk with my friend over H+, what combo are you running?

Is anybody also noticing worse battery life on 1.62? It's much more stable, but it seems like it sucks battery a lot faster than before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
No change even after BP, wouldn't even finish booting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Seems that GPU is stuck at 300...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Read my post! I said to do a battery pull if you got sruck booting.

Also GPU getting pegged at 300 is an issue with every kernel right now besides bms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I figured you knew about it; not a big deal but maybe we could attribute some battery issues to it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Stock kernel and 1.6 didn't worth either. No change in anything else. I'm using it over WiFi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
I don't see much difference in battery life in my usage.

Other than when testing a new release, my phone is rarely unplugged.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Just a quick question regarding to my previous post about the Vine app crash, is there a way in Trickster Mod to force the GPU from going to high and crashing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akitten007:
Just flashed this a couple days ago. Running perfectly, everything smooth. Didn't know butter came in a zip file! Thanks pwncakes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's not because the GPU is running at a high speed, otherwise you would get a crash every time you pulled down your QuickSettings drawer. It's because of the way that the app calls upon the GPU, and it's an issue with the app itself, in conjunction with CM 10.2. Only ROM that may work is AOKP, but even then it may be hit or miss.

If you still want to try, just go to GPU on the right hand side of Trickster, and set the max speed to 300 MHz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Thank you, I'll try it out. I would try Task's AOKP but I've used it before and it's just not my cup of tea plus this is so much better! Oh well, I'll get by somehow lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Try out one of the AOKP's in the Android Development thread, they're a lot smoother and not as in your face as Task's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
In case it was not clear, I did a battery pull.

So the problem might be the GPU issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
That or slap on BMS, my GPU seems to get to 400 but I had random reboots so I'm not sure if they are related.

Is 400 the normal high limit or it it considered overclocked at that speed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
No, the reason it wasn't booting is because the boot up process drastically changed, and the values are changed for the modem start up. The same thing happened to me, and a battery pull, or just holding down the power and letting it restart a little seemed to fix it.

Some people won't even have this issue, so far it's just been us two facing this problem with the boot on this version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
So I guess if anyone else has the boot issue aside from me, I should be glad its you? LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
its not just to two of you, i am also having the issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] freshiem:
Definitely noticing some massive battery drain. Nothing out of the ordinary on GSAM, Bettery Battery Stats that points to anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jacobz1996:
want to revert to 1.9

i was trying to revert back to 1.9 but wen I try to it says fatal error. idk what I am doing wrong :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Did you update to the 4.3 modem/bootloader from the leaked 4.3 TouchWiz?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jacobz1996:
yes i did i used the link that was put on here. i really want to go back to 1.9 can u help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
You either have to:

A) Update binary script to make sure that the modem is included.

B) Install older modem and bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
There's also a nice little surprise in the d2att folder ;)

lots of new features, some which have been requested. I'll fix the RomDb and push an update in a little bit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zapper_master:
I love surprises

That is awesome, thanks PWN. So it looks like its 2.22 and the new kernel. We are so spoiled !!!!

-----sorry to mislead, I was anticipating, should say "Thanks in advance"...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
Where is this folder you speak of?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
No love for canuckians
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Why i am unable to find the surprise in the d2att folder? Nothing is there after v2.20.. Mind sharing the link?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Thankfully I didn't post anything yet!

I need to revert 2 changes in the kernel, but that's it! Otherwise everything has been working perfectly fine so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's more than that, it finally has long press to sleep and the option to change quicksettings tile sizes are now in the builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
Quantum works great on my Bell S3, just don't flash the new radios
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
I'm running fine with 2.22 and 1.6 on Rogers as well. I was moaning about the Lack of hardware driver updates for our radio/modem.

If Rogers actually releases an upgrade to 4.3 I suspect 4.4 will already be published.

Sent from my SAMSUNG-SGH-I747 using Xparent BlueTapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
They seem to work just fine though. My biggest issue is picking a ROM at the moment!

There are basically 3 things I miss when I'm on Quantum. HALO, custom background for notification drawer and network speed indicator. But... usually less features means more stability so that's when I come back to Quantum.

Also, since PWN said that the GPU doesn't go to 400 unless on AOKP, that leaves me even more confused.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] distracto:
pretty new to Quantum and ROMS in general, but did like this feature on a ROM i tried out.Is this a feature that would ever make it into Quantum?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I never said that. I said that it doesn't dip down to lower than 300 Mhz really unless you're on BMS, or (maybe) on AOKP as it is built using different sources.

It hits 400 all the time on our devices. Literally all the time :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
Gimme pwncakes awe yea..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Glas4d:
There is an app in the play store called "Cool Tool". It can display network speeds as well as a bunch of other stuff. Give it a try. I like it more than the network speed indicator on those other roms because it takes up significantly less room.

https://play.google.com/store/apps/details?id=ds.cpuoverlay&hl=en
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aex90832:
So stupid question: Is it preferential to use the leaked UCUEMJ2 modem/bootloader with 2.25, or is it better to use UCDMG2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
Hopefully an update tonight then!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
I got new version available notification through romdb tool and it downloaded 2.25 version. is this latest experimental build ? How come i don't see this on OP . There 2.20 is latest ????

Where do i find details about change log of this 2.25 and is it ok if i do dirty flash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Myself, I'm sticking with MG2 unless/until it becomes necessary to update. I don't mind being on the cutting edge, but I rely on my phone too heavily to be on the bleeding edge. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Hey [MENTION=1683096]PwnCakes193[/MENTION] - the BMS kernel uses the Simple GPU governor by default. Might be something you could add also?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Hurray! 2.25! Thanks for your awesome hard work to make awesome releases, Pwncakes! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
I didn't even see that, thank you.

How did you know about the update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Luck I guess! I went looking for test builds, clicked the wrong folder and voila!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zapper_master:
Looks like surprise time

PWN- so looking in the d2att folder I see 2.25 staring right at me ! Is this the rom and kernel all in one with the 2 tweaks you needed to do ? Haven't flashed it yet, actually just downloading. I do not know how you have any sort of "normal" life with all the time you keep putting in but on behalf of all your faithful followers a serious thank you and gratitude for you keeping us all on the leading edge in development and a build quality that exceeds others.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
Anyone else getting a force close when opening the messaging app?

Never mind, reflashed and all is good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Sorry guys I got caught up with a lot of stuff once I got the updated to work, I'll post a changelog soon, it fixed my battery life finally!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Awesome. Does that mean, the 2.25 build is good to be flashed ?? full wipe needed or dirty flash is ok ???\\

thanx in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zapper_master:
Go ahead and flash. All seems good here!

---------- Post added at 10:27 PM ---------- Previous post was at 10:25 PM ----------

Sorry, should have mentioned I dirty flashed with no issues to this point, just an FYI
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fendulon:
Awesome. So what about the kernel? Should we use Quantum 2.25 and the 1.62 kernel? Or do you have something packaged with 2.25 that is more updated than the 1.62 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zapper_master:
Hey Fen- looks like kernel 1.62+ is built in, this kernel was built in 10-27 when looking in about phone. Hope that helps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
I am going to flash this new ROM without clearing any cache or dalvik. Basically I don't wan to go through setting up each app/data again. And I should be good with that flash ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zapper_master:
That is exactly what I didn't because I was feeling really lazy and didn't want to set anything up again. Actually I have done this the last couple of flashes, no issues before and So far its working great on 2.25.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
The best way to dirty flash (that's what flashing updates without wiping is called) is to wipe /cache, wipe dalvik cache, and format /system BEFORE flashing the update and Gapps. This way, all the previous gunk and unnecessary stuff from the rom is wiped away, but you keep all apps, settings, and other stuff. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
With this approach, I don't lose any of my data ? For example, say Facebook login details and stuff
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Exactly. Wipe cache, Dalvik cache, and system

ONLY

. Do

NOT

wipe data. This will retain all of your data and settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Was it really that hard to find 2.25? LOL There were enough clues and anyone who has been in this thread long enough should know about dev-host...

While everyone was wondering where the update was, I was already downloader #1 :victory:

Great work as always, Pwn. I love dirty flashing early in the morning... :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
I got scared for a second, I flashed, set everything up, rebooted and the phone did non boot, stuck at logo. I did a battery pull, tried to boot again and it finally did but it probably took a good 2 or 3 minutes for the spinning logo to show up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Good to know your **** doesn't stink...

For those that don't know - click on the link in the OP for the ROM, when the page comes up, click on the link labeled "Tommy Tarts" (Pwn's alter ego) or you can click here ==>>http://d-h.st/users/TommyTarts.

It will take you to a list of the files he has on DevHost, including test builds, kernels, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Nope, I've just always believed the following:

"Reading the documentation fully is a prerequisite to getting help for your particular situation. I know it's harsh but you will have to get so far on your own before you can get reasonable help from a list full of busy people. A mailing list is not a tool to speed up your day by being spoon fed." -- Simon White
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I understand where you're coming from, but that kind of hostile "use the search function, you ignorant n00b!" attitude, which is prevalent in many other XDA forum threads, is something we work very hard to keep out of this one. Respectfully, if you can't contribute anything other than a snarky, smart-a** comment when someone asks a question, it's probably best to just hang back and chill. We're trying to keep this a friendly, helpful thread, not one that'll drive users away. Thanks for understanding!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
I disagree. Not sure if you are a mod or dev but regardless it is hard and frustrating to fill a thread with simple and easy to find questions. Something as simple as reading the OP or my personal pet peeve "dirty flashing" which causes problems, is sometimes is hard XDA is definitely full of jerks and I try to be the nice guy that assists others with easier problems. If it is too obvious or simple I will ignore the question entirely simply because, I am where I am today because I tried to learn and figure things out myself. I asked Google and some devs questions but most are Pm's or friends I have that are able to understand me than me.

All I'm trying to say is that cussing and filling this thread with non-sense is ridiculous and not necessary. Yes I know I'm doing it right now but to be honestly I'm responding because you blew up on someone and made him sound like a bad guy when he didn't say anything like what you just said and he is partially right. He could have posted a link to help anyways but the link is in the op. The reason the op did not post for all to see is because it's a test build. Not for the public. In sure he doesn't mind but it's at your own risk. Now thank you for YOUR understanding. Just so you guys know if anyone needs assistance I am always available just send a pm. Simple or complicated I try to help

Crack-Flasher
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
Oh look... Fast Charge! Thanks PWN!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Was I really being hostile? I'm not the one who trotted out the S-word. Did everyone forget what LOL means? And the smilies?

I also don't have a profile picture displaying the finger in front of my face like a certain developer on XDA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
This release is just a super bugfix type of release. I'm at 90 minutes screen on, with 3 hours awake and 12 hours on altogether, I'm only at 53%.

Running stock interactive/row, temp throttle, Z RAM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Sorry, but in point of fact I was calm, reasonable, and polite in my response. I am not the one being hostile here. (And in response to your first question, I've been doing the computing thing for over 30 years, so I think I've more than earned the right to speak from experience.)