Database Users

Did anyone get Appinventor by Google running on HD2?

Hey guys,
I was granted access to the beta of Android App Inventor and wanted to start playing around with that software and my HD2 running android. However, I cannot manage to get a connection to the phone via USB. (Selection: Connect to Phone in Block Editor does not work for me).
So, is there anyone working with App Inventor paired with HD2?
Thank you for your help and advice in advance,
jokeR

Download the Android SDK (if you haven't already), and install the package, "Usb Driver Package, revision 3".
Then plug in your HD2, if it doesn't auto-install do the following:
Right click my computer - manage - device manager,
find your HD2 in Other Devices/leo
Right click it, Update Driver Software
Browse my computer for driver software
In the text box: C:\android-sdk-windows\usb_driver (adjust accordingly)
Click next and it should install.

also only some builds have usb connection working i am using darkstones build and usb works fine

Currently I use this build: "shubCRAFT CM6RC2/Froyo" .
I still did not manage to complete a connection. The Block editor quits with an error "We made a mistake! Please help by reporting this bug:
Problem getting project defitions for phone: ...longurl..."
I will retry installing SDK and Extras and driver.
So, after reinstalling everything it still does not work:
"Leo" is listed in Devices as: "Android Composite ADB Interface" - is that the right driver?
I also tried to use a virtual Android device utilizing the SDK, but sadly that did not work as well. I have the Desktop of the virtual Android on my Screen, but clicking connect in Block editor does not connect to the virtual device (the Leo is unplugged in that scenario).
:/

make sure USB debugging is enabled in the application settings

Yes I have App Inventor. It's working OK for my on Darkstones build, but like you, I have issues with Shub's build.
For some reason or another - and I'm not sure how - I got it running just fine with no phone connected at all. I was able to complete the project and save it just fine. Maybe it was a bug...

I tried Darkstone's built, had USB debugging enabled, but it still did not work for me Don't know what to do next.
Anyone working with virtual devices or other builds that could work?
Thanks in advance for your help.

[USB Drivers] Galaxy S GT-I9000 (Working on ICS)

Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk

Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben

Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2

What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000

METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.

I'm going to test in my desktop this weekend to check if it works with it.

I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.

I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA

Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf

I got my i9000 recognized using the latest drives from the Google sdk

That‘s great

http://ics.samsung-updates.com/addons/usb_driver.zip

oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA

oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?

IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)

USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK

IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me

The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !

these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.

I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.

Clockworkmod Tether on Windows 8

Trying to install clockworkmod tether on windows 8 laptop but is failing saying tapinstall.exe failed. Eventvwr shows error 1722. Any help would be appreciated.

ixiduffixi said:
Trying to install clockworkmod tether on windows 8 laptop but is failing saying tapinstall.exe failed. Eventvwr shows error 1722. Any help would be appreciated.
Click to expand...
Click to collapse
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.

JSmith549 said:
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.
Click to expand...
Click to collapse
I will try this once I get home. If this works you, my friend, are my hero.

Thank you for this, solved my problem as well!

JSmith549 said:
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.
Click to expand...
Click to collapse
Looks like it changed a little with 8.1. Now its located in:
Setting > Change PC Settings > Update and Recovery > Under Advanced Click Restart Now

JSmith549 said:
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.
Click to expand...
Click to collapse
Thank you - mine also worked!!!! :good: ur my :angel:

Is Samsung ADB Driver ALSO Not Digitally Signed In Windows 8.1?
crsmith6196 said:
Thank you - mine also worked!!!! :good: ur my :angel:
Click to expand...
Click to collapse
Your solution allowed Tether to install for me. Do I need to do the same thing for the Samsung ADB drivers?
73 DE N4RPS
Rob

I can get Tether installed on both my Windows 8 Laptop and my Galaxy Nexus device (running 4.3, no root) and I used to be able to use Tether with no issue about one year ago. Now, however, when trying to initiate Tether, this is what I'm presented with:
Starting Tether...
C:\Program Files (x86)\ClockworkMod\Tether\node-tuntap
Opening tun device.
Opening tun device: null
Waiting for interface to get ready... (forker, waiting 5 seconds)
Waiting for interface to get ready... (postSetup, waiting 5 seconds)
Forking worker.
Tun/tap device IP: 10.0.0.1
Reading tun/tap device...
Opening tun device.
adb binary path: "C:\Program Files (x86)\ClockworkMod\Tether\win32\adb.exe"
Checking phone status...
tun worker initialized.
Listening on tether port...
0A3C31D90400C017 New device found.
0A3C31D90400C017 Connecting to device.
0A3C31D90400C017 Checking if package is installed.
Error listing pacakges. Assuming Tether.apk is already installed.
0A3C31D90400C017 Setting up adb port forwarding to port 30002.
0A3C31D90400C017 adb port forwarding results:
{ '0':
{ [Error: Command failed: error: device offline
] killed: false, code: 1, signal: null },
'1': '',
'2': 'error: device offline\r\n' }
0A3C31D90400C017 Error forwarding:
{ [Error: Command failed: error: device offline
] killed: false, code: 1, signal: null }
0A3C31D90400C017 Creating relay for device.
0A3C31D90400C017 Tether error:
{ '0':
{ [Error: connect ECONNREFUSED]
code: 'ECONNREFUSED',
errno: 'ECONNREFUSED',
syscall: 'connect' } }
cleaing up relay connection
0A3C31D90400C017 Tether connection closed.
cleaing up relay connection
0A3C31D90400C017 Tether connection closed.
This is just repeated infinitely until I manually stop Tether on my computer.
Since this is the only thread that comes up when searching for Tether issues on Windows 8 machines I could find, is there anyone who can help me figure out how to get this back to working order?

