Jump to content

NuShrike

MoDaCo Silver
  • Content Count

    291
  • Joined

  • Last visited

Everything posted by NuShrike

  1. Doesn't work on my bootloader locked, OTA updated Nexus 7 through Windows 7. Tried with and without N7 lockscreen.
  2. Let me get this straight, so having any root (perm/temp) doesn't get rid of the default apps, so the only way is to disable them -- beyond flashing a new rom? And is anyroot needed to use PackageManager? nevermind, anyroot is required. Disabling apps now. Thanks!
  3. Development is done for the HD2 (I use it as daily-beater now) -- alternate version compatible with O2 is a short stretch. But there's no GUI, and can't resolve how to monetize it since MarketPlace won't accept it with all the background hacking. My experience with donations hasn't been that great, so ...
  4. Well, going to have to eat these words. TMOUS HD2 actually has FPU-enabled kernel. Only issue is the float-point libs don't use it, but this project fixes that anyways.
  5. Okay, the MWIPS I've been testing on is more realistically in the ~35-50 MWIPS range. It is better than stock, but only about ~2.5x increase. Should be bigger impact on slower cpus such as s3c6410. The > 50.x version (I've been averaging ~80.x) is doing unsafe things that generally works on the faster Snapdragon, but will totally fail and hang the device once the CPU load goes up. Not fixable until MS releases a FPU-enabled OS kernel, but not ever happening because of Wimpy7s. Anyways, next step is GUI control panel.
  6. I'm do doubt GLBenchmark though having seen some of the quality of their resulting code, such as getting a default color buffer instead of one optimized for the device. Results in poor benchmark results in WM, but probably a AMD/Qualcomm driver bug. So SKTools benchmarks on TMOUS HD2: stock: Integer 796.2459 Moves/25 usec Floating Point 19.482 MWIPS vs fpu-enabled: Integer 794.8475 Moves/25 usec Floating Point 113.728 MWIPS ~ 5.8x improvement on Snapdragon's FPU performance. I do know square-roots are 36x faster. Great for 3D, if anybody was still programming for this platform.
  7. Once I get it onto the Marketplace ... Meantime, seems to work okay on the HD2 except for a kmode patching problem, but not much speed diff in GLBenchmark esp in FPU benchmark.
  8. Okay, so I didn't read ActivateDeviceEx() closely enough and the registry was not set quite right. Well, not stuck on this anymore.
  9. 1. Yes. 2. MS may have tightened up security which may be related to CF's hacking of Marketplace security. I'm not having issues related this yet except I can't start up the driver (nor any dummy one) and get error codes back that explains what's wrong, so far ...
  10. Thanks for the response. Actually, the driver isn't publicly released yet so you're just signing the .exe, not the actual dll. At least progress is being made on this project again after the fubar with Clove.
  11. Hm. interesting link. I've gotten: 158099 Firefox 3.6.3 535610 Chrome 5.0.375.17 414590 Opera 10.51 11616 Opera 10 in my HD2 (No FPU Enabling running yet, plugged into power) Flash is pretty cpu-sucking.
  12. So working on this on my TMOUS HD2, I'm stuck on loading the driver where it pops a dialog when trying to enable the device in TaskManager saying: "Device Load Error The operation completed successfully." I'm at loss because this driver in the same ABI form loaded up on the Acer M900 (which I no longer have) fine, so I can only guess that I need to sign it? Probably need to talk to ChainFire about this. Meantime, I'm still investigating, but the FPU comes enabled in the stock TMOUS HD2 rom. I'm not sure if the kernel is context switching the registers, but with the Snapdragon being so fast, I haven't gotten multiple-threads to tangle each other yet with the old tests. More on this later. ... Funny enough, I got permanently banned off howard forums by live_strong whom claims I made a racial slur by comparing the recent immigration bill in Arizona (USA) to be a facist as making Jews wear their stars of the time. Did I make a racial slur with those exact words? Moderator response thread.
  13. Back in the saddle a bit with Clove Technology still sitting on my Acer M900 repair for 4 months going now. Built on WM 6.5.3 DTK, but not using any of the extended features, yet. Tested on T-Mobile HD2. @zeeuwsmeisjeman: I tried to exclude explicitly \\Network, and \\Bluetooth directories now. @drewcam888: It is setting the registry settings to 1 for 1 second, 20 for 20 seconds, 60 for 60 seconds, for me on HD2.
  14. So at this point due to Clove Technology, I'm abandoning my Acer M900 (which they're still physically holding on to) which has been my only development platform. This means LevelSight M900 is also being abandoned, but not FPU Enabler. I'm waiting for the T-Mobile HD2 to be released (in 2 days), and then maybe I can resume some work. As evil as HTC and Qualcomm has been, Clove, Acer, and Samsung are just 2nd-strings ... Clove, slightly cheaper, but not worth the trouble.
  15. Thanks, that's just more kindle on the fire. I've already sent post making them well aware they're in breach of Sale of Goods Act already. My problem is I can't get enforcement on any of this without Small Claims Court, where I need help with the UK side ... else, I'll have to personally fly over there and deal with the paperwork directly.
  16. Actually, it would be better to spread the word that Clove disrespects its customers by holding merchandise hostage for "repairs" for months (a large percentage of the lifetime of a mobile), and they seem too cheap to do exchanges. It would help me even more if there's somebody in UK that can help me with forwarding the correspondence (with a UK post code, etc) to ease filing small claims against Clove.
  17. The button is Chainfire's code.. probably not worth tweaking currently. As for protection, not much of it here in the USA. UK does, but I've found it little difficult to get help from UK resources, and the time-zone difference delays response a bit.
  18. Thanks for all the support! So Clove responded to my post deadline (of March 1st) by EMAIL, that they think they still think they've handled the situation in a "satisfactory manner". I know they've been highly courteous, but they've still held up the repair longer than reasonable and convenient. Their good is primarily unsatisfactory. They've also reserved the right to "take action against the" third party "emails without any contact with" me. I don't like the threatening sound of that, nor how they refused to delineate in any text how they're on the correct side of the Sale of Goods Act. So I'm not sure how to proceed at this point.
  19. Great idea! Tell them: So something to that effect? Thanks!
  20. So development of this is now ENTIRELY being held up by Clove Technology. They're currently violating the British Sale of Goods Act of 1979 because they've been holding on to my Acer M900 for the sum of 2 months for repairs, and refusing to give me an exchange or refund. Let them know how YOU feel about them stopping the development of FPU Enabler (and anything else from me) at their email here: [email protected]
  21. All current skills in hacking have been in WinCE5 (equiv to Win98) -- until somebody has hacked WinCE6 (equiv WinNT-gen), all bets are off. The kernel/driver/memory model is so different, all the current entry points are a wash. Then, since wimpy7 (WinP7) is even a newer kernel that hasn't existed anywhere yet ...
  22. o a bit laggy with the fps skipping on a really fast CPU with supposed fast graphics hardware o really bad use of screen space (felt like watching only left-half of a bigger screen or always in zoomed in mode in Opera/Safari Mobile) o looked really hard to get to any place quickly without a lot of swiping around the interface o didn't really show off any newer/better OS innovation like webOS did o the lack of chrome made the UI look unpredictable and difficult to navigate without a lot of memorization o Zune/PlaystationHome type UI doesn't belong on WVGA when you just magnify up all the UI elements loosing all of the resolution advantage (a screen many times the extravagant PalmOS 320x480 res, it shows LESS information) o Spring 2011 (you know it for any manufacturer variety) and requiring all new hardware with no target manufacturer deliverables (who's making a compatible phone and I have to throw away all current investment?) is no deal o new OSs take a really long time to mature I'm starting to look really hard at Android or iPhone now. If webOS survives and comes to GSM, it's even more ideal.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.