[Kernel]netarchy-toastmod, Stable: 4.3.1 Beta: 4.3.4 (17-Mar-2011) Now With HDMwIn
- Status
The only difference between the two are the init sequences for the epson, the values in the second build are from the htc released source while the first comes from the makeshift kernel.
Sent from my Evo4g with tapatalk
Sent from my Evo4g with tapatalk
Actually at the moment the epson gets higher fps, though when proper fixes are found for both there really should not be a difference in performance.
Sent from my Evo4g with tapatalk
Sent from my Evo4g with tapatalk
Which is "better" is largely subjective, both will eventually be properly uncapped and fps isn't likely to be better on one vs the other
Sent from my Evo4g with tapatalk
My biggest concern from the get go is the screen tearing. It's extremely annoying lol. Do you have any idea of a difinitive fix for this or anything of the sort?
Bah, I'll take screen tearing any day over choppy screen and touch lag.
But yes, better vsync is better.
Is there anywhere to get the stock kernal in case you wanna go back to stock? Ive been looking but cant find it anywhere.
So, the only problem that remains with this kernel, is the screen tearing? Nothing "Breaks" with this? (Camera, Wifi, Bluetooth, etc.)
I am running Damage Control 3.2.3, with the Aloysious theme.
What is "Screen tearing"? Is there a video or screenshot somewhere, to see this, before I flash, so I can decide if it is something I am willing to deal with?
I am running Damage Control 3.2.3, with the Aloysious theme.
What is "Screen tearing"? Is there a video or screenshot somewhere, to see this, before I flash, so I can decide if it is something I am willing to deal with?
The FPS fix seems to be consistent, but while it's always there as far as FPS2d is concerned, you can flip through the 7 home screens and it feels like you have it applied for a few swipes. But after a few swipes, it seems to start the touch lag again and slows down when swiping. It seems you can resume the quickness by opening an app and then coming back to the home screen. But like before, it goes back to having the touch lag after a few seconds; almost like something in the kernel kicked into action, like a governor on the fps. The slow down also occurs in the app list as well.
I hate to criticize, especially considering the camera actually WORKS on the kernel, but another note is when you record video on the camera, the screen tearing appears in the video itself, even when watching what you had recorded you can see the tearing. I will say though, the tearing in this fix is definitely less noticable. In the very first one, it was pretty bad, and the camera didn't even work.
I hate to criticize, especially considering the camera actually WORKS on the kernel, but another note is when you record video on the camera, the screen tearing appears in the video itself, even when watching what you had recorded you can see the tearing. I will say though, the tearing in this fix is definitely less noticable. In the very first one, it was pretty bad, and the camera didn't even work.
Last edited:
I can't reproduce it as well (It happened twice last night). Must of been a coincidence or something. FYI using with latest Fresh rom and works perfect. I will definitely keep my phone on this kernel. Thanks again for modifying this kernel for us Epson folks
You can find the stock kernel here:
http://outboundlink.us/anxo/dr_ta_1...ww.4shared.com/file/3Urm5V15/stockkernel.html
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
25NOTICES: If you are noticing abnormally high battery drain and/or uptime, and you've updated to PRI 1.90, it has come to my attention
that this PRI has been problematic for a number of people, often resulting in large uptimes and/or poor battery life.
This issue affects people regardless of whether or not they are using a custom kernel
Downgrading your PRI and NV to 1.77 has been reported to resolve this issue.
You can find all PRI and NV versions by clicking here.
Due to troubling reports of battery issues possibly caused by the SBC battery charger modification, it is worth mentioning that by using any SBC build, you
fully assume any and all potential risks that the SBC modification may pose.
2.2 Kernels (THESE WILL NOT WORK ON 2.1 ROMS):
These have only been tested against the rooted HTC 2.2 stock rom, they *may* work on the various custom 2.2 roms,
but this is NOT guaranteed. MAKE A NANDROID BACKUP JUST IN CASE!
-----------------------------
Beta Testing Builds
When making a post about any issues concerning beta builds, please include ALL of the
following information if possible:
1. Which kernel build(s) (ie; bfs/cfs havs/nohavs etc) are you using with the issue?
2. What Rom are you using?
3. If known, what OTA base is your rom using (ie; is it based on 3.29, 3.30, 3.70, etc)?
4. Does the issue persist if you go back to a stable kernel build?
5. The issue being experienced (obviously ;D)
4.3x:
To clear up some confusion that is apparently being spread around,
4.3x builds do in fact work on all current evo models, not just the newest model.
4.3.4:
--CFS builds--
No SBC:
4.3.4-cfs-nohavs-noUV-nosbc (No Undervolting)
4.3.4-cfs-nohavs-suv-nosbc (Static Undervolting)
4.3.4-cfs-havs-less-nosbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-nosbc (More Aggressive HAVS)
SBC: Use sbc builds at your own risk.
4.3.4-cfs-nohavs-noUV-sbc (No Undervolting)
4.3.4-cfs-nohavs-suv-sbc (Static Undervolting)
4.3.4-cfs-havs-less-sbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-sbc (More Aggressive HAVS)
For older beta builds click here.
---------------------------------------
Stable Kernels:
Universal Builds:
4.3.1:
--CFS builds--
No SBC:
netarchy-toastmod-cfs-havs-nosbc-universal
netarchy-toastmod-cfs-nohavs-nosbc-universal
--BFS builds--
No SBC:
netarchy-toastmod-bfs-havs-nosbc-universal
netarchy-toastmod-bfs-nohavs-nosbc-universal
These use Koush's anykernel for installation and should theoretically work on -any- rom.
*note* This is designed to be flashed over a phone that already has a working kernel of some kind flashed,
whether it's a stock kernel, or another custom kernel. In other words, if you can currently boot up your phone into whatever rom you have, this should work. ;D
The universal kernel also does not contain the tweak scripts of the normal build (ie; zipalign on boot and the dalvik tweak), it's intended to be a universally compatible kernel.
This also happens to mean the universal builds will probably work on CM
For older builds click here.
-------------9Rumors of my death are greatly exaggerated.
CFS Builds for 4.3.4 are up for testing, now with support for HDMI mirroring via HDMwIn, courtesy of Team Win.
Notes for Revision 4.3.4
- HDMwIn support added, you still need to download the free HDMwIn app
from the android market to use HDMI mirroring
- Timer tick set to 1000hz
- Unnecessary extra debugging turned off for public builds, should result in a small speed boost
BFS builds later, once I finish beating this wimax bug to death.6
I just found out about the SD card speed issue/fix a few minutes ago. Looking into it for integration in the next build.
New posts
-
[ROM] [UNOFFICIAL] [11] DotOs 5.2.1 [G530FZ/F/H]- Latest: PuszekReksio
-
-
