yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigdog_nick:
I had a very frustrating day today with my phone running the latest 4/9 update on a fresh install. Not sure really what was going on, but I had initially dirty flashed 4/9 over 4/5 and I was getting constant locks and reboots, I would say about 20-30 reboots in an hour, enough to drain my battery.

So I wiped everything and installed 4/9 fresh, only to get stock on the AOKP bootanimation. I decided to rewipe everything once more, but this time, TWRP gave me an I/O Error /Data/Lost+Found. I could no longer wipe data/system/cache... nothing. I tried to install over it but ended up with the same error.

I just got home from work and after 6 hours of not having my phone, I managed to get it up and running on 4/9. I had to finally format data which wiped everything internally and I'm guessing reformatted my internal to ext4 (or something).

I know it probably has nothing to do with the rom itself, but I just wanted to know if anyone has every come across this? I found a thread on XDA talking about faulty emmc straight from Samsung. I really hope not.

Edit: After about 2 minutes of on time, I had the freeze/reboot problem again. Going to Odin back to stock and see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Mentioned in the TWRP thread. A few found a solution.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] illegalchaos:
Do you still get the duplicate lost+found folders at this point?

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tuse0708:
Graphical Lag When Launching Apps

Is everyone still experiencing the graphical lag when launching apps? I'm coming off a fresh wipe and the 4/9 build. I know that when I disable hardware overlays it fixes it, but I was just wondering if it was something everyone else was doing as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
running smooth here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychemage:
I've tried redownloading (the checksum is fine), updating recovery (TWRP and CWM), and I cannot get 2013-04-09 build to flash. I keep getting

"

assert failed: getprop("ro.product.device") == ...

E:Error in /sdcard/o/aokp_JB_4.2.2...

(Status 7)

"

Suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Some people mentioned that deleting the first line in the update.prop fixed it. Do a little search, I'm sure you'll find it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Try OCing and using Zen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigdog_nick:
I don't. I used Odin to return to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychemage:
Re-reflashing CWM 6.0.3.0 solved it. Thank you though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
Actually your response is incorrect. Your kernel does not appear to have 384 as a usable frequency, 378 is the equivalent I assume, however performance control has the low frequency default set to 384 thus resulting in the actual low frequency of 486. In fact the entire performance control app is jacked. For example using set on boot in voltage settings is broken, force close on boot, and changing any setting in the cpu settings results in the cpu changing the maximum clock speed to whatever it feels like resulting, in my specific case, in the phone getting extremely hot and discharging rapidly. So a better response would be to suggest setting 378 as the low or advising people to not use performance control. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Or. You could simply use whatever app of choice that you would like to set whatever frequencies/voltages you like. This is android and one of the best parts of android is being able to download apps that can add more functionality. I don't recall telling anyone that performance control is solely that app to use when setting clock speed or voltages, so I'm quite unsure what the focus of that app has anything to do with the response you gave. I don't use the app personally, so I wouldn't know or care about it. But anyways. The information you are giving is in all reality incorrect. Clock speeds can be set to whatever the user chooses and that was my response in my original post. If an app (Performance Control) gets in the way of that, it still doesn't void the simple fact that the user CAN choose whatever clock speed they want. So if you could be please at least get your information straight before posting I'm sure other users would appreciate it. 378 is one of the frequencies. I'm unsure what the need to state the obvious is? Source is and has always been available. You should probably take a look at it to avoid these types of posts. ;)

P.S- There are tons of apps that can solve this problem if Performance Control isn't working to a users satisfaction. Voltage Control, Trickster Mod, ect... just to name a few. :D

As I stated. The user can choose what ever clock speed they want. I chose 189. I have 189.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
1. performance control was mentioned because it comes packaged with your rom and is broken but never the less is still packaged with your rom.

2. the user specifically stated "In performance control"

3. I used numerous apps to test the issue in question and 384 is NOT a usable frequency OUT OF THE BOX but PERFORMANCE CONTROL defaults to that frequency OUT OF THE BOX.

Do you not have any helpful bones in your body? haha.

(EDIT) Looking at your picture do you see 384 anywhere???????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) I never said anything about 384. Just because the user was wrong doesn't change the fact of the matter.

