Status
Not open for further replies.
Search This thread

xak944

Senior Member
Jun 9, 2010
379
211
0
North Carolina
[*]Tethering with android-wifi-tether 2.0.5-pre7
  • I can now see the SSID broadcast (which is more than I've seen on any EVO FroYo ROM), connect, and get DHCP.
  • Traffic is PAINFULLY slow to the point of being unusable. Pinging the phone's gateway gives 1,000+ ms response times, with high packet loss. A simple ping google.com does not always succeed.

[/LIST]

After doing a dalvic wipe, cache wipe, uninstalling and then installing android-wifi-tether 2.0.5-pre8, IT WORKS!!! Getting over 1Mbit down on 3G. Ping times are good, and DHCP and routing tables are working fine as well. THANKS to all the devs that made this happen!

So happy to have tethering back on Froyo... :cool:

P.S. Posting this over tethered connection!
 

Biofall

Senior Member
Mar 17, 2009
2,314
538
0
Philadelphia, PA
I wasn't getting an error message, I just flashed and rebooted and was stuck on splast. I went into recovery, wiped cache partition and dalvik cache, then flashed kernal, then rebooted, finally worked. Will report on stats later. Also, what setCpu settings are yall using? I'm new to it and hopefully I can get some good profile advice now that this thread is booming
 

xak944

Senior Member
Jun 9, 2010
379
211
0
North Carolina
When you reboot, does it say 4.0 kernel -dirty like mine?
meh, I'll live with this right now until future updates.
With the dirty kernel, 8mp is working, as well as Google Goggles and such that weren't working with 3.7.8

# uname -a
Linux localhost 2.6.32.15netarchy-toastmod-4.0-g4afa082-dirty #2 PREEMPT Wed Aug 11 12:55:44 CDT 2010 armv7l GNU/Linux

Confirmed that Google Goggles is working now as well! Must've been something to do with the camera code.
 

scriptx

Senior Member
Jan 9, 2008
350
40
0
I can't seem to flash the new 4.0 fresh kernel. I'm running Fresh 3.1.0.1
In recovery i get
...
Writing BOOT:...
E:Error finishing BOOT:
E:Failure at line 8:
write_raw_image PACKAGE:toastmod.img BOOT:
Installation aborted

I've never had a problem like this flashing new kernels before, and I'm currently coming from 3.7.8b-fresh.

Suggestions?

I'm receiving the same error above when flashing the 4.0-Fresh-compatible kernel within clockworkmod recovery.

HW 0002 coming from (and reverting back to) 3.7.8b-Fresh compatible
 

RTC88

Senior Member
Jul 12, 2010
194
13
0
Hey I would also like to congratulate the brains and bunnies of Netarchy.. I thank you so much, I played back videos I made recording with your 3..7.8b Kernal and now on that 46" XBR9 it just looks amazing.. ;) Before, flashing the stock kernal and running videos recorded at higher frame-rates, absurdly bad! :p Now, it's all in there.. Thanks To you..

But.. I have a question, what in God's name is the Evo Switch everyone says is not working.. I have everyting working, thus, not knowing what is the Evo Switch, I am not sure now.. :rolleyes: Is this when you press the screen button next to the back arrow, I really dont know, this is sad.. I never thought this would happen, I know my Evo inside and out.. LoL..

K, thanks for the help, But, whats the Evo Switch?

It is basically an app that allows manual manipulation of the T2, thus allowing you to further refine your fps.

Sent from my PC36100 using XDA App
 

daving313

Member
Jul 8, 2010
39
0
0
Like the others have stated, thanks thanks thanks.

Still seeing partial wake usage coming out of Android that I do not get when running the stock kernel. Is this just a result of having higher performance?

Not running any task killers, overclock/underclock widgets. Thanks!
 

kmartburrito

Senior Member
Mar 17, 2006
723
50
0
39
Denver, CO
When you reboot, does it say 4.0 kernel -dirty like mine?
meh, I'll live with this right now until future updates.
With the dirty kernel, 8mp is working, as well as Google Goggles and such that weren't working with 3.7.8

Interesting, mine says that as well...

2.6.32.15netarchy-toastmod-4.0-g4afaXXX-dirty <--there were numbers where XXX is but wasn't sure if that was a SSH code, so I omitted them.

It said installation aborted though...I'm going to flash back to stock kernel and try again.
 

PlankLongBeard

Senior Member
May 24, 2010
1,173
64
0
On The Moon!
Thank You!

It is basically an app that allows manual manipulation of the T2, thus allowing you to further refine your fps.

Sent from my PC36100 using XDA App

I Thank You for your answer.. Another thing, Can you guys confirm that your getting pictures out on the "big screen" aside from videos out through HDMI? Or was that only created for videos, I think I remember doing pictures too...?

Damn you can tell, not using the HDMI on 3.7.8B and below, I have forgotten how this thing was even built.. LoL..

Thanks! ;)

Edit: Went looking for the App.. Typed Evo Switch in the Market, nothing.. Is that the Exact name? Would love to try this out.. Oh, and the pictures, anyone figure that one yet?
 
Last edited:

fazzmanic

Senior Member
Jun 14, 2010
199
6
0
Atlanta
Pretty sure OC is not working...

Can't chose anything other than 1152 (over 998)
Setting Performance or On demand just defaults back to On Demand
I also get no performance decrease/increase when setting back to stock speeds/oc.

FPS seems to be fine.
 
Last edited:

kindaskimpy

Senior Member
Dec 31, 2009
101
14
0
Miami, FL, U.S.A.
Thank you so much, netarchy! Man, you're fast! You rock!

