Related
So everyone is wondering why the Nexus One Launcher just keeps FC'ing, and how come the Droid can just install, and WHAM! it works. ANY ANSWERS????
the droid luancher is just a themed Rosie.apk. we already have Rosie (sense UI). the nexus launcher is probley having shared uid issues or something. thats just a guess though.
I think you have me wrong, Im talking about the native nexus launcher not the rosie 2.1 combo
use the open eclair launcher2.apk it works fine
jriley60 said:
use the open eclair launcher2.apk it works fine
Click to expand...
Click to collapse
can you post a link
uumm not while i'm driving try "search"
iloveandroid said:
I think you have me wrong, Im talking about the native nexus launcher not the rosie 2.1 combo
Click to expand...
Click to collapse
no i was explaining what the droid (themed) rosie was. the nexus launcher is going to need opengl 2.0 to be fully functional. and to get it to instal ur gonna need an aosp rom. we had aosp build on the heroc forum but things went south with the leak of a .29 kernel. causing the drivers for touch screen to not be compatible with anything but htc built and modified builds. but before the .27 kernel came along i backported the opengl drivers from the .29 kernel into the old .27 kernel enabling the 2.1 opengl drivers which are opengl 1.1 for the msm7k devices. the nexus one like many other new devices has a different arch and gpu that alows them to have opengl 2.0. our devices just dont support it. the best lwp we can get are only lwp from the market that are half baked/ home brewed lwp. so yeah ther is a chance u could port one of the few builds that have support for the nexus launcher and other nexus goodies. but in the end it will be fairly buggy as it was on the heroc. ie Eris and heroc are basicaly the same devices. only a few minor differances.
jriley60 said:
uumm not while i'm driving try "search"
Click to expand...
Click to collapse
I don't quite follow, when you get home can you just PM me, sorry I'm slow today
Just taking a guess here, but this link might help you out..
http://forum.xda-developers.com/showthread.php?t=631894
ECLIPS3 said:
Just taking a guess here, but this link might help you out..
http://forum.xda-developers.com/showthread.php?t=631894
Click to expand...
Click to collapse
Err, same thing FC
http://www.youtube.com/watch?v=udGIhcaMB28
Seems to work fine for me now, with live wallpapers as well
I seem to remember that when the leak first came out there was some "issue" with the opengl that shipped inside of the update. That *might* be whats going on here. I'd suggest looking around for that thread, as there may be answers to your questions in it.
ya
I've been trying to say live wallpapers worked with the launcher2 from open eclair for a while..just not the wallpapers that ship with the phone
jriley60 said:
I've been trying to say live wallpapers worked with the launcher2 from open eclair for a while..just not the wallpapers that ship with the phone
Click to expand...
Click to collapse
yeah the only real issue with the nexus one launcher that we had with the heroc, was the app tray was a little laggy and bothered a lot of people.
the lwp though were just issues with the stock lwp. like i said the ones in the market worked ok. some were a bit laggy though and would at times bring the phone to a crawl. i remember one did for sure. that was the "logcat lwp" i loved it but it was easily seen that lwp werent meant for our hardware.
but yeah i think its possible to get a few of the stock ones to work also. i cant remember what me a maejrep had to do to get them working. but i do remember them still being to buggy. but yeah most of the market ones were ok and would run for the most part fine.
I still cant find a working launcher2 someone please POST A LINK!!!!!!
iloveandroid said:
I still cant find a working launcher2 someone please POST A LINK!!!!!!
Click to expand...
Click to collapse
THEY'VE POSTED MANY LINKS THAT WORK FOR EVERYONE ELSE!!!!!!1111
There's no need to shout.
The reason for the confusion is because hes on the earlier leaked 2.1 not the rooted 2.1
iamkewl said:
THEY'VE POSTED MANY LINKS THAT WORK FOR EVERYONE ELSE!!!!!!1111
There's no need to shout.
Click to expand...
Click to collapse
Then could you point me in the right direction please
im not quite sure if ur device needs to be rooted or not, cause ive tried a few different apks in reference to the launcher 2 and all i get is FC's.
good luck finding it..and when u do, link me sir.
FireSokar said:
The reason for the confusion is because hes on the earlier leaked 2.1 not the rooted 2.1
Click to expand...
Click to collapse
X2...................
Sir I'm a newbie on forum things so i dont know if i did type in the right page well just wanna ask if the multitouch thing of the android phones will be available in topaz in the future builds thanks
anon1234 said:
Sir I'm a newbie on forum things so i dont know if i did type in the right page well just wanna ask if the multitouch thing of the android phones will be available in topaz in the future builds thanks
Click to expand...
Click to collapse
Nope. Multitouch not supported in Topaz (resistive screen).
Xinot said:
Nope. Multitouch not supported in Topaz (resistive screen).
Click to expand...
Click to collapse
Well, couple of weeks ago i saw a beta version somewhere were multitouch was realised in a beta version for resistive screens.
J-r0en said:
Well, couple of weeks ago i saw a beta version somewhere were multitouch was realised in a beta version for resistive screens.
Click to expand...
Click to collapse
I don't think this would work under Andriod tbh. Even if it did it isn't *true* multi-touch, it's not really what you'd expect at the moment, I think it will get better though, but because Andriod is difrent from WinMo I highly doubt it would work for it... Correct me if I'm wrong.
multi touch is coded into the application and resistive touch screens can do multi touch but the sdk that was released on xda is for multi touch on wm6.x
anarchyuk said:
multi touch is coded into the application and resistive touch screens can do multi touch but the sdk that was released on xda is for multi touch on wm6.x
Click to expand...
Click to collapse
its not true multitouch, better call it dualtouch. when touching the screen with two fingers, the device reports the coordinates in the middle of these two touch spots.
with a sudden change of coordinates an app can guess you are using two fingers, so it can calculate the second touch spot using some math voodoo.
so simply said, its not important if you use windows mobile or android, its important your app supports dualtouch by itself!
laforma said:
its not true multitouch, better call it dualtouch. when touching the screen with two fingers, the device reports the coordinates in the middle of these two touch spots.
with a sudden change of coordinates an app can guess you are using two fingers, so it can calculate the second touch spot using some math voodoo.
so simply said, its not important if you use windows mobile or android, its important your app supports dualtouch by itself!
Click to expand...
Click to collapse
What is not true? your rant is does not actually go along the lines of showing what I said wrong? Does the multi touch version of google maps work on the topaz? ermmmm computer says NO!
anarchyuk said:
What is not true? your rant is does not actually go along the lines of showing what I said wrong? Does the multi touch version of google maps work on the topaz? ermmmm computer says NO!
Click to expand...
Click to collapse
mmh, seems my english is not that perfect to understand what you try to tell you. i didnt want to correct you, instead i wanted to clarify whats behind the technology of dualtouch. btw multitouch means more then two fingers
laforma said:
mmh, seems my english is not that perfect to understand what you try to tell you. i didnt want to correct you, instead i wanted to clarify whats behind the technology of dualtouch. btw multitouch means more then two fingers
Click to expand...
Click to collapse
Multi-touch impleis more than one. (Multiple)
Dual touch specifies only Two (2) touches, Tri-touch would specify three (3) touches. So Multi-touch is correct.
From Thefreedictionary.com
mul·ti·ple (mlt-pl)
adj.
Having, relating to, or consisting of more than one individual, element, part, or other component; manifold.
hehe multitouch doesnt even work on the hero properly never mind on a resistive touch screen!!
Can someone confirm if the Google Maps update 5.0 on Htc Hero has the 3D tilt
, cause when I swype down with two fingers all it does is zoom out , and doesnt tilt
or rotate the map.
Confirmed. Doesn't work for me.
maxpower47 said:
Confirmed. Doesn't work for me.
Click to expand...
Click to collapse
that kind of defeats the purpose of the update I think
Was just trying to figure this out too. Hero definitely doesn't have it. Maybe it's lacking a necessary hardware sensor?
dkratter14 said:
Was just trying to figure this out too. Hero definitely doesn't have it. Maybe it's lacking a necessary hardware sensor?
Click to expand...
Click to collapse
I just dont understand ,it has to support multitouch, and as far as I know Hero does have multitouch .
Probably has to do with our pathetic gpu. But the update is most definitely worth it, because we do get offline maps and vector based maps (loads much faster).
maxpower47 said:
Probably has to do with our pathetic gpu. But the update is most definitely worth it, because we do get offline maps and vector based maps (loads much faster).
Click to expand...
Click to collapse
That makes sense , well I think we can't expect much of a phone being pushed to it's limits .
rcml01 said:
That makes sense , well I think we can't expect much of a phone being pushed to it's limits .
Click to expand...
Click to collapse
Some over in the aospMod thread are saying it's worked for them
peteytang said:
Some over in the aospMod thread are saying it's worked for them
Click to expand...
Click to collapse
3D tilt is (slightly) different from the compass feature. If you're in one of the supported cities, zoom into the 3D layer and the "my position" button turns into the compass button.
Make sure you have the updated street view installed also
Sent from my HERO200 using XDA App
andygu3 said:
Make sure you have the updated street view installed also
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I have the latest Street view and still no 3d tilt on HTC HERO Cyanogen Nightly build#166 , So only AOSP rom is working with this feature?
rcml01 said:
I have the latest Street view and still no 3d tilt on HTC HERO Cyanogen Nightly build#166 , So only AOSP rom is working with this feature?
Click to expand...
Click to collapse
Again, compass is different from 3D tilt. The Hero doesn't support tilting or rotating
http://www.google.com/support/mobile/bin/answer.py?answer=1079043
Engadget said they did a test and it will not work on any phone not running 2.0 or later
I can't imagine anyone here is not running something later than 2.0!
MarkerB said:
I can't imagine anyone here is not running something later than 2.0!
Click to expand...
Click to collapse
co-sign!!
One guy in the CDMA thread said he got it working... does the CDMA Hero have a different spec/gpu to our GSM Hero?
Calico5 said:
co-sign!!
One guy in the CDMA thread said he got it working... does the CDMA Hero have a different spec/gpu to our GSM Hero?
Click to expand...
Click to collapse
Lol, this IS the CDMA Hero forum
c00ller said:
Lol, this IS the CDMA Hero forum
Click to expand...
Click to collapse
I think he knows that. He's using a similar product to bring up a point. We're allowed to reference other products on this forum, if they may have a bearing on our product.
Mine doesn't even have smooth zoom transition, nor a compass on top, nor the ability to pre-fetch maps in settings. Anyone else having these problems? I've uninstalled...cleared cache...tried everything. No go.
Anyone know what I'm doing wrong?
alexthearmo said:
Mine doesn't even have smooth zoom transition, nor a compass on top, nor the ability to pre-fetch maps in settings. Anyone else having these problems? I've uninstalled...cleared cache...tried everything. No go.
Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
yes same thing
alexthearmo said:
Mine doesn't even have smooth zoom transition, nor a compass on top, nor the ability to pre-fetch maps in settings. Anyone else having these problems? I've uninstalled...cleared cache...tried everything. No go.
Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
Prefetch maps is automatic when you start google nav. This is from http://googlesystem.blogspot.com/2010/12/google-maps-5-for-android-3d-maps-and.html "The new 3D view makes maps more intuitive and easier to use, but that's not all. Since Google no longer has to download map images from its servers and vector-based maps require 100 times less data for all zoom levels, it's feasible to cache data. "Rather than having a static set of maps when installed, Maps will automatically start caching the areas you visit the most when your device is plugged in and connected to WiFi (e.g., the nightly charge)." You can't manually control caching, but it's an important first step toward an offline Google Maps."
Hey guys,
Just to let you know there is an application out there now to take care of force recalibration of the screen.
When I first got my nook I know it didn't register touch properly, so I ran some commands and it started working fine.
Decided I should make my first app something that helps people, so here you go. Checkout "nook screen recalibrate". It's a simple minimalistic application the re calibrates then reboots
Updated Version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Here's the market link.
Helpful since you don't have enough posts to post links yet. But thanks for this app!
Ironically when I go to the link and try to push it to my NC, it says it's not compatible. :X
Fine print mentions that is only works with GB (android 2.3 and above).
yep.. i dont think any rom uses anything lower than that
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
assid2 said:
yep.. i dont think any rom uses anything lower than that
Click to expand...
Click to collapse
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
Not sure what exactly that application does.so can't comment.
Sent from my Nexus One
byronczimmer said:
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
Click to expand...
Click to collapse
I think it should work. I shall reduce the requirements.
However there is no way to check cause my touch is working perfect now
However I find it performs better slightly if I do this once a week
Sent from my Nexus One
Updated release v2.0
Updated to version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Force closes on nookie 2.2
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Strange, I had reduced the minimum requirements
I have no other froyo device to test on, let me check once again against an emulator
Sent from my Nexus One
Ok maybe this is in my head, but if I run this every couple nightlies, touch feels slightly better and responsive.
Maybe it's the nightly, maybe the way it interacts, maybe the screen de sensitises over time, maybe it's all in my head
If anyone cares to do some testing, that would be great
Sent from my Nexus One
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Let me know if you wanna try this so I can publish to the market
Sent from my NookColor using Tapatalk
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Try cleaning your screen prior to running the application, make sure you don't touch the screen prior to restarting
Sent from my Nexus One using Tapatalk
kruuth said:
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Click to expand...
Click to collapse
same thing on my end. I ended up reflashing the latest cm7 nightly and its back to the way it was
Sent from my NookColor using Tapatalk
That's extremely strange. First time I've heard issues like this crop up. Do you have a screen guard or something
Sent from my NookColor using Tapatalk
For those who would want to try, scews the S2.
But the link from nolook actually fixes it.
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
edit: only fixed it for a short time. i'm back with some bad touch.
can you attach the .apk i cant go to market to download!! plsss
Thunderbolt's version of Skype WITH VIDEO is now available.
http://www.droid-life.com/2011/04/11/download-skype-with-video-on-android/
It won't directly install for some reason (some how locked to the Thunderbolt?)
Would be real nice on the Atrix. Wish I could help more, but I'm just a dummy.
Thank you all very much. I bow to all your great feats.
eatkabab said:
Thunderbolt's version of Skype WITH VIDEO is now available.
http://www.droid-life.com/2011/04/11/download-skype-with-video-on-android/
It won't directly install for some reason (some how locked to the Thunderbolt?)
Would be real nice on the Atrix. Wish I could help more, but I'm just a dummy.
Thank you all very much. I bow to all your great feats.
Click to expand...
Click to collapse
This is an app, not a development thread. It should go in the Themes and Apps section.
^ disagree its a request for some DEV help on getting this to work on atrix. i'd really like for this to work on the atrix. been dying for skype video since last year.
^^^ Requests belong in Q&A or General - not Development...
http://gititbit.ch/sKa1
here is a direct link to the apk
dasmoover said:
http://gititbit.ch/sKa1
here is a direct link to the apk
Click to expand...
Click to collapse
cant install for some reason.
anyone else tried?
i couldnt get it to install either. Anyone pls explain how to get this to work
eatkabab said:
Thunderbolt's version of Skype WITH VIDEO is now available.
http://www.droid-life.com/2011/04/11/download-skype-with-video-on-android/
It won't directly install for some reason (some how locked to the Thunderbolt?)
Would be real nice on the Atrix. Wish I could help more, but I'm just a dummy.
Thank you all very much. I bow to all your great feats.
Click to expand...
Click to collapse
i took a quick look... it appears that it would not be an easy & quick fix / rebuild i dont think, the entire program is written to use and be depended on <uses-library android:name="com.htc.device" />... before taking on this project id wait out as skype said that att was suppose to get releases of its video call first so id think we cant be to far behind
For anyone interested, here is the deodexed apk decoded and built with apk-tool.
Note: This cannot be installed yet.
http://dev.gitbrew.org/~dasmoover/android/apk/dev/com.skypevideodeodex.apk
ekerbuddyeker said:
i couldnt get it to install either. Anyone pls explain how to get this to work
Click to expand...
Click to collapse
it doesn't work because it was not made for this phone. even if it did install, it wouldn't work with our camera because moto uses its own camera driver since froyo doesn't have one (gingerbread will). htc uses its own FFC driver as well.
dLo GSR said:
it doesn't work because it was not made for this phone. even if it did install, it wouldn't work with our camera because moto uses its own camera driver since froyo doesn't have one (gingerbread will). htc uses its own FFC driver as well.
Click to expand...
Click to collapse
So sounds like it works on all HTC phone?
Sent from my MB860 using XDA Premium App
dLo GSR said:
it doesn't work because it was not made for this phone. even if it did install, it wouldn't work with our camera because moto uses its own camera driver since froyo doesn't have one (gingerbread will). htc uses its own FFC driver as well.
Click to expand...
Click to collapse
?? so how does yahoo video chat, fring, and other video call apks work on several devices? obviously it wasnt made for the phone, thats why the thread was posted] to modify it and get it to work.
b15love said:
?? so how does yahoo video chat, fring, and other video call apks work on several devices? obviously it wasnt made for the phone, thats why the thread was posted] to modify it and get it to work.
Click to expand...
Click to collapse
Because they contain drivers for all the phones they know of with FFCs I would bet.
Could it be that because att doesn't have 4g yet, Skype is holding out?
I apologize If I posted this in the wrong forum. It seemed logical for me to put it here...
zerocool79346 said:
Because they contain drivers for all the phones they know of with FFCs I would bet.
Click to expand...
Click to collapse
Probably right. Here is Motorola's API:
http://developer.motorola.com/docstools/library/motorola-front-facing-camera-api/
It is so frustrating that using the same system (android) and also having a front camera but we cannot use the same app (skype with video).
yup but that was specifically develpoed for the thunderbolt, I assume if it does get officially launched with it, it will be a matter of time before that spreads to being on other devices (much like when they launched skype in the first place on android) the key question is will they fix the sound issues that moto's config gives these voip programs.
ytwytw said:
So sounds like it works on all HTC phone?
Click to expand...
Click to collapse
I'm guessing no, but for reasons other than the camera driver.
b15love said:
?? so how does yahoo video chat, fring, and other video call apks work on several devices? obviously it wasnt made for the phone, thats why the thread was posted] to modify it and get it to work.
Click to expand...
Click to collapse
as I learned in the (otherwise useless) motorola atrix dev conference, the FFC driver for the atrix is written BY motorola. Android 2.2 does NOT have a standard FFC driver and so every phone that has an FFC and is running 2.1 or 2.2 is using their own FFC driver. That is why Tango and Qik did not work for the Atrix immediately when it was released, and Qik had to release an Atrix-only version of the app.
When gingerbread comes across all devices, it will have a standard FFC driver. But until then, every company running 2.2 uses their own and that is why these aren't compatible apps.
eatkabab said:
Could it be that because att doesn't have 4g yet, Skype is holding out?
I apologize If I posted this in the wrong forum. It seemed logical for me to put it here...
Click to expand...
Click to collapse
More than likely, it's because AT&T didn't want Skype to release it yet.. the carriers have a surprising amount of influence on app developers. Think of how the Inspire and Atrix still don't have HSUPA enabled whereas the iPhone 4 has had it since its release. My guess is they don't want to overload their already fragile network
r34p3rex said:
More than likely, it's because AT&T didn't want Skype to release it yet.. the carriers have a surprising amount of influence on app developers. Think of how the Inspire and Atrix still don't have HSUPA enabled whereas the iPhone 4 has had it since its release. My guess is they don't want to overload their already fragile network
Click to expand...
Click to collapse
I know and people like me who have a bell atrix thats not even on bell have to suffer.
Sent from my Nexus One using XDA App