[Q] first KToon install and no Wifi, ... with intangibles. please advise. - T-Mobile, Samsung Galaxy SIII

Apparently I can't post, its the first time I've tried to and I'm sure I can articulate my question better than many so its agrivating i can't ask you and Persieus via the forum.
Here goes. I can get long winded so...
(short version)
d2tmo, cleaned up and TitanBU all apps removed mostly, giving me a spaciaous 50% Internal or so with ExtSD getting full.
Used Mobile Odin Pro to first upgrade the Baseband to current T999UVUENC2.
I was on the MD5 and rocking CM11 m2 forever..., I didn't notice any issues at all after the basband and called girlfriend and clashed with clans abit via wifi I presume.
Then came....
NANDRIOD. 3GB transferred to my EXTSD (I've a stockpile of them, nands that is)
and MOBILE ODIN PRO KT747 with DATA/CACHE and Dalvik all wiped, rebooted into recovery, looked up after unable to find fix permissions, CWM apparently took it out in newest versions as people used it like a placebo. thats that and I reboot. KT splash, CM 11 m2 animation. and ALL is Well, except my WIFI won't come on.
I'm convinced that somewhere in the thread I had read from recent posts of people with similar problems. with an Easy fix...
1)I'm fully prepped with SuperSU1.99, CM11 m6 and next 4 nightly's and nandroids ufff course
2)I don't USE TouchWiz yukk, and having found a .zip of the TW 4.4.2 on my SD along with the 5/13/2014 and the 5/12/2014 AOSP's
Basically I question weather I'm a retard and put the TW on my device and its causing this. (My first ROM flash was a rom for another Phone) embarrassingly enough a long long time ago...lmao SO i have a history of boneheaded mistakes.
How should I go about this? My sincerest Appreciation in advance for your time.
Kernel Version
3.4.89-cyanogenmod-g2a5ecd4-dirty
[email protected]#1
Tue May 13 21:30:31 MST 2014
Is that the AOSP installed?
if so...howcan i fix my wifi then?
Good Day to you sirs,
and Ma'aMs?
Sincerely,
Smashing Atoms
Its 12 o clock here, I'm gonna go drink patiently while I eagerly await the verdict if i'm dumb or not.

Just so I understand your Current State.
You had Flashed the TW 4.4.2 along with KT747 AOSP Kernel. Now everything else worked but no WiFi. Is this right ?
Assuming the above is correct, I bet you got the TW 4.4.2 Rom from Docholiday77's thread. That rom comes with its own version of KT747. So don't flash anything else if that's the Rom you want. So reflash the Rom and then wipe Dalvik+Cache. All will be well.
Now if you do want to go back to CM or you had CM all along, then just Flash the latest CM you have followed by KT747. Don't forget to wipe Dalvik & Cache. All will be well again. Otherwise restore one of your Nandroids.

Perseus71 said:
Just so I understand your Current State.
You had Flashed the TW 4.4.2 along with KT747 AOSP Kernel. Now everything else worked but no WiFi. Is this right ?
Assuming the above is correct, I bet you got the TW 4.4.2 Rom from Docholiday77's thread. That rom comes with its own version of KT747. So don't flash anything else if that's the Rom you want. So reflash the Rom and then wipe Dalvik+Cache. All will be well.
Now if you do want to go back to CM or you had CM all along, then just Flash the latest CM you have followed by KT747. Don't forget to wipe Dalvik & Cache. All will be well again. Otherwise restore one of your Nandroids.
Click to expand...
Click to collapse
yes, I'm not exactly in a rough spot, suppose I would just like to know what went wrong. there is some misccomunication (i get carried away).
Had CM11 m2 installed, made a nand, flashed a kernel, My 64GB ExtSD is almost full, you must imagine an occasional zip here or there not in its place. When flashing I try to leave the bare essentials at root. After apparent successful flash of KT747 which I aquired from ktoonsez's threads. It became apparent quickly that I did not have Wifi enabled. a little reading and a little verifiying. and I found 3 kernels on my root ExtSD, 20140512, 20140513 both AOSP (for CM of course) but I found a 5-13 KT TW in the same directory.
alot of info to describe either
a) I should just start again cause wifi didn't take. (this time I'll flash m2 to m6 cache/data dalvik, restart, kernel)
b)It was caused beacuse I'm running a TWKernel with CM.
either way it raised concern and i felt the need to collaborate. sorry my previous message confusingly had your name in it. I was looking for actives in the thread and was PM them the same message, but at the 2nd person not recieving PM I figured whatever, put it in the Q n' A. My only problem is that I figured the names that i seen the most giving answers weren't going to see my message.
The last time I made a mistake of wrong file for wrong device...It was a bloody chrismas miracle i brought the device back with my lack of knowledge and experience at the time with what i know now to be a simple bootloop, at the time it scared me though.
I kinda got an immediate uh-oh fearful feeling from this too, just seeing the TW kernel in my inventory *scary* I'll let you know how it goes. gonna NAND now., find 8 places to post "Awesome" and then go to the thread and boast my kernel probably fixes my MPDecision logcat errors.
Hoorah

I'd delete the KT747 TW zip file.
Your Point B is correct / Valid.
Follow Point A. Except Do it this way.
Flash CM > Flash KT747 20140513 AOSP > Wipe Dalvik & Cache > Reboot & Profit.
Everything you said is valid and makes sense. Don't beat yourself too much about it. We all do it at one time or another. My name or not, I'd have helped you here. I do know without having 10 Post Score, you can't PM XDA Members. I do encourage this forum rather than PM as that allows others to help or profit from our discussion.
EDIT - If the MPDECISION error repeats after all this, please elaborate on the details.

Perseus71 said:
I'd delete the KT747 TW zip file.
Your Point B is correct / Valid.
Follow Point A. Except Do it this way.
Flash CM > Flash KT747 20140513 AOSP > Wipe Dalvik & Cache > Reboot & Profit.
Everything you said is valid and makes sense. Don't beat yourself too much about it. We all do it at one time or another. My name or not, I'd have helped you here. I do know without having 10 Post Score, you can't PM XDA Members. I do encourage this forum rather than PM as that allows others to help or profit from our discussion.
EDIT - If the MPDECISION error repeats after all this, please elaborate on the details.
Click to expand...
Click to collapse
I sit golden with WIFI access, updated CM and a new Kernel. thanks again. When I peep a logcat here in a bit, I will jump for joy if the MPdecision errors are gone, I wasted so much time and effort troubleshooting that wascawy wabbit. I could be mistaken but I believe i saw in update log for the kernel improved or updated MPdecision. If i feel the need to collaborate on the issue I'm sure you'll see me around those threads real soon.
Thanks again

