yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] WhatzinyourphonE:
@ neoobs, keep looking and I bet you'll find something to with a virtual keyboard. This is big. take your time and just separate all the coding and what not, then have a look at it all.

Since Android is open sorce and all, is this ok with google? Or will they define this as an illegal hack? Even if you found a way to activate multi touch how would you implement it in all the programs?
[G1 Android Development] neoobs:
As far as I am told this is legal and legit.

I can't compile because

A) no linux (but I am dual booting now)

B) I can never figure out how... I always get errors and I hate how linux just runs through the console at 100 lines per second so I can never see what is going on.
[G1 Android Development] alapapa:
all i have to say is:

WOOT!
[G1 Android Development] MarcusMaximus04@gmail.com:
Try piping the compiler output into less/more? i.e.

*compiler and arguments* | less

or

*compiler and arguments* | more
[G1 Android Development] neoobs:
huh you lost me... but it is ok I don't need to know I am really dumb when it comes to certain things. I just think it is too much work... what can I say I am lazy.
[G1 Android Development] vertigo1:
Actually

Although everyone is correct that non-hardware supported touchscreens act the same way when messed with in this matter, that doesn't mean this device doesn't still have the capability. All other WinMo phones use a resistiive-touch display. The HTC Dream and Apple iPhone use capacitive-touch screens. Look at the underlying technologies. The HTC Dream definately has the ABILLITY to do it, it's just not support in this version of the software. Capacitive screens are very flexible.
[G1 Android Development] neoobs:
I think it is supported just not turned on LOL I think if enough of us that knew what we were doing went through the code we would see that a lot of stuff is just commented out maybe because there is a bug here or there.
[G1 Android Development] Fnorder:
Won't work as errors usually go to STDERR

Try:

STUFF 2>&1 | tee logfile
[G1 Android Development] RyeBrye:
Another update

I wrote a proof of concept app.

http://www.ryebrye.com/blog/2008/11/22/g1-multitouch-proof-of-concept-video/

Maybe I'll do some gesture stuff next week, depends on how much time I get. I might work on a pinch-to-zoom implementation though.
[G1 Android Development] momentarylapseofreason:
Good choice in music! :)

I know that it's just glitches, but when I showed my buddy, he insists STILL that those glitches are actually the software going back and forth between the 2 fingers (same can be done on a non-multitouch screen).

Thanks for the work though!!!!! Can't WAIT to see what else you have in store for us!!!
[G1 Android Development] Phromik:
The G1 is really, actually capable of multi-touch (for real)

Never mind, didn't see RyeBrye's post in the other thread. Feel free to delete.
[G1 Android Development] Darkrift:
Even if that were true, it is enough to show 2 fingers moving. With this method (even if its showing one finger then the other) it would know that the fingers are moving together/away from eachother and be able to act accordingly.
[G1 Android Development] neoobs:
To really prove it can you make the app turn on and off the multitouch feature dynamically? Then you can see the difference between single and multitouch and that would really stick it to the man.
[G1 Android Development] keatonreckard:
can whoever made the app move your fingers independantly?(like move them toward each other then away and toward each other and so on) because you keep them moving parallel and i still think this is kind of a software glitch, not true multitouch.
[G1 Android Development] faaque2:
Full Working Multi-touch

http://lukehutch.wordpress.com/android-stuff/

not confirmed.
[G1 Android Development] cboy007:
New Multitouch Video

http://www.androidauthority.com/ind...-multi-touch-demo-works-with-stock-g1-kernel/

PROGRESS!
[G1 Android Development] momentarylapseofreason:
http://lukehutch.wordpress.com/android-stuff/
[G1 Android Development] momentarylapseofreason:
Why would you post this in 2 threads?
[G1 Android Development] Phromik:
Sweet. At least there is some progress and at minimun, multi-touch zoom is capable, so that's good. Looks promising. ;)
[G1 Android Development] Koush:
RyeBrye already demo'd multitouch a few months ago:

http://www.ryebrye.com/

