Develop Bugs

[Q] Problem with HTC TOUCH PRO

Hello guys, I have to ask you a question that I can not resolve for months.
I have a HTC TOUCH PRO, and every kernel I try to always have problems.
At first the device works well and is also very fast, but hopelessly after a while it stops. When you first start can last hours and then crash, but already the second hangs after a few seconds.
I've tried almost every kernel, even the "msm-htc-linux-20101204_005141-package.tar" by the comments that seems to be the best for my device, but nothing. I'm desperate and I do not know what to do.
Can you tell me how to solve this?
Waiting for reply.
Thanks to everyone that I will respond.

I'm not sure what your problem actually is. Sounds like the system_server bug... Make a call to voicemail, phone should speed back up.
Also, the newest kernel is 1253. The autobuild service has fallen behind GIT, see this thread to get the most up-to-date GIT commits.

i must only update with this kernel?

master9 said:
i must only update with this kernel?
Click to expand...
Click to collapse
The kernel (zImage) goes hand-in-hand with the modules file.
Still not sure what you mean tho.

The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.

master9 said:
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
Click to expand...
Click to collapse
You say it's fast, but the phone freezes...?
Where does it freeze?
XDAndroid is far from 'stable'...

Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.

djdafreund said:
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
Click to expand...
Click to collapse
O___o I did not realize that. All RAPH's...? Do we have logs? I need information man!

I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.

djdafreund said:
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
Click to expand...
Click to collapse
Oh right, that. Screen shifting seems isolated to the RAPH800 and DIAM500. Probably RAPH500 as well, and I'm not sure what the other DIAM is... perhaps there is a DIAM800, not sure. Either way, seems to only be the CDMA devices.

But of course LOL. I personally love my Touch Pro, but WOULD love to upgrade if i had the money. But yeah, the dreaded shift problem til it's fixed. Not a BIG deal for now, since previous kernals will hold us off til that's fixed.

Nothing, i have the same problem

master9 said:
Nothing, i have the same problem
Click to expand...
Click to collapse
You still haven't properly elaborated on your actual problem. Vagueness will get you nowhere, except frustrate people.

I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.

master9 said:
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
Click to expand...
Click to collapse
Seems to be a pretty big language barrier here... "any kernel I mountains"...?
So has Android ever worked for you? What build(s) have you tried?

Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.

master9 said:
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
Click to expand...
Click to collapse
What about FRX03? I can't really help you with any build but that one - if you're using a different build, you'll need to get help in those threads. Generally if you just throw up a post like this, use FRX03 (or AOSP, whatever) as your base to test off of.
If it works in that build, but doesn't work in one of the others - then it's that build. If they fail in both builds, then it's a general issue with Android - or, you've just done something wrong .

I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.

Keep in mind, most neopeek variants require two partiations to be setup as primary (one FAT32 and one EXT2). You might find it a tad difficult in finding someone to help you troubleshoot your process unless you seek help from with-in the thread that you downloaded superfroyo or any other neopeek variants. It is rare to find but then again, you could just as easy try out FRX04 and post your feedback in that thread too. See THIS post for info on downloading the FRX04 update file but you will probably need to downoad THIS package first, then update the system.ext2, rootfs and kernel package after the fact. Stinebd has links for the rootfs in his sig.
n-Joie! (Enjoy)

master9 said:
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Click to expand...
Click to collapse
Again, you're using funky version. As R^72 said, get help with those versions in that thread.
If you want help, at least try FRX03. You haven't even given it a shot. Then you can update to FRX04, and if that all works - then try something more complicated like a Neopeek build!

[Q] Problem with root on custom rom