miguelshihto said:
I can get Tether installed on both my Windows 8 Laptop and my Galaxy Nexus device (running 4.3, no root) and I used to be able to use Tether with no issue about one year ago. Now, however, when trying to initiate Tether, this is what I'm presented with:
Starting Tether...
C:\Program Files (x86)\ClockworkMod\Tether\node-tuntap
Opening tun device.
Opening tun device: null
Waiting for interface to get ready... (forker, waiting 5 seconds)
Waiting for interface to get ready... (postSetup, waiting 5 seconds)
Forking worker.
...........
This is just repeated infinitely until I manually stop Tether on my computer.
Since this is the only thread that comes up when searching for Tether issues on Windows 8 machines I could find, is there anyone who can help me figure out how to get this back to working order?
Click to expand...
Click to collapse
I'm getting the same thing - no luck with it so far.
Anyone who's figured this out - it'd be much appreciated if you can help!

Surface Pro 3
So i just bot a surface pro 3 and i was trying to instal clockworks tethering system and it wants me to download .net frameworks version 2.0, but when i try to download it, it says i already have it. I could relay use some help!

bit late...
javiertrevino73 said:
So i just bot a surface pro 3 and i was trying to instal clockworks tethering system and it wants me to download .net frameworks version 2.0, but when i try to download it, it says i already have it. I could relay use some help!
Click to expand...
Click to collapse
.NET Framework 2.0 is not installed on Windows 8 by default.
To install it, go to Control Panel – Programs – Turn Windows features on or off – Check ‘Microsoft .NET Framework 3.5.1′ – OK.
Note, that .NET Framework 2.0 is included into version 3.5.
Source: wishmesh.com/2011/09/net-framework-2-0-is-not-installed-on-windows-8-developer-preview-by-default

I just bumped up from windows 7 to 10 and when I go to use my tether all I get is this C:\Program Files (x86)\ClockworkMod\Tether when I push start. I haven't read any issuse regaruding tether and windows 10 I doubt I am the the first, does anyone here have any idea what is going on?

Durteedee said:
I just bumped up from windows 7 to 10 and when I go to use my tether all I get is this C:\Program Files (x86)\ClockworkMod\Tether when I push start. I haven't read any issuse regaruding tether and windows 10 I doubt I am the the first, does anyone here have any idea what is going on?
Click to expand...
Click to collapse
I'm also having this same issue so compatibility appears to be broken in Windows 10.

Durteedee said:
I just bumped up from windows 7 to 10 and when I go to use my tether all I get is this C:\Program Files (x86)\ClockworkMod\Tether when I push start. I haven't read any issuse regaruding tether and windows 10 I doubt I am the the first, does anyone here have any idea what is going on?
Click to expand...
Click to collapse
I'm having the same problem myself, I just reported it to the developer so hopefully there will be a fix before too long.

Temp fix at least.
XTCrefugee said:
I'm having the same problem myself, I just reported it to the developer so hopefully there will be a fix before too long.
Click to expand...
Click to collapse
Not too sure, I'm no developer, but I believe there may be issues with the adb drivers. I installed PdaNet+ (same type of app.) and it specifically says Win10 compatible. I allowed it to overwrite the adb drivers with the driver's it determined to be correct and the PdaNet+ app works and tethers to my laptop. I am unfortunately in an area right now with only 2G service so I will not be messing around with it too much tonight but maybe tomorrow I can see if it is going to be a replacement or maybe the new drivers will work with the CM Tether software.

Well i hope they can get too or soon. I dont think its my adb drivers

sprint users
pdanet+ is blocked by sprint.
masqman said:
Not too sure, I'm no developer, but I believe there may be issues with the adb drivers. I installed PdaNet+ (same type of app.) and it specifically says Win10 compatible. I allowed it to overwrite the adb drivers with the driver's it determined to be correct and the PdaNet+ app works and tethers to my laptop. I am unfortunately in an area right now with only 2G service so I will not be messing around with it too much tonight but maybe tomorrow I can see if it is going to be a replacement or maybe the new drivers will work with the CM Tether software.
Click to expand...
Click to collapse