2.) Just because an app is packaged with my ROM doesn't void the reality that other apps can be used.

3.) I do have helpful bones. Just read throughout XDA and other teams githubs that I contribute to. It's not a very complicated thing to do.

4.) You quoted a post of mine and are mentioning the users mistakes that were made in HIS post? Drugs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I NEVER SAID 384. You need to learn how to read posts. Look at my source if you need to. There is no 384. I am not the creator of performance control. If you have an issue with it then you need to take it up with the developer of that app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
"Figured I'd ask questions here instead of the development thread and get flamed lol. In performance control the CPU doesn't drop below 486 even if I have 384 chosen. I'm guessing that is correct? Just making sure I wasn't doing something wrong."

that is the users question.

performance control defaults to 384 which makes your actual lowest frequency 486.

are you still confused???

---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------

so a better answer to the user would have been this exactly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Performance control doesn't have anything to do will the actual frequencies of the kernel. Are you confused? Read source if you need to. I can help it if and app that I did not create interferes. The user has a choice.

Either way. Now I'm curious. Other then taking jabs at me in your very first post . What have you contributed here? Are you going to fix this? Have you even looked at source to try and troubleshoot? Because I'm not sure if you've noticed. But you have accomplished nothing here dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Ok guys looks like a reminder is needed. Remember roms posted on XDA are built for the Devs use and how they use their device. Then they decide to share it. Simple as that. They are not required to support, modify or do anything else to the rom to suit other people. IF you have a problem with the rom then by all mean. Build one yourself and I think you will learn a new found repsect for what is done here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
He is not required to answer anything. As for poor support. The devs here are not required to support anything and if they do then they do it their own way. Dont like it then build one yourself and support it how you see fit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
Understood. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
lmao. You must be new here dude. You might not know this. But XDA is actually a site made for developers. Just remind yourself that. You make up probably about 2% of the users that think like you and have these expectations of how support here should work.

The user asked a question. I answered it. Drop it. You're not helping at all here. If your qualm is about "poor support" then you have no business here. Support expectations belong elsewhere. Most likely at someones job.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
I've been here longer than you. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Ok knock it Off. how long you have been here doesnt matter as you seem not to understand what this site is for.

http://xdaforums.com/showpost.php?p=16682226&postcount=2441
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Perfect. Now please get back on topic, which is support for this ROM. ;)

P.S- Just filling you in on a little secret. Instead of coming into this thread and taking your silly little jab at me. You could have actually contributed something very easily. With you being a software developer, I wouldn't think it would be too hard for you to troubleshoot this issue you're seeing. It could've gone a little something like this...

@task650

I noticed that the Performance Control app is screwing with the minimum clock speeds and defaulting to 384Mhz when your kernel doesn't support that frequency. Could you take a look into that?

Just as simple as that. You would've actually contributed something rather then go on a rant about your expectations of something that I do for fun and for free. Or you could've went more in depth and checked out the source, figured out the issue, and then fixed the issue. Then just send me a pull request for it.

Now would be a great time to drop this and just use my example above for future reference if you actually want to help further the development of this ROM and/or help other users out. Thanks. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
It's time for my first "does anybody else" post!

Does anybody else have any issues with their external SD card randomly unmounting itself after waking the phone from sleep? Sometimes a reboot will fix it, other times I have to take the card out and put it back in.

Apparently, you need that AND a lesson on how to read.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
He really doesn't get it. Anyway, just wanted to pop in and say thank you for the latest. Flashed while out on the job site because the equipment never showed up, which means I get to sit on my A$$ and get paid today. :D Have to say you did one hell of a cleanup and System tuner is working perfect for whatever frequency I want. Running buttery smooth at .189->.81 Ghz Wheatley & Row. It's easy to exceed expectations if you don't have any, but your skill for developing is overflowing the cup. ;)

---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------