If you intend to use KT747 Kernel, you HAVE to delete MPDECISION. that file interferes the Kernel's Hotplugging.

Perseus71 said:
If you intend to use KT747 Kernel, you HAVE to delete MPDECISION. that file interferes the Kernel's Hotplugging.
Click to expand...
Click to collapse
That I had no idea, but I'm not surprised. I haven't been able to do a log yet :/ I'm just getting to removing excessively excessive gigs from extSD. I've been extremely patient with my device while it allows TitanBU to hang for seemingly eternity attempting to restore youtube+data.
I think You tube stopped downloading user defined videos while on wifi for offline viewing a lil' while ago...don't know why i need it at all then. Thanks for PRO tip on MP, I'll have to do much more reading on the papers before I yank it, but I'm sure its a worthy cause. MakePoor decisions has fruitlessly occupied my attention long enough!!!
I haven't had to deal with so much restoring/reinstall (due to my mishap) since I went from 10.2rc to 11.
Is the MP Decisions surgery invasive? I'll have to lookup the Hotplug to refresh exactly what its doing. but I know it interferred plenty with my tasker Profile based govorner switcher. effectively the reasoning behind MP coming to my attention to begin with (tasker logs).

The mpdecision file runs in our system as a vendor executable file and it controls the governor for cpu. This file is very important as it defines performance of your cpu1, the file gets executed every time your screen goes off, hence cpu1 control operations are useless because the mpdecision file overwrites the cpu1 governor settings to userspace and ondemand, userspace is the governor when cpu1 is online and ondemand when offline.
The above meddles with the Hotplugging by the Kernel. It will also interfere if you are switching the CPU by Tasker. Since you have Nandroid Backups, I suggest you rename the file to mpdecision.bak. That way it will still be there but just won't be executed.
Now some Food for thougth. KT747 includes several Governors that incorporate Hotplugging. For others you have ability to force Hotplugging.
The point about Hotplugging is that it will disable secondary CPUs when the system is very idle, and enable them again once the system becomes busy. This is achieved by averaging load over multiple sampling periods; if CPUs were online or offlined based on a single sampling period then thrashing will occur.
Within the KTweaker app, you have option of setting several Governer Parameters. (See the link about OverClocking / Undervolting in my signature). This makes Sysfs entries for “hotplug_in_sampling_periods” and for “hotplug_out_sampling_periods” which determine how many consecutive periods get averaged to determine if secondary CPUs should be onlined or offlined. Defaults are 5 periods and 20 periods respectively. Otherwise the standard sysfs entries you might find for “ondemand” and “conservative” governors are there.
Source - Link
If you want to know more about Hotplugging, you will need to read up on how Linux introduced and does Hotplugging of CPU Cores. Here's a link.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715

Related

[Ask Your Questions Here] Questions & Answers for Epic 4G Users