I pointed out that the driver code was in fact reporting the multitouch values, and that his driver modifications were unnecessary (somewhere on this forum). The multitouch information is just not handled/exposed at the Java API level. http://xdaforums.com/showthread.php?t=452647

Give a man some credit ;)
[G1 Android Development] g1ftmfw:
i want multi touch so bad!!!!!!!!!! cmon devs please make this happen!!!!!
[G1 Android Development] momentarylapseofreason:
That's the thing... read the page it links to. He has fixed the Java issue
[G1 Android Development] cboy007:
why dont we have multitouch?! some people say it has something to do with a patent apple filed, but then you see microsoft surface and the palm pre and tons of other devices having their applications do the same thing that apple's does.

did google choose not to include this? will they enable it in the future? (cupcake surprise? =D)
[G1 Android Development] dixxa:
have a look !

http://lukehutch.wordpress.com/android-stuff/
[G1 Android Development] bshakil:
Full Working MultiTouch on the T-Mobile G1 Android Phone

Ok i know a lot of ppl are waiting to hear this ..

Here is the Video

http://www.youtube.com/watch?v=enAinQizxyM

Here is the link to Instructions (thanks to Luke Hutchison for detailed Description)

http://lukehutch.wordpress.com/android-stuff/

Current Steps Posted on his website are as follows.

"If you follow the directions I link to (and then the instructions that those pages link to), then you should be able to do the following pretty easily — the instructions are very clear:

(1) reflash your phone to RC29, which is rootable

(2) get root

(3) reflash your bootloader, and reinstall system keys so that you can in future flash anything you want

(4) reflash to a hacked RC30 (JesusFreke’s version) — rooted

(5) download the Android source, apply my patch, build it, and flash it over the top of RC30 using fastboot to flash system.img and boot.img

(6) to go back to where you were, reflash JF’s RC30 (you may or may not have to reflash the engineering bootloader before that). If the phone won’t boot, try wiping your personal data (Alt+W) in the reflash screen.

Note that there is one step missing in the linked instructions: After you reflash/wipe the system, you often have to go into system settings and re-enable USB debugging to proceed any further.

All that is pretty straightforward and won’t break your phone at all if you follow the instructions exactly. From that point on, if you ever brick your phone, all you need to do is put in an SD card with either a replacement bootloader or a replacement system (Linux + Android) image, and hold down two buttons while switching the phone on — and you can go back to your old setup.

Because the Android source code in git is not fully functional, I don’t recommend keeping your phone reflashed — my address book, messaging, and the soft keyboard were all broken using git head, and I would miss most incoming calls — so I flashed my phone, spent three days and night hacking this, then went back to RC30 because I couldn’t bear my phone to be broken like that for any longer…

The best idea is to try to follow the instructions, and ask on some of the linked bulletin boards if you get stuck. Good luck!"

I am sure XDA Developer community will be able to help bringing the current efforts of Luke Hutchison to the next Level.
[G1 Android Development] Meltus:
Pretty cool, but does this actually have any use atm? Or would someone need to develop some multitouch apps?
[G1 Android Development] Smokuevo:
tooo much ill just wait
[G1 Android Development] ArronL:
This is nice and it is a little too much to do by yourself.

Maybe JesusFreak can add this onto his custom rom?
[G1 Android Development] momentarylapseofreason:
Repost ... yawn
[G1 Android Development] benmyers2941:
The last post got merged into the massivly unproductive multi-touch theroy thread. Hopefuly this one will stay seperate
[G1 Android Development] Gary13579:
Seriously. XDA mods need to back off, I've said it a couple times now. Thread merges are completely counter productive, especially for massive cluster Nuts of useless posts like that.

Edit:

I refuse to be called that.....

Watch the choice of words used, please. :)
[G1 Android Development] khoaitaychienvn:
oh well, so people have to be more careful to post anything here, eventhough they just wanna contribute something, unless they wanna get some bash
[G1 Android Development] stogchris81:
noob

Is there anyway to make this easier to install? I have root , however I would not be able to follow these instructions.
[G1 Android Development] Preech2003:
UPDATE:

On the Iphone the "Lite" Version of "LightBike" is Released and it is Free & only 1 player but the "Full" Version will be released in Febuary & will allow 2 Players at once on one screen to play.