Its *not* usb drivers...
...because
adb devices
and
adb shell ps
...work just fine (after authorising).
Justin C thinks its changes to .Net on the ClockWorkMod forum (I can't post a link unfortunately).
Specifically I think the exe is failing to create the virtual network device (TAP) which then gets passed to run.bat
run.bat should then open up the windows firewall but it just fails with very little output when given no TAP index.
So it could also be driver related. I tried briefly adding some third party Windows 10 TAP driver but to no avail.

[PSA/FIX] Newest adb doesn't work on WinXP + 5x USB drivers that work

I happen to update platform-tools in the Android SDK from version 23.1 to version 24 on an older PC.
The newest adb.exe included with v24 no longer works on WinXP.
You will get the following error upon startup:
adb.exe - Entry Point Not Found
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.
Click to expand...
Click to collapse
In case anyone is curious, I tracked the change down to this one:
https://android-review.googlesource.com/#/c/203387/
ADB
I've attached the v23.1 adb and fastboot to this post in case someone needs the previous version (which works fine with 5x up to at least MTC20F)
Just unzip and you can use adb/fastboot from the resulting platform-tools-v23.1 directory or copy them over to where your normal platform-tools directory is.
USB drivers for 5x
I also included USB drivers that work with 5x. These should work for 32/64-bit for winxp and vista. Win7 is maybe, haven't tested.
They WILL NOT work with win8 and above due to changes in driver enforcement. I am not sure about win8.x but on win10, there is a built-in driver that works with adb. To get bootloader/fastboot driver, just allow win10 to search for drivers. It will load Marshall London Bootloader Interface. This is for a different phone from music company Marshall, but it works fine since it is an Android-based device.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.

Not sure if it matters to that many people these days, but it was confirmed the change in adb is not a bug and will persist going forward, so if you ever need to run adb on a WinXP box or emulator, you'll need to retrieve platform-tools-23.1 or earlier.

WinXP compatible platform-tools also could be downloaded from official repository:
http://dl-ssl.google.com/android/repository/platform-tools_r23.1.0-windows.zip

Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.

Greefus said:
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Click to expand...
Click to collapse
Actually Windows 7 is still installed on nearly half of all desktop and laptop computers: https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0. Did the most recent SDK drop support for it?

For anyone who wants to use adb on the latest version of Android Studio running on Windows XP use the adb .exe from version 23 and paste it into the platform tool folder. Keep a copy of the new adb.exe just in case you need it. No need to use the entire v23 platform tool folder.

The references in this thread have so far appear to refer to latest adb compatibility, particularly for Windows XP.
Does the latest fastboot still work fine with Windows XP? If not, what was the last known-good or thought to be last known-good version for Windows XP?

Hi
The adb from the v2.3.1 works fine with my win xp, thank you for the file.

Hello,
I am another WinXP user facing the error
"adb.exe - Entry Point Not Found. The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll."
@sfhub & @Sintetix
Thanks for the info and provide the latest version supported by XP ...
Are you aware of any important changes / additions in the future versions to be concerned of?
Regards
---------- Post added at 11:16 ---------- Previous post was at 10:47 ----------
Just to let you know,
C:\v23.1>adb devices
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:
I am trying to connect an Asus Transformer tablet with "MTP file transfer" mode on WinXP Service Pack 3 laptop... cable is fine and the plan is to move from custom ROM (Android 6.0) to Stock (JellyBean) ... Something I already did few years ago having Win10 (I have the receipe used then)
I think I better get a fresh Win7 on my primary Win10 PC and start from there... I never liked W10 anyway ... and since I did mods to [finally &effectively] stop the [annoying, unwanted & plenty of bugs] Win10 updates ... I got funny errors when using dev stuff ... even DotNet ...
And I need to think a better O.S for the XP PC ...
Time to change. Regards

Before jumping to my major O.S actions,
I gave a chance to my Asus Transformer tablet with another cable under the W10 PC and the latest adb (r29.0.2-win) and this second time it worked fine ...
The first time and first cable did not work (reason that drove me to the WinXP PC thinking the cause was Win10)
fastboot devices
was literally returning
???????????? fastboot
But this second time with another cable
fastboot devices
returned
BLAxxIDxxSTRING fastboot
And I was finally able to perform the format and flash series of commands to return my tablet to the stock ROM ...
As I understand this thread is about WinXP, for testing purposes, I hooked my fresh flashed tablet to the WinXP PC with the successful spare cable, and
adb devices
got again
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037
Certainly I don't have the explanation of this, but I can tell you is not because a faulty cable or something related to the tablet.
And something scary to add: the first cable looks in good shape and is the one used every day to charge the tablet without any delays or issues ...
Hope someone find this useful and provide more insight. Regards

adb device error not found

i am trying to follow this article https://www.drivereasy.com/knowledge/solved-adb-device-not-found-error-on-windows/
but the issue is android studio looks different now with the new update and i don;t see extra to install the correct usb driver i am trying to install a rom on the phone i am in twrp and the phone wont adb or mount system the computer sees the driver as aosp mako but adb doesnt work could i get some help from the experts its been a while and trying to rewrap my head around the android sdk current version studio as they call it now or someone who has a minute we can try team viewer and see how i configure this once and for all
solved it this android studio is way better