CLICK HERE TO GO TO THE WIKI
I have decided to open a Questions and Answers thread on this section of the forum. This is a good way to keep the number of new threads with questions down to a minimum, which will make new threads essentially for people that are contributing to the Samsung Epic 4G. This includes, but is not limited to, people that are providing the following:
- Roms & Kitchens
- Programs & Apps
- Fixes & Tweaks
- Skins & Themes
- Tips & Tricks
I would like to request the help from other members to keep the thread in order and in check. This will have the added side effect of creating an ever self updating knowledge base that will far extend the content of the Wiki. This will in turn save us from having to answer the same question a billion times...
Please refer to the Wiki first before asking any questions though! It can be located here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700
CLICK HERE TO GO TO THE WIKI
Any idea when the OTA push for2.2 will start?
jg187211 said:
Any idea when the OTA push for2.2 will start?
Click to expand...
Click to collapse
Unfortunately, we don't have anyone in the community who has inside access to that information. Some of our members are affiliated with Sprint, and so have slightly more reliable rumors, but even their sources have thus far been wrong if they quoted a specific date...
So I hope you understand that I'm not being a jerk when I say, we won't know until it actually happens (and this will probably always be the case)
That being said, this most recent leak (DK28) seems stable so far IMO, so it could potentially become our official update
ok im a total noob to all this stuff. i followed the guide to update my epic to 2.2. the problem is, that the camera, gallery, and a couple other apps dont work. Can someone help me? Should i go back to 2.1, if so, how do i do that?
EDIT: Angry rant removed, thanks to the mods for a quick response (and to the member who's post was removed: no hard feelings, I hope you understand)
Just remember to read before posting, to make sure your post will be relevant and not redundant
jayzn210 said:
ok im a total noob to all this stuff. i followed the guide to update my epic to 2.2. the problem is, that the camera, gallery, and a couple other apps dont work. Can someone help me? Should i go back to 2.1, if so, how do i do that?
Click to expand...
Click to collapse
Whenever flashing a ROM using either recovery, it's always a good idea to wipe the phone (as in factory reset - I'm not referring to wiping the cache or the dalvik cache, although both steps are also usually recommended)
If you used the odin method described in this thread: http://forum.xda-developers.com/showthread.php?t=861213
then you might have flashed the wrong tar - DK05 and DK17 both had the camera problem, make sure you have the DK28 file.
If you have the right tar, then you could have an incomplete download... I doubt that though, when that happened to me, my phone wouldn't boot at all. But you might want to redownload the tar just to be sure (double check the filesize after it finishes and before you flash, if it seems too small then it messed up again)
That's the best general advice I can offer, but if you'd like to provide more details about the method you used (especially a link to the guide you used, if it isn't the one I provided), someone here might be able to identify where you're going wrong
i followed the instructions from http://forum.xda-developers.com/showthread.php?t=861213. i didnt use odin, i just used the .zip method. it took me a lot of tries cause i kept getting errors. the second mirror link worked for me, but like i said, my camera, gps, gallery and some other apps dont work.
oh and everytime i try to flash again, i get the error.
It sounds like you're either starting from the wrong rom or not wiping the phone before flashing the zip. All of the zip updates I have seen require you to start from DI18 stock (root an clockwork seem to be okay in my experience, all other mods must be removed) - if you have installed any custom roms, your best bet is to follow the odin method using the stock DI18 tar - so you may as well just skip the zip methodand odin to the stock DK28 tar
And you absolutely must wipe the phone (again, factory reset - I suspect many people are just wiping the cache and/or the dalvik cache).
Sent from my SPH-D700 using XDA App
Odin flashing
I've got a quick question. I'm looking to move to a build using the DK28 information release and it requires that I update the pit and modem files on my phone using Odin. Do I need to flash a 2.2 rom right away or am I safe to boot into my current rom first?
KaiXXV said:
I've got a quick question. I'm looking to move to a build using the DK28 information release and it requires that I update the pit and modem files on my phone using Odin. Do I need to flash a 2.2 rom right away or am I safe to boot into my current rom first?
Click to expand...
Click to collapse
Are you doing the strictly odin method (full froyo in a tar file)? Or an update.zip?
The odin method *should* include the modem and everything (and you use the updated pit in the same process) - you'll have to read the particular thread that you got the download link from, but I haven't noticed any odin tar files that required the modem separately
For the update.zip method, I don't know if it matters whether you flash the modem before or after applying the zip through recovery - I don't think either one overwrites the other, but that's a part of the process I can only guess about. But regardless of when you odin flash the modem, that's when you'll use the new pit file (the same as the odin-only method above).
As far as I know, the primary difference is that the update.zip doesn't inherently overwrite user data (but you'll probably have broken programs that FC all the time, which means a wipe is necessary, making this somewhat null). I prefer the odin method because it is a fresh flash of the entire system (I usually let it repartition as well - no one else has posted about that feature so I have no idea if it's a fluke that it hasn't given me problems)
Hope that helps
which is the best
so i have updated to dk28 froyo 2.2 i like battery life and performance can anyone offer info on which is the best rom for me or just some insight on which rom is the best overall
How do I stop running applications from starting every time I restart my phone?? I have the start up auditor but for some reason everytime I restart my phone the apps I have disabled keep restarting themselves and I have to go into the running programs and disable them manually. WTH?? Doesnt programs constantly running in the background kill the battery life?? How do I disable apps from starting?
youngpro83 said:
How do I stop running applications from starting every time I restart my phone?? I have the start up auditor but for some reason everytime I restart my phone the apps I have disabled keep restarting themselves and I have to go into the running programs and disable them manually. WTH?? Doesnt programs constantly running in the background kill the battery life?? How do I disable apps from starting?
Click to expand...
Click to collapse
How I understand it, especially with Froyo, you shouldn't have to kill programs in the background, if said 'background' process or service is working normal or efficiently. I still kill the DRM process when I reboot my phone, and not sure if it's still causing drain issues.
Also (someone else confirm this), I believe that constantly 'killing' certain background processes actually uses MORE battery, since it has to constantly restart itself. I've had a much more stable device *not* using auto killers, and just sniping one here and there that I know to cause drain.
Some reading material on GC, tho, in regards to memory management
Ignore me!
devo52 said:
so i have updated to dk28 froyo 2.2 i like battery life and performance can anyone offer info on which is the best rom for me or just some insight on which rom is the best overall
Click to expand...
Click to collapse
A lot of it is personal preference - this early in the game, the primary differences between the roms are going to be mostly cosmetic. So for now, the best advice I can offer is to try each of them and decide which theme you like. Regardless of how you upgraded, you had to use odin, so you have succeeded at the most difficult step of the process - and odin can bring your phone back to life if something goes wrong, so it's an invaluable skill to have.
In the meantime, keep watching the threads (quietly, unless you have a question that hasn't been asked already - we're working on cleaning up the forum to make it easier for everyone to find answers... but I digress...)
It's too early to be sure of any of the fixes out there - we have at least three separate fixes for the GPS issues; some people find success with one, others with another, and a lucky few don't need the fixes at all... so in summary, we can't say which is better or worse just yet, stay tuned and decide whether you want to experiment on the bleeding edge, or wait for these things to be stable and thoroughly tested.
And if you have any doubts, just stick with the stock DK28 for now
tl;dr, questions in BOLD.
Okay, after spending the entire night scouring the internet/this forum and starting from absolutely zero-knowledge about the Android OS, I managed to update my Epic to 2.2, and root the phone. Now, I'm kinda stuck as far as customization goes. I see all these cool skins and battery life mods and stuff, but they don't exactly offer any steps as to how to install them. Since I don't exactly know what file-types do what, I'm kinda shooting blindly at trying to update/install something "custom" onto the phone. So, my question(s) is/are:
What does the ROM do?
What does the ROOT do?
I know the root basically "unlocks" your phone, but that's all I know. The process of customizing the phone still remains a mystery. (that's the problem with following step-by-step instructions, rather than actually knowing what you're doing.)
I also don't understand the purpose of flashing a phone. Flashing, in my experience is to update something, like say a BIOS. But that sets the system back to square 1 as far as all settings go, in this particular example.
If I flash, with say Odin, after having updated to DK28 and "rooting," won't this make all the "customization" that I've done prior basically 'null' because I've just flashed the phone into a blank-state?
Sorry if these are questions easily answered by searching, but I just spent my entire sleep-cycle trying to find the answers to these questions, and managed to only get so far. I look forward to the answers On another note, I am now EXTREEEEMELY pleased with my phone. Before this evening, I was just the regular, old run-of-the-mill enduser. I liked the cool built-in customizations and all the apps and what not, but never dreamed of being able to customize my phone to THIS EXTENT. So, now it's something I'm very interested in doing..it makes my phone truly mine.
zdavidi said:
What does the ROM do?
What does the ROOT do?
Click to expand...
Click to collapse
Did you see the link to the Wiki in the original post of this thread? That's where I started when I first got here, it helped me understand the basics.
zdavidi said:
If I flash, with say Odin, after having updated to DK28 and "rooting," won't this make all the "customization" that I've done prior basically 'null' because I've just flashed the phone into a blank-state?.
Click to expand...
Click to collapse
It depends on what you flashed with Odin. If you only flash a modem file, then your customizations and apps are untouched. If you flash an entire ROM in "tarball" form then not only does it re-write the modem but it also overwrites all user data. Think of the latter as resetting the phone to stock and works even if you cannot boot up.
When can we expect a custom Kernel with netfilters for wifi tethering?
n00b question.
If an SDK version is released (say, like, Gingerbread today), does that mean chefs could take it and cook up a ROM for ANY phone (say, like, the Epic)? Or do they need something else to do that?
Remove Touchwiz Launcher (consequences?)
Hey-- I'm using Quantum 2.0.0 ROM, and I never use the touchwiz launcher. Does anyone know if it's safe to just remove the apk? (TouchWiz30Launcher.apk) or is there other functionality tied to it?
I use LauncherPro, fyi.
Please forgive my ignorance... I've searched the forums, looked at the wiki...
I use titanium backup and am now running the DK27 froyo build by noobnl. My question... How do I restore my e-mail accounts to the phone everytime without having to re-type them in? I've been flashing a rom every other day on average since I got the phone and it's getting REALLY old.