They will charge for the full Version

Availiable on the Iphone App Store only...
[G1 Android Development] Koush:
It's not possible to add Multitouch to anything but the upcoming cupcake right now. There is no tag of the "RC30" builds in the Android source. Just Release-1.0.
[G1 Android Development] Preech2003:
what are u taking about. did u do your research & click on my links. U can achieve multitouch on a regular modded RC30 that jesusfreak made. here are the directions right here:

(1) reflash your phone to RC29, which is rootable

(2) get root

(3) reflash your bootloader, and reinstall system keys so that you can in future flash anything you want

(4) reflash to a hacked RC30 (JesusFreke’s version) — rooted

(5) download the Android source, apply my patch, build it, and flash it over the top of RC30 using fastboot to flash system.img and boot.img

(6) to go back to where you were, reflash JF’s RC30 (you may or may not have to reflash the engineering bootloader before that). If the phone won’t boot, try wiping your personal data (Alt+W) in the reflash screen.

Here is the Video

http://www.youtube.com/watch?v=enAinQizxyM

Here is the link to Instructions (thanks to Luke Hutchison for detailed Description)

http://lukehutch.wordpress.com/android-stuff/
[G1 Android Development] JesusFreke:
Unfortunately, I don't think multi-player like this would be possible, due to the way multi-touch on the G1 works. There are some fundamental limitations that would make something like this unplayable.

In particular, if there are two touches on the screen that are near each other in a row or column, then the phone "snaps" the points together in that row/column, because it can't differentiate between the two touches. In some cases, it's even possible for the points that it reports to be completely different than where you are touching the screen.
[G1 Android Development] momentarylapseofreason:
All that just to plug your site?

Your site needs a lot of work for one.... screaming, distorted intros don't sell shirts and navigation is horrid. Not to mention that having 2 shirts to choose from isn't pleasant.
[G1 Android Development] Preech2003:
YES JesusFreak there are limitations but.....

in the "LightBike" for iphone. this would work simply becuz one finger is at one side of the screen & the seconds players finger is at the oppisite side of the screen. case Closed. No fingers would have to ever do any movement that is close to each other & they both fingers stay at the oppisite side of the screen. both fingers do LEFT & RIGHT motions only in the 2 player version of lightbike. So give it a try & see if this is a feature that u can turn on and off in your new RC Rom.

Give it a try yourself then watch the Pankaku 2player demo video. it really works!!
[G1 Android Development] JesusFreke:
Watch luke's video again.. In particular, watch around 1:10-1:20.

See how his fingers are on opposite sides, but sometimes when they cross each other, the reported positions are actually opposite of where his fingers are. And notice how the 2 points "snap" when his fingers cross each other? That's the reason something like this wouldn't be feasible on the G1.
[G1 Android Development] Preech2003:
Ok your right jesus freak & koush but lets get down to the nitty gritty

I think You'll both Agree that this will definately proof my work. Definately!

I also sent a simular tutorial to "Robert Green" The developer of the "Light Racer 3D" game coming out in a couple of months.

For the MultiTouch 2Player "Light Racer 3D" game for G1 to work correctly just like the Iphone "LightBike"game; You will have to place the 4 LEFT & RIGHT directional buttons on the 4 corners of the G1 Screen so they dont cross the middle. The buttons can't be placed No where close to the middle of the screen so that the G1 multitouch dosent interlace both finger into one and snap the 2 fingers movements together into one finger movement. The good thing is u dont have to drag left or drag right to turn left or right. U just simply TAP the screen once (NO SLIDING or DRAGING).

If you look at the Iphone "LightBike" Demo Video Link provided below, U will see on the 2player mode demo that the 1st Player on the bottom is "TAPPING" the "Bottom" LEFT & RIGHT corners of the screen & the 2nd Player on the Top is tapping the LEFT & RIGHT "Top" corners of the screen so there is no sliding across the middle Axis of the screen to get a "SNAP" together error joining the two fingers gestures into one. Infact TAPPING instead of SLIDING is the most genius thing that the guys at the Pankaku Development Team could have done. Because it makes it perfect for a direct port of the game onto a G1 thats "ROOTED" with MultiTouch if they wanted too....... which they dont.

CONCLUSION:

So in conclusion when this "Light Racer 3D" game is being developed make sure fingers dont have to cross in the middle of the screen & make the gestures TAPPING gestures not SLIDING or DRAGING Gestures. U must put the 4 buttons at the 4 corners of the G1 Screen.

Example 1:

-LEFT & RIGHT Buttons on Bottom

-LEFT & RIGHT Buttons on TOP

-BOTTOM is for Player 1

-TOP is for Player 2

BOOM! That simple.

Using Luke Hutchinson's Multitouch Tutorial would work in this manner.

I really hope this was helpful. BUT if u read what i wrote and analize the LightBike Iphone Demo Video Carefully. U will see exactly what im talking about.

*In the video for demo 2 look very carefully where the players are TAPPING there fingers on the screen:

http://www.youtube.com/watch?v=XdzIw01JuG8

*Here's the YouTube Video For Luke Hutchinson's MultiTouch App. I downloaded

& it works great for ZOOMING IN & OUT in google Maps & google browser:

http://www.youtube.com/watch?v=enAinQizxyM

*Once Again Here's Luke Hutchinson's Tutorial on how to achieve multitouch:

http://lukehutch.wordpress.com/android-stuff/

-SEE WHAT IM TAKING ABOUT NOW "JF"

-THIS SHOULD PROOF MY POINT "KOUSH"

Stay Blessed Ya'll

OVER n OUT!
[G1 Android Development] Koush:
If you read the article, you would know that cupcake is a requirement to do the multitouch stuff. You would also know that I wrote the Cupcake installation guide that you are talking about and is also referenced in Luke's post.

Which leads me to my original point.... when you build off the Android source, you are building Cupcake (which is still quite unstable). Multitouch is only possible on Cupcake, because the source code for RC30 is not tagged in the Android branch. I.e., it is not possible to build RC30 with the changes you would need to make. And it is not possible to "patch" RC30 to add multitouch. Unless someone has figured out how to patch the classes.dex in framework.apk. And I'm going to take a wild stab and say, that's not going to happen.

God my brain hurts, I'm going to bed.
[G1 Android Development] Preech2003:
KOUSH

MOD EDIT: Removed reference to inappropriate content

Im just joking KOUSH. JF's NEW 1.4ROM is a success & includes multitouch. that new 1.4 is amazing. i told you we the multi touch was capable & here it is. Im still talking to Robert Green to get the LightBike 3D to use the full multi-touch capibilitie but it will happen.

Peace. Talk to u later
[G1 Android Development] vette95:
Man, if anyone sees one, I'll spread it (not anonymously) all around , and Apple can't do jack-"gastric system by-product" about it.

As I remember, on one of the flashes to my G1 i got multitouch on the browser, but then I updated and it's no more, though i remember seeing some file, an XML file I could delete from my droid and the multitouch would magically return. If anyone sees a link on what this file is, I would be VERY grateful.
[G1 Android Development] bolmedias:
Nice necropost you got there.
[G1 Android Development] rage2wrath:
Digging up some lost treasure.
[Google Pixel 6 Pro] bush911:
Forgive me, If I am asking something that was previously answered.

I have been looking around this community, also did some homework, but I am still confused and need double-check.

It seems that fastboot flashing is getting more and more complicated these days. I always just did a flash-all bat (after removing -w) and flashed the patched img for my previous Pixel 1 and 3.

I have flashed my Pixel 6 to November firmware, January firmware, patched with the latest magisk without disabling any flags for now.

Everything goes well until I happen to flash several third-party kernels using EXKM. I am not very sure whether flashing a kernel or recovering to magisk patched stock kernel via EXKM causes the issue.

Now every time I boot the phone, the annoying corrupted message shows up. I was stupid that when I saw that message, I immediately flashed the stock boot.img, then the full firmware. It turned out that I can move forward by pressing the power button after the corrupted message appeared. You must know, that annoying message is still there.