They always get sorry right before they get banned. :D :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Well. One of the basics would be to at least read and comprehend thread titles. This is clearly a Q & A thread for a ROM that I release. Not a "Critique task650's Responses" thread. So there's and issue you can look at working on. You actually didn't even help the user with the post you first referred to dude. That's just odd. Not only did it not help the user. But you also didn't even give the proper info which is clearly stated in the OP of this thread. So there's another issue you can work on. Read OPs before you post. Saying stuff is doing stuff and stuff isn't working properly doesn't cut it. Pull a log. Show the source that's screwed. Come on dude.

So it's pretty clear and apparent that you aren't here to aid in users issues at all. You are here to criticize my responses? Well that not what this thread is for. If you want to help a user, go for it. If you want to critique my responses go elsewhere as that doesn't belong here. You have totally derailed this thread today. I'm not sure if you've noticed, but you accomplished absolutely nothing here and on top of it you haven't even helped one person. You're not going to change anything here.

I've asked you already to leave. You just can't comprehend the facts of the matter here. I can't help you with that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I haven't had an issues with this personally. But it seems to be a common issue for the device in general. Sdcards seem to get wacky. You could try backing everything up to your computer, formatting the sdcard, and then see if it helps with the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
To Be Helpful

If you have just flashed this rom and haven't touched any settings at all and you are wondering why performance control shows a default low frequency of 384 but an actual low of 486 it's because this kernel does not have 384 as a usable frequency so performance control chooses the next best thing for you, 486. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It works fine for me. :)

P.S- Users should always play with settings to see what works best for their device with a custom kernel. Default values are usually not what works best for the majority. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KennyG123:
Thread cleaned

There will be no arguing in this thread

If you are not answering or asking a question please leave

Thank you for your cooperation

Friendly Neighborhood Moderator
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeyl:
Question: How am I going to get my flash fix now that the dev thread is closed? :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Just because I close the thread doesn't stop that download links from working. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeyl:
Nice!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Thanks Task. I really hope this isn't a sign that my phone is killing my card.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
I've had SD cards on my DSLR go whack on me so it could just be the card degrading. Not necessarily the phone's doing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uzii305:
Okay I have a question I use LMT launcher and I want to know how to find the camera app. When I look for the app it shows the gallery. Is there any way to find the camera app by itself and be able to pull it up in LMT launcher?? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please go ask any questions or concerns with LMT in that apps thread. Gallery is the camera and vice versa.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] inkblaze:
Hi Task, your rom is fantastic but I wanted to find out if it's possible to get a version of your kernel without the underwear splash screen. It's cute to see it the first time around but if there's a no fuss underwear less splash screen for those of us who concede that pink unicorns are for little girls and tighty whiteys are for little choir boys it would be awesome to have that option to disable that splash.

Otherwise, thanks again for the great work. It's tip top. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No. It's a 2 second splash screen. You need to use a different kernel if the 2 seconds is just too much for you guys to handle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xLordNitro:
So I'm getting this RILJ wake lock, do I need to flash a new modem? Suggestions on how to fix this? I think it's the cause of my battery issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Seeing your signal, it would makes sense to flash another modem. Perhaps the newer one for your carrier (look in the modem thread).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xLordNitro:
Currently on the newest one. My university building just has bad signal. But I'll refresh the modem.

---------- Post added at 09:59 AM ---------- Previous post was at 09:48 AM ----------

It's still occurring, would perhaps an ODIN back to stock rooted and then installing everything again help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Did you try other modems? That'd be the first thing to do.

Also, I expect you did a clean flash (factory reset, wipe cache/dalvik/system).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xLordNitro:
Yeah just flashed one of the older modems, seems okay. And yes I did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xLordNitro:


Should I be concerned by this? I'm seriously considering an ODIN back to rooted stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
Hey guys...

I tried searching for this but its kinda hard to explain... So I have this problem where when I am on the web, or on ifunny, or even flipboard and I view a page, the screen shifts to something that was displayed a few seconds back (in the past) and then comes back to the "current" (present) screen. Anyone have this problem and found a fix? Also I saw the screen flickering FAQ but I didnt think this was a screen flicker problem. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Try searching "screen jump" - that will get some hits. It has been a problem, was supposedly resolved, but only Task would know that for sure...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
okay, well I checked for the screen jump and only 2 other people had this issue and they were on kt kernal whereas I am on underwear. I have been dirty flashing for a while now so maybe thats the issue. Ill do a nice fresh install and report back later!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You answered your own question. You haven't follow the installation instructions for this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qbnb:
Actually, I have this issue as well, even after a very clean flash (followed the instructions to the letter) and while on the underwear kernel. It doesn't bother me all that much though, so the only reason I brought it up was because I saw your post. Please let me know if a clean flash resolves the issue for you.