Answers to common questions about SyndicateROM Frozen

This is a guide I’ve put together from my (in)experience with flashing ACS. It mainly comes from the replies of k0nane and theimpaler747 in the SyndicateROM thread. However, since there’s so many pages that can be tricky to search for idiots like me who just throw up random posts for others to solve their problems, I thought it would be good to summarize it along with anything I happened to notice from flashing a couple of Epics. Consider it the FIBI guide.
Step 1: Read all posts by k0nane on page 1 of the SyndicateROM thread before doing a damn thing! http://forum.xda-developers.com/showthread.php?t=976194
Instructions for CWM are in this thread: http://forum.xda-developers.com/showthread.php?t=897612
Useful hotkeys:
Download mode - Hold down 1 on the keyboard when you power on the phone
Recovery mode - Hold Volume down+camera+power to power on the phone
Reset phone - Hold volume up+camera+power. This generally works when the phone is completely locked up.
Flashing:
When going between versions of ACS, check their notes to see if you need to do anything other than flash. You can go between some versions without wiping or losing anything. You can also flash between standard and fully loaded without wiping or losing anything.
Sdcard doesn’t mount in CWM, but shows up in Android - Format the sdcard in Android.
Boot hangs on the Samsung screen – Redownload, format your SD card and reflash
Boot screen flashed between different things – Wipe cache & data 3x and reflash
Journaling:
Enable journaling – In CWM, go to backup and restore. Backup, then restore using that backup. Journaling enabled!
Make it so you don’t need journaling – Keep a copy of the ROM on your phone at all times. Should you ever have data corruption, jump into CWM and flash the ROM again. It’s quick, no wipes needed.
If you restore a backup made in CWM and want to have non-journaled again – Flash the ROM after restoring.
Other issues:
FC in a specific app – Go into manage applications and clear data for that app
FC in several apps – In CWM > Advanced, try fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
If you have any major issues that seem unresolved, Odin everything back to stock with EB13, format your sdcard in android, re-download everything, re-install CWM, re-read all of k0nane’s posts on page 1 and try again.
If you want ads back – Install adfree from market and hit revert
If your phone is freezing often - Flash either the vision kernel found here: http://forum.xda-developers.com/showthread.php?t=1012136 or the Twilight 1.0.4 kernel found here: http://forum.xda-developers.com/showpost.php?p=12504067&postcount=5904. I haven't had the freezing issues, but I'd recommend trying the vision kernel first as it has some other potential benefits.
Recommended tweaks and add ons:
Fugutweaks – This will smooth out a few random things on the phone. I’ve noticed more responsiveness on the lock screen and icons on my homescreen. Small, but nice. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=981125
Impaled Keyboard – Makes the keyboard less likely to skip keys. Still have some, but they’ve gone down a lot. I use the Speed Demon Edition, still had a fair amount of dropped keys with standard one. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=1025533&page=18
SetCPU – Handles scaling the CPU and overclocking. Use ondemand setting for smooth performance. If you have issues when the phone is idle or it doesn’t wake up properly, set minimum CPU to 200Mhz. Free for XDA members, APK can be found here: http://forum.xda-developers.com/showthread.php?t=505419
Battery Calibration – If you want to calibrate your battery without going into CWM, grab the app from this thread: http://forum.xda-developers.com/showthread.php?t=1024867. It’s now available from the Android Market.
Vision Kernel – Pretty much Twilight + gives you 1.4Ghz and Voodoo colour which improves balance when brightness is at 100%. Flash in CWM, wipe dalvik. Kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1012136
And a final note that I'm now about 10 hours into testing... if you are using fully loaded and want better battery life, really try standard. It very easy to switch, it flashes over fully loaded with no wipes or data loss, the only thing you lose is that it resets your homescreens. But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Great info! I recently installed the newest SyndicateROM 1.1.0 on my Epic and the only trouble I had was with the included Twilight 1.1.0 kernel. My phone kept freezing and I would have to pull the battery to reboot.
This is an issue that has been documented with the ROM and is said to be caused by the kernel and its adjustments to voltage and overclocking, not all phones handle this well.
To fix the issue I flashed the Twilight 1.0.4 kernel, as suggested by k0nane, and I am about a day into testing without any freezing issues. The only problem is that the Twilight 1.0.4 kernel has a known issue with video recording and it does not work.
Let me say that the performance increase from installing SyndicateROM and ext4 are well worth the trouble.
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
is your brightness at 100%??? what was the difference between standard and fully loaded again??
VeNoM vZ said:
is your brightness at 100%??? what was the difference between standard and fully loaded again??
Click to expand...
Click to collapse
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
k0nane said:
SyndicateROM Standard includes LauncherPro. All Samsung and Sprint bloatware are completely gone!
SyndicateROM Fully Loaded - the choice of ACS team lead rjmjr69 - features TouchWiz instead of LauncherPro, and adds in Social Network Sync, Facebook, BuddiesNow, Program Monitor, and the stock live wallpapers. All the rest of the bloat is still gone!
Click to expand...
Click to collapse
Catalyst Shift said:
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
Click to expand...
Click to collapse
The brightness for battery life.
No, brightness is not at 100%. I generally use 0-25%, though I'll kick it to 100% when viewing photos or when I'm outside. Even with the lower brightness setting, I'd always have to recharge in the afternoon. I'm still doing a lot of testing for ways of having the battery last longer, today is longest it's ever gone for. I'll be adding more information when I feel like I've got a solid way of having it all setup.
OP, could you add the freezes and "terrible battery life" solutions? Namely, flash the kernel in the second post or VisionKernel. It's the most annoying one to answer multiple times daily.
Thanks much for this! Hopefully people read it.
I want to get the battery situation on my phone sorted out before adding it to the list. I was having pretty bad battery life, but switching to standard and removing gallery has made my phone last all day for the first time ever. I want to do some experiments between setcpu options, juicedefender and the vision kernel to see what works best. Hopefully by this weekend I'll have a more detailed idea as to how to get better battery life.
But for now, anyone having battery issues my current setup is using ACS standard and replacing gallery with quickpic. This has doubled my battery life.
Hey wassup everyone, first time writer long time viewer, and first let me say thanks to all the great people that have provided us with great roms for the epic and the syndicate team as well, Im currently using a Epic 4G with sindicate rom freeze 1.1.0 and i must say its awesome, aside from my battery dying really quickly when im runing it at 1.3ghz its actually great, usually i end up operatig it at 800mhz to actually save some battery life last me for 3 days at a time, and when i have it pluged in or show off my awesome epic i raise it back upto 1.3ghz, big difference cuz when i raise it up there my battery drains rather quickly like 3 percent a minute or so.....
well anyways now that, thats says, I have CWM 3..0.5 with syndicaterom twilight 1.1.0 and ive been sucessful at loading custom boot animation, but one thing is that im having trouble is loading the animation with sound? any idea onhow i can od that?, what are the steps, cuz so far ive been using root explorer to transfer and change bootanimation to load up on my screen, but i have no idea where to put the sound or how to even get it to load with the bootanimation any one have any ideas? please help, i do all his trought my phone, put the bootanimation on my sd and work from there and trasfer it to the system/media, most bootanimation that do have sound on them say to put it on the system/custimization/resources but i look every where and the syndicate rom doesnt have that archieve just the system/media, how can i load the sound into my boot? and how can i change the power off animation as wll?
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals..
This might.. just maybe (crosses fingers) alleviate the never ending repeating of questions in the main sfr thread
Catalyst Shift said:
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
Click to expand...
Click to collapse
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
The first sign of trouble came when I installed a fresh version of SyndicateROM 1.1.0 and then flashed Vision kernel 1.1. The phone booted-up fine but when I went to shut down it immediately froze and I had to pull the battery.
Im going to stay on Twilight 1.0.4 kernel for a while until I find something else.
I have tested Twilight 1.0.4 kernel for about a day or two and have not had any problems so far. I even overclocked with SetCPU to 1.2GHz without any issues.
tmspyder said:
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals.
Click to expand...
Click to collapse
I would be more than happy to contribute my experiences if this gets up and running. PM me with any updates to the "SyndicateROM [TSG] WiKi"
Please Help a Novice
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen. Have I bricked my phone? How do I recover? Please please please help...Haven't even had my phone for a day...
By the way, the error I'm getting is:
ClockworkMod Recovery v2.5.1.0
E:Can't open /cache/recovery/log
I backed up before I installed this ROM, and Restore brings me back to this same screen / message
mercerma said:
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen.
Click to expand...
Click to collapse
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Hey, great idea for the thread.
Something I learned:
I was having AWFUL freezing problems. Tried all the fixes (vision kernel, old twilight) to no avail. If these don't fix your problems, try Genocide Kernel (on these forums). Solved my problems.
Catalyst Shift said:
But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Click to expand...
Click to collapse
Ok, so im thinking of switching to the standard edition of he rom cuz im currently using the fully loaded added the 1.0 kernel vision on it to get the 1.4ghz, and its pretty smooth its stable at times so im keeping it at 1.3 for now until its set more stable..... however when u said that ure at 10 hours and u still have 62% whats the speed u have ure epic set at and whats the brightness?
Nolyrics2 said:
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
Click to expand...
Click to collapse
Fix permissions in CWM/etc.
Kernels cannot cause that. It's that simple.
Nolyrics2 said:
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Click to expand...
Click to collapse
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
I installed CWM previous to transferring the rom to my sd card
I did not the first time, but per instructions on the page where I downloaded the ROM, I reformatted my sd card, redownloaded the ROM, wiped everything 3x's and tried to reinstall. Same result. I keep getting the error on just about everything I do that states "E:Can't open /cash/recovery/log"
And thank you for your advise, any more would be greatly appriciated. I did search the forum, but there is so much information, hard to find what I really want, especially as a novice. I plan to not be a novice for long thanks to xda!
mercerma said:
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
Click to expand...
Click to collapse
I could probably answer that question, im still a noob, but from what i know u need to install CWM version 3.0.5/6 in order for u to run does roms, thats why ure having trouble flashing it, since Syndicate roms are EXT4 Base Roms anything lower then CWM3 wont support since they are RFS files, go here and follow the steps
http://forum.xda-developers.com/showthread.php?t=976194
download the CWM3 and root it again, u can run the CWM Root over the previous 1 so dont worry, i did it that way and i had no problems what so ever, as to check to see what modem u had, go to settings, about phone, under base band version check to see if the last 4 letters says EB13, or DK28, or if u have the ECO5 which is the newest stock base update that came out.
Also its best to know if ure phone is from stock, or if u updated from any of the first 2 version updates, EB or DK, if u where like me that waited for the update and stayed at Eclair then updated when the ECO5 OTA came out then u should be fine....
Just incase u are from a update of EB or DK here is the link for does 2 versions of CWM3
http://forum.xda-developers.com/showthread.php?t=897612
if im wrong then someone please correct me im still a noob learning.
EDIT: just noticed that u said ure phone is messed at that point, umm u can try to do a factory reset then restart ure phone see if that fixes the problem, then try follow the steps above, if that doesnt work, u will have to download odin, which is also in that link and reflash back to stock, everything is there so if u follow does instrunctions u wont have a problem.....its actually pretty easy.....

