Develop Bugs

Ram usage

Hello everyone im getting way to much ram in use causing the phone to lack. If I reboot the running services are minimal and no lack but the running services start to pile up by themselves (example maps and why 2). Can someone compare there usage. Im stock unroot.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

With maps, in location services turn off wireless network locating and only use gps. Maps, when network locating is on, Maps issues crazy amounts ie thousands of kernel wakelocks.
You're not lagging due to RAM you're only using half of your memory.
Sent from my SPH-L900 using Tapatalk 2

It was low when I took the screen shot but I've seen it go up more than 1.2g. I only have about 10 apps install from the market as of now cause I just recently got the phone and planning on rooting.

LaloHigh said:
It was low when I took the screen shot but I've seen it go up more than 1.2g. I only have about 10 apps install from the market as of now cause I just recently got the phone and planning on rooting.
Click to expand...
Click to collapse
You may be using 1.2gb of memory but your note2 has 1.75gb of usable ram. The stock ROM has about 100apks that qualify as bloat. Even at stock my n2 didn't noticeably lag.
Sent from my SPH-L900 using Tapatalk 2

Skripka said:
You may be using 1.2gb of memory but your note2 has 1.75gb of usable ram. The stock ROM has about 100apks that qualify as bloat. Even at stock my n2 didn't noticeably lag.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Yeah theres alot of ram left but my phone starts lacking around 1.2. I just wanted to see if someone is experiencing the same. Guess ill root and remove bloat and see what happens.

LaloHigh said:
Yeah theres alot of ram left but my phone starts lacking around 1.2. I just wanted to see if someone is experiencing the same. Guess ill root and remove bloat and see what happens.
Click to expand...
Click to collapse
Really, I'm stock unrooted since the release date and never experience any lag. I'm hesitant to root not because of no experience is because this phone is the only phone I've used that is super smooth while still rocking stock unroot.

I uninstalled my apps first and see if its one of them.

Performed a factory reset and now the ram looks normal and no lack. Thank you both for the feedback.

[Q] Knox'd up

Saferoot worked very well for me without a hitch. These knox issues are a pain in the [email protected]#. I wish I could get a clear answer that I will void my warranty on a sealed brand new S4 I bought off Swappa from a TMobile Employee who won it in a contest (I SCORED ON THE PRICE - $300 and this leads me to believe I might be able to get a warranty somewhere because it arrived perfectly sealed) had to brag. I've never turned a phone in for warranty before but there is so much Knox BS and *****ing out there it is hard for a noob to decipher if you can safely load a mod by Saferoot - no Knox issue there - Clockworkmod - there goes Knox - then flash your favorite mod to the SD and boot to it. What versions are safe and since I'm begging where is the best Google Mod. IF I LOOK AT THOSE STUPID BALLOONS ANOTHER DAY I'LL POP THEM. IF all I am going to do is trip a flag then up theirs I don't care I've never sent a phone in for repair EVER I take care of them. I read about Safestrap but that appears to be VZW and ATT only. We apparently have a different bootloader but is that bootloader Knox sensitive? I can't figure it out as much as I dig and I'm half way to china. If there is a mod for dummies thread out there that accounts for those of us stupid enough to take the 43 OTA and get Knox'd up...haha I'd contribute gladly to the expert who helped me. Normally I'd just go for it knowing hardbrick is difficult and digging can get rid of a softbrick but knox has me afraid after all the forum banter. Somebody point me to that mod for dummies thread and assure me that even if I trip my knox which it would be nice not to do I will be safe. Also confirm that there will be no workaround like safestrap for us TMO's anytime soon and I'll nuke this puppy as soon as I can reach my USB cord...You will be my new SENSAE

Wow.
Sent from my SGH-M919 using XDA Premium 4 mobile app

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The same methods work from before for rooting/flashing as before.
Here are instructions: http://www.w0lfdroid.com/2013/12/Ho...-and-Root-Samsung-Galaxy-S3-S4-Note2.html?m=1 Once you trip Knox the only bad thing that happens is it says se android not enforcing (or something like that every time you reboot).
Sent from my SGH-M919 using XDA Premium 4 mobile app

Rooting and Knox - don't care about it

I am thinking about getting a Galaxy Note 3.
I am saying up front: I don't care about tripping Knox. All I want to do is root the phone, put the best bootloader on it, and install CM11.
What should I know prior to doing this, and are there any downsides?

ajm786 said:
I am thinking about getting a Galaxy Note 3.
I am saying up front: I don't care about tripping Knox. All I want to do is root the phone, put the best bootloader on it, and install CM11.
What should I know prior to doing this, and are there any downsides?
Click to expand...
Click to collapse
Just do it and don't look back.
Only downside with CM11 (for me atleast) was the fact that sometimes it would feel a bit "glitchy" when scrolling. Also the replacements for s-pen and it's program isn't as easy and smooth to use as the ones that comes with TW.

Rickdaddy said:
Just do it and don't look back.
Only downside with CM11 (for me atleast) was the fact that sometimes it would feel a bit "glitchy" when scrolling. Also the replacements for s-pen and it's program isn't as easy and smooth to use as the ones that comes with TW.
Click to expand...
Click to collapse
You have CM11 currently on your device? If not, what ROM do you recommend?