Also, I've tried searching but perhaps I haven't found the right terms; I was wondering why the SMS notification disappears after I open the Messaging app (but not each individual message) and if there was any way to disable that action so that the notification remains until I've read/responded to every message?

Additionally, is it possible to grab a previous/newer version of the stock email app as the one included in the gapps package doesn't seem to have pinch-to-zoom or a fit text to page option (like the Gmail app). I figure it's a reach but I might as well ask while I'm at it. <b>edit:</b> I'm able to zoom in, but not zoom out far enough to fit the email into the window.

Otherwise this is a truly fantastic ROM! Thanks for all the hard work Task and to everyone who makes these threads so informative and entertaining. :thumbup:

Sent from space using xda app-developers app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ralphie1267:
I only get phantom scroll when viewing apps. But it's very minimal..it seems to happen less with this new release I'm gunna let it settle in since I just flashed new release last night.. Of course i fully wiped.. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
What CPU temp are you guys getting while idle?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
~36c

But since all phones are different, it could be higher or lower on your side. Also, OC/UV can affect it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Great yea same. First two cycles I would get up close to 50 shortly after I started using the device. Third cycle I'm below 40 during moderate use. Guess it just had to settle in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
......

I'm just going to leave these ...... here. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kjportie:
Is anyone having trouble with their SD card? Its giving me a blank SD card notification but when I put into another phone or my computer it works totally fine.

---------- Post added at 10:50 AM ---------- Previous post was at 10:45 AM ----------

Never mind I'm just gonna reformat its my 64gb card not working in this phone properly. My 16gb worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
revert to a prior release for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cucumbersmell:
Trickster Mod Set on Boot Not Setting on Boot

Trickster Mod was just added as a system app in today's build, but I'll definitely take this to the Trickster Mod section if needed. Not that it's relevant to the S3, but it works flawlessly with my N7.

My phone doesn't like the highest frequency. I set the Max to 1512 MHz in Trickster Mod, but it won't stick on reboot. I get the "Set on boot completed" notification each time, but it still shows 1674 MHz being used in both Trickster Mod and CPU Spy Plus.

Has anyone else been able to get their setting to stick after rebooting?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Been using this app for quite a while now and haven't seen this occur. I would fully wipe and try again. Or at least clear data for the app, reboot, and test it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cucumbersmell:
Thanks, Task. Not sure what the deal is with my phone. On your previous release I had tried Trickster Mod, Performance Control, SystemTuner and got the same result of it just not sticking after a reboot. I have clean flashed, fresh installed, cleared all app data and still no joy. : (

Really appreciate your work! And definitely not a deal breaker. KT's kernel boots at 1512 MHz max, so I've been using it for now. But, I'll keep trying your kernel on each release to see what results I get. : )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No problem. This kernel also boots at 1512 Max. So I'm not really sure why you would be having the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cucumbersmell:
For some reason mine default boots at a 1600ish max on your kernel. Even after a clean flash. Maybe it's time for me to wipe it all and start from the ground up. Thanks, again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
I hope you are referring to wiping the internal and external memory areas, or stock and back lol. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geauxlsu83:
Help?!

OK this is getting ridiculous... task.. i've looked at the faq, the readme...searched google numerous times. took advice from ppl that pm'd me.. and it still doesn't work.. man when i had the gs2 i never had this problem. just please help someone.. im getting quite frustrated :( i've edited the update script in . zip file i've flashed the latest cwm , it still won't install. i must be missing something
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) I do help people.

2.) Why haven't you tried flashing a different ROM? That should've been one of your first steps in the troubleshooting process.

3.) If you've edited the updater-script and updated your recovery and it still doesn't work then you should probably just use a different ROM. I hear cyanogenmod is good.