Related
Does anybody think it will be possible for the OS on the Google phone to run on our PPC-6800's? please excuse my noobness if this has already been discussed but I was just curious.
http://it029000.massey.ac.nz/vogue/
Just follow the directions and everything should be groovy. Enjoy! :-D
aaron580 said:
Does anybody think it will be possible for the OS on the Google phone to run on our PPC-6800's? please excuse my noobness if this has already been discussed but I was just curious.
Click to expand...
Click to collapse
I would like to add that it's really a "beta" and shouldn't be used as your "main" OS; as it's nowhere close to 'ready' (at least in my opinion) for this device.
I mean; go ahead and check it out, but don't expect it to be your phone's primary OS.
It was way cool to check it out and play with it but still very unstable but its getting there.
Cant get it to boot
Well I downloaded the files to boot it and i click on the harot boot exe hit run and then it hangs. Where are the actual directions on how to run it? Is there any?
aaron580 said:
Well I downloaded the files to boot it and i click on the harot boot exe hit run and then it hangs. Where are the actual directions on how to run it? Is there any?
Click to expand...
Click to collapse
You might want to put the files on a different SD card as I think it needs to be on a Fat32 partition.
It is a 512mb formatted to fat32 and it still doesnt work. I downloaded the android zip and not the sdk though if that might be the problem.
I actually figured out my problem. i kept all of the files in the folder and didnt extract to the root. my fault.
Do I have to install that heret bootloader first or should the olipro one I have work?
boot loader
No olipro is not even part of this. All you have to do is put all of the files in the root of your SD card and run it like an app and linux will boot. Keep in mind that there are so many bugs in it that you will never want it as ur primary os
development
Is anyone currently working on / developing a workable Android OS that we can flash, as opposed to using the Haret.exe file to essentially shell over Windows Mobile?
I installed this in the last couple of days, and have been able to make calls, access Google Maps, the browser, etc....but have no access to the keyboard, an on screen keyboard, etc.
I'd be willing to help test out anyones work if so. Thanks!
none of the buttons on the mogul works. a few of the keys work on the keyboard.
Update.
Join the HTC-linux chat channel.... If you want to help out. So far not many people on there own a Titan, so i've been trying to do my best to help out... The guys on there are extremely helpful... They will walk you through everything, and if you give them the information that they need, they will be able to develop more things for our titan... We are working on getting the keyboard working as of right now.... if you go in there... talk to dcordes, ginge, or ali1234... they will help you out... Like i said if we get more people in there we will be able to use Android to it's full capabilities... DZO has it working almost perfect on the Vogue.... The touch screen is still kinda wild in my opinion.... So we need to find a way to improve that as well...
wasupwithuman said:
DZO has it working almost perfect on the Vogue
Click to expand...
Click to collapse
When I get done with this Hurricane B.S. here in Texas i'll get with this guy and see if I can port any of it over.
Also something I'm interested in. Windows Mobile is tiring me, and I honestly would feel more comfortable running my phone on a *nix. Plus, it seems like Android is gaining momentum where WM seems to be losing it.
ilovethisplace said:
Also something I'm interested in. Windows Mobile is tiring me, and I honestly would feel more comfortable running my phone on a *nix. Plus, it seems like Android is gaining momentum where WM seems to be losing it.
Click to expand...
Click to collapse
We just need ppl to get the keyboard and buttons on the Titan to work on Android. It will be done in good time, it's just there's no timeframe.
I've noticed that the touchscreen is quite flaky, too. Frankly, I think that's higher-priority than some of the hardware buttons.
ilovethisplace said:
Plus, it seems like Android is gaining momentum where WM seems to be losing it.
Click to expand...
Click to collapse
...in that a single device has been launched from naught?
WM device sales have not decreased... Revice your statements and be honest. Android is immature. Particularly in that it lacks choices in software and suffe from odd OPEN development hesistency from Google. Android is a nice toy but it is not yet ready for widespread adoption. So, again, let's be honest and drop the rah-rah Android versus WM hyperbole.
It will great to have another OS to run on our HTC phones -- particularly the Titan -- but Android is unlikely to be on par to what WM provides within the useful lifespan of our current devices. As such, Android on the Titan is a great developmental toy.
Problems with tha applications !!
Hey !! i have run the haret.exe on my mogul but i have some problems, one of them is the calibration, it looks like the calibration of the screen is not the correct but anyways, that is not the main problem, the main problem is that i dont know how to close and application , i have tried with all the buttons and the application doesnt close, so i have to reset the mogul to start again.
The version on this link http://it029000.massey.ac.nz/vogue/ is the correct one to the PPC6800?? or what is the correct version for the mogul??
Thanks in advance for your help !!
marcos862 said:
Hey !! i have run the haret.exe on my mogul but i have some problems, one of them is the calibration, it looks like the calibration of the screen is not the correct but anyways, that is not the main problem, the main problem is that i dont know how to close and application , i have tried with all the buttons and the application doesnt close, so i have to reset the mogul to start again.
The version on this link http://it029000.massey.ac.nz/vogue/ is the correct one to the PPC6800?? or what is the correct version for the mogul??
Thanks in advance for your help !!
Click to expand...
Click to collapse
The buttons are complicated...to tell you the truth i hold down a bunch of random buttons on the keyboard...hahaha... but hold on... i'll try to map them right now...
Q = unlock
Q = menu (WHILE INSIDE PROGRAMS)
Shift = QUIT
Windows button = QUIT (one might be minimize, idk for sure)
hope that helps...make sure your getting the newest Android release... DZO has 1.0 on his website...http://it029000.massey.ac.nz/vogue/
Hi, I made a video of the problem here:
http://www.youtube.com/watch?v=sRXcBcpSD1w
It's minor, but I'd still like it fixed.
I heard about this as well... does look annoying. What application did you use to test that?
Timmmmmm said:
Hi, I made a video of the problem here:
http://www.youtube.com/watch?v=sRXcBcpSD1w
It's minor, but I'd still like it fixed.
Click to expand...
Click to collapse
I think "Yet Another Multitouch Tester" or something. There are loads of them in the market.
Yea I was just curious. I use multitouch visible test which shows coordinates as well and I tried to replicate this on my Nexus S... doesn't have that threshold though, it's similar to the Nexus One. Wonder why samsung would add that...
BTW could you tell me how many simultaneous touch inputs the screen can register? The original SGS and Nexus S can register 5 according to multitouch visible test. Nexus One as you know can do 2 but when you cross each axis they flip.
Timmmmmm said:
I think "Yet Another Multitouch Tester" or something. There are loads of them in the market.
Click to expand...
Click to collapse
I got up to 10 and then ran out of fingers...
There's no axis flipping problem.
Ok so the physical touchscreen technology is very good... it's just samsung has written in this threshold movement delay, that's a bummer lol.
Timmmmmm said:
I got up to 10 and then ran out of fingers...
There's no axis flipping problem.
Click to expand...
Click to collapse
I think the touchscreen is so extremely sensitive they decided to fool-proof the phone.
without this "sticking" there would be no way for an average person with shaky fingers to register a TAP not a micro-SWIPE.
kreoXDA said:
I think the touchscreen is so extremely sensitive they decided to fool-proof the phone.
without this "sticking" there would be no way for an average person with shaky fingers to register a TAP not a micro-SWIPE.
Click to expand...
Click to collapse
I doubt it. It's virtually impossible to perfectly tap on other phones and it's not a problem. I'm pretty sure 'micro-swipes' are detected by the software layer as taps.
Well does it affect the phone usage otherwise?
I just checked on 3Gs (havent got the S2 yet, damn these late release dates ) and sure enough it has the exact same delay and skip when I slowly try to scroll say web pages. Its always been good enough for me though.
I would be more interested in an accuracy test to see if there are any major issues with the hardware itself. Last test I saw showed everyone but the iPhone digitizer having abysmal performance, I remember the Droid loosing the finger signal all the time.
Any links to the touchscreen performance test you mention?
As for the "deadzone" for touch input, CyanogenMod7 for the SGS has this aswell. Furthermore, it also has a "feature" where if you move your finger slower than a certain speed across the screen, homescreens/browser pages etc will just ignore the touch input. So if you want to minimally correct the framing of a webpage, if maybe the text is just cut off on the side, you need to quickly swipe a very short swipe to get any movement on the screen. Trying to slowly change framing is not possible.
Hardware is fine though, multitouch tests has no filtering like deadzones or speed thresholds.
I have this problem to, Its definitely software I think.
I wonder if its easy to mod to get rid of this deadzone/minimum threshold for scrolling. Anyone able to take a look. Its quite annoying in some things and my old android phone didnt do this.
Angry birds doesn't bypass the problem. It's quite hard to see underneath your finger but the problem is definitely there in "Angry Birds Rio".
Scrolling in some views don't show the problem so badly, presumably because they use the relative movement of each move event, rather than the absolute distance from the down event.
Yeah problem is still there in angry birds my mistake.
Its quite annoying in nova hd when you want to move the crosshair a tiny amount. You can't because of this problem
Anyone know what file in the source could be edited to maybe stop this ?
sorrowuk said:
Yeah problem is still there in angry birds my mistake.
Its quite annoying in nova hd when you want to move the crosshair a tiny amount. You can't because of this problem
Anyone know what file in the source could be edited to maybe stop this ?
Click to expand...
Click to collapse
my hunch is this source is not available, and somewhere in samsung's closed framework or similar.
i know on cyanogen rom, you can go look at the source code for ADW launcher, and you can locate the touch input source code. and you can find all the algorithms like dX, dY, that are used to register swipes, motion, scrolls, etc. its all pretty complicated and impressive code actually.
i'm sure samsung has equivalent code somewhere.
So if we got rid of touchwiz and used ADW launcher would the problem still be there?
sorrowuk said:
So if we got rid of touchwiz and used ADW launcher would the problem still be there?
Click to expand...
Click to collapse
Good question. I'm curious.
Still same problem with adw launcher
This looks more like a kernel thing to me in the touchscreen driver...
Are we able to edit/mod/patch the touchscreen driver in the kernel or is this only something samsung can do ?
sorrowuk said:
Are we able to edit/mod/patch the touchscreen driver in the kernel or is this only something samsung can do ?
Click to expand...
Click to collapse
We have the sources. I'm checking out the frameworks first though in case it's obvious.
Has anyone had an issue with the keyboard thinking that keys are being held down even though they are not? Not sure if this is an android issue but it had never happened when I ran Winmo on the phone.
Running latest kernel, ryannnathans sd setup and highlandsuns ril addition.
I will be typing along and suddenly get like 80 a's in a row with no way to stop it.
It may be the physical keyboard dying but I thought I would ask before I attack it with compressed air and a screwdriver.
FireRaider said:
Has anyone had an issue with the keyboard thinking that keys are being held down even though they are not? Not sure if this is an android issue but it had never happened when I ran Winmo on the phone.
Running latest kernel, ryannnathans sd setup and highlandsuns ril addition.
I will be typing along and suddenly get like 80 a's in a row with no way to stop it.
It may be the physical keyboard dying but I thought I would ask before I attack it with compressed air and a screwdriver.
Click to expand...
Click to collapse
Nothing physically wrong with the hardware, definitely an issue with our port. Not sure if anyone has nailed down the reason, but it seems to be if you're typing and some background process starts up, it can screw with the phone. I've also seen it where the keyboard appears to completely 'cut out' - nothing will be typed.
For both issues, sliding the kbd closed & reopening usually fixes it. This has fixed my issues 100% of the time when the kbd cuts out - however, it has not always resolved the repeat key bug...
I will try the keyboard slide. thanks.
I just had over 200 w's. LOL.
As long as I can stop it its tolerable.
FireRaider said:
Has anyone had an issue with the keyboard thinking that keys are being held down even though they are not? Not sure if this is an android issue but it had never happened when I ran Winmo on the phone.
Running latest kernel, ryannnathans sd setup and highlandsuns ril addition.
I will be typing along and suddenly get like 80 a's in a row with no way to stop it.
It may be the physical keyboard dying but I thought I would ask before I attack it with compressed air and a screwdriver.
Click to expand...
Click to collapse
Yep, I've seen it several times. It seems to happen when the CPU seems to be maxed out for whatever reason. My phone is usually sluggish and on screen buttons are slow to respond too when it's going on. I'm guessing the CPU is getting overloading and missing some of the hardware polling cycles. As a result it doesn't pick up the change in the button state and proceeds as if the button is still being held down. Aside from arrrghhh's suggestion of opening/closing the keyboard, pressing another key seems to interrupt the process (but it will happen again). For me, the main times I have run into the problem was when my phone was NOT overclocked. Certain apps (e.g. Super Manager) seemed to cause the issue more than others too.
Yeah, I have noticed that it only repeats a letter if I hold it. Now I only tap a letter a few times, for example if I want a few 2's I would push 2 a few times instead of holding it.
If it starts repeating what solves it for me is what arrrghhh said, slide the keyboard in and then back out.
I'm still not sure why this occurs though. Maybe the method it uses to emulate keyboard needs a bit of tuning
i believe the stuttering letter bug (hope this name will catch on ) is caused by something in the keyboard backlight commit as that is where is started. In gingerbread when you hold down a key it doesnt repeat it instead gives an option to use variations of that letter, because of this maybe in gingerebread this bug is not as annoying
iv used gingerbread but havnt taken any notice of wether i had the bug or not, its not as bad lately on the kernal i use but i will take not next time
That's an interesting observation, I thought the bug always existed but I can easily believe it has to do with the keyboard backlight. I was looking at that code the other day, it definitely looks suspicious.
Sent from my FRX06+ TP2 using Tapatalk
i have been getting this for quite sometime now...it only started when the backlight in the keyboard started working..
coolwater22 said:
i have been getting this for quite sometime now...it only started when the backlight in the keyboard started working..
Click to expand...
Click to collapse
It does *seem* like the bug was introduced around then. Not positive tho, wish there was a way of tracing/reproducing this issue.
Perhaps trying files from before backlight was added?
If I had the time to look back I would.... Maybe in the next few nights.
I always hit home and let the maelstrom of letters work itself out and then return to what i was doing (texting usually).
gallahad2000 said:
I always hit home and let the maelstrom of letters work itself out and then return to what i was doing (texting usually).
Click to expand...
Click to collapse
Also I have recently noticed that closing/opening the keyboard again seems to stop the progressing letters.
And when you open/close the keyboard the backlights go off then on. This is another observation which hints that the keyboard backlight commit is at fault. It also may be useful to note that when you shut the keyboard it doesn't stop the letters, it is upon re-opening when it stops.
This bug has always been worth putting up to have keyboard bl but it still would be nice to have someone clean ir up and see if they could remove the bug
Jandyman said:
This bug has always been worth putting up to have keyboard bl but it still would be nice to have someone clean it up and see if they could remove the bug
Click to expand...
Click to collapse
We look forward to your patch!
I guess I'll save Jandyman the trouble. I've worked out the patches for userland keyboard and buttonlights. I also now have a kernel with the keyboard light stuff disabled. Will be testing on my phone for the next couple of days and see how it behaves. (So far so good, while entering this post...)
Sent from my FRX06+ TP2 using Tapatalk
highlandsun said:
I guess I'll save Jandyman the trouble. I've worked out the patches for userland keyboard and buttonlights. I also now have a kernel with the keyboard light stuff disabled. Will be testing on my phone for the next couple of days and see how it behaves. (So far so good, while entering this post...)
Click to expand...
Click to collapse
Awesome. I'm sure he'll appreciate that .
FYI, I was going to bug you about this - if the caps/FN and kbd hooks should be in userland anyways, perhaps that rewrite should begin...?
I'm not so sure about caps/fn. I don't think there are any userland hooks for them. Or, haven't found them yet.
Sent from my FRX06+ TP2 using Tapatalk
highlandsun said:
I guess I'll save Jandyman the trouble. I've worked out the patches for userland keyboard and buttonlights. I also now have a kernel with the keyboard light stuff disabled. Will be testing on my phone for the next couple of days and see how it behaves. (So far so good, while entering this post...)
Sent from my FRX06+ TP2 using Tapatalk
Click to expand...
Click to collapse
That's great to hear thank you highlandsun.
When I first noticed the touchscreen issues, I immediately came here. Read all the threads, including the ones about 8-point multitouch, and in one of them, can't remember which, someone posted about having changed the driver to not time out. Is this mod available anymore. I remember the poster saying that the phone was extremely sensitive when you do that mod, but I think I could get used to it.
Sent from my MB855 using xda premium
so i guess it's a no?
I remember about the 8-point multi touch, that was member kennypow3rs! Cannot recall seeing or hearing about the other one. Sorry.
There's a zip you can push through root explorer if you're stock rooted. I'm unlocked on the CM7 rom and it doesn't have that issue anymore and now I have 8 touch points instead of 2.
Ill find the link in a bit and update post.
Found it: http://forum.xda-developers.com/showthread.php?t=1383246
right, i've seen the 8-point zip, i was referring to someone saying they got rid of the error where when you leave your finger in one spot too long, the touchscreen stops responding. say when you're trying to run around in Shadowgun or GTA III. i could have sworn someone said they played with the touchscreen driver to get rid of that time out.
deciplesteve said:
right, i've seen the 8-point zip, i was referring to someone saying they got rid of the error where when you leave your finger in one spot too long, the touchscreen stops responding. say when you're trying to run around in Shadowgun or GTA III. i could have sworn someone said they played with the touchscreen driver to get rid of that time out.
Click to expand...
Click to collapse
I know. Cm7 fixed that issue and added 8 points.
I spent almost 2 hours last night attempting to do the 8-point thing. I then started on Hennsey and said F* It and watched 2 and 1/2 Men!!!! Cannot remember after that!
I believe the timeout was a necessary evil as the screen freaks out without it.
Sent from my MB855 using Tapatalk
So I got the Note and downloaded my n64 emulator onto it. Runs games beautifully BUT whenever I would play anything where I had to hold a button down, like Mario Kart or F-Zero, I could control for about 20 seconds until all input died. I would then have to let go of the controls and start holding again.
I thought this was weird...so...
I downloaded multitouch testers. 2 inputs OK, 3 inputs OK but the more fingers I added the more inputs would glitch in and out. Could get up to 7 and then all touch would fail.
So...
I went to Rogers and told them my issue. One of the girls working there had a Note so we downloaded a multitouch tester on it and got the same results as my Note. Then we opened a brand new Note and downloaded a multitouch tester...same issue as mine.
So could anyone test their multitouch and post results? Thanks
bump to the top
I got 7 as well befor multi-touch freaked out. I technically got 8 but it was not stable at all...
redneck.nerd said:
I got 7 as well befor multi-touch freaked out. I technically got 8 but it was not stable at all...
Click to expand...
Click to collapse
who the **** is actually utilizing 7 point multi-touch? Are spiders buying this phone?
orangekid said:
who the **** is actually utilizing 7 point multi-touch? Are spiders buying this phone?
Click to expand...
Click to collapse
I said in the first post that its affecting games. Learn to read before you open your big mouth.
Sent from my SGH-I717R using XDA App
This is the same thing that would happen on the Atrix. Apparently leaving your fingers in one place too long is interpreted by the software as a drop of water being on the screen and the sensor would go crazy.
I tried it on a multi touch tester and it happens everytime I leave 2 fingers in the same place. Also goes bonkers when over 7 inputs are on the screen.
With the Atrix someone actually disabled the water drop feature, maybe a similar fix can be made for the Note.
via my AT&T Note
theonedub said:
This is the same thing that would happen on the Atrix. Apparently leaving your fingers in one place too long is interpreted by the software as a drop of water being on the screen and the sensor would go crazy.
I tried it on a multi touch tester and it happens everytime I leave 2 fingers in the same place. Also goes bonkers when over 7 inputs are on the screen.
With the Atrix someone actually disabled the water drop feature, maybe a similar fix can be made for the Note.
via my AT&T Note
Click to expand...
Click to collapse
Thank you for this information. Glad to know that someone knows the cause or possible cause.
Using Antutu tester I get 7 Max inputs as well as the timing out of all inputs after 15 seconds or so.
Tested using antutu...
Touch starts going nuts at 5 inputs for me. Loss of touch at around 10 seconds (I did not time it).
Actually just did some more testing... I can make it do all sorts of crazy stuff. I can make a ghost 2nd finger, cause finger 1 to blink loss of location.
I did notice it will never time out if only one finger is on screen or if 2nd finger is continually tapping.
Also noticed that it will not register touch while using s-pen (can't think of a use anyway).
Kinda sucks as a large motivation for me was playing games. I may go look at how the atrix guys fixed theirs and see if it would apply to us.
Sent from my SAMSUNG-SGH-I717 using XDA App
Um how would you use more than 2 while gaming?
Eric-1987 said:
Um how would you use more than 2 while gaming?
Click to expand...
Click to collapse
Are you serious?
A simple game like mario on NES even requires 3. Left or right+Run+Jump
This is a serious issue. One that made me have to switch back to the Galaxy Nexus for the time being (I had a Galaxy Nexus but sold it for the Note) Its upsetting because I love to draw, and found the Note amazing...maybe I will pick up another sometime but for now I only need one device.
If I had known this I'd have never got the Note in the first place because now I own a Galaxy Nexus that I didn't personally buy brand new and maybe I will have issues with it.
Why include such a stupid feature. I've used all my androids and iphones in the past whilst it rained and it was fine. **** sakes.
Hey guys, i saw the post on the N7000 Q&A, i just tested it, can get to 10 fingers very stable, and 11 fingers (with the help of a friend) then it stops detecting, hope that helps.
To clarify the previous post, I asked on the 7000 forum if their phone had similar issues. Appears they do not. I am downloading Samsung kernel source to see if the issue is in the kernel level driver or if it is somewhere in user space.
Sent from my SAMSUNG-SGH-I717 using XDA App
just finished taking a look at kernel driver... seems to be the issue. Some code that doesn't appear in the int'l version that pertains to ghost touch checking.
Matches timeout of first finger after 4 seconds when using two fingers.
Sent from my SAMSUNG-SGH-I717 using XDA App
So which is the better option, change the timeout to something longer (I tried 20 seconds and it works fine)... or remove the functionality of the ghost touch detection all together?
Sent from my SAMSUNG-SGH-I717 using XDA
tablets are supposed to have more muti touch points then phones in theory,,,,but this is a good question, or a setting in build prop to have more responsiveness would be nice, am gonna call a friend who works at Samsung tommorow and see if there is a option for better responsiveness or if this is the best it will get,,,no game will support a 7 finger console so its unneeded and a waste,, i mean i can touch it with one hand with all fingers but testing it with two hands its just overkill in my eyes..
this is the first phone I have had out fo 10 in the past year that does not support 10.
I get 5
Well my main concern was just removing the timeout (I, like the op, like playing roms).I already made a kernel just changing the timeout, but was looking to see if people thought we should just lose the ghost touch all together.
Sent from my SAMSUNG-SGH-I717 using XDA
redneck.nerd said:
I got 7 as well befor multi-touch freaked out. I technically got 8 but it was not stable at all...
Click to expand...
Click to collapse
I've got to 10 using this program-
https://play.google.com/store/apps/...mNvbS50aGU1MTFwbHVzLk11bHRpVG91Y2hUZXN0ZXIiXQ..
MultiTouch Tester
Okay, so I built a kernel with ghost touch completely shut off and it has been working great (little over a day now). At the moment my plan is to run it through tomorrow and if I still have no issues I will release it hopefully sometime Sunday evening for testing. I am thinking of making a version that allows turning it off an on from userspace (or set timeout), should someone want that feature, but I don't know.
As far as 10 finger multitouch goes....
I really can't think of a single time where I thought to myself, "if only my 7th finger on the screen would register correctly.." so I will likely not bother with that unless someone shows a real need.
Sent from my SAMSUNG-SGH-I717 using XDA