Well to start with I want to start this thread because the desire is a great phone but it has it's limitations, but we have seen what kind of great devs we have arround here if I were the ceo of HTC I would imediately hire all of you great guys. Anyway this thread is about a hack for true multi touch for the htc desire as you propabely know the desire has just 2 input and if you cross axes it gets disturbed. So this hack is made by a droid incredible dev and the dev says it is possible for every amoled display.
What the hack does:
- it gives you true multi touch ( for the htc droid incredible )
in my opinion I don't need a multitouch screen that supports 10 touches at the same time all I want is fully working dual touch so I can rotate google maps and if the touches cross axes they don't get disturbed
any way here is the original thread:
I'm sure everybody knows by now, but the multi-touch bugs seem to be related to the recovery. In my little bit of free time I have been working on an updated recovery that supports multi touch for all devices.
I am fairly confident that all amoled devices are able to get either 3 or 5 point multi touch, but it seems that there still may be issues with some (or all) SLCD devices, this is why I need many testers. So for those of you who are willing to help out, I need you to follow these instructions:
1) Download http://chad0989.dyndns.org/PB31IMG.zip
2) Place on the root of your SD card.
3) Boot into hboot (vol down and power when turning on)
4) Select yes when it asks if you want to start update.
5) Select no when it asks you if you want to reboot.
6) Choose recovery
7) Flash a KNOWN working multi-touch kernel.
Reboot and use the multi touch test app from the market to see if you have more than 2 touch points.
Report back the following:
1) Are you SLCD?
2) Yes or no on more than 2 touches
3) What atmel touch device you have - open a terminal and type cat /sys/android_touch/vendor and report what is says.
4) Hardware version
Thanks everyone!
SLCD Only:
Since the one above still seems to not be working for you guys, heres another try at it:
http://chad0989.dyndns.org/PB31IMG-test2.zip - Don't forget to rename it to PB31IMG.zip and place on the root of the SD.
Also has anyone with an SLCD ever had multitouch an any time? What were the conditions that you had it?
SOURCE: http://forum.xda-developers.com/showthread.php?t=906721
I AM NOT A DEV I ONLY WANTED TO START THIS SO I HOPE SOMEONE COULD FIX THE MULTI TOUCH PROBLEM I AND ALLOT OF OTHER PEOPLE WOULD BE REALLY GRATEFULL
NOTE: This is only for use by DEVELOPERS, and those confident in flashing untested software to their devices.
No offence
Please delete threat!?
Wow! Nice work, but seems a bit risky
Sent from my HTC Desire using XDA App
From what I've read, and partly concluded myself, the screen is limited to 2 (two) points. It's a hardware limitation. No amount of software can change this. What has been done though is to improve the prediction of movement to counteract axis flipping.
I would also advise nobody to flash this file because it's a recovery image for a different board. Although brick is unlikely, it could result in some bad stuff.
EDIT:
Yes, remove this thread. It's not useful.
blatently the op just copied and pasted this from the incredible forum and hasnt even tested it himself
why may i ask?
because i did, the recovery is made for the incredible and incredible only
you can only flash the recovery via fastboot as the desire doesnt understand that pbimg
i flashed it via fastboot and guess what? boot hang because its for the incredible
i flashed back to the amonRA i was using before because i have s-off and i can do these things
rather than copy and paste, you should test things yourself first
also you should ask if anyone can work on it and like back to the incredible thread you took it from. a decent dev might be interested
because you copied the thread it makes it look like the recovery is compatible
he says EVERY DEVICE because he was referring to EVER VERSION OF THE INCREDIBLE, some xda admin saw this and thought he meant all androids and made a news article
Sounds interesting, but might be worth reading the whole thread. Quite a few people ask if this would work for the Desire, and the consensus seems to be that it is a hardware limitation with the Touchpanel on the Desire (as has been mentioned in a few threads, here in our very own subforum).
From what I understand, the hack used in the Incredible is kernel-based. We would need someone to look into the Inc kernel to find out what the hack is, then attempt to compile a Desire specific kernel for us to try. Even then, from what I understand, best we could hope for is resolution of the "crossed axis" and "sticking points" issue that plague - true (ie >2 finger) multitouch is out of our reach due to the Clearpad display. Though, I would happily accept a patch that gets rid of the crossed axis issue.
Since I have about exhausted my tiny knowledge about kernels etc, will have to sit back and hope someone more able turns up!
BTW, the original post in the Incredible thread states that this will work for all devices. What they mean is that the hack will work for all variants of the Incredible (ie AMOLED/SLCD; S-On/S-Off) NOT all Android devices
Would highly recommend you only try this if you know what you're doing/ need a new paperweight.
In his defence, don't think the OP was trying to claim this works for the Desire - rather, trying to bring this knowledge into the Desire fora, in the hopes of a passing dev taking an interest.
Daelyn said:
From what I've read, and partly concluded myself, the screen is limited to 2 (two) points. It's a hardware limitation. No amount of software can change this. What has been done though is to improve the prediction of movement to counteract axis flipping.
I would also advise nobody to flash this file because it's a recovery image for a different board. Although brick is unlikely, it could result in some bad stuff.
Click to expand...
Click to collapse
Well as i said i am not a dev my self i just started this for the devs and i didnot tried to flash that recovery i just posted this maybe its useful for some devs anyway as i said in my first post i don't need more than just two finger input as long as they are full functional if the desire display sensor is realty limited to just two finger inputs (although the dev says this hack is losibble for every amoled display) maybe some devs can make a hack so that the two finger input works well so that you can twist the new Google maps with two fingers in other words if the desire s display is limited to a dual input i want a fully working dual input and that's why i started this thread
I'd suggest you post a disclaimer and warning that this is only for Developers and unless users are confident, they should steer clear of this for now. Make it nice and prominent in your first post!
A question, is this hack working on Droid Incredible only because HTC changed the touch-panel on the Incredible? They change our Clearpad 2000 with touch-panel made by Atmel. There is no hack developers can do if the problem is the hardware...
Am I the only one who thinks this thread should be deleted?
I can see that a lot of eager people might, not reading the entire thread, flash their phones and stuff them
Yeah should be remove.
It's good that after the post, a senior member pointed out right away that this is not for desire.
The guy did not say to flash your phones, it's for devs to see if they can use this to solve some issues with the desire touch panel. The thread should not be deleted. Stupid people brick their phones because they do not read trough the entire thread, they deserve what's happening to them.
craoul said:
The guy did not say to flash your phones, it's for devs to see if they can use this to solve some issues with the desire touch panel. The thread should not be deleted. Stupid people brick their phones because they do not read trough the entire thread, they deserve what's happening to them.
Click to expand...
Click to collapse
no but his post can be read that its possible to flash as it has links
if it was a good thread for devs it would be like
"multi touch hack for incredible found, is it possible a dev can look at xxxthread reagarding this issue to see if it can be implemented into desire kernals and a 2.5.0.5 cm recovery built to support it?"
I read the entire thread, i also flashed it from the incredible thread not this one as XDADEVS did exactly the same and posted it on a news article as "all androids" with an image of a nexus S with loads of fingers lol
the dev is only interested in the incredible
As for bricks, its not really a brick. none s-off people cannot flash it as our desires do not understand that pmimg so the only way is via fastboot with s-off
recovery just hangs so you can power off and then flash your old recovery back on
not dangerous, just pointless
NOTE: This is only for use by DEVELOPERS, and those confident in flashing untested software to their devices.
Thread closed as this could be dangerous if you are unaware as to what you are doing.
Related
Have there been any rumors or murmurs of any development on any ROMs or kernels for the Echo?
Jamin13 said:
Have there been any rumors or murmurs of any development on any ROMs or kernels for the Echo?
Click to expand...
Click to collapse
Not a one that I am aware of. I sent a message to the XDA Admins regarding an Echo section, but nothing has ever come of it.
J
Ahah, thanks.
I guess there's no interest in it. D:
Sent from my M9300 using XDA App
i was surfing google and there is one. its a maybe if it even works since i havent tried it. but according to the site u can update ur froyo 2.2 to 3.1 im not sure how well it is,but id like a root that can help keep battery life last longer and the most updated software that android has to offer.
bmanscap28 said:
i was surfing google and there is one. its a maybe if it even works since i havent tried it. but according to the site u can update ur froyo 2.2 to 3.1 im not sure how well it is,but id like a root that can help keep battery life last longer and the most updated software that android has to offer.
Click to expand...
Click to collapse
If you update to 3.1 can you still root it?
Just_Josh said:
If you update to 3.1 can you still root it?
Click to expand...
Click to collapse
I'm pretty sure those are fake considering 3.1 is for tablets.
Sent from my Kyocera Echo.
^^^^3.1 Ports to android phones have been acheived, it doesnt have to be on a tablet always
mahgiaz47 said:
^^^^3.1 Ports to android phones have been acheived, it doesnt have to be on a tablet always
Click to expand...
Click to collapse
Yeah, that's true.
I still don't trust it too much considering there isn't a Clockwork Recovery Mod or any method of flashing those to the phone AFAIK.
Rooting Yes! It's Great! But lack of backup util is scary
Yes, my Echo has been rooted for four months using Z4root.
I haven't tried to find an alternate ROM because, frankly, the stock one is so much better than anything HTC ever offered me.
My main interest in rooting the Echo was to get rid of all the dumb Sprint apps and, most important, extend battery life by using power saving apps only available with rotted phones My favorites being SetCPU and and Timeout3G.
Also, if you like to blacklist callers without ever hearing half or three quarters of a ringtone before the call if blocked, Root Call Blocker is the best blocker in the Market, but as the name implies it is for rooted phones only.
Anyway, all these things work great and I can get through an entire day (most of the time) on one recharge ... even more impressive I can leave the phone off the recharger at night and start the next day having lost only three to five percent of the charge ... as opposed to 40-50 percent before rooting.
The problem -- and its a very real problem -- is that there is no way that I have found to do a Nandroid or other complete system/recovery backup for the Echo.
When I open ROM Manager Premium it tells me there is a new version of Clockword MOD available, but, of course, it's lying ... at least in regard to the Echo.
If I try to use the backup current rom option in ROM Manager it reboots and freezes on the green symbol with the yield sign and need to be hard rebooted by pulling the battery.
Now, to make matters worse, Sprint has started downloading auto firmware updates that may or may not brick rooted phones. Since my phone is now working perfectly the way I want it to I wouldn't install the updates anyway if I could avoid it but avoiding it is the issue ... there is a toggle to turn off checking for and auto downloading Android updates but none for eliminating auto firmware updates.
So two questions?
1. Has any figured out how to backup the Echo?
2. Does anyone know how to disable auto system updates?
Thanks
In answer to your 2nd question, if you are rooted, install File Expert, hit menu button, settings, file explorer settings and check root explorer.
exit file expert (should not have an icon in the status bar)
open file expert, hit back 2 times, goto system, hit menu button, more, mount, mount as read write.
goto etc, security, long press on otacerts.zip, file operations, rename, otacerts.zip.bak.
it will tell you about the update and download, but wont install because it cant validate.
if someone doesnt post a reply to your 1st question by tomorrow, I will tell you how to do that too, but right now I am going to bed...this post may not make a lot of sense, but hopefully you can figure it out, if not, let me know and I will clean up tomorrow.
Sorry it took me so long to thank you
I've been overseas and out of touch ... your solution fir disabling auto system updates is great ... thank you.
Do you know if anyone has figured out how to do a Nandroid type backup on the Echo yet?
For the record, I love this phone more every day ... which is quite the reverse from my experience with various HTC and Samsung smart phones.
Yes, the release Echo is a bit prototypy, but there will, hopefully, be an Echo 2 with a smaller band between the screens, etc.
What most people will never know is how incredibly misleading most of the reviews were. Not exactly untrue, but misleading.
For example, almost everyone panned the Echo's camera for being slow, producing under-saturated colors, only having a 2-1 zoom ratio, etc.
Truth is there is nothing wrong with the Echo's camera, hardware-wise it is the best phone camera I have ever used (and I used to shoot pictures for a living,) far better than a couple of HTC 8mp cameras I've tried.
What is horrible is Kyocera's implementation of the standard Android operating and color control system. It is just awful, even worse than HTC's (Samsung is pretty good with this), which I would have said was impossible.
Download a decent camera app from the Market and the Echo shines. Vignette, my current favorite, virtually eliminates the standard app's focusing and shutter delays, produces rich, sharp color correct images and offers a 10:1 zoom ratio.
ekb606 said:
I've been overseas and out of touch ... your solution fir disabling auto system updates is great ... thank you.
Do you know if anyone has figured out how to do a Nandroid type backup on the Echo yet?
For the record, I love this phone more every day ... which is quite the reverse from my experience with various HTC and Samsung smart phones.
Yes, the release Echo is a bit prototypy, but there will, hopefully, be an Echo 2 with a smaller band between the screens, etc.
What most people will never know is how incredibly misleading most of the reviews were. Not exactly untrue, but misleading.
For example, almost everyone panned the Echo's camera for being slow, producing under-saturated colors, only having a 2-1 zoom ratio, etc.
Truth is there is nothing wrong with the Echo's camera, hardware-wise it is the best phone camera I have ever used (and I used to shoot pictures for a living,) far better than a couple of HTC 8mp cameras I've tried.
What is horrible is Kyocera's implementation of the standard Android operating and color control system. It is just awful, even worse than HTC's (Samsung is pretty good with this), which I would have said was impossible.
Download a decent camera app from the Market and the Echo shines. Vignette, my current favorite, virtually eliminates the standard app's focusing and shutter delays, produces rich, sharp color correct images and offers a 10:1 zoom ratio.
Click to expand...
Click to collapse
I don't think it's possible without a custom recovery and there doesn't seem to be much hope with that.
The only way we would get some development on this would primarily be if a dev was given an Echo. All we need is a recovery and then we can move from there.
Sent from my Kyocera Echo.
It just seems like there should be some way to backdoor into the root system via USB or tether and hijack every bit and byte on it onto a hard drive ... given Android's huge user base, you'd think some clever hacker would have already figured that out and posted the hack somewhere.
ekb606 said:
It just seems like there should be some way to backdoor into the root system via USB or tether and hijack every bit and byte on it onto a hard drive ... given Android's huge user base, you'd think some clever hacker would have already figured that out and posted the hack somewhere.
Click to expand...
Click to collapse
I want to say whatever clever hacker it is may be too clever to put it out in the open to be patched...or sucks too much to crack the Echo. XD
Sent from my Kyocera Echo.
website
heartheecho.webs.com im co owner. check it out.
Humm....over 600 members in it's infancy...we have gingerbread root, recovery, themes, bootamimations, and many members wondering why xda has refused to make a Kyocera Echo section. It's not like there isn't any interest in the phone, it sold well, and even today your lucky to find one under 150$ on ebay.
Thanks to the developers who gave the echo the chance it hasn't gotten on here in xda.
Not hating, just saying...why? why isn't there a dedicated section for us Echo owners after all this time? Why ignore us after repeated request? I don't get it. It's a Great phone. My 1900+ benchmark matches or beats many phones listed on xda.
Dual-screens make for too big a challenge? A dedicated few don't think so.
I gave up my Evo 4g for this phone....Twice. There's just something about this phone I really like, eh?...
Personally I'd like to see what the big shots on xda could do with this phone. That's all we were hoping really...more Rom development.
goygacon said:
Humm....over 600 members in it's infancy...we have gingerbread root, recovery, themes, bootamimations, and many members wondering why xda has refused to make a Kyocera Echo section. It's not like there isn't any interest in the phone, it sold well, and even today your lucky to find one under 150$ on ebay.
Thanks to the developers who gave the echo the chance it hasn't gotten on here in xda.
Not hating, just saying...why? why isn't there a dedicated section for us Echo owners after all this time? Why ignore us after repeated request? I don't get it. It's a Great phone. My 1900+ benchmark matches or beats many phones listed on xda.
Dual-screens make for too big a challenge? A dedicated few don't think so.
I gave up my Evo 4g for this phone....Twice. There's just something about this phone I really like, eh?...
Personally I'd like to see what the big shots on xda could do with this phone. That's all we were hoping really...more Rom development.
Click to expand...
Click to collapse
I don't know why people aren't big into this phone either. Probably cause it wasn't a HUGE hit like all the others. Its gotta be all the "bad reviews" on the web. We tried emailing xda admins, talking to other devs, and just trying to get it noticed. I'm thinking some real reviews. You know? If anyone notices all the reviews on the web EVERYONE is still unrooted, on stock 2.2, and barely knows what the phone was MEANT to be used for, MULTITASKING!!!!!!! But now that here I am ranting about it, my brain just came up with this hopefully awesome, cool idea. We should make a real review. I'm not saying stock 2.3.4. Take my phone for example. Deodexed, themed, rooted, cmw based recovery, mods, Apps ported, super fast, scores on benchmark over 2000+, speed tests, and anything else. Its time. Time for some development on this nexgeneration dual-screen phone. It can and will be done! That is all.
Sent from my M9300 using xda premium
VI agree this phone isn't done yet its super close to stock 2.3.4 which would make for decent ports we need up to date reviews and more publicity it worked with the lg thrill and optimus 3D hell go to other forums requesting PM developers who work with the N1 dInc and htc evo 4g they could all help us and all have cyanogenmod lets get this ball rolling what do u say guys?
Ps I've posted on a couple sites a way to root 2.3.4 super easy if that's your issue then you will be rooted soon
Sent from my M9300 using Tapatalk 2
Build Kyocera Echo Stock ROM from source?
I don't know if anyone cares about this phone anymore, but I would like to build the stock ROM from source code and see where I can go from there.
I have AOSP android-2.3.4_r1 built (generic-eng) and running in emulator, and M9300_Gingerbread_kernel_code_2006.zip and M9300_Gingerbread_other_code.zip and Echo SDKs (v1.3 and v2.0) downloaded.
Where do I go from here? Anybody gotten any further?
Thank you, anyone who still likes this phone.
DulacLancelot said:
I don't know if anyone cares about this phone anymore, but I would like to build the stock ROM from source code and see where I can go from there.
I have AOSP android-2.3.4_r1 built (generic-eng) and running in emulator, and M9300_Gingerbread_kernel_code_2006.zip and M9300_Gingerbread_other_code.zip and Echo SDKs (v1.3 and v2.0) downloaded.
Where do I go from here? Anybody gotten any further?
Thank you, anyone who still likes this phone.
Click to expand...
Click to collapse
Have you made any progress? Do you still have any files related to the echo?
http://dev-host.org/44vcopsjxq3o/ics.criminal_inspire.zip
All thanks goes to the guys over at the DHD forum.
This is just to inform you all it's out there.
Don't look for what works/doesn't.
You're going to have to post a lot more than that for this to be here. Kernel sources/info, proper credit, approval to post, etc. It looks like you just took the stuff from the DHD thread, put the TS fix from shaky in there, packaged it, and uploaded. Not trying to steal your thunder, but I think you should structure this a bit better, and also get approval from zFreak, DH, Shaky, Lord, etc.
Wasn't meant to be much more then that, and I gave credits, they kind of sum them up.
Ease of use/awareness.
Well unless you're actually going to do dev work, this is really a general post. *shrug* .. Cool though, hopefully people go check out the DHD thread.
Mind you for anyone that uses this data is shaky at best and drops. As well this is an Alpha build. Make a nandroid before installing and there is no support on this. If you have bugs just report them in the DHD android dev thread for ics.
I thought it was confirmed in the dhd thread that data didn't work at all and that touch screen was just a pointer?
Also gapps is not included and I can't find a place to download them.
Edit: I just flashed it. Touch screen is a pointer. No data. No wifi. No sound. No gapps. No SMS app. No hardware acceleration so its very slow.
I'm very impressed with the developers bit this is an early alpha build and not even worth looking at by non developers.
this is not in the right forum, this belongs in general
EvoXOhio said:
I thought it was confirmed in the dhd thread that data didn't work at all and that touch screen was just a pointer?
Also gapps is not included and I can't find a place to download them.
Edit: I just flashed it. Touch screen is a pointer. No data. No wifi. No sound. No gapps. No SMS app. No hardware acceleration so its very slow.
I'm very impressed with the developers bit this is an early alpha build and not even worth looking at by non developers.
Click to expand...
Click to collapse
I haven't flashed it at all. Did you flash the most recent version for inspire from this thread? Or is it the DHD post that you flashed? I know in the DHD thread they had it as pointer with nothing working. But towards the end it was working correctly.
I haven't flashed it just been reading the thread twice daily to keep up since it started. They have gotten a lot of work done. The only concern I have at this point is that they are commenting put a lot of things in the building process to get it to work. Time will tell.
jsm7483 said:
I haven't flashed it at all. Did you flash the most recent version for inspire from this thread? Or is it the DHD post that you flashed? I know in the DHD thread they had it as pointer with nothing working. But towards the end it was working correctly.
I haven't flashed it just been reading the thread twice daily to keep up since it started. They have gotten a lot of work done. The only concern I have at this point is that they are commenting put a lot of things in the building process to get it to work. Time will tell.
Click to expand...
Click to collapse
I flashed the dhd one and the latest inspire one. Both had touchscreen as a pointer.
You need to ask Dev permission to use their stuff. Also unless you are a Dev you really shouldnt release anything unless it is mostly working.
Links removed untill permission is given.
Thread closed
EDIT: This bug has been fixed thanks to SebastianFM's talent and his new kernel v1.30.2
You can find it there:
http://forum.xda-developers.com/showpost.php?p=23817605&postcount=1674
Thanks to all the people, gamers or not, who contributed to track this bug down, tried several ROMs/kernel and reported their results
--------------------------------------------------------------------------------------------------
As I'm not a dev., I didn't dare to post in the development section
HTC did it again I fear, in ICS, our touchscreen drivers have a major problem.
You may have not noticed it at all since it only concerns "dual touch", but not when swiping fingers, so pinch to zoom is OK.
Here is this bug, I'll try to explain it, but watch the very short video I made to clearly show it, it's way better than words!
The problem occures only if you're using two fingers on the screen, it never occures with 3 or 4 fingers.
If you keep a finger pressed on the screen (touch 0) , then "click" the screen several times with another finger (touch1), two very annoying events will happen:
1) touch0 and touch1 will swap, even if you never released touch0. The only way to avoid it is to move touch0
2) touch1 may sometimes become sticky (especially if you click fast, then slowly), for some milliseconds or even for 2 or 3 seconds
Many of you may never notice this bug, since there's mostly one kind of apps that require this kind of "touch behaviour"=> games, especially racing games.
You keep one finger pressed to accelerate, then click briefly with another finger to steer left/right. The result of the bug is that the car will stop accelerating, stop steering until you release the first finger again......
Here is another testimony, explaining the problem in different words:
Originally Posted by kdm06
I think I replicated the fault you had via multi touch vis from the market. It is specific but reproducible. Holding down one finger, rapidly tap with the other finger. After a few taps the order of the inputs reverses. ie it takes the tap as input 1 even though the other finger has been pressed constantly. This is visualised by a colour change of the input points. I can see how this could be an issue gaming. Afraid I don't have the skills to tackle it though. Just thought I would state that I can see it.
Click to expand...
Click to collapse
HERE IS THE VIDEO OF THE PROBLEM:
http://youtu.be/30ogIc_Yib0
NOTE:
- I tried 3 different ICS ROMs, 2 of them based on 3.30.401.101, they all had the problem, it is included in HTC's code (so I guess into touchscreen drivers)
- This problem did not exist in Gingerbread ROMs
-other people could duplicate this bug, you can try it by yourself with a multitouch tester from the market, do like I do in my video, if you can't duplicate it, please tell me!!!!!
I know it may only concern gamers, but I feel like having a resistive screen again
I wish a coder here could have a look at ICS touchscreen drivers to find a workaround to this bug
Stupide question : could it be possible to simply take Gingerbread touchscreen drivers and use them instead of ICS included ones? If yes, where are those drivers located?
Stupide question 2: are these drivers part of the ROM, of the kernel, or part of the firmware?? (<= coding noob inside )
THANKS IN ADVANCE !
--------------------------------------------------------------------------------------------------
Usefull Testimonies:
Not only gamers are concerned:
DeoreDX said:
I've noticed this for a while because although I dint play games I use the ics multi touch keyboard holding down numbers button to type numbers and you let go of the button and it goes back to letters and it doesn't work right any more.
Click to expand...
Click to collapse
Weird... I just tried it with a multitouch tester app and had the same thing happen.
It's not a massive problem (for me anyway), but im still interested in what's causing it.
Also, how is it "like having a resistive screen again"?
Other than if you do this one thing the screen works perfectly....
happened to me while playin dead space.
Has happened to me while playing .
I have never noticed this issue but its definately something that im sure most of us would like fixed, have you forwarded this on to some devs?
sromer said:
Also, how is it "like having a resistive screen again"?
Other than if you do this one thing the screen works perfectly....
Click to expand...
Click to collapse
That's the point: resistive screens were able to recognize only one point, just one finger.
A trick was developed to emulate (with less or more success) pinch to zoom, (if my memory is good,using the fact that if you touched two points on a resistive screen, it was like if touching only one point in the middle of your 2 fingers)
That's what we had on smartphones, except the iphone mad (and some RARE with low CPU devices?)
Then came the HD2!
Beside its 1ghz CPU (the HD2 was not the first, Toshiba came first), the HD2 was a real revolution with its dualtouch capacitive screen, allowing Windows Mobile users to finally play games like it was already possible on an iphone, emulators became great (try to play mario or a racing game with only one finger^^), some native racing games were out, etc
Why do I feel like an old school smartphone user now? lool It was only 3 or 4 years ago
Now I feel like having with a resistive screen again, impossible to fully enjoy Fpse, N64oid, SNESoid, NESoid, GEARoid, etc
Even some native Android Games tend to be hard to play, especially racing games if you don't want to use the G-sensor (also some FPS, when your character refuses to shoot, or keeps on alking for 2 seconds after releasing the screen, etc)
Well, that's a gamer bug I fear
liamstears said:
I have never noticed this issue but its definately something that im sure most of us would like fixed, have you forwarded this on to some devs?
Click to expand...
Click to collapse
I've talked about this bug in ARHD thread, since it's the ROM I'm using, but in vain, I guess it's something a ROM chef (with all respect due) won't/can't fix, so I'm posting here to try to get coders' (maybe kernel developers?) attention
________________________________________________________________
Thanks all for reporting that you have this bug too, and for your attention, I feel less lonely now
Just tested this issue on multitouch tester, using arhd 6.3.0 firmware 3.30. Thanks for making us aware with this issue
Sent from my HTC Sensation XE with Beats Audio using xda premium
I think this may be kernel related, send a couple pm's to kernel dev's it wont hurt
I don't think much can be done until ICS kernel source is released officially
Sent from my HTC Sensation Z710e using Tapatalk
overthinkingme said:
I don't think much can be done until ICS kernel source is released officially
Sent from my HTC Sensation Z710e using Tapatalk
Click to expand...
Click to collapse
Jan seems to be good at editing, try him, he managed to hexedit a nice OC/UV kernel....
I have also noticed this when playing zombie dash but i thought it was a problem with the game
I fear we'll have to wait until HTC releases the source of the kernel .....
And I'm pretty sure they will release it as-it-is, including the bug (they've done it before!)
I confirm that i have the same problem while playing modern combat and asphalt.
Didn't have this problem with GB ROM.
Yep, I'm having this problem too while playing Modern Combat 3.
I thought it was just me
I think many people had the problem and though it was the game they were playing, or just their device
Actually, it affects everyone using ICS on the Sensation
I wrote to some devs, not all of them answered, anf for the answers I had, they say we'll have to wait until HTC releases the kernel source.
So we have to choose:
1) going back to Gingerbread and have working multitouch, but lower GPU performances
2) keeping ICS but stop playing games that require 2 fingers
3) Buying a Samsung ( well, they never had touchscreen bugs like this, they do real drivers )
4) Going to AOSP, say goodbye to Sense.
That's pretty sad. I wonder how they beta-test ROMs and kernels at HTC, they already did it with the HD2 (Y coordonates auto-alignment), now they are doing it for the Sensation. HTC just sucks when it comes to drivers.
What is worse is that we can't even complain to HTC, or tell them there's a bug they should fix before releasing ICS ROMs, we're using a leak !
(if someone here is close enough to HTC, please tell them!)
What can be good, is that once ICS is out, I'll go back to S-ON and stock ICS to complain about my non-working multitouch so that they exchange my phone
if this problem dosen't exist in cm9 sensation roms so it dosen't kernel relaeted problem since they are using the same sense kernel
roytev said:
if this problem dosen't exist in cm9 sensation roms so it dosen't kernel relaeted problem since they are using the same sense kernel
Click to expand...
Click to collapse
That's a very good point here!
Do they use the exact same kernel? The same SebastianFM is using to provide us o/c with ICS ?
If yes, we definitly need feedback from cm9 users, can they reproduce the bug or not??????????
The devs who answered my PMs tend to say it's kernel related, with cm9 users feedback, we'll know for sure if we have to wait for HTC to release the source, or if something can possibly be done (like using Gingerbread drivers? Can it be done??)
Bump.
Any news/PM's/etc?
Nothing new
I sent 5 PM, 2 devs answered, telling we have to wait for HTC to release sources.
And I guess I'll have to install CM9 on my device to see if it has the bug...or not!
I've noticed this for a while because although I dint play games I use the ics multi touch keyboard holding down numbers button to type numbers and you let go of the button and it goes back to letters and it doesn't work right any more.
... if I want to load a custom ROM. BTW, I'm not a programmer just an engineer who only speaks two human languages.
Please explain the "reloaded bootloader" part. Perhaps "relocked"?
In general, try explaining in more human language what you have and what you're trying to achieve, it'll help this thread - currently it looks like this: :silly:
Jack_R1 said:
Please explain the "reloaded bootloader" part. Perhaps "relocked"?
In general, try explaining in more human language what you have and what you're trying to achieve, it'll help this thread - currently it looks like this: :silly:
Click to expand...
Click to collapse
I meant to say "loaded".
I found a forum where it was recommended to load HTC's bootloader instead of flashing a new ROM but after doing all that and then looking for ways to modify my phone I see a thread on this forum that says that was a mistake.
Anyway my whole point of this exercise was to try to get the maximum performance (and longevity) out of my mytouch that I bought so I really like the idea of making it lean and mean and fast. I'm no programmer just a father of three girls trying to make my money go father during this recession(depression for me). TIA
Bootloader doesn't affect the regular phone functionality in any way. The only times where it gets useful are times of trouble - recovering from something bad.
Of course, it doesn't substitute a ROM in any possible way. These are completely different and unrelated things.
Jack_R1 said:
Bootloader doesn't affect the regular phone functionality in any way. The only times where it gets useful are times of trouble - recovering from something bad.
Of course, it doesn't substitute a ROM in any possible way. These are completely different and unrelated things.
Click to expand...
Click to collapse
I appreciate your advice and I'll take your word for it regarding the usefulness of bootloader for my desired purpose but understand the noob's predicament that using a google search one doesn't always get correct information, ie in this case the advice to load bootloader was in an android forum.
Fortunately, I've been browsing other threads on this very useful forum and have found out from the HTC Glacier wiki that I need to downgrade my operating system. Anyway I think I'm on on the right track.
While your still here could you recommend me a stable ROM to install and a good free SIP/VOIP to use so I can use my google voice account on my HTC? :good:
Anything Gingerbread is fine - Sense 3 / Sense 3.5 / CM7 / MIUI (not v4), there are several recommended ROMs.
Jack_R1 said:
Anything Gingerbread is fine - Sense 3 / Sense 3.5 / CM7 / MIUI (not v4), there are several recommended ROMs.
Click to expand...
Click to collapse
Glad I'm not the only one who likes GB.
Sent from my HTC Glacier using XDA
I have no intention for hacking or anything i just want to use it for pentest on my systems.
Okay so i downloaded aircrack for ubuntu and extracted the sbin files and the bin files and pasted them into my system/bin and afterwards i went to terminal emulator and typed
su
aircrack-ng
and to my supprise it loaded. I have posted some screenshots.
So i think with some efforts and the right scripts it would work.
So anyone with the knowledge can help out.
**************UPDATE**************
i just uploaded the aircrack-ng file.
I am Very Sorrry. If you downloaded the first file i posted, that wont work, i have posted the correct one. so please download this one
aircrack-1.1-static.rar (1.90 MB)
Okay so i have found a site on which a group of developers were able to create some files to allow the Nexus one & Galaxy S II run in monitor mode.
here is the website.
[[ http://bcmon.blogspot.com/2012/09/working-monitor-mode-on-nexus-one.html ]]
If we are able to get the mytouch into monitor mode, we would be able to run "Aircrack" ont the packets.
According to the website, we need to Build the KO for our device.
The problem now is, i have no idea of how to create those KO files.
If anyone finds a nice tutorial, pls share it here and i would try and follow it to get the monitor mode working. (that is if possible).
************************************UPDATE***************************************************************************
Guys i have finnally figured out how to put the mytouch 4g in monitor mode.
here are the steps.
Download glacier_Pac_JB_4.2.2-V22.01_20130325-085620.zip
from here : http://d-h.st/5bA
(please flash Gapps)
Then Download this Kernel it was created by coderz ( i have uploaded it so see below.)
Afterwards head towards my other thread here ( http://forum.xda-developers.com/showthread.php?t=2302678 ) and download ubuntu distro the small image.
After the download load open the apk u downloaded from the other thread and select launch and choose ubuntu.
after it has launched, install aircrack.
from this guide ( http://answertohow.blogspot.com/2012/10/how-to-install-aircrack-ng-on-ubuntu.html )
Next head towards here ( http://pkgs.org/ubuntu-12.04/ubuntu-main-i386/iw_3.2-1_i386.deb.html ) for the IW package since its not available
in the ubuntu distro.
Now you are clear to go.
Now type these in the terminal emulator where the image was launched ( please do not open another tab in terminal emulator, use the one that was opened by the ubuntu distro.)
type
Su
Airmon-ng start 6 p2p0
and voila there it is you would see monitor mode started.
Please forgive me if somethings arent clear.
I am so happy to the extent that i cant even type.
What is that?
Sent from my myTouch 4G using xda premium
mymeatb18 said:
What is that?
Sent from my myTouch 4G using xda premium
Click to expand...
Click to collapse
I thinks it's something to hack wifi with.
Sent from my MyTouch 4G using xda app-developers app
N_otori0us_ said:
I thinks it's something to hack wifi with.
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Actually its used for penetration testing but when it is used in the wrong way becomes a hacking tool.
So it can be used by someone to gain access to a secured WiFi network?
Sent from my myTouch 4G using xda premium
mymeatb18 said:
So it can be used by someone to gain access to a secured WiFi network?
Sent from my myTouch 4G using xda premium
Click to expand...
Click to collapse
yea i guess so. Dont really know much about it.
Which package did u download I can't find one that has bin and Sbin in it?
Sent from my GT-P3110 using xda app-developers app
I've been building the kernel module, which is what a "KO" as you called it is, into my customized kernel for about a week now. I've also successfully inserted said module into memory and that's about where I end as the binaries that come packaged with the source code aren't linked correctly for the glacier and can't interface correctly and I haven't taken the time to recompile them yet. The plus side is that this may save me having to do that but that also means that if you want the module you have to use my kernel and that is a hazard in and of itself, haha. I lack the post count to post it in the proper forum and I refuse to circumvent that restriction by posting it in the incorrect forum so for the moment I'm hosting it myself.
If you're interested in taking the chance send me a message but I'll tell you now the kernel variation, D3M0N as I've named it, is not for the faint of heart and you could do real damage to your device if you are careless as mine allows overclocking up to 2Ghz and let me tell you it gets hot enough to blister a finger on the metal battery cover. I have it set to run at 1.4 by default so you may want to adjust it to suit your needs and it's designed for 4.2.x ROMs and I can't guarantee it'll work with any other version of Android but I can build the module for any kernel version as long as the source is available as well.
On a final note, the aircrack suite is a hacking tool and hacking is not bad, cracking is the malicious brother of hacking and either way you're responsible for your own actions, not anyone else. That being said, I'm not liable for what you do or don't do. And to clarify, aircrack itself is only useful for WEP secured networks and it is not useful by itself. This isn't directed at anyone in particular but I thought I'd clear up the assumptions I felt were being made because there's no reason for ignorance and the only crime related to ignorance is refusing the ignorant the chance to be educated wherever possible. I hope nobody takes offense to the term ignorant because everyone is ignorant to something and everyone was ignorant at some point.
Sent from my myTouch 4G using xda premium
zygh0st said:
I've been building the kernel module, which is what a "KO" as you called it is, into my customized kernel for about a week now. I've also successfully inserted said module into memory and that's about where I end as the binaries that come packaged with the source code aren't linked correctly for the glacier and can't interface correctly and I haven't taken the time to recompile them yet. The plus side is that this may save me having to do that but that also means that if you want the module you have to use my kernel and that is a hazard in and of itself, haha. I lack the post count to post it in the proper forum and I refuse to circumvent that restriction by posting it in the incorrect forum so for the moment I'm hosting it myself.
If you're interested in taking the chance send me a message but I'll tell you now the kernel variation, D3M0N as I've named it, is not for the faint of heart and you could do real damage to your device if you are careless as mine allows overclocking up to 2Ghz and let me tell you it gets hot enough to blister a finger on the metal battery cover. I have it set to run at 1.4 by default so you may want to adjust it to suit your needs and it's designed for 4.2.x ROMs and I can't guarantee it'll work with any other version of Android but I can build the module for any kernel version as long as the source is available as well.
On a final note, the aircrack suite is a hacking tool and hacking is not bad, cracking is the malicious brother of hacking and either way you're responsible for your own actions, not anyone else. That being said, I'm not liable for what you do or don't do. And to clarify, aircrack itself is only useful for WEP secured networks and it is not useful by itself. This isn't directed at anyone in particular but I thought I'd clear up the assumptions I felt were being made because there's no reason for ignorance and the only crime related to ignorance is refusing the ignorant the chance to be educated wherever possible. I hope nobody takes offense to the term ignorant because everyone is ignorant to something and everyone was ignorant at some point.
Sent from my myTouch 4G using xda premium
Click to expand...
Click to collapse
Thats cool. So have you tried your new kernel with the aircrack suit i have uploaded or have you tried airmon or monitor mode with the zips found at the website i posted.
And thanks also for clarifying the hacking concept.
I just want to help in unleashing the power of the mytouch 4g. As i have seen and tested, there are many things that the mytouch 4g can do that people didnt really know about. Like Fm transmitting, this feature works on the mytouch 4g. I tried it myself. All its needs is the apk(if anyone needs it He or She should free to ask and i would send it to him or her). All it needs to work is the stock 2.2 Glacier rom as thats which i tested it on.
So as i have already said. You could pass by the website and download the packages and who knows, it might be easier than you think.
Thanks again for contributing. :good:
mickeyasamoah said:
Thats cool. So have you tried your new kernel with the aircrack suit i have uploaded or have you tried airmon or monitor mode with the zips found at the website i posted.
And thanks also for clarifying the hacking concept.
I just want to help in unleashing the power of the mytouch 4g. As i have seen and tested, there are many things that the mytouch 4g can do that people didnt really know about. Like Fm transmitting, this feature works on the mytouch 4g. I tried it myself. All its needs is the apk(if anyone needs it He or She should free to ask and i would send it to him or her). All it needs to work is the stock 2.2 Glacier rom as thats which i tested it on.
So as i have already said. You could pass by the website and download the packages and who knows, it might be easier than you think.
Thanks again for contributing. :good:
Click to expand...
Click to collapse
Yes, I did try the binaries from the OP; unfortunately they weren't the solution to my problem. Fortunately they seem to be just fine and my problem was due to an error on my part (I had duplicate binaries in /system/xbin while I was intending to use /system/bin and failed to realize it right away.) I set up an old Netgear router I had lying around and threw a random string in as the WEP key and was able to reverse it in ~12 minutes with the maximum CPU frequency at 1.4Ghz. Not bad at all as far as I'm concerned given that it takes ~5m on my laptop.
I've stabilized the kernel I've been mutilating so it's far safer than I previously alluded to, haven't had a single panic or hard lock in a good 18+ hours and I've been running it to death so my offer still stands for any who'd rather not deal with compiling it themselves. For those that do, my Github is always open: http://github.com/zygh0st/android_kernel_htc_msm7x30-3.0.git
BTW, thanks for starting the discussion; nice to see I'm not the only one who is interested in mobile devices as possible vectors for breaches of security in ways most people wouldn't consider. The next step is to give Reaver a shot, though I think it has a successor at this point but I can't recall the name of it. I doubt it's feasible, at least not on this device since if the time scales in a similar manner you'd be looking at nearly 24 hours but with something like a Note 2 or S4 one would expect to find a significant reduction in time I'd think, but I could be mistaken.
zygh0st said:
Yes, I did try the binaries from the OP; unfortunately they weren't the solution to my problem. Fortunately they seem to be just fine and my problem was due to an error on my part (I had duplicate binaries in /system/xbin while I was intending to use /system/bin and failed to realize it right away.) I set up an old Netgear router I had lying around and threw a random string in as the WEP key and was able to reverse it in ~12 minutes with the maximum CPU frequency at 1.4Ghz. Not bad at all as far as I'm concerned given that it takes ~5m on my laptop.
I've stabilized the kernel I've been mutilating so it's far safer than I previously alluded to, haven't had a single panic or hard lock in a good 18+ hours and I've been running it to death so my offer still stands for any who'd rather not deal with compiling it themselves. For those that do, my Github is always open: http://github.com/zygh0st/android_kernel_htc_msm7x30-3.0.git
BTW, thanks for starting the discussion; nice to see I'm not the only one who is interested in mobile devices as possible vectors for breaches of security in ways most people wouldn't consider. The next step is to give Reaver a shot, though I think it has a successor at this point but I can't recall the name of it. I doubt it's feasible, at least not on this device since if the time scales in a similar manner you'd be looking at nearly 24 hours but with something like a Note 2 or S4 one would expect to find a significant reduction in time I'd think, but I could be mistaken.
Click to expand...
Click to collapse
Wow Hurray!!!!!!!!!!!!!!. My problem now is that i am not using an AOSP Rom but a Sense Rom (Vipertouch) so would this kernel work on it??
Or wait i checked ur github, is that a package for ubuntu?? cause i can see some makefile in it??
Bro if you really want to pen test from your android download dSploit.
It doesn't require custom kernals or anything. Would you like me to find a link?
Sent from my myTouch 4G using xda app-developers app
I already have that, but it doesnt crack wep passwords.
Sent from my HTC myTouch 4g using xda app-developers app
mickeyasamoah said:
Wow Hurray!!!!!!!!!!!!!!. My problem now is that i am not using an AOSP Rom but a Sense Rom (Vipertouch) so would this kernel work on it??
Or wait i checked ur github, is that a package for ubuntu?? cause i can see some makefile in it??
Click to expand...
Click to collapse
Makefiles are generally going to be found anywhere that there is code written in C and as far as I know, or recall for that matter but that may not be saying much given my poor memory, the Linux kernel has been written in C since its inception. I tried flashing the kernel with Vipertouch earlier today but it never made it past the bootlogo so I'm going to say that it doesn't play nice (which is expected.) I've spent a little time hunting around for source code to the kernel that Team Venom used but I haven't come across it yet. As soon as I find the source for an ICS/Sense compatible kernel I'll see if I can't crank something out for you. Shouldn't be too hard, I'm just preoccupied and haven't had a good stretch of time to devote to finding what I need but I'm sure it'll be easy to find because one of the Sense ROMs ought to link to a repository I'd think (I hope so anyway, haha)
If you're familiar with compiling the kernel in Ubuntu then you're pretty much familiar with compiling kernels for Android, you'd just need to set up your build environment properly which is trivial in Ubuntu. If you're interested at all, here are a couple of links, one to a thread that I referenced a few times myself and one to XDA University's Guide to building a kernel from source. I'm no expert by any means, at least not with regard to Android specific issues, but my mind and the contents therein are at your service for what it's worth :good:
zygh0st said:
Makefiles are generally going to be found anywhere that there is code written in C and as far as I know, or recall for that matter but that may not be saying much given my poor memory, the Linux kernel has been written in C since its inception. I tried flashing the kernel with Vipertouch earlier today but it never made it past the bootlogo so I'm going to say that it doesn't play nice (which is expected.) I've spent a little time hunting around for source code to the kernel that Team Venom used but I haven't come across it yet. As soon as I find the source for an ICS/Sense compatible kernel I'll see if I can't crank something out for you. Shouldn't be too hard, I'm just preoccupied and haven't had a good stretch of time to devote to finding what I need but I'm sure it'll be easy to find because one of the Sense ROMs ought to link to a repository I'd think (I hope so anyway, haha)
If you're familiar with compiling the kernel in Ubuntu then you're pretty much familiar with compiling kernels for Android, you'd just need to set up your build environment properly which is trivial in Ubuntu. If you're interested at all, here are a couple of links, one to a thread that I referenced a few times myself and one to XDA University's Guide to building a kernel from source. I'm no expert by any means, at least not with regard to Android specific issues, but my mind and the contents therein are at your service for what it's worth :good:
Click to expand...
Click to collapse
OOOKay. But the only problem is that my pc fell and had developed some kind of fault so at the moment i am PC-less. But i hope to get it repaired soon. but in the meantime can you upload an already compiled version of the kernel so that i and anyone else who is intrested could download?? you know like a flashable zip or something and did you flash the kernel for the vipertouch through the recovery?? If so i dont think it would work. They created the rom in such a way that they change most of the directories so you would have to use thier inbuilt flasher. I guess. last time i tried flashing a bootanimation through recovery but it didnt work. So i guess u use thier inbuilt one.
mickeyasamoah said:
OOOKay. But the only problem is that my pc fell and had developed some kind of fault so at the moment i am PC-less. But i hope to get it repaired soon. but in the meantime can you upload an already compiled version of the kernel so that i and anyone else who is intrested could download?? you know like a flashable zip or something and did you flash the kernel for the vipertouch through the recovery?? If so i dont think it would work. They created the rom in such a way that they change most of the directories so you would have to use thier inbuilt flasher. I guess. last time i tried flashing a bootanimation through recovery but it didnt work. So i guess u use thier inbuilt one.
Click to expand...
Click to collapse
That's cause bootanimations on sense are in a different location then sense. I think
Sent from my myTouch 4G using xda app-developers app
Yea. So i guess the kernel also might be in a different directory. And also i have just remembered that i flashed a different kwrnel from the recovery and after the bootanimation, it failed to continue and got stuck. Reason why am saying all this is because, when i enter the root of my device, i see many folders that u wouldnt see in a normal rom (cyanogen, aosp, aokp,) as far as i know. So i guess he should create a flashable zip of the kernel and maybe steady the directories of the rom and maybe it might work.
Sent from my HTC myTouch 4g using xda app-developers app
mickeyasamoah said:
Yea. So i guess the kernel also might be in a different directory. And also i have just remembered that i flashed a different kwrnel from the recovery and after the bootanimation, it failed to continue and got stuck. Reason why am saying all this is because, when i enter the root of my device, i see many folders that u wouldnt see in a normal rom (cyanogen, aosp, aokp,) as far as i know. So i guess he should create a flashable zip of the kernel and maybe steady the directories of the rom and maybe it might work.
Sent from my HTC myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Disclaimer: Some of this may come off harsh, it's unintentional I assure you; I've been told by many people I sound like I'm being a jerk when I simply know no other way to present the information than in as simple a form as possible, so reader be warned and do try not to take offense!
Actually, all of the directories you see under / (the root of the filesystem or root for short) DO exist on every Android installation regardless of the version or ROM for the most part. There are a few alterations between major Android versions (think Gingerbread to ICS or ICS to JB) but those are mostly related to the SDCard or external filesystems in general. There are also differences related to specific devices, for example; you won't find /data/media on devices that don't have an internal storage designed to mimic an SDCard (such as the Samsung Galaxy series.)
That being said, the kernel does not reside in a directory at all, it resides on a partition that is mounted as /. The kernel's ramdisk is actually where /init and /init.rc and such actually are and that is why you can't change them and have the changes persist across reboots even if the root partition is remounted as read/write. In addition to this information, one does not simply "move things around" within a deeply rooted filesystem structure like you were rearranging furniture.
And to get to the real information you're after, the reason your device fails to boot when you flash an incompatible kernel is because the kernel and the ROM, for lack of a better example, don't know how to speak to one another and one get's pissed off and they stop talking; or in other cases one gets severe dementia and repeats itself indefinitely (bootloops anyone?). Oh, and the bootanimation.zip is in the same place on every Android device. You don't need to flash it at all, it goes in /system/media/ but you'll have to remount /system as read/write first (which is why flashable zips are convenient, you don't have to mess with it and you're going to have to reboot anyway to see your new animation, right?)
And in closing, the directory structure of Team Venom's ROM and every other ROM that exists is about 99% the same. You may not have seen it before, but there's no need to drag out Shrodinger's poor cat is there? I assure you it's been there lurking in the shadows What I need is the source code to a kernel that is known to work with ICS/Sense ROMs, and as I previously stated in another post I simply haven't looked that hard yet. I have an errand or two to run this early afternoon, but you have my word I'll do my best to try and get a working kernel to you by 0500 GMT, which is midnight for me. That gives me 12 hours from now, too easy And it'll be flashable, I'm a lazy person to be honest so I have a script that compiles the kernel, builds the ramdisk, makes the boot image from the two, creates a flashable zip, uploads said zip to the device, creates a script for recovery (I use TWRP 2.5.0.0 FYI) to flash the zip and reboot, and then reboots the device into recovery. That way I only have to press return once
I hope you found some of that useful and if you'd like any more information I'd be happy to give you all that I have, it's kind of an uncontrollable thing with me so be mindful of what you ask because you will get a wash of info in return and my stop button seems to work sparingly, haha. Have a good day!
zygh0st said:
Disclaimer: Some of this may come off harsh, it's unintentional I assure you; I've been told by many people I sound like I'm being a jerk when I simply know no other way to present the information than in as simple a form as possible, so reader be warned and do try not to take offense!
Actually, all of the directories you see under / (the root of the filesystem or root for short) DO exist on every Android installation regardless of the version or ROM for the most part. There are a few alterations between major Android versions (think Gingerbread to ICS or ICS to JB) but those are mostly related to the SDCard or external filesystems in general. There are also differences related to specific devices, for example; you won't find /data/media on devices that don't have an internal storage designed to mimic an SDCard (such as the Samsung Galaxy series.)
That being said, the kernel does not reside in a directory at all, it resides on a partition that is mounted as /. The kernel's ramdisk is actually where /init and /init.rc and such actually are and that is why you can't change them and have the changes persist across reboots even if the root partition is remounted as read/write. In addition to this information, one does not simply "move things around" within a deeply rooted filesystem structure like you were rearranging furniture.
And to get to the real information you're after, the reason your device fails to boot when you flash an incompatible kernel is because the kernel and the ROM, for lack of a better example, don't know how to speak to one another and one get's pissed off and they stop talking; or in other cases one gets severe dementia and repeats itself indefinitely (bootloops anyone?). Oh, and the bootanimation.zip is in the same place on every Android device. You don't need to flash it at all, it goes in /system/media/ but you'll have to remount /system as read/write first (which is why flashable zips are convenient, you don't have to mess with it and you're going to have to reboot anyway to see your new animation, right?)
And in closing, the directory structure of Team Venom's ROM and every other ROM that exists is about 99% the same. You may not have seen it before, but there's no need to drag out Shrodinger's poor cat is there? I assure you it's been there lurking in the shadows What I need is the source code to a kernel that is known to work with ICS/Sense ROMs, and as I previously stated in another post I simply haven't looked that hard yet. I have an errand or two to run this early afternoon, but you have my word I'll do my best to try and get a working kernel to you by 0500 GMT, which is midnight for me. That gives me 12 hours from now, too easy And it'll be flashable, I'm a lazy person to be honest so I have a script that compiles the kernel, builds the ramdisk, makes the boot image from the two, creates a flashable zip, uploads said zip to the device, creates a script for recovery (I use TWRP 2.5.0.0 FYI) to flash the zip and reboot, and then reboots the device into recovery. That way I only have to press return once
I hope you found some of that useful and if you'd like any more information I'd be happy to give you all that I have, it's kind of an uncontrollable thing with me so be mindful of what you ask because you will get a wash of info in return and my stop button seems to work sparingly, haha. Have a good day!
Click to expand...
Click to collapse
Thanks very much for your contribution. And dont feel bad or anything for your answers. I love to read especially when they are things that have to do with ICT or electronic Gadgets. So am cool with that.
And once again, thanks for your help and time,this could be a break through or a start to a new life for the mytouch 4g.
With this, we [ you (zygh0st), Notorious, me and some other young developers] could come out with a rom which has the necessary drivers and files to run Most Linux/Ubuntu/ Debian Distros and apps without any difficulties, Reason is that, the Linux/Debian?Ubuntu Images Available now lack some drivers and abilities to do certain things. SOme of which is Wireless tools in Ubuntu. ( I tried searching for wireless tools for these images but there wasn't any, the ones available were those for i386 and amd64. But those images needed one for armel.) So as i said this could be the beginning a very big project for a rom that fully supports Distros and has all the drivers for pentesting.
But until then we would be waiting for the kernel.
Thanks Again Buddy.:good:
Alrighty, well I had a little bit of unforeseeable life happen and I had to tend to that. That being said, undoubtedly it hasn't gone unnoticed that my given deadline is well, dead. It's proven a little harder than I anticipated to get the drivers to compile with 2.6.35 than it was with 3.0 and I haven't sorted it out in the short amount of time I've had this weekend. I'll have some time this evening, barring any additional cataclysms of course; so I plan to try and get it knocked out then. For those running JB, I've decided not to release my currently working (and I use the term working loosely) as I've discovered it causes an interesting issue that I'm having trouble tracking down and it may end with me having to start over from scratch unless I can find it. It works in its current state, however, and it may be an issue unrelated to the kernel itself but whenever I switch to a different one it goes away so I'd rather not risk putting something out there that is known to have frustrating issues. Bugs are one thing but when you press unlock and nothing happens for close to 45 seconds, that's just broken. Anyway, I feel like I'm threadjacking so this will be the last mention of it I make here and to get back onto topic, if anyone would like to try and succeed where I haven't yet I'd be glad to lend a hand with integrating the driver especially since I have the changes required to get it to compile cleanly with kernel version 3.0; though it was really only a single section of code that needed to be changed at all. Once again, my apologies for the delays but better to take time and do it right than to smash it together and hope the tape holds.