To cut a long story short,

Now I need your help to confirm before proceeding.

1. If I try to live with this corrupted message, is there any further potential damage to my phone, will it become soft-bricked even bricked?

2. If I am going to disable these flags, will it be a must to disable them every time I monthly flash the google firmware?

3. For now my phone is with the latest January firmware and that annoying corrupted message is rooted. How can I proceed? just

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

then, reboot the bootloader and do a flash-all without removing -w

then flash patched boot image.

Will the above operations get rid of the corrupted message and bring my phone back to normal?

Thanks very much in advance for your attention and I appreciate your comments pretty much

Stay safe
[Google Pixel 6 Pro] bush911:
OK, I have finally managed to flashed January firmware with flags disabled, skipping reboot, and patched again.

For now, the annoying message disappeared. That is to say question 3 get answered:D

I do like this

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-oriole-slider-1.0-8013568.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-oriole-g5123b-93368-211225-b-8029609.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot --disable-verity --disable-verification --skip-reboot update image-oriole-sq1d.220105.007.zip
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot root24001.img
fastboot reboot

echo Press any key to exit...
pause >nul
exit

credit to @guruoop

Answeres to question 1 & 2 still welcomed
[Google Pixel 6 Pro] gpvecchi:
Sorry, but I read Oriole... Do you have a P6 or a P6 Pro? P6 Pro is Raven, not Oriole... Oriole is P6.

Could you have the wrong firmware?
[Google Pixel 6 Pro] Lughnasadh:
1. That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. See documentation below.

Also, pressing the power button puts the phone in restart mode and will allow you to boot up in this circumstance. I don't believe "living" with this corruption message will lead to any further damage to your phone, but can't be 100% sure of this.

2. Depends. You no longer have to have them disabled if using Canary 23016 or newer to boot a Magisk-patched boot image. However, some custom kernels may still require them to be disabled, depending on whether they have updated the Magiskboot binary to Magisk 23016 or later. Others that provide a boot image (among other images) you can probably just patch the provided boot image with Magisk 23016 or later without having to disable verity and verification. Best to check with the custom kernel developer beforehand (or check in their OP and threads).

So, depending on whether you are using a custom kernel that may require these 2 flags to be disabled will determine whether you need to keep those flags disabled when updating to a new monthly security build. If just updating, then you don't have to keep these flags disabled. If you decide to keep these flags enabled, and then later decide to disable them you will have to perform a factory reset after disabling them again.

Boot Flow | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] XSLdesire:
that's also the issue I run into
[Google Pixel 6 Pro] bush911:
Thank you very much for your detailed explanation, it really helped.

To conclude:

Once these flags are disabled, every time flashing a full image will re-enable them again if I don't add "--disable-verity --disable-verification --skip-reboot" to the flash-all.bat.

Once the flags are enabled again, next time if I disable them again, it will lead to a factory data reset again.

Am I right?
[Google Pixel 6 Pro] bush911:
Thank you for your attention. I mean to post here as it is more active here:)
[Google Pixel 6 Pro] Lughnasadh:
Correct. Although you don't need to add the --skip-reboot unless you are doing something else like flashing the patched boot image during the same flashing session, which it appears you are doing, so yeah, all good 👍
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] huyho255:
Hello everyone,I'm using the Corvus rom for the Redmi Note 5, but its not connect to the computer; however, it works on other phones. Could someone please assist me?
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] jack lamters:
Be sure to use the cable that came with the device. Some cables can charge the phone, but not connect to a computer. ... Restart your device and computer. Update device software to the latest version
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] huyho255:
It used to connect the cable, but since installing Corvus, it no longer does.
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] jack lamters:
Can you try another cable or try to connect it using another computer?
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] huyho255:
It works on other phones, and I only have one computer.

It works on other phones, and I only have one computer.
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] jack lamters:
Do you receive a pop-up in your Xiaomi when you plug it in with your pc? if yes, choose the option with share data or transfer data. if nothing above works, I recommended you try to connect your phone with another pc.
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] huyho255:
Yes, I selected data transfer, and I will attempt to connect with a different computer, thank you.