ajm786 said:
You have CM11 currently on your device? If not, what ROM do you recommend?
Click to expand...
Click to collapse
I ran slimkat for a week on my phone before I switched over to hyperdrive. Slimkat just came out with an update so I may go back to that. Hyperdrive runs smooth for being TW, but my only gripe is that the rom (or TW) requires a whopping 6gb right off the bat whereas slimkat was only a few hundred MB.

Rickdaddy said:
I ran slimkat for a week on my phone before I switched over to hyperdrive. Slimkat just came out with an update so I may go back to that. Hyperdrive runs smooth for being TW, but my only gripe is that the rom (or TW) requires a whopping 6gb right off the bat whereas slimkat was only a few hundred MB.
Click to expand...
Click to collapse
6GB? That's ridiculously hilarious.

ajm786 said:
6GB? That's ridiculously hilarious.
Click to expand...
Click to collapse
maybe I'm wrong, but that's what it shows up under system memory.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

No, I think you're right. That's the Touchwiz OS. I remember people were complaining big time about that. How they bought 16GB versions and only got about half that because the OS takes up so much space.

Thanks for the input everyone. I bought the phone last night. It should be here by the weekend, and I'll start toying with it.

Good luck on your beast phone

Exchanged devices - bootloops and other issues

Please can a mod sticky this - please record any issues with recall exchanged devices ONLY. Thanks
Start message with BOOTLOOP or OTHER ISSUE.
It will be interesting to see whether the bootloop issue goes away with exchanges.

I'm only getting my exchanged unit this Sunday. I've been without my Note 7 for four days now, after bootloops bricked my phone. So it bricks before my battery exploded.
I'm keeping a very close eye on this thread.

BozQ said:
I'm only getting my exchanged unit this Sunday. I've been without my Note 7 for four days now, after bootloops bricked my phone. So it bricks before my battery exploded.
I'm keeping a very close eye on this thread.
Click to expand...
Click to collapse
I'm suspecting other issues may be present...I really hope not though. The damage that would do to Samsung...

Bad performance could be related to battery problems. I own N7 exynox and had no problem with the device. Now I'm waiting for the replace phone.
Sent from my SM-N920C using XDA-Developers mobile app

I think all those problems are battery related

Scheduled for an exchange on the morning of 17 Sep. Hopefully I'll have nothing to report here. Fingers crossed.

Well the first problem I've found...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cannot access s health or Samsung secure folder apparently caused by unauthorised software. No root. Just installed all apps that were on the previous note 7. Any ideas appreciated. I've emailed Samsung
Sent from my SM-N930F using Tapatalk

bonerp said:
Well the first problem I've found...?
?
Cannot access s health or Samsung secure folder apparently caused by unauthorised software. No root. Just installed all apps that were on the previous note 7. Any ideas appreciated. I've emailed Samsung
Click to expand...
Click to collapse
Some people have suggested plugging it into smart switch via pc or mac and running an initialisation and firmware recovery. Saw someone suggest it could be some battery testing software that Samsung have used before shipping and not taken back off. So a reinstallation should sort it. I can't verify personally as I'm STILL awaiting a replacement device but there's a few people with your issue it seems

Trying it now thanks
Sent from my SM-N920C using Tapatalk

http://forum.xda-developers.com/showpost.php?p=68690963&postcount=1860
Smart swirch suggestion
Sent from my Tab S using XDA Labs

Update from Verizon

I got this message to update my phone. I am gonna call verizon and tell them to stop sending me stupid messages like this.
Anyone else get this text from verizon?
I have updates blocked on my S8+
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I am still running Build AQGL and reading all the negative posts on here about the last few updates. I think I will just stay on this build. Still gonna call the big V and be put on the do not ever bother list.
It's funny they try to scare you into updating your phone. I have never ever had an issue with calling out.

well good luck not being able to make calls to certain devices. I can't understand why you wouldn't want to be informed of OS issues like this. suit yourself.
Sent from my Galaxy S8+ using XDA Labs

diet.tampon said:
well good luck not being able to make calls to certain devices. I can't understand why you wouldn't want to be informed of OS issues like this. suit yourself.
Sent from my Galaxy S8+ using XDA Labs
Click to expand...
Click to collapse
Funny I don't have issues... If I did I would just go back to using my rooted Moto X Pure anyway or the Note 4. I always have a few phones to use on standby.
Plus there are alot of negitive posts about the updates and people wanting to flash back so why take the update. I don't see a reason.
Don't try to fix what's not broke. So far my S8+ is doing well other than we can't unlock the bootloader and root.
I will move on to another device before long that is. :good:
:silly:

Another reason not to update... You do these updates and all Verizon does is put more crap apps on your phone... I would never buy a branded verizon phone again. unlocked is the only way to go.

Then you don't get to ***** when the tides are turned and the unlocked versions are the last ones to get any kind of update on them. Cause lately that's what I've been seeing...the unlocked versions may not have any "carrier bloat" but they are SO FAR behind in updates (Security or OS updates)
kendive said:
Another reason not to update... You do these updates and all Verizon does is put more crap apps on your phone... I would never buy a branded verizon phone again. unlocked is the only way to go.
Click to expand...
Click to collapse

nozzleman_85 said:
Then you don't get to ***** when the tides are turned and the unlocked versions are the last ones to get any kind of update on them. Cause lately that's what I've been seeing...the unlocked versions may not have any "carrier bloat" but they are SO FAR behind in updates (Security or OS updates)
Click to expand...
Click to collapse
Don't really care about updates... If the phone works I leave it alone!!
If I was worried about it I would go back to rooting and do the custom ROM thing again.
.