I am currently using the SyndicateROM Frozen 1.2 rom, but I've noticed an issue recently. I've only just registered, and because of that, I can't post in the thread for this rom to ask my question. (http://forum.xda-developers.com/showthread.php?t=1131544)
My issue is with the latest Superuser app. It successfully installs the 3.0 su binary, but when the phone is rebooted, the 2.3.1 su somehow keeps coming back. Any other changes to the system folder stay, so it seems like it's not entirely being overwritten, so I'm not sure why the su binary keeps reverting when the phone reboots. It didn't have this issue in the stock rom, so I have to assume it's something wrong with the custom rom, or the included kernel.
I know the 2.3.1 su is perfectly functional and I don't specifically need the 3.0 Superuser app, but I always prefer to have the latest software when working with things like this. A flaw like this causes some serious problems for me.

On the first page of q & a:
http://forum.xda-developers.com/showthread.php?t=1296148
On the second, if you bothered to look:
http://forum.xda-developers.com/showthread.php?t=1294977
http://forum.xda-developers.com/showthread.php?t=1291457
http://forum.xda-developers.com/showthread.php?t=1290966
Now please, search first. I see your 1 post count but these are all easy to find.

Sorry about that. I did try to use the Search, and it didn't come up with anything (perhaps I was searching the wrong thing). I skimmed through the topics too, but I must have missed it.
Thanks for the help. Now it's just a matter of getting the maker of the rom to fix their error.

chuman72486 said:
Sorry about that. I did try to use the Search, and it didn't come up with anything (perhaps I was searching the wrong thing). I skimmed through the topics too, but I must have missed it.
Thanks for the help. Now it's just a matter of getting the maker of the rom to fix their error.
Click to expand...
Click to collapse
Actually, its the kernel. Are you running the one that came with Syndicate Rom Frozen?
hint, reply to get your post count to 10

That would be correct. It's the only kernel I found that supports voodoo and overclocking to 1.2GHz. Before using the rom, I had another kernel that supported voodoo, but no overclocking.

chuman72486 said:
That would be correct. It's the only kernel I found that supports voodoo and overclocking to 1.2GHz. Before using the rom, I had another kernel that supported voodoo, but no overclocking.
Click to expand...
Click to collapse
Find Genocide 2.0 and flash that. It has superuser 3 fixed and it can overclock to 1.4 ghz, voodoo included.

I'm pretty sure that's the kernel I have. When the phone boots, it says Genocide 2.0 below the Samsung logo.

chuman72486 said:
I'm pretty sure that's the kernel I have. When the phone boots, it says Genocide 2.0 below the Samsung logo.
Click to expand...
Click to collapse
Hes updated it to work with superuser 3. Check the thread

I just noticed that. Hopefully he fixed the sbin issue instead of just loading the faulty version with 3.0 so we don't end up in the same issue when the next su update comes around.

chuman72486 said:
I just noticed that. Hopefully he fixed the sbin issue instead of just loading the faulty version with 3.0 so we don't end up in the same issue when the next su update comes around.
Click to expand...
Click to collapse
By that time we will have official Gingerbread and Cm7 compliant Cyanogenmod lol

[ROM] ZN Custom Firmware - 1.014.00_ZN-v1.2

Hello. Here's the second version of our ZN Custom Firmware. It is created by ZeroNull and vdsirotkin (4pda.ru). The original post is here.
WARNING - If it works on your device, be careful, as with an unlocked bootloader you can brick you tab faster than you can imagine.
Installation:
1) You'll need to do everything, what is written here or here. If your bootloader is already unlocked, and recovery is installed - you can miss this point.
2) Download the firmware - http://depositfiles.com/files/smnuqxxei
3) Install it using CWM or TWRP
4) That's all!
Features:
Patched 1.014 ICS kernel. Now mounting of /system partition is unlocked
modded boot.img
Better battery saving in standby
Rooted
NTFS SD cards supported
Init.d scripts enabled
bind-dir with autorun support from init.d (not working with NTFS)
Superuser and AcerRing is integrated in system partition
All Acer's and some Google's apps removed
Packages included (in user partition, removable via Apps Manager in Settings)
Adobe flash player
BSPlayer Lite
GPS Test
ES File Explorer
Quadrant Standart
Quick Boot
QuickBoot
Titanium Backup
Touch Recalibrate
"DIGI Clock" and "Weather forecast" widgets
Custom build.prop integrated
Root mode for adb unlocked
AcerRing with corrected background picture
Battery in %
Custom bootanimation: Frosty-Boot [v.Acer] with GEARS for Acer Iconia Tab A100
Screenshots:

