[ROM] Plutonium,Neodium,Titanium [21916,28244]

[youngpro83]

Originally Posted by kirstein

Gotta agree with you except I don't think 8-5 was any better than 8-7 so no reason to flash back. I think the homescreen glitch along with all the other Sense flashes have more to do with Cookie than 2017. I had the same issues with earlier builds, and I've read about them on other ROMs too.

Yeah Id have to agree with U about not really seeing or feeling any difference. To be honest if there wasnt that strange looking internet slider after first flashing 8-7 than By first glance I could not have seen anything too drastic in changes if any at all. Might have to take Ur advice and just stick to 2017 for now. I got my phone all tweaked out so not flashing back would definitely save me some time.

[CoryNat]

Originally Posted by youngpro83

Yeah Id have to agree with U about not really seeing or feeling any difference. To be honest if there wasnt that strange looking internet slider after first flashing 8-7 than By first glance I could not have seen anything too drastic in changes if any at all. Might have to take Ur advice and just stick to 2017 for now. I got my phone all tweaked out so not flashing back would definitely save me some time.

Hey Young - you still on 2017? I was wondering if you were seeing something I am. If I go to the twitter tab and update, it will update but if I try to scroll to see the new tweets it will sort of bounce back down to the one that was at the top before the update. If I leave the tab and come back, it will have the new tweets on top as you would expect. Re-flashed and it did this from the get go as well.

[bobbyblack]

Have anybody noticed when in landscape, when you get an in-coming call it doesn't show up?

[tryinghard]

Originally Posted by darren.wlsn1

why to #1 yes to #2 no to #3 are you using clean ram or sktools to clean system?

In opera browser there is no X button in IE there is an X button. Why is opera better than IE

I am not using any clean ram or sktools, where do I get them from, how to use them and how often should I use it?

[lw123]

Originally Posted by tryinghard

In opera browser there is no X button in IE there is an X button. Why is opera better than IE

I am not using any clean ram or sktools, where do I get them from, how to use them and how often should I use it?

The X button does not close the program you are running. It just still running at the background.
When you use X button to close IE, IE is still running. No wonder you see the memory usage going up after a while. Even IE has X button, you should still use its menu and select "Exit" to close it.

You can tap the upper left corner of the screen to bring up ArkSwitch and close the programs you do not need. Then you will not have memory problem.

[darren.wlsn1]

Originally Posted by tryinghard

In opera browser there is no X button in IE there is an X button. Why is opera better than IE

I am not using any clean ram or sktools, where do I get them from, how to use them and how often should I use it?

dump ie and use opera and heres clean ram.
http://forum.ppcgeeks.com/showthread.php?t=59447

[GaryMcQ]

Originally Posted by CoryNat

Hey Young - you still on 2017? I was wondering if you were seeing something I am. If I go to the twitter tab and update, it will update but if I try to scroll to see the new tweets it will sort of bounce back down to the one that was at the top before the update. If I leave the tab and come back, it will have the new tweets on top as you would expect. Re-flashed and it did this from the get go as well.

Cory, yes I've noticed that. Just assumed it was something I installed that made it act like that. BUT, if you've re-flashed, I guess it is definitely a bug in the Twitter portion of this build. Gets kind of aggravating to not be able to scroll down and see the latest messages. Really not a great big deal though. I'm not heavily into twittering.

[CoryNat]

Originally Posted by GaryMcQ

Cory, yes I've noticed that. Just assumed it was something I installed that made it act like that. BUT, if you've re-flashed, I guess it is definitely a bug in the Twitter portion of this build. Gets kind of aggravating to not be able to scroll down and see the latest messages. Really not a great big deal though. I'm not heavily into twittering.

Cool. Thanks for checking. I agree. Not a big deal. Just hop to the next tab and come back.

[youngpro83]

Originally Posted by CoryNat

Hey Young - you still on 2017? I was wondering if you were seeing something I am. If I go to the twitter tab and update, it will update but if I try to scroll to see the new tweets it will sort of bounce back down to the one that was at the top before the update. If I leave the tab and come back, it will have the new tweets on top as you would expect. Re-flashed and it did this from the get go as well.

Originally Posted by GaryMcQ

Cory, yes I've noticed that. Just assumed it was something I installed that made it act like that. BUT, if you've re-flashed, I guess it is definitely a bug in the Twitter portion of this build. Gets kind of aggravating to not be able to scroll down and see the latest messages. Really not a great big deal though. I'm not heavily into twittering.

Originally Posted by CoryNat

Cool. Thanks for checking. I agree. Not a big deal. Just hop to the next tab and come back.

Yup I too had this happen the other day. I thought it was just a minor glitch, but I guess its a little bigger than that if all of you are experiencing this. Like CoryNat said just a quick slide over a tab and back fixes it so not a deal breaker for me.

[darren.wlsn1]

twitter issue is on other cooks 2017 also.