Running Fresh3, Wireless Tether 2.0.5pre7 is working just fine for me. As a matter of fact, I'm using it right now to post here and test my 3G speeds.

I also ran Linpack, Quadrant and fps2d while over-clocked at 1.152GHz. Not impressed with my Quadrant score or my MFLOPS as reported by Linpack but yay for 53FPS!!!
 

Attachments

  • quadrant.jpg
    quadrant.jpg
    27.8 KB · Views: 54
  • fps2d.jpg
    fps2d.jpg
    25.5 KB · Views: 53
  • linpack.jpg
    linpack.jpg
    25.8 KB · Views: 57

randymac88

Senior Member
Aug 30, 2007
112
0
0
After doing a dalvic wipe, cache wipe, uninstalling and then installing android-wifi-tether 2.0.5-pre8, IT WORKS!!! Getting over 1Mbit down on 3G. Ping times are good, and DHCP and routing tables are working fine as well. THANKS to all the devs that made this happen!

So happy to have tethering back on Froyo... :cool:

P.S. Posting this over tethered connection!

I can confirm as well...posting this over tethered pre-7. Thanks netarchy! We'll see about battery life now I guess...
 

skydeaner

Senior Member
Sep 29, 2008
870
129
0
champaign
xda.chambanatech.com
btw confirmed working great on baked snack 2.5.

OMFG i've never actually tested a difference between an uncapped and a capped screen. haha it is so much smoother. All day today i have been on my phone because i left my laptop at home. Man oh man what a difference this makes in the smoothness of scrolling and whatnot. Thanks again. Now if i could get get you to make it 1.3ghz able


Man it is a big enough diference, i dont see how they can sell the evo without it. It literally pains my eyes to look at it with the stock kernel now.
 
Last edited:

RTC88

Senior Member
Jul 12, 2010
194
13
0
I Thank You for your answer.. Another thing, Can you guys confirm that your getting pictures out on the "big screen" aside from videos out through HDMI? Or was that only created for videos, I think I remember doing pictures too...?

Damn you can tell, not using the HDMI on 3.7.8B and below, I have forgotten how this thing was even built.. LoL..

Thanks! ;)

Edit: Went looking for the App.. Typed Evo Switch in the Market, nothing.. Is that the Exact name? Would love to try this out.. Oh, and the pictures, anyone figure that one yet?

It is not in market search the xda forum.

Sent from my PC36100 using XDA App
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 25
    NOTICES: 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.

    "netarchy-toastmod" is a kernel originally based on the GoDmOdE sources (Courtesy of Toast) integrating my work on fixing the fps for the Epson panels, and as of version 3.6.1, also integrating a fix for the Nova panels that does not require the use of Evo switch or manually setting any registers, etc, courtesy of work done by AssassinsLament (Well done on the nova fix). Special thanks needs to go out as well to Cyanogen and the cyanogen mod team, as a number of bugfixes and updates to the kernel in recent revisions have been ported over from cyanogen mod to enhance the overall netarchy-toastmod experience.
    So what's in the kernel?
    - Overclocking Support
    - HDMwIn (As of 4.3.4)
    - Audio gain tweaks (read: make it louder!)
    - Fps Fixes
    - tun.ko for openvpn users
    - CIFS support (as of 4.2.2)
    - BFS (in select builds)
    - BFQ (in select builds)
    - HAVS (as of 4.1.9)
    - Assorted fixes/tweaks (that are sadly too numerous to list here)
    - An army of rabid naked bunnies
    The zipalign script in the kernel's modified inits is based on code in the Damage Control rom, and extended to check more places for apps.
    The Dalvik code in the inits is courtesy of Ninpo/Hacre from the VillainRom team (over in the HTC Hero forums).



    mroneeyedboh has written a handy little kernel starter guide with a lot of general information about custom kernels and various terms you might see flying around (such as cfs/bfs, havs/nohavs, etc).
    You can view this guide Here

    Current Revision: Stable: 4.3.1 - For Froyo Sense roms | Beta: 4.3.4

    A note on multitouch:
    Some of you may have used my 5point multitouch test builds with success, others with failure. Research has shown that the Evo's contain at least 2 different versions of the touch sensor, one of which does not support 5point multitouch (but it DOES support 3point). You can check which sensor you have using adb by issuing the following command: "adb shell cat /sys/android_touch/vendor" and examining the result. If your result is ATMEL_x0080_x0016, your phone can support 5point. If your result is ATMEL_x004F_x0016, your phone will only support up to 3point.

    Disclaimer:
    While these builds have been deemed generally safe, it is not feasible to account for all possible combinations of custom roms and uses,
    custom roms may experience some breakage depending on how some features are set up, as these builds are not aimed at any one particular rom.
    As such your mileage may vary, use these at your own risk.
    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! :D
    If you get force closes on the camera, go to Menu -> Settings -> Applications -> Manage Applications -> All -> Camera -> clear data.
    -----------------------------
    2.6.32-based Kernels:
    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.


    -------------
    9
    Rumors 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.
    7
    Ok, this line of kernels is officially discontinued.

    There's no point continuing these as these are Froyo kernels and people have moved on to gingerbread. Once HTC get off their asses and actually releases the gingersense sources, I will probably make a new kernel thread for that.
    6
    Net, love the kernels btw! was curious if you plan on adding some code to the kernel to unlock the hidden r/w speeds of our sd cards?? the quick fix just isn't that sweet if it's not done automatically when i start the phone!

    I just found out about the SD card speed issue/fix a few minutes ago. Looking into it for integration in the next build.
    4
    In other news, the semester is done \o/

    The ending tally for this semester: 3 A's, 1 B.

    Now I can spend some time working on mah phone! ;D
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone