Give me about 15 minutes. I'll post a TEST kernel in this exact post. Can't sleep anyway.................
looking forward to it!
Give me about 15 minutes. I'll post a TEST kernel in this exact post. Can't sleep anyway.................
Read the post with the link for 2.3 test. It'll show you.seems to be working fine. can u enlighten us what u changed from ver 2.2 to make it work? just curious how "serious" the issue was...
Thank you for the test kernel! Works great placed a few calls and received a few. Did a couple videos too just for testing purposes. No issue at all. Thanks! Hope you sleep well when you do!
Will provide more feedback as the day progresses
seems to be working fine. can u enlighten us what u changed from ver 2.2 to make it work? just curious how "serious" the issue was...
Alright testing 2.3 test 1 now.
Sent from my SM-N920T using Tapatalk
---------- Post added at 05:36 PM ---------- Previous post was at 05:36 PM ----------
Read the post with the link for 2.3 test. It'll show you.
Sent from my SM-N920T using Tapatalk
---------- Post added at 05:43 PM ---------- Previous post was at 05:36 PM ----------
So after hearing customer care tell me how much unlimited minutes, text messages, and unlimited data I have left for 5 minutes or so, I haven't experienced a reboot. I'll keep testing to be sure but tool chain seemed to be an issue.
Sent from my SM-N920T using Tapatalk
Yikes! Lol. You're welcome broThanks all for providing feedback and it seems we are at the bottom of the issue. I'll make the proper reverts visible in my gitHub source in just a short while after my own device is cured of my self induced bootloop
I'm on coj5 with Darth stalker v6 and after about half a day and a dozen phone calls I finally got the random reboot during a phone call. I was driving so I couldn't pull a log before it was overwritten.Can you two please share/compare your device firmware version?
PDA/ROM
Bootloader
Modern
etc etc
I'm on coj5 with Darth stalker v6 and after about half a day and a dozen phone calls I finally got the random reboot during a phone call. I was driving so I couldn't pull a log before it was overwritten.
Heading to test your test kernel.
I'm on coj5 with Darth stalker v6 and after about half a day and a dozen phone calls I finally got the random reboot during a phone call. I was driving so I couldn't pull a log before it was overwritten.
Heading to test your test kernel.
I can't even get my phone to boot with the test kernel. Idk if its because of Darth stalker v6 or what but I've tried two different downloads and it just stays spinning at the Darth stalker splash screen. I'll try again in a bit when I can plug it up to my computer and pull a log.The TEST kernel has been reported reboot free
http://xdaforums.com/showpost.php?p=64054724&postcount=300
I can't even get my phone to boot with the test kernel. Idk if its because of Darth stalker v6 or what but I've tried two different downloads and it just stays spinning at the Darth stalker splash screen. I'll try again in a bit when I can plug it up to my computer and pull a log.
v2.3 update for SM-N920-T / W8 device variants
Same as v2.3_TEST-1 + a few extra commits. Check out the change-log in Post #2.
Not tested > I have a SM-N920C
- XDA RULE #1 'SEARCH BEFORE POSTING". Please READ Posts #1-3 BEFORE flashing !!
- Please CLEAR SYNAPSE DATA before flash: device settings > Applications > Application manager > Synapse > force stop > clear data
Have fun
Cheers
UITA
thank you again! can you give us an idea as to..what s next? i mean in the next version of the kernel? do u have any priorities?
- More Note5 variant support
- UKSM
- KT governor ?
- PEWQ changes
- SELinux permissive / enforcing experiments
- Fix root being left as r/w. Should be r/o
- Toolchain - think we can do better than a 2014 build
- Headset audio - not work during calls (try take a look)
- update build scripts for gitHub to include ramdisks and auto re-pack to boot.img (will take loads of time and testing)
- Further Synapse additions and tweaks
- Update my Tab-S kernels !
.
.
.
- List goes on and on, but not all at once
YesI have the same exact set up so it's not the rom. Did you clear Synapse settings?
Your time is much appreciated.. glad your back man.Just testing Linaro toolchain 5.2 used by Arter. No in-call reboots unlike the newer 5.2.1...................
I'll give it a good test
Edit: unfortunately, false hopes. perhaps there are a few patches somewhere to help. A lot of trial and error...........
[COLOR="Red"]PLEASE SHOW RESPECT TO ACTUALLY [COLOR="PURPLE"][B]READ POSTS #1-3[/B][/COLOR]
[URL="http://xdaforums.com/announcement.php?a=81"][B]XDA RULE #1 "SEARCH BEFORE POSTING"[/B][/URL] (GOOGLE, XDA & THREAD),
IF YOU DON'T LIKE A UP-FRONT "MATTER OF FACT" APPROACH,
[B]THEN DON'T BOTHER POSTING[/B]. [/COLOR]
* Based on official Samsung source: [URL="http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=n920"]Samsung OSRC[/URL]
* ramdisk source: N920TUVS2COKC
* Compiled with Linaro gcc-linaro-4.9-2015.02-3-x86_64_aarch64-linux-gnu
* Linux 3.10.96
* [COLOR="red"]AUTO-ROOT binary v2.52[/COLOR] & Install busybox v1.24.1-Dorimanx
* [COLOR="Red"]KNOX WARRANTY VOID: 1[/COLOR]
* [COLOR="red"]SELinux PERMISSIVE[/COLOR] (for Titanium Backup and other apps to work correctly)
* adb insecure
* stock dt.img
* init.d script support (drop in script & set permissions to 755 or 777 and reboot)
* [COLOR="red"]DEEP SLEEP FIX[/COLOR]
* [COLOR="red"]IN-CALL REBOOT BUG "FIX"[/COLOR]
* Possible Screen Mirroring / AllShare Cast fix
* Secure storage = false (should prevent WIFI settings & passwords wiping on reboots)
* RAM management tweaks
* GearVR [U]reported[/U] working (depends on ROM/firmware version installed)
* [B]Synapse app support[/B] for many kernel configurations + more !!
* Many descriptions are in the app ! If you require more info, don't be lazy, please [B]SEARCH[/B] like I did ;)
[COLOR="Red"]* Under-volting can cause instability
* Over-clocking can cause freeze/reboot, heat & damage to CPU, GPU or other hardware
* Any customizations may void warranty
* May not be suitable for your device or customizations
* UpInTheAir is NOT responsible, the person you see in the mirror is !![/COLOR]
1. DEVICE MODEL ?
2. ROM and firmware version (build number, boot-loader etc) ?
3. EXACT steps taken to reproduce YOUR issue
4. Screen-shots (if applicable)
5. Did you read Posts #1-3 completely?
6. Did you search the thread, XDA or GOOGLE?
7. Did you follow the install instructions EXACTLY?
8. What was your previous kernel?
9. Do you have any other known kernel tweaking apps, scripts or mods? ([B]remove them[/B]). [COLOR="Red"]This includes Xposed etc[/COLOR]
10. Try older kernel (if available)
11. Factory reset ?
12. Try latest stock [B]UNMODIFIED[/B] firmware (without custom ROM - if you have installed) and factory reset
13. Delete your ROM BusyBox (kernel uses it's own in /sbin)
lsmod
This feature allows to have two different intervals for dirty page
writebacks and to dynamically manage them when the system has been
resumed (it's active) or when has been suspended.
Three new procfs parameters are exposed inside /proc/sys/vm path:
- dynamic_dirty_writeback is the activation status of this feature,
set 1 to enable it, set 0 to disable it and use the standard behaviour
- dirty_writeback_active_centisecs is the interval for the dirty page
writebacks when the system is active (screen on)
- dirty_writeback_suspend_centisecs is the interval for the dirty page
writebacks when the system is suspended (screen off)
This feature is in part inspired on Francisco Franco's patch:
https://github.com/franciscofranco/mako/commit/34d79548cf16b69c7d0154836018e7f258a22947
There are literally pages and pages of you, your followers and others that have come into this thread doing exactly what this rule says not to. If I were to clean up every comment that belittles, berates or offends someone, their intellect or their abilities, you wouldn't have much of a thread left here my friend.2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Posting for others to google search something or read the OP is absolutely fine, but keep in mind that not everyone will turn up the same results you did, either because they are unsure what they are looking for, or they have searched a different query string. It happens. Do we at XDA expect hand holding and spoon feeding? No, but we do expect more than our developers just dumping a project in the forums and referring people to the OP that may or may not have the requested information. As for the rest of the members, when they begin to get belligerent with other users, as the OP it's your job to keep your threads on topic and friendly. We are here to assist you, clean whatever needs to be cleaned and sort out the riffraff, but we can't do that if it's not reported or you include yourself in it.10. Help others if you can.
If you see posts from others where you can help out, please do so. This place exists because people are helping each other, and even if you are relatively new to the matter, there's probably quite a few people with less experience than you, who could benefit from what you've learned. Don't be shy.
You are exactly right, took the words right from my mouth.You realize this back and forth does little for anyone at this point. This isn't Facebook, I am assuming you have made your point? Otherwise you are just making more posts people will have to scroll through looking for answers.
Sent from my SM-N920T using Tapatalk