Issue closed. Delete this please.

Hi guys, I urgently need your help! Yesterday my phone drastically slowed down, I don't know what may have been.
I was using cyanogenmod 10 with Franco kernel (I was testing 512 GPU version). So I tried restoring a backup, but no use, slooooow!
I did all the wipes and reflashed CM10 from scratch, with gapps. Problem still exists! Tried reflashkng Franco Kernel (380 GPU) and still the same. At first I thought I might have fried my GPU, but Franco kernel updater app shows gpu working.
So I think this may require a total wipe (including sdcard) and a stock good image reflash from the gn toolkit.
I'm attaching a log right after boot (which took AGES). It seems to me that something's not right.. by I need HELP!
Thank you guys...
http://db.tt/k3dz0aP9
I am not an expert of reading logs yet so probably another member will help you more regarding that.
It seems you have already done a full wipe and tried installing/flashing again but I am not sure which procedure you followed. So my suggestion is to put on your SD card a ROM and kernel, maybe Trinity just for a change, then do full wipe and install the ROM and the kernel so it will be all fresh with a new kernel as well.
If it is still slow, then download any app that would control the CPU and GPU speed to ensure of their speeds running now.
At worst case, returning to stock should help a lot in determining if it is a software or (hopefully not) hardware problem.
Good Luck
I found out that other people have this problem, so I'm asking in the already open threads. Close this please.
Sent from my Galaxy Nexus