First . Anyways, some screenshots would be nice .

Theonew said:
First . Anyways, some screenshots would be nice .
Click to expand...
Click to collapse
And what would you like to see on them?

ZeroNull said:
And what would you like to see on them?
Click to expand...
Click to collapse
The Acer ring for one. Were any modifications done to the UI, or does it have the stock look?

There are no UI changes, all the changes are made "inside" of the firmware

is this just a custom boot image?
If you have changed ro.product.model to A500, the Acer recovery installer app (once I release an A100 version) will think its an A500.
Sent from my SPH-D710 using Tapatalk

no, it's not only the boot.img, there are some other changes.
Well, if someone have installed recovery to install this firmware, so he or she won't need to install it again. Am I right?

I can't figure out how to download this. I don't read rushian (or greek or whatever that is). I entered the captcha and then clicked the link that LOOKed like what I was supposed to and it starting download some file ending with .msi so I canceled it.
Usually, custom ROMs come with their own boot.img, so if someone installs then, then a custom ROM, then this gets overwritten. if they install this, on top of their custom ROM, it'll work, unless the custom rom had a custom boot.img that it was dependant on.
Can you tell me if ro.product.modelalias still says A200 with this patch?

Sorry, tomorrow i'll upload it to some other place. To download this file untick where it's written smth about Яндекс.Бар. And there won't be any .msi file. Or use Google Translate
You are right, there is a custom boot.img, and many features in the firmware depend on it. But boot.img is not the only feature of this firmware. That was what I wanted to say
In build.prop it's written ro.product.modelalias=A100.

ZeroNull said:
Sorry, tomorrow i'll upload it to some other place. To download this file untick where it's written smth about Яндекс.Бар. And there won't be any .msi file. Or use Google Translate
You are right, there is a custom boot.img, and many features in the firmware depend on it. But boot.img is not the only feature of this firmware. That was what I wanted to say
In build.prop it's written ro.product.modelalias=A100.
Click to expand...
Click to collapse
Got it, downloading now. The link dissappeared when I hit the Translate button. But unchecking the checkbox worked. Thanks!
I updated my code to look at both ro.product.model and ro.product.modelalias.
Thanks!

the slowed down cpu is for better battery life? might be installing later

You're right.

What impact would slowing the cpu have on the overall performance? Thanks

utctigers said:
What impact would slowing the cpu have on the overall performance? Thanks
Click to expand...
Click to collapse
Some tasks (especially heavier ones) will not be as snappy (only if the cpu is limited to the slower speed also depending on how slow it is set to). The battery life should be significantly better though.

thanks, any plan on adding USB host mode?

Theonew said:
Some tasks (especially heavier ones) will not be as snappy (only if the cpu is limited to the slower speed also depending on how slow it is set to). The battery life should be significantly better though.
Click to expand...
Click to collapse
is there a reason we cant incorporate smoothass governors etc into the kernel? limiting to 500mhz is pretty unproductive...if your require alot of processing itll take twice as long at 500mhz to accomplish its instructions...thus using the cpu twice as long as it would have if it was able to ramp up to 1ghz to take care of it.
lower cpu is only helpful in an idle state to conserve power...why on earth would we want to lock it at half its speed?
Sent from my SGH-I897 using xda premium

ptesmoke said:
is there a reason we cant incorporate smoothass governors etc into the kernel? limiting to 500mhz is pretty unproductive...if your require alot of processing itll take twice as long at 500mhz to accomplish its instructions...thus using the cpu twice as long as it would have if it was able to ramp up to 1ghz to take care of it.
lower cpu is only helpful in an idle state to conserve power...why on earth would we want to lock it at half its speed?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
No, there is nothing stopping the integration of more governors into the kernel. If you do heavy usage on the tab with the cpu underclocked so low (and limited at that point), then yes, it will put more strain on the processor. One would want it set so low for conserving battery (and not really using the tab for anything e.g. While you're sleeping). I usually set profiles on my devices to lower the frequency and set the governor to conservative when the screen is off (never done it on this device though).

Raul77 said:
thanks, any plan on adding USB host mode?
Click to expand...
Click to collapse
Our hardware (motherboard) doesn't support it.
ptesmoke said:
is there a reason we cant incorporate smoothass governors etc into the kernel? limiting to 500mhz is pretty unproductive...if your require alot of processing itll take twice as long at 500mhz to accomplish its instructions...thus using the cpu twice as long as it would have if it was able to ramp up to 1ghz to take care of it.
lower cpu is only helpful in an idle state to conserve power...why on earth would we want to lock it at half its speed?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
The reason is called "kernel sources". Without 'em we can't do anything (overclock, add governors) with our processor.
If you look at the usage of frequences, you'll see, that 80% of the working time the frequence is 200 mgz. And while testing, I didn't meet any problems with 456mgz, all the programs and games work smooth, and still 80% of the usage time is on 200mgz.
If you don't like this slowing down, why on earth you can't disable is? everything is written in the 1st post

thx
Thx to you !!!
Il Will try it today.
Systèm in RW mod ?
The memory swap is integrated ?
Obligation of full wipe before installation ?
And the last question... have we to make a advanced restoration of the unlocked Boot with CWM after flashing.
THANK YOU in advance for your answers to my question.....

samco08 said:
Thx to you !!!
Il Will try it today.
Systèm in RW mod ?
The memory swap is integrated ?
Obligation of full wipe before installation ?
And the last question... have we to make a advanced restoration of the unlocked Boot with CWM after flashing.
THANK YOU in advance for your answers to my question.....
Click to expand...
Click to collapse
Yes, it's included in root access
If it's not written about memory swap, than it's not intergated
No, /data must not be wiped, and /system/ will be wiped automatically, but only in 1.XX versions. 1.XX.X are only a kind of small update to already installed firmware
No, recovery and bootloader are deleted from this package, so they will stay as they were.

[Kernel] Deported / Stockish [Sprint Discussion]

This is the support thread for the Sprint variant of the StarKissed Note 4 kernel.
This kernel currently supports all North American carriers through the use of specialized release packages that will detect your device version and make appropriate adjustments.
Kernel Development Thread:
http://forum.xda-developers.com/showthread.php?t=2915824
Issues, Reports, & Configuration
Direct installation available via Flashify (for root users) - Android Apps on Google Play
Heimdall with the S5 patch is needed to flash from a computer. Odin cannot flash this kernel.
Additional information for Sprint variant:
Potentially Unavailable:
Potentially Unsafe:
Incomplete / Inactive:

OK, I've tried everything, time to ask for help. I've used quite a few kernel tuning apps, including your own, and no matter what i try, my settings won't restore on boot for one, and two, no matter what I set my min/max CPU to it will randomly jump back up to 1728 Min and 2803 Max and change my governor to interatcive. I'll notice my battery draining quicker, that's when I catch it and adjust it down. What am I doing wrong?
Sent from my SM-N910P using Tapatalk

egodriver07 said:
OK, I've tried everything, time to ask for help. I've used quite a few kernel tuning apps, including your own, and no matter what i try, my settings won't restore on boot for one, and two, no matter what I set my min/max CPU to it will randomly jump back up to 1728 Min and 2803 Max and change my governor to interatcive. I'll notice my battery draining quicker, that's when I catch it and adjust it down. What am I doing wrong?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Nothing. It's an issue with the policies. I will be compiling a new version shortly that should address it.

A new version has been posted that should resolve the reset on boot.
One thing to keep in mind is that if you are using an app to handle your settings, allow the phone to fully boot before launching the app. Sometimes opening it right away will end up reading the boot settings and replacing the settings it was about to load with those. The startup settings are hard-coded into the kernel and changing them tends to cause a bit of instability that isn't worth introducing.

still no luck
twistedumbrella said:
A new version has been posted that should resolve the reset on boot.
One thing to keep in mind is that if you are using an app to handle your settings, allow the phone to fully boot before launching the app. Sometimes opening it right away will end up reading the boot settings and replacing the settings it was about to load with those. The startup settings are hard-coded into the kernel and changing them tends to cause a bit of instability that isn't worth introducing.
Click to expand...
Click to collapse
It still doesnt stick. I try to underclock the min and it still goes up to 1497600.

Thank you very much for the suggestions yesterday, but it looks like not using the _64 toolchain was the problem.
New problem, it boots to the download mode screen saying boot failed. I thought I'd start simple to troubleshoot. If I break apart one of your images (14 MB) and rebuild it with:
Code:
mkbootimg --kernel twisted-zImage --ramdisk twisted-ramdisk.cpio.gz -o boot.img
The resulting boot.img is 11 MB, whereas yours is 14 MB, and it fails to boot. I'm not sure why it's several MB smaller. I looked at your script, but the image generation is in another script it seems. Am I using an old mkbootimg or something? I don't know could account for 3 MB at the mkbootimg stage. I also tried using unmkbootimg to get the other flags shown below, but that didn't help.
Code:
--base 0x1dfff00 --cmdline 'splash=silent console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --pagesize 4096
Thanks again for any suggestions.

ffolkes said:
Thank you very much for the suggestions yesterday, but it looks like not using the _64 toolchain was the problem.
New problem, it boots to the download mode screen saying boot failed. I thought I'd start simple to troubleshoot. If I break apart one of your images (14 MB) and rebuild it with:
Code:
mkbootimg --kernel twisted-zImage --ramdisk twisted-ramdisk.cpio.gz -o boot.img
The resulting boot.img is 11 MB, whereas yours is 14 MB, and it fails to boot. I'm not sure why it's several MB smaller. I looked at your script, but the image generation is in another script it seems. Am I using an old mkbootimg or something? I don't know could account for 3 MB at the mkbootimg stage. I also tried using unmkbootimg to get the other flags shown below, but that didn't help.
Code:
--base 0x1dfff00 --cmdline 'splash=silent console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --pagesize 4096
Thanks again for any suggestions.
Click to expand...
Click to collapse
Kernels now use DTB. The other script handles that. You also may need a new mkbootimg if you have never dealt with DTB. Older binaries don't include the parameters.
In all honesty, most of these questions can be answered just by looking at the commits in the stockish repo. It doesn't contain all of the extra modules and modifications, but it has the same core changes to build it. If 50 commits seems like too much to dig through, you may not want to develop kernels. You will typically be wandering through kernels with 1K+ commits looking for one change.

twistedumbrella said:
A new version has been posted that should resolve the reset on boot.
One thing to keep in mind is that if you are using an app to handle your settings, allow the phone to fully boot before launching the app. Sometimes opening it right away will end up reading the boot settings and replacing the settings it was about to load with those. The startup settings are hard-coded into the kernel and changing them tends to cause a bit of instability that isn't worth introducing.
Click to expand...
Click to collapse
Still no luck with the new version.

fifapro23 said:
It still doesnt stick. I try to underclock the min and it still goes up to 1497600.
Click to expand...
Click to collapse
fifapro23 said:
Still no luck with the new version.
Click to expand...
Click to collapse
Nothing was changed in respect to that issue as you have noted by replying to the same post both times.

fifapro23 said:
It still doesnt stick. I try to underclock the min and it still goes up to 1497600.
Click to expand...
Click to collapse
I just read this statement again and realized this is our first real case of PEBCAK
The minimum is the absolute lowest the cpu is allowed to drop.
The maximum is the absolute highest the cpu is allowed to increase.
It is a range, not strictly one or the other.
If you set your min to 268 and max to 2.5, it is not 268 or 2.5 only. It could also be anything between them, such as 1.5 or 422
Yankeractive tends to favor 1.5, but that is in the governor design. It's something that will eventually be adjusted during cleanup.

sorry

I reverted back to 20.47 from 22.12 because it was sticking at 1.4. Also for fast charge options, what does failsafe do? And do we just keep fast charge to disable or force ac?

ryanalan82 said:
I reverted back to 20.47 from 22.12 because it was sticking at 1.4. Also for fast charge options, what does failsafe do? And do we just keep fast charge to disable or force ac?
Click to expand...
Click to collapse
I haven't looked into failsafe. I used the defaults from the Note 3 for that since I never use it.
Depends if you use it or not. Disabled is will not boost USB or wireless charging. Force AC will boost them to emulate an AC charger.

Ok now having the 1.4 sticking on 20.59. Reverting to earlier today.

ryanalan82 said:
Ok now having the 1.4 sticking on 20.59. Reverting to earlier today.
Click to expand...
Click to collapse
The update was only posted about 5 minutes ago. It will show 1.4 when you touch it because that is the touch boost.

How do i download your kernel i csnt figure out how to find it.. it just keeps tskimg me to mega website????

shawn01 said:
How do i download your kernel i csnt figure out how to find it.. it just keeps tskimg me to mega website????
Click to expand...
Click to collapse
Installation Instructions:
Download the image file from Goo or Mega to install via flashify, rashr, etc
Click to expand...
Click to collapse
If you don't feel like looking back at the big discussion in the dev thread on issues with Mega, that is the alternative.

sorry im struggling here. I installed twrp and booted into recovery and now i cant boot my phone back it goes nack to twrp but something comes up saying kernel is not seandroid enforcing set warranty bit: kernel. I never fladhed anything but twrp. So im hoping to find stovk kernel zip so i can flash fro, twrp..

shawn01 said:
sorry im struggling here. I installed twrp and booted into recovery and now i cant boot my phone back it goes nack to twrp but something comes up saying kernel is not seandroid enforcing set warranty bit: kernel. I never fladhed anything but twrp. So im hoping to find stovk kernel zip so i can flash fro, twrp..
Click to expand...
Click to collapse
If it says warranty bit is kernel, that isn't booting back into recovery, that is a normal boot. You just have to be patient until it finishes. The downloads here are not the stock kernel anyway. Both versions are modified kernels.

It goes back to trwp recovery every time

Q&A: [KERNEL] [ROOT] [SM-G920P]SkyHigh MM 6.0.1 Kernel

For Q&A regarding the tdhite port of the SkyHigh kernel.

Is there a specific version of Synapse we need to install? The one of the Play Store doesn't seem to work. I get boot settings cancelled.

Boot settings will cancel until you set things and reboot. Also you need to wait a few minutes before rebooting because it will consider a reboot in less than two minutes from saving settings means instability. The first boot is considered unknown so unstable.
I am using the standard Synapse and set a bit of over and underclocks, ktoonservative governor and all works well.
Sent from my SM-G920P using Tapatalk

What settings would you recommend for battery saving?

Euronymous88 said:
What settings would you recommend for battery saving?
Click to expand...
Click to collapse
+1 for this

Well change governor to ondemand so it uses power when u use it. Im not sure but You have to find something that works for you test it on a whole battery cycle. Im tryn the ktoonservative governor. Theres alot of guides on the govnerors so many im not sure where to send a person.

This kernel has many features so can you guys tell me the best cofiguration of this kernel on synapse(gov , cpu freq ,..etc) please . im new here :d
Sent from my SM-G920P using Tapatalk

I'd suggest under-clocking both a57 and a53 t o minimum. Then set governor to ktoonservative. Go to the a53 gov page and set no_extra_cores_screen_off to 0 so you get sufficient background cycles, for example bluetooth headset music listening.
Sent from my SM-G920P using Tapatalk

are there any compatibility issues with xposed
i was getting reboot every 5 to 10 minutes till i re flash the xposed zip which stopped the reboot but when i get calls and screen goes off the phone locks up till the caller disconnects. the screen is not responsive. not sure if xposed is to blame but I rebooted into safe mode as well no dice

cyberone3 said:
are there any compatibility issues with xposed . . .
Click to expand...
Click to collapse
The screen blank think is not xposed. I've been able to reproduce another way.
So, question for screen blank issues (anyone): are you using the ktoonservative governor?

Fail private mode!
im using Galaxy S6 G920P & i flashed your kernel into my device but when i open my private mode, it's fail to open :'( a lot of my pictures in there. Can you help me to fix private mode? thanks!!!
Sorry my bad English.

tdhite said:
What ROM? I am not seeing any phone issues on stock ROM with this kernel and I use it extensively. So not sure what's up without a log or something to debug.
As for xposed, I never use it and do not plan to as it is the worst form of security hole. Root is one thing, but granting something rights to your entire Android API with full root access at all times is just plain asking for trouble, imho.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
stock mm with exposed work nice and snappy till i get a call then after a few minutes with screen off seems to lock up till i'm off the call

My phone won't boot wit this kernel. Also causing problems wit Xposed (when/if it does boot).

I have no problems ran it a week and also did a fresh start reflashing a rom and skyhigh kernel still no problems with xposes or calling what modules yall running.

JoeFCaputo113 said:
My phone won't boot wit this kernel. Also causing problems wit Xposed (when/if it does boot).
Click to expand...
Click to collapse
Ummmm, first it won't boot, then it has trouble with xposed when it does boot. huh?
What problems? Posting that there are issues is great, but I obviously need a tad more to go on than that to fix anything.

072868532 said:
im using Galaxy S6 G920P & i flashed your kernel into my device but when i open my private mode, it's fail to open :'( a lot of my pictures in there. Can you help me to fix private mode? thanks!!!
Sorry my bad English.
Click to expand...
Click to collapse
Knox and root will cause havoc with private mode. Please search the threads (or just do a Google search and you'll get a bazillion pages for "samsung private mode knox root).

Jimmy1life said:
I have no problems ran it a week and also did a fresh start reflashing a rom and skyhigh kernel still no problems with xposes or calling what modules yall running.
Click to expand...
Click to collapse
xposded module
allowlongsms
amplify
appopsxposed
enable batterystats permission
greenify
instragram suggestions hider
neopowermenu
nosafevolumewarning
pandora patcher
secure settings
snapprefs
tumblr adaway
use usb for marshmallow
volume slider delay fix for marshmallow
xinsta
youtube adaway
youtube background playback

tdhite said:
Ummmm, first it won't boot, then it has trouble with xposed when it does boot. huh?
What problems? Posting that there are issues is great, but I obviously need a tad more to go on than that to fix anything.
Click to expand...
Click to collapse
Yes IFFF it does happen to boot (only got it to boot once) I kept getting FC with Xposed. On boot screen it never says "Kernel is Not SEAndroid Enforcing" like it usually says with other kernels. It just gets stuck at the splash screen 99% of the time.

Yea i use with no problems.
gravity i just like pop ups disabled and long press back to kill
youtube adblock
greenify
Well good luck guys

JoeFCaputo113 said:
Yes IFFF it does happen to boot (only got it to boot once) I kept getting FC with Xposed. On boot screen it never says "Kernel is Not SEAndroid Enforcing" like it usually says with other kernels. It just gets stuck at the splash screen 99% of the time.
Click to expand...
Click to collapse
Which splash screen? Samsung or sprint? If the latter, please get me a logcat of the boot: hook up usb and issue this:
asb shell logcat >boot.log
Post that log please.
Sent from my SM-G920P using Tapatalk