[Q&A] [KERNEL][AOSP4.4/5.0/5.1] dkp - d2att - 4/25/15

Q&A for [KERNEL][AOSP4.4/5.0/5.1] dkp - d2att - 4/25/15
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][AOSP4.4/5.0/5.1] dkp - d2att - 4/25/15. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
whodisname said:
I had to restore a backup today. Battery got to 10% turned on battery saver for a few seconds before remembering this could be an issue still (build 4/25 PAC ROM) then my battery went dead after a while. Wouldn't boot past the Samsung logo. Hot to recovery and after getting it charged to about 50% tried again. Vibrate once, Samsung logo then blank screen then repeat and repeat some more. Restored nandroid. The kernel also deleted itself once after accidentally over clocking to like 1900 or some such (damn touchscreen )
Click to expand...
Click to collapse
I'm also on 4/25 build of PAC ROM. I used Voltage Control and set zen as I/O and asswax as governor. Went to bed with the phone plugged into a USB charger. This morning when I checked it, the notification light was blinking but the phone would not wake and after a hard reset I got the vibrate, Samsung logo, blank screen, repeat. I had to restore to an earlier back up.
I just got a new battery after getting one that was defective last week (wouldn't charge right and drained super fast) just got the new one. Noticed that every time the battery was removed I had to reinstall the kernel.
Whenever I power the phone down completely and try to turn it back on the phone boot loops on the Samsung splash screen. The only way to get it to boot properly is to go into recovery and having it reboot into system. Additionally if I'm fully booted into android and I reboot from the power menu it also boots properly.
Regarding freezes, the only build that won't freeze (I hope :fingers-crossed is the one that I posted to the main thread a day or two ago. It's not in the normal MediaFire downloads, so check the thread for a link.
There have been a lot of reports of boot issues, but I don't have any idea what's going on. I haven't run into this problem, so I don't have any solid information yet. In addition to the usual helpful information (ROM & build date, etc.), a last_kmsg would be a huge help. You'll have to get it from recovery, though.
Try to boot normally. When it fails, boot into recovery. If your phone doesn't reboot automatically, don't pull the battery, hold power to reboot instead!
If you have adb handy, just "adb pull /proc/last_kmsg" and you're done.
Using a file manager (TWRP's builtin or Aroma Filemanager or whatever), navigate to /proc, and copy last_kmsg to /sdcard.
PM me the logcat (hint: /sdcard is actually internal storage, confusingly enough )
Official Nightly
Edit: wrong thread
Can't Flash DKP
I've used this kernel before and been able to flash it successfully. But now whenever I try
To flash it I always get a bootloop. I've tried flashing it with Oct L ROM, PAC ROM,Cyanide L
But it never works. I flashed it and cleared cache and dalvik and tried using fix permissions
to see if it would work but it still doesn't boot.
ocufb24 said:
Whenever I power the phone down completely and try to turn it back on the phone boot loops on the Samsung splash screen. The only way to get it to boot properly is to go into recovery and having it reboot into system. Additionally if I'm fully booted into android and I reboot from the power menu it also boots properly.
Click to expand...
Click to collapse
The same problem here please help
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
aumast said:
The same problem here please help
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
My first thought would be reflashing your current bootloader and modem.
If that fails, then flashing a stock rom. I'm not sure if either of these will fix things for you, but I haven't seen any one else make suggestions. The device has secondary bootloader partitions and these may be what are allowing the phone to boot in those cases where it does.
dawgdoc said:
My first thought would be reflashing your current bootloader and modem.
If that fails, then flashing a stock rom. I'm not sure if either of these will fix things for you, but I haven't seen any one else make suggestions. The device has secondary bootloader partitions and these may be what are allowing the phone to boot in those cases where it does.
Click to expand...
Click to collapse
Are you quite sure about this advice? This looks like a recipient for a brick.
whodisname said:
Are you quite sure about this advice? This looks like a recipient for a brick.
Click to expand...
Click to collapse
If you reflash the bootloader and modem you are currently on there should be no bricks occurring. As far as flashing a stock ROM, always make certain you are flashing one with the same bootloader and modem that is now on the device.
In neither instance would a person be downgrading the bootloader and modem, they would also be keeping both the bootloader and modem at the same version. I haven't seen where anyone has reported this causing a brick, have you?
What is your kernel setup?
governor etc
1. Flashed the kernel, as you can see in my signature however I used to use the Ktoonsez/Task650 kernel. I have to say the leankernel scheduler is amazing. Saves a lot of battery, however in terms of underclocking, is there anyway to get more 'steps'? I cannot lower the voltage for a lot of frequencies in between say 1200mhz and 800mhz as I would with the Ktoonsez kernel. Also the minimum is not low enough, and it seems like the only way I can lower it is by using the flashed zip.
2. Can I use the Ktoonsez kernel with this rom, any tips on stopping both rom/frequency controllers from interfering with each other?
zetsui said:
1. Flashed the kernel, as you can see in my signature however I used to use the Ktoonsez/Task650 kernel. I have to say the leankernel scheduler is amazing. Saves a lot of battery, however in terms of underclocking, is there anyway to get more 'steps'? I cannot lower the voltage for a lot of frequencies in between say 1200mhz and 800mhz as I would with the Ktoonsez kernel. Also the minimum is not low enough, and it seems like the only way I can lower it is by using the flashed zip.
2. Can I use the Ktoonsez kernel with this rom, any tips on stopping both rom/frequency controllers from interfering with each other?
Click to expand...
Click to collapse
Ktoonsez has kernels for both Touchwiz and AOSP based roms. It's been awhile since I read the OP of his kernel thread but it should say if it is good. I don't recall much about Task650 KitKat.
Help with random reboots
I am using the 7/29 revert spinlock kernel and have been having random reboots a few times a day with this version and the normal version. I have last_kmsg.txt . This is the link to the txt file in my google drive : https://drive.google.com/file/d/0B4Oi85yG9ALcTS1saXFCamRnaDQ/view?usp=sharing
I had to paste the link as text because I'm new and cannot insert a link into a message yet. I hope that's ok.
If you have time to look it over and see if you can tell me anything I might be doing wrong or if it's a kernel issue I would appreciate it.
Thank you sir!
dkp 2.1 GHz
Can you tell me how i can setup this kernel? How increase voltages?
Use a kernel app such as trickstermod.
whodisname said:
Use a kernel app such as trickstermod.
Click to expand...
Click to collapse
I understand. How much increase voltage? I don't found.
I don't know. I undervolted all one "step". If you are overclocking, seems prudent to step up in like fashion as before. (I.e. step up 50-75 millivolts every other step over. Something like that. Just be sure to have a solid backup.
Hey. I have this thing on here. It sometimes loses all signal. Just every once in a while. Don't have a logcat cuz its extremely intermittent. Anyone else have that? Otherwise its awesome and no other problems. Stable, random reboot twice in 2 months. That's it. No overheat, no lag, amazing! Super good!

Lagging poor performance.

Having major problems with my Note 4. It is often really sluggish. Has horrible lag. Sometimes it just randomly resets. And, when it resets, sometimes it goes straight to download mode and says could not do normal boot at the top. For example, right now it has been on the Samsung galaxy note 4 boot screen for a few minutes. I had to pull the battery for it to boot. Sometimes, when I press and hold the power button, it doesn't respond.
I have tried a number of fixes.
-Factory reset.
-Full wipe
-Format data, then full wipe
-Odin back to stock firmware (KK, LP and MM)
-Restore backup from TWRP
I searched and saw another thread with similar symptoms, but it was pretty old with only one response. I am really at a loss as to what to do. I can only assume it is hardware related. I haven't really dropped it. No water damage. Always in a case.
Any help would be appreciated
I had the exact same issues you are describing. It ended up being the only reason i upgraded to note 7. Now of course note 7 is being recalled & i wish i could go back to a fully functional note 4.
Hope somebody has a solution for this!
The OP describes a bad flash or OTA update, corrupt partition or failing eMMC. I'd advise replacing battery as a first step of troubleshooting. Make sure it's charged fully at least once and have 75% or more capacity before starting.
I've never had to do anything risky with "PIT with repartition" or "nand erase all" but there are other advanced forums for that but I don't venture into recommending risky measures I haven't performed with experienced guidance. You could find these by googling or visiting Sammobile specific forums- I don't think it's acceptable to post external links.
But before I considered risking those methods there's some steps I'd eliminate first (warning: they may seem redundant but if having issues, I'd be thorough even if it appears redundant):
1. Backup and boot system, enable developer mode and enable USB debugging.
2. Disable reactivation lock in Settings/Security.
3. Open SuperSU app and fully un-root.
4. Wipe everything but extSdCard, factory reset and format data and power down and pull battery. Get serial number from underneath battery for Smart Switch.
5. Install Smart Switch on PC.
6. IMO, you should Odin stock tar before using Smart Switch if previously rooted.
7. Use Smart Switch to either install latest update or emergency restore phone. I didn't know Smart Switch worked in Note 4 so refer to Sammobile.
8. Once done, Check stock for stability for days before opting to do anything unless you've duplicated same results. If you have a true hardware issue, it may be evident while trying these steps.
9. Determine if you need to do anything further. I can't help with the riskier stuff; I've been fortunate enough not to experience anything warranting a risky procedure.
Sent from my SM-N910P using Tapatalk
i am now having this same issue on my note 4. i have gone through all of the steps outlined in this thread. The only thing i haven't tried yet is a full repartition. Any thoughts? OP have you had any success?
Thanks,
JD
I succeeded in a full brick lol. That's about it. Wont even charge/power on.
last night i re-odined with a pit file. I had selected re-partition, nand erase and hone EFS clear. I did get a successful odin and the phone had to reactivate with sprint. IN the end i still have the very laggy performance, phone sometimes not responding and spontaneous reboots.
All of this started in an instant. Everything was running fine on a TW rom that i had been running for about a week. I went to use the camera, the app froze and the speaker made a slight static kind of sound and then all of this started. No matter what kind of rom i put on here they now all act the same. very strange.
JD
JudasD said:
last night i re-odined with a pit file. I had selected re-partition, nand erase and hone EFS clear. I did get a successful odin and the phone had to reactivate with sprint. IN the end i still have the very laggy performance, phone sometimes not responding and spontaneous reboots.
All of this started in an instant. Everything was running fine on a TW rom that i had been running for about a week. I went to use the camera, the app froze and the speaker made a slight static kind of sound and then all of this started. No matter what kind of rom i put on here they now all act the same. very strange.
JD
Click to expand...
Click to collapse
Doesn't sound like you're having all the issues posted by the OP if stock was fine for a week and you can Odin successfully and have no issue until installing a custom ROM.
You replaced your battery and stopped using older ones? That camera issue was either a bad battery or incompatible camera in a custom ROM, IMO.
The stock ROM that worked fine for a week and the custom ROM that spontaneously reboots, which were they? Most likely, you're limited to what mods you can apply. In that condition, were you using stock or custom kernel? Kernel tweaker or none? Am I wrong to conclude your issue is the custom ROM and possibly custom setups?
Could you describe the random reboots? I've personally experienced a scenario where a ROM may run fine until user factory resets and ItsOn tries to install its bootstrapper but cannot with custom kernel or missing resources. It's persistent though, got a prompt to reboot with no issue or reason given when all seems well except the prompt to reboot that may actually become unexpected reboot if notification it's disabled and ignored. Some have found its best to factory reset and wipe internal memory when this happens and then install custom ROM cleanly. @freeza even added a line in script to delete /carrier/ItsOn folder and contents when that was identified as the issue when not wiping internal memory when completing ItsOn bootstrapper prior to installing custom ROM. I believe that works in that scenario but it highlights a need for user to follow OP install to prevent that in ROMs that omit that line in scripts. This could be a disconnect where phone isn't tested but deemed compatible with Sprint and data patch.
But kernel tweaks can cause issues with random reboots. The kernel I use works well with interactive governor but the rest are not as stable or fluid. I can under volt but only 25 or 30 mV and I limit over clocking to 2 steps above stock, no further (goal is stability without hurting battery with reasonable gains). You should consider that each processor has already been profiled to run within a specific volt to frequency table based on its ability so there's little room to limit with no adverse effects. Major steps can have adverse effects. Over clocking should also be given the same respect. We're already maximizing performance near threshold of stability. Think small steps, rather than large. Using the developer recommended kernel tweaking app is paramount for success as well.
Swapping kernels repeatedly may also leave your phone in an incompatible state so that even restoring boot.img partition to stock isn't helping. The reason is the modules the kernel uses. Developers will modify the contents of /system/lib/modules. Hopefully that's done in a compatible way but each custom flash over pre-existing custom setup may not be ideal but works best flashed over stock modules. If developer has done thorough testing, maybe the adverse effects have minimized but you can see where not having the phone for testing may impact users. Restoring boot.img only leaves the modules in unintended modification, especially for stock boot.img
Just a few examples of why a custom ROM may not be as compatible as stock for some users or carrier subscribers. You should mention the ones not being so compatible when comparing to stock as well as knowing that custom kernel tweaks and applications may not work as well on all ROMs.
There is a possibility you've chosen an incompatible ROM; ported ROMs may be nearly fully functional but have issues like you described. There's many workarounds posted in this forum that admittedly aren't fully functional; much effort has been shared by a few that have given much effort to find most compatible ROM but I think we'll get more stable support out of the box for Sprint version on Sprint from @tx_dbs_tx soon enough if your phone holds up- the OP describes an all too common failure with eMMC failure on Note 4. Sprint compatibility is tougher due its network and porting ROMs is tedious and may not work fully on phones not on hand for test.
Sent from my SM-N930P using Tapatalk
samep said:
Doesn't sound like you're having all the issues posted by the OP if stock was fine for a week and you can Odin successfully and have no issue until installing a custom ROM.
You replaced your battery and stopped using older ones? That camera issue was either a bad battery or incompatible camera in a custom ROM, IMO.
The stock ROM that worked fine for a week and the custom ROM that spontaneously reboots, which were they? Most likely, you're limited to what mods you can apply. In that condition, were you using stock or custom kernel? Kernel tweaker or none? Am I wrong to conclude your issue is the custom ROM and possibly custom setups?
Could you describe the random reboots? I've personally experienced a scenario where a ROM may run fine until user factory resets and ItsOn tries to install its bootstrapper but cannot with custom kernel or missing resources. It's persistent though, got a prompt to reboot with no issue or reason given when all seems well except the prompt to reboot that may actually become unexpected reboot if notification it's disabled and ignored. Some have found its best to factory reset and wipe internal memory when this happens and then install custom ROM cleanly. @freeza even added a line in script to delete /carrier/ItsOn folder and contents when that was identified as the issue when not wiping internal memory when completing ItsOn bootstrapper prior to installing custom ROM. I believe that works in that scenario but it highlights a need for user to follow OP install to prevent that in ROMs that omit that line in scripts. This could be a disconnect where phone isn't tested but deemed compatible with Sprint and data patch.
But kernel tweaks can cause issues with random reboots. The kernel I use works well with interactive governor but the rest are not as stable or fluid. I can under volt but only 25 or 30 mV and I limit over clocking to 2 steps above stock, no further (goal is stability without hurting battery with reasonable gains). You should consider that each processor has already been profiled to run within a specific volt to frequency table based on its ability so there's little room to limit with no adverse effects. Major steps can have adverse effects. Over clocking should also be given the same respect. We're already maximizing performance near threshold of stability. Think small steps, rather than large. Using the developer recommended kernel tweaking app is paramount for success as well.
Swapping kernels repeatedly may also leave your phone in an incompatible state so that even restoring boot.img partition to stock isn't helping. The reason is the modules the kernel uses. Developers will modify the contents of /system/lib/modules. Hopefully that's done in a compatible way but each custom flash over pre-existing custom setup may not be ideal but works best flashed over stock modules. If developer has done thorough testing, maybe the adverse effects have minimized but you can see where not having the phone for testing may impact users. Restoring boot.img only leaves the modules in unintended modification, especially for stock boot.img
Just a few examples of why a custom ROM may not be as compatible as stock for some users or carrier subscribers. You should mention the ones not being so compatible when comparing to stock as well as knowing that custom kernel tweaks and applications may not work as well on all ROMs.
There is a possibility you've chosen an incompatible ROM; ported ROMs may be nearly fully functional but have issues like you described. There's many workarounds posted in this forum that admittedly aren't fully functional; much effort has been shared by a few that have given much effort to find most compatible ROM but I think we'll get more stable support out of the box for Sprint version on Sprint from @tx_dbs_tx soon enough if your phone holds up- the OP describes an all too common failure with eMMC failure on Note 4. Sprint compatibility is tougher due its network and porting ROMs is tedious and may not work fully on phones not on hand for test.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I apologize i was not 100% clear in my previous post. I was running a custom rom when the camera issue happened. Since then any rom i install is very laggy and has spontaneous reboots. This includes stock odin roms with no mods at all. I have also tried multiple batteries.
JD
JudasD said:
I apologize i was not 100% clear in my previous post. I was running a custom rom when the camera issue happened. Since then any rom i install is very laggy and has spontaneous reboots. This includes stock odin roms with no mods at all. I have also tried multiple batteries.
JD
Click to expand...
Click to collapse
OK, my mistake too. Maybe you said that before and I didn't follow the flow of your comments.
You did the nand erase all but do you typically wipe internal memory and factory reset prior to flashing ROM or stock tar? I also prefer to power down and pull battery before going to download mode and flashing stock tar.
If you've done everything and get random reboots on stock or failed to normal boot or eMMC failure, that may be your eMMC failing or other internal failure. I would expect it only gets worse over time- time to repair our replace. I just did my local research with uBreakItIfixIt and the guy says I'd have to bring in my own part but labor is only $10 plus tax to replace main motherboard. Part lists on web for $80 or more. Amazon has a listing for it too.
https://www.amazon.com/gp/aw/d/B01M..._SY340_FMwebp_QL65&keywords=Motherboard+N910P
Sub $100 repair estimate isn't so unreasonable compared to increasing cost of upgrading to locked phone with no root possibilities. But HTC is an option if their offering is appealing. I'm thinking maybe 2017 HTC has an appealing upgrade that I may find worthy for the money. Sure wish an OEM would duplicate the Note 4 on a refresh with updated internal components.
If my phone were to break today, I'd give that a go. I trust business names like Amazon and uBreakItIfixIt. Ubreakitifixit usually has parts on hand for simple or common repairs like screens, internal batteries and USB ports. That outfit just did an economical repair in an iPhone 6 for my wife. Replaced screen and battery for just over $160.
Sent from my SM-N930P using Tapatalk

Categories

Resources