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.
Related
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.
It's sad to say that the Sensation is far from Sensational.
Today I've probably used the phone the most out of the 4 days I've had it and it's been issue after issue.
Firstly, I added some more music to the phone, it refused to group the albums properly. Reset the cache and this caused all sound alerts and notifications to go haywire, resetting them to random tracks from my music collection.
Secondly, after resetting the ID3 tags several times with different software I'm now left with my music completely fragmented, the worst is an album of 42 tracks which the phone displays as 28 separate albums of the same name.
Also, I've been experiencing a lot of signal dropouts today. (Other phone on same network sat next to it on full signal)
On top of this, numerous "little things", e.g. interface is slow and unresponsive compared to SGS and SGS2, battery life is pretty rubbish when doing anything but standby, many default Android software stripped out.
I called HTC support, they didn't even know what model the phone was from the IMEI and could not offer any assistance with any issues. I asked if there were any planned software updates and the response was, "you already have the latest Android software 2.3"
It's a real shame because the design of the phone and the screen are superb, but HTC's software is terrible.
This is why I'm waiting till it's rooted and unlocked. Custom ROMs always fix such issues.
Darnell_Chat_TN said:
This is why I'm waiting till it's rooted and unlocked. Custom ROMs always fix such issues.
Click to expand...
Click to collapse
With the new bootloader, it could never happen?
Initial units could be buggy. You may try replacing this.
Woov. "..but HTC's software is terrible"
I'm really suprised to see that comment for an HTC phone. HTC's good at software. At least that's how they're known in many years.
Sorry but these little issues could happen on first units. I'm sure HTC's gonna fix these issues wiith updates. Right now you can use different music player and home launcher. Hope you can solve them.
Philio25 said:
Secondly, after resetting the ID3 tags several times with different software I'm now left with my music completely fragmented, the worst is an album of 42 tracks which the phone displays as 28 separate albums of the same name.
Click to expand...
Click to collapse
Aww, I hate it when that happens to my iTunes library
I don't know what you mean about the interface being slow and unresponsive though. Granted, I'm using Launcher Pro rather than the stock launcher (mainly because I like to have a 5x7 grid to play with) but when I was using stock it seemed pretty speedy to me. The rest of the phone is definitely lightning fast.
I've been pleased with the battery life too. It's beating what I used to get on my Nexus One, and that always seemed enough for me.
As for stripped out software, I wouldn't mind swapping back to the stock android messaging app. But I prefer the Sense contacts and dialler. Not sure what else has changed really
Anyway, sad to see you're not enjoying it like I am
try to pull up your music on your PC in a tag editing program & see if it's all different in there. I use mp3tag to edit all of my music to match perfectly.
Figure_desire said:
Woov. "..but HTC's software is terrible"
I'm really suprised to see that comment for an HTC phone. HTC's good at software. At least that's how they're known in many years.
Click to expand...
Click to collapse
It reminds me of the Touch Pro 2, granted it was Windows which sucked ass, but HTC released the first version of the "full" Sense Skin as an update and it totally killed the phone. The software simply required power the hardware couldn't deliver.
To give you an example, I showed the phone to a guy on my dev team today who's not really very interested in phones. His first comment was "how come the Android UI isn't as smooth and fluid as the iPhone?" then I showed him the SGS running stock Gingerbread and he thought it was much smoother.
If you run this phone side by side with the Samsung devices, they piss all over it for UI speed and responsiveness, even the single core SGS1.
xnifex said:
try to pull up your music on your PC in a tag editing program & see if it's all different in there. I use this to edit all of my music to match perfectly.
Click to expand...
Click to collapse
I've finally solved this one, it's due to the "Artist Album" tag which MUST be the same for all songs or HTC's player thinks they are in different albums.
Strange thing is this tag is not editable in any of my editors, but you can edit it via Windows Explorer.
The fact you mentioned the letters s g s and the number 2 ensures this thread will soon descend to fanboy central......
Regards.
lynxboy said:
The fact you mentioned the letters s g s and the number 2 ensures this thread will soon descend to fanboy central......
Regards.
Click to expand...
Click to collapse
Damn, what happened to the good old days when that would only happen when someone mentioned "I" and "Phone" in the same sentence.
Philio25 said:
It reminds me of the Touch Pro 2, granted it was Windows which sucked ass, but HTC released the first version of the "full" Sense Skin as an update and it totally killed the phone. The software simply required power the hardware couldn't deliver.
To give you an example, I showed the phone to a guy on my dev team today who's not really very interested in phones. His first comment was "how come the Android UI isn't as smooth and fluid as the iPhone?" then I showed him the SGS running stock Gingerbread and he thought it was much smoother.
If you run this phone side by side with the Samsung devices, they piss all over it for UI speed and responsiveness, even the single core SGS1.
Click to expand...
Click to collapse
Agree with you. That's a fact.
According to earlier HTC phones everyone knows Sense UI isnt that smooth but it is pretty fast and stable. That's another fact. For me speed and stability is more important. If there is a problem with them and you're saying there is, I have a problem too. I'm sure HTC is gonna fix these things. Because dual core is new and Android 2.3 doesn't support it naturally. So it needs time. But you're right there shouldn't be any lag on dual core phone like this.
Op has to understand that bugs are usually associated with early adaptors. Wouldn't hurt to do a swap.
Sent from my GT-I9100 using XDA App
intruda119 said:
Op has to understand that bugs are usually associated with early adaptors. Wouldn't hurt to do a swap.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
But wouldn't a new device have the same issues?
philio are you serious?
i have the tbolt, and i love my phone, but when looking at sensation's specs, it really does blow my bolt away..
however my gf is planning on getting the sensation when it releases.
My point of view is, that if your submerge into the root world, a little drops here and there shouldn't be a big deal, as we all know there will be updates to fix this, not to mention your phone is future proofed for the next two years..
everyone only focuses on the negative but never the positive.. i think the only other phone in the market that is better then the sensation is sgs2.. and thats not even close to being out in the US..
enjoy your 2.3 ginger bread, 3.0 sense.. Unlike you, the majority of us HTCers are now just starting to use the leaked 2.3 and its not completely reliable, as well as using work in progess 3.0 sense which is not a complete port.
consider yourself very lucky to be using an HTC with technology that the rest of us are still waiting on..
spread the love not the hate, because people will always find something to ***** about..
I've come from a galaxy s, even with gingerbread on it I still much prefer my sensation, sure there will be bugs, like any new release, but I find the sensation a lot more of a polished experience, I'm actually using a lot more features getting more out of android than I did on the galaxy s.
Philio25 said:
With the new bootloader, it could never happen?
Click to expand...
Click to collapse
Oh yes it will, as some others with similar having already been cracked.
This game is nothing new and even before Android, HTC played this same game with WM devices and they would also get cracked.
Philio25 said:
If you run this phone side by side with the Samsung devices, they piss all over it for UI speed and responsiveness, even the single core SGS1.
Click to expand...
Click to collapse
Being a SGS owner I really hope you're not saying the Sensation is as, or even more, laggy than a single core Galaxy S. That would be a huge disappointment.
Try mp3tag which is free and lets you edit all tags. Works for me
samnada said:
Being a SGS owner I really hope you're not saying the Sensation is as, or even more, laggy than a single core Galaxy S. That would be a huge disappointment.
Click to expand...
Click to collapse
That is because he is comparing it to an SGS running AOSP Gingerbread which is completely tweaked in every way to optimize the ROM. Apples and oranges, apples and oranges. Imagine this phone with CM7 on it (which is what I'm sure his SGS is running). Can you say Sensation = M3, SGS = scooter?
Sucks it's not working out, but how you like a phone is ALL relative to what YOU like and feel about it.
Hi Guys,
Just trying to get a feel of the progress the various ongoing projects in DEV
I'm noticing we're switching focus from CM6 to CM7, but there are a few CM7 releases going on, MIUI, Ho No, JYdaddy, and one of them seems to be aimed at the Korean Motoroli 720
However the CM7 from fjfalcon seems to be the real deal for our XT720, and it's safe to assume it's stable enough as a daily driver? if one don't mind the missing Video Recording feature, and the 3D Gallery, Camera & Capacitive Touch LEDs needs fixing?
Are there any work around App or Fix for the mentioned issues?
hmmmm, wasn't there some post from mcblehner ?
trying to slide the above onscreen
Yes he delete without anything reason if I was to get banned I could do more in other sites.
I like to help people if he deletes this I'm filing a complaint on him.
Done!
Sent from my XT720 using xda premium
Man Allgamers an awesome mod. One complaint won't do anything. He only follows the rules, which a lot of people don't. He moves and deletes threads and posts as he sees fit. He doesn't just do it for fun.
Sent from my Nexus S running super fast on Koushs CM9 alpha 11 with the awesome Franco kernel
I know this is off topic, but it's really not in XDA's interest to ban productive devs if they can avoid it.
From what I've read XDA moderators/admins gave them plenty of notice and warning, had direct discussions and communication, but for whatever reason the people behind that ROM could not or would not comply with XDA rules. I think it can be frustrating because XDA don't give a lot of information about why bans happen--but if you think about it XDA isn't the best venue for that. It's better overall if things like this are handled in private (as they apparently were) and that bans are enforced rationally and calmly. Consider that after they've been banned, the devs can't really defend or present their case here, so it's only fair that XDA moderators/admins show restraint also remain silent. It seems a little scary for threads and posts to disappear without much of an explanation, but honestly, I think that's the absolute minimum that XDA moderators must do to enforce a ban when you think about it.
Edit: back on topic... I am working on a new CM6 release but it's slower than I would prefer. My froyo build system just seems to be all messed up--I tried all sorts of things to get it back up while korg was down and I think I messed something up somewhere and it's taking longer to figure that out than I anticipated.
Mioze7Ae said:
Edit: back on topic... I am working on a new CM6 release but it's slower than I would prefer. My froyo build system just seems to be all messed up--I tried all sorts of things to get it back up while korg was down and I think I messed something up somewhere and it's taking longer to figure that out than I anticipated.
Click to expand...
Click to collapse
Thanks for the update Mioz
IMO the CM6 seems to run better than the CM7 in the XT720, however i'd like to have CM7 as the main daily driver when it gets more polished, and the memory optimized
peshovec said:
hmmmm, wasn't there some post from mcblehner ?
Click to expand...
Click to collapse
mchlbenner said:
Yes he delete without anything reason if I was to get banned I could do more in other sites.
I like to help people if he deletes this I'm filing a complaint on him.
Done!
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
it was irrelevant, and off topic to the question in this thread
details here http://forum.xda-developers.com/showthread.php?t=1368294
normally we wouldn't even offer a FYI
AllGamer said:
Hi Guys,
Just trying to get a feel of the progress the various ongoing projects in DEV
However the CM7 from fjfalcon seems to be the real deal for our XT720, and it's safe to assume it's stable enough as a daily driver? if one don't mind the missing Video Recording feature, and the 3D Gallery, Camera & Capacitive Touch LEDs needs fixing?
Are there any work around App or Fix for the mentioned issues?
Click to expand...
Click to collapse
I can assume that if someone don't mind of HD camcoder, it can be fit for daily usage. the last update he pushed on 30th is a real deal. I've installed it on my XT720 yesterday and it's all stable. Battery life improves a lot and 3D gallery, camera and touch button LEDs are all working. Though, media LEDs needs a fix. I'd say it is better than any CM6.3 ROMs which FM radio and some other major things still not working.
spiderx_mm said:
I'd say it is better than any CM6.3 ROMs which FM radio and some other major things still not working.
Click to expand...
Click to collapse
The FM radio has been working on 6.3 RC4 for quite a while (RC4 is buried in the thread). At the time I didn't promote it to the primary release because I thought I was close to fixing the screenshot problem. Anyway CM7 uses the fix that came from there.
the Video recording is the least of the concern, it's just in CM7 seems like we have less memory resources to run bigger games, that runs fine on CM6 but no other room.
that's why i say CM6 seems to be better optimized still, at the moment
once CM7 reaches that point, it'll be a daily driver for sure.
i don't really play much games in the phone, but they are good to test ROMs fluidity
a few games i usually use for testing free from market
SCRABBLE Free https://market.android.com/details?id=ca.jamdat.flight.scrabblefree
and any of the Angry Birds
you'll think SCRABBLE is nothing, but that game requires some crazy resources for just a "text" game
in our base ROM that Dexter whipped up for us, wouldn't even run it at 1Ghz
on CM6 RC3 it runs really nice in stock speed 720 Mhz
on CM7 (fjfalcon release) it kinds of load, after killing a lot of stuff in RAM, and even so it runs rather choppy compared to CM6
AllGamer said:
SCRABBLE Free https://market.android.com/details?id=ca.jamdat.flight.scrabblefree
and any of the Angry Birds
you'll think SCRABBLE is nothing, but that game requires some crazy resources for just a "text" game
Click to expand...
Click to collapse
+1 to this. Scrabble does consume a ton of memory when you play it and it can cause the phone to get extremely hot. Actually, I have see it hit 122f before and I quickly ended the game and powered down for a bit, but neither the game or the phone froze on me.
I just returned my HTC One S under buyer's remorse for a number of reasons.
Severely Broken Multi-Tasking
As has been more publicized for the HTC One X, the memory management is so aggressive that you can barely multi-task at all. It's like the Generation 1 iPhone. Especially a killer, since one of my main uses cases is to listen to streaming NPR.
Signal Fluctuation Issues
I think the signal fluctuation issue was largely fixed by the recent update. Pre-update, sometimes I would spontaneously have no signal at all. Post-update, sometimes the signal drops precipitously for no reason at all, but hasn't gotten to the point of "X for no signal".
Bluetooth Spontaneously Disconnecting/Crashing
The bluetooth would spontaneously disconnect, pretty frequently--probably once every 2-3 hours of use. A couple of times I think it even caused the phone to re-boot. Again, since my #1 use case for my phone is voice calls for work (I know, who would have though, voice a primary usage for a smartphone! ), and my #2 is streaming NPR, this is a big problem.
Screen Size
I knew what I was getting, but I had really wanted a 4.6" widescreen (like GS2). I was willing to compromise on this, but it was a factor. Had I known T-Mobile would get the GS3 so promptly, I probably would have held out from Day 1.
Menu Button
For the many apps not updated to ICS, you lose quite a bit of space in portrait mode, due to the on-screen menu button. I know this isn't HTC's fault, they are following the Google spec, but it was a real bummer (and compounds the screen size compromise). I am thinking Samsung made a much better choice with the GS3 by going against Google's intent and including the menu button. Surprised this hasn't been discussed more, it is a real bummer.
It's all personal preference.
The multitasking issue has been greatly improved (some would argue fixed) over the stock settings. Signal issues could be a result of several things (location, firmware, hardware, etc.); likewise with the Bluetooth issues you mentioned. I am very pleased with the screen size and the portrait menu button doesn't bother me. Hopefully the GS3 (or whichever phone you are switching to) meets your needs.
WCCobra said:
The multitasking issue has been greatly improved (some would argue fixed) over the stock settings.
Click to expand...
Click to collapse
how? i can't get One X multitasking fix scripts to run no matter what. i can edit the minfree values manually but they are getting reset on the next boot. the extreme values probably affect the overall performance too. are there some other methods to improve it?
What ROM are you using. Sounds like the init.d script is not running on boot.
The One S would really benefit from AOKP, CM9 or any AOSP based rom. But development is really stagnating. The community for this phone just suck and thats unfortunate cause it is a decent phone for the price.
wilcoholic said:
The One S would really benefit from AOKP, CM9 or any AOSP based rom. But development is really stagnating. The community for this phone just suck and thats unfortunate cause it is a decent phone for the price.
Click to expand...
Click to collapse
I think development for this phone is going rather well. I think you should appreciate what the developers have already put out for us, its their time and they do it for free. You have an expectation which is just wrong.
We already have a CM9 and a MIUI rom, more will follow. You have to realise its still very early in the phones life.
Your options are to get a One X or SGS3 or deal with it. Alternatively you can build your own rom, I'm sure it will be great.
Ben is right stop being so ungrateful they use up their time and deliver awesome roms for free
Sent from my HTC One S using xda premium
WCCobra
i triple checked everything. the boot.sh is properly modified, the init.d scripts have the right permissions. even if i execute the script manually the minfree values never change, they are always the same. like i said, at this point i'm not even sure if all other ROM scripts are being run and active. i'm on the latest TrickDroid currently but the same thing was happening on Zydroid as well. if you have any other tips regarding this issue please do share!
Are you sure there are not multiple init.d scripts running and conflicting with each other?
Can you move out all of the init.d scripts except the one running the minfree settings. Also, try adding a line to the script to have it create a file so you know it ran:
touch /sdcard/Download/test.txt
Do you mind posting screenshots of what you are seeing?
OP wanted a larger screen and really didn't matter about anything else. He decided he wanted GS3 and put a little blame on everyone else. Should have just waited a bit man no need in downing guys that are working hard and also loveing the S One. I have tons of devices and picked this one for my own reason and glad I did. Have very little problems with it at all. We have some great guys working doing a great job, and if you've been following one-x s-off. There real close and that's going to be good for us as well.
Sent from my HTC VLE_U using XDA Premium HD app
WCCobra,
i tried to reboot with just the multitasking script inside init.d, it didn't create the test txt file. i'm not sure about the original TrickDroid scripts you see there though. when i rebooted without them the system behaved unstable so perhaps some of them do run? it's confusing to me.
the values in the minfree file from the screenshot are the original One S values that never change no matter what i run and how.
place the touch command in 01trickdroid
just tried that, no txt being created.
Check the locations. Your init.d scripts are all in /etc/init.d They should be in /system/etc/init.d
--------
Ah, nm it's a softlink
I have a very splited opinion to the One S. I really do love this phone and i dont want to return it! But there are some issues which bother me. The HTC build quality is very impressive but all my HTC phones had a small defect.
HD2: i had to put a small piece of paper between the battery and the backcover to make it fit tight.
Desire: the vibration motor had a small disfunction.
One S: the glass is on the top left not glued accurately.
These are problems u can fix at HTC but they were not worth it to lose the phone for 2 weeks. There is the chipping problem on the black One S. The touch button issue. It seems like HTC tries to build a great quality phone but dont test it long enough.
Gesendet von meinem HTC One S mit Tapatalk 2
I know there are defects out there that's part of manufacturing. I'm just glad I got a good one. Also I still have my hd2 and use it everyday as a WiFi router in my truck. Even dropped it off a three story roof and busted the case and cracked the digitizer but keeps on going... Wished all phones were built that way
Sent from my HTC VLE_U using XDA Premium HD app
Been using the bullet proof rom since I got this phone about 10 months ago, as much as I would like to switch to something better, I cant because it looks like almost every rom available is pre-alpha pre-beta, comes with a bunch of things not working, or has battery issues.
I know the Doubleshot isnt a popular phone, but this is really starting to suck. Seems to me that someone decides to build a new rom, makes a few updates over 2-3 months, then completely abandons the project due to getting a new phone. Wash, rinse and repeat.
Id love to have a cyanogenmod 7 mod, yet alone 9 for this phone, or even a stock ICS 4.04 rom, but it doesnt look like its ever going to happen with this phone. I think this will be the last HTC phone I buy, ive had 3 of them (one was WinMo 6.0) and none of them had official updates. All I can do now is watch people post a ROM, provide a few updates, then completely abandon the project.
What is the most stable ICS or CM9 rom available? Cause I sure as hell dont see it in the developers forum.
Well....you COULD look about 5 posts below this one and get a clue or two. http://forum.xda-developers.com/showthread.php?t=1858512
But if you missed that one I can certainly see why the hell you "missed" anything you might like over in the Developer's Section. The real beauty of Android is you can just say "To HELL with the official updates". KWIM?
Usually reading through what others post about a ROM helps make the choice in what to flash. Seems how there are a few recent threads with almost this exact thing I take it your not the reading type? Just because something is labeled alpha or beta does not mean their not stable enough for a daily driver, it just means not everything works. 90% of our "dev threads" are ROMS you would never see ( ie from a different device ) so having them 90% functional, only missing features from the other device ( because ours can't do them ) is great development.
Blue was kind enough to post system.img and boot.img from the latest ota ( links could be shot because of a goo crash ) and dsi made the dsixda kitchen that will cook them images into a rooted Stock ROM. The kitchen will need a file added to tools/edify_defs ( its a script that allows the kitchen to know the partition locations of your device ) because he dropped support a while ago, but it works great as a tool. So you could always start there and once you get some things under your belt you could jump in and lend a hand in this long term support you are seeking?
Sent from my myTouch_4G_Slide using Tapatalk 2
I do think that people arrive at your conclusions due to three main reasons:
- The misunderstanding that developers are doing this for the users. ( some may, by far most are not)
- The user mentality of owning a smart phone. You want to have this device as long as you can, and get the most out of it.
Most devs see it another way. They want to stay on the cutting edge and try to break new ground. Regardless of how awesome a device is at launch, you are still looking at a limited window of time before it's old hat.
I think that more and more you will be seeing devs moving on more quickly due to the commercial success of the smart phone. Not just an expensive device for a few, anymore they are a dime a dozen for the many.
I've owned 3 doubleshots, still have two. Have an SGSIII, and am thinking about picking up one of the SGSIII international models.
...and that is fast becoming the M.O. of development. Squeeze out whatever learning you can until you benefit more from newer hardware.
Some devs will work on a device until it's about to or just starting to lose it's resale value so they can minimize the move forward.
- The third - and arguably most important reason - is the average user has no idea how much time, effort but most of all frustration goes into working on a device.
Especially for newer devs. For every one accomplishment, there are many, many failures. Failures that may have taken days of almost around the clock work. Failures that - in order to reach - took the place of spending time with friends, significant others or social gatherings. Giving up that day with your friends at the beach just to spend the whole time working on something that not only doesn't work, but even the parts of it you can salvage aren't useful.
This is what learning is like when you are the steward of your own education. You have to make sacrifices like ignoring your friends and family, cutting down on work hours, blowing off your girlfriend for a box with a screen.
Guess what - that whole graphics project for bulletproof that resulted in a 3 part tutorial? A 70 something hour bender where I walked away from the machine twice for less then ten minutes a pop for a quick bathroom break and to make some ramen noodles.
It was ramen noodles because I stopped working for a few months to learn android and build stuff for the doubleshot. Pennies can only be pinched so far.
...and I can't tell you how much I despise and hate actually doing graphics work. It makes me agitated and angry.
But ya know what? I did it to show what could be done and generate tutorials so other people could do it and free me to do other things, yet still enjoy the visual entertainment/enhancements the community would bring.
...and I was let down, in a big way. No one else really got into doing it. No one else invested the time to make graphical mods to. apk files we have or to sense. ( no slight to the very few of you that did)
You've had this phone for ten months, where are your roms, mods or graphical enhancements and stuff?
You argue that so few get involved - yet you do little to help.
This device was my first step into the dev ring. If I can be as successful at it - no reason you can't too. If you'd rather spend time doing other things, well, you never will learn to dev.
These kind of threads are disheartening. The community survives and thrives through your participation. By not pitching in to help, you are forcing the few that do to bear the weight of all forward development for the device.
Don't complain that we few are burnt out when you can't count yourself amongst us.
This division is one you highlight, while we try to eliminate. Come to our side and help out.
Bulletproof had over 2,000 downloads when I checked last back in march/april. No one used it as a springboard to build on?
At the end of the day...
elister said:
What is the most stable ICS or CM9 rom available? Cause I sure as hell dont see it in the developers forum.
Click to expand...
Click to collapse
... it's waiting for you to make it.
WeekendsR2Short said:
Well....you COULD look about 5 posts below this one and get a clue or two. http://forum.xda-developers.com/showthread.php?t=1858512
Click to expand...
Click to collapse
Oh I saw that, but i'll pass on an alpha build, need something stable, plus im not sure what version of Android thats even based on.
WeekendsR2Short said:
Well....you COULD look about 5 posts below this one and get a clue or two. http://forum.xda-developers.com/showthread.php?t=1858512
But if you missed that one I can certainly see why the hell you "missed" anything you might like over in the Developer's Section. The real beauty of Android is you can just say "To HELL with the official updates". KWIM?
Click to expand...
Click to collapse
strapped365 said:
Usually reading through what others post about a ROM helps make the choice in what to flash. Seems how there are a few recent threads with almost this exact thing I take it your not the reading type? Just because something is labeled alpha or beta does not mean their not stable enough for a daily driver, it just means not everything works. 90% of our "dev threads" are ROMS you would never see ( ie from a different device ) so having them 90% functional, only missing features from the other device ( because ours can't do them ) is great development.
Click to expand...
Click to collapse
When I see a rom posted in the developers forum, if its based on ICS 4.0 or better, all I do is read the what works and what doesnt work section. For a long time it seemed almost every rom had problems with the SD card being used as a USB Flash drive (meaning I would have to disconnect the SDHC, connect to reader just to copy files). Now the problems tend to either be camera related (which I absolutely need) or battery issues in which it gets hot or drains faster.
So way early on, I was reading through pages upon pages of posts to see if problems get resolved (which often they dont unless they post another build), but now I just read the first page to get to the details (to see whats not working in the rom), then pass when there are too many things not working.
I kinda like the official update, because they tend to be stable.
elister said:
Oh I saw that, but i'll pass on an alpha build, need something stable, plus im not sure what version of Android thats even based on.
Click to expand...
Click to collapse
U need to lower you rom standards or make the perfect cm9/ics rom. I had a problem with our device not having enough roms until someone explained to me that we don't need 20 diff cm7 roms or 10 diff ics roms. Our devs do a good job so we don't need those the amount of roms we have is good look at the older smartphones and their roms. U see they are not up to date. (Like most of ours)
Sent from my myTouch 4G Slide using xda premium
lower your rom standards?
K7Cobb said:
U need to lower you rom standards or make the perfect cm9/ics rom. I had a problem with our device not having enough roms until someone explained to me that we don't need 20 diff cm7 roms or 10 diff ics roms. Our devs do a good job so we don't need those the amount of roms we have is good look at the older smartphones and their roms. U see they are not up to date. (Like most of ours)
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
lower your rom standards?
i totally agree with the op. i'm not complaining about the great work the devs are doing. they're doing what they do because they love it and that's great. but every rom has issues in the "doesn't work" section and there's no reason us users shouldn't be asking for a rom with nothing left that doesn't work. i mean that should be everyones goal, right?
if there was a single rom with no known issues, i'd be on it in a heart beat. especially a sense-less one. i'd even take gingerbread if it was no known issues.
and as for "we don't need 20 different cm7 roms and 10 different ics roms" ... of course we don't. i'd like to see ONE of each that's fully working.
polarbearmc said:
lower your rom standards?
i totally agree with the op. i'm not complaining about the great work the devs are doing. they're doing what they do because they love it and that's great. but every rom has issues in the "doesn't work" section and there's no reason us users shouldn't be asking for a rom with nothing left that doesn't work. i mean that should be everyones goal, right?
if there was a single rom with no known issues, i'd be on it in a heart beat. especially a sense-less one. i'd even take gingerbread if it was no known issues.
and as for "we don't need 20 different cm7 roms and 10 different ics roms" ... of course we don't. i'd like to see ONE of each that's fully working.
Click to expand...
Click to collapse
Yes thats the goal but if theyve released the rom with 1 or 2 problems then why should it be a problem. I use virtuous infinty and has 2 problems thats it. Dont quote me but i dont think there is a PERFECT ROM. Because again it is a rom not made by the company but our devs. And then again the roms our devs make have less serious problems than the ones companies have
Sent from my myTouch 4G Slide using xda premium
polarbearmc said:
lower your rom standards?
i totally agree with the op. i'm not complaining about the great work the devs are doing. they're doing what they do because they love it and that's great. but every rom has issues in the "doesn't work" section and there's no reason us users shouldn't be asking for a rom with nothing left that doesn't work. i mean that should be everyones goal, right?
if there was a single rom with no known issues, i'd be on it in a heart beat. especially a sense-less one. i'd even take gingerbread if it was no known issues.
and as for "we don't need 20 different cm7 roms and 10 different ics roms" ... of course we don't. i'd like to see ONE of each that's fully working.
Click to expand...
Click to collapse
Then you get the invite to either put up some work, or fall back to the shadows. You guys asking for stuff we do for free in our free time sucks. And to see how unappreciated we are. If we pulled all links everyone that's whining now would be in tears
Sent from my myTouch 4G Slide using Tapatalk 2
strapped365 said:
Then you get the invite to either put up some work, or fall back to the shadows. You guys asking for stuff we do for free in our free time sucks. And to see how unappreciated we are. If we pulled all links everyone that's whining now would be in tears
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
EXACTLY. I'm not a dev but this is what I did not want to happen but seems like nobody can agree
Sent from my myTouch 4G Slide using xda premium
For those that haven't taken the time to READ to see what others are saying about how a ROM works......well there is no excuse for you and IMHO have no business saying a word about anything. If a person is so smart that they know how things SHOULD work but can't even figure out a few commands in ADB & how to make it work then you're getting things backasswards. Just download it, evaluate it and if you don't expend the friggin' TIME to read then just STFU!
What you're showing is ABSOLUTELY NO RESPECT for the vast amounts of time and effort these developers have sat at home alone into the wee hours of the morning LEARNING by trial & error and collaboration among themselves for their OWN betterment. NOT FOR OURS!!! We are ALL damn lucky that they see fit to share ANYTHING with ANY of us and ask for nothing more that a little honest feedback and an occasional THANK YOU!
now....off my friggin' soapbox
polarbearmc said:
lower your rom standards?
there's no reason us users shouldn't be asking for a rom with nothing left that doesn't work. i mean that should be everyones goal, right?
Click to expand...
Click to collapse
We shouldn't be asking unless we can help in some way, shape or form. As you said, all the devs are doing what they can though we may not be aware of it. Look at how much time Blue put in Bulletproof alone. Kudos Blue!!!
If you want a ROM with no known issues, it exists! Go back to STOCK! LoL One of each ROM that's fully working will not happen because of the reasons that Blue listed and I agree with him completely. And the term "lower your ROM standards" is very fitting to me. It doesn't mean settle for less, but more so just pick the ROM that best suits you. They are there.
My DD right now is MikXE for various reasons and I've never had a single problem with it...at all. I don't use WiFi tethering or WiFi calling but those are features important to some(now I'd LOVE for just 1 feature to be added to it *cough* screenoffmusiccontrol Strapped *cough* LoL), but if it doesn't I'm not going to die. Already perfect in my eyes and I love it the way it is! And Blue's Bulletproof is flawless, everything works!
If a person doesn't like reading then XDA isn't the place to be. Sometimes within the thread there are tips shown that will fix some issues within the ROM that one might not know existed without reading. Then, in other threads there are ways to tweak things to get certain features working in the ROM that may show as not working in the OP...sometimes! Either way, if we want EVERY single feature on the phone working (Even the ones we don't use?) then Stock/Bulletproof is the only way to go. Otherwise, just get a new phone...?
Makes no sense feeling we deserve better for our phones when we have better, but just not up to "our standards". What the devs do...is FREE! As Strapped mentioned, if we had none of these ROMs/Threads, what would we do then? I for one sure as hell don't want to find out!
WELL SAID!!!!
Threads like this sincerely make me sick. I'm an end user ONLY for lack of a viable machine to build on... Somehow i figure building roms on the device isn't feasible (haha!) But my first reaction to this thread was "don't flame the guy don't flame the guy."
These developers have taken what some people get paid to do and enhanced it to almost an art form where they are singularly doing the job that entire DEVELOPMENT teams get paid to do for MONTHS at a time and you have a developer like XMC working on 4 roms at a time AND a kernel and whatever else AND a real job and school or whatever. Seriously if they aren't doing enough for you then code your own dream rom or run miktouch (which ran off stock kernel PERFECTLY for me for the first three months I was rooted).
Besides... What is stable for me might not be for you, or for any of the other end users here. I've ran MikXE, Vanillabean, MikMIUI, CM9 alphas 2-6, Paranoid Android and am currently running Virtuous Infinity alpha 2. ALL have been more than stable enough to function for me with a few quirks... Given i don't depend on Wifi as much as some, but still. Everyone makes a huge deal out of 1080 camcorder but seriously on this screen nobody can tell a resolution difference. I needed gps to work well and calling to work... I was a pizza delivery guy so that was what I needed to be stable.
Seriously to the OP - IF you aren't brave enough to try roms and see what works for you (seeing as how i've had ZERO of the reported bugs i've seen on most of the roms i have run) then stfu and do us all a favor and go back to stock or get a nexus and have a good time. There you can have 50 versions of everything you could ever want to ***** about. OR become a viable member of this great team and contribute. Help test the roms because stability is only a NAND away.
*steps off my soapbox*
And to answer the subject question:
There are plenty of stable roms to choose from. Most every rom here can be used as a daily driver... It just comes down to what YOU can live with as far as bugs go... After all stock had that battery getting really hot "bug" didn't it?
Wifi disconnecting with screen off without an app seems so inconsequential compared to a bug that can fry your device, right? Lets not forget that i've been testing roms and kernels that might've fried my device with only a G1 as a backup LOL.
Oh yeah... And in case you guys missed it...
TBalden, Kornyone, XMC-Wildchild,Strapped365, Sun_Dream, Blue and the rest... You guys kick ass. Let me know if you're ever in Bama and i'll buy you all a beer or several. And... Welcome riyal as well! You have taken my doubleshot from stock hell to the ecstasy that is whatever os i feel like running at any given time.
Sent from my HTC Doubleshot running Virtuous Infinity 1.33 alpha 2.
Well to tell all the ICS ROMs around here should have been stable already only if we were given ICS updates. Problem is we were not and developers recycle CM source code or ROMs from other HTC devices praying that most of them would work to bring up ICS on our device. Ok that's fine but there are propriety files still missing or incompatible drivers which makes the bugs. Unless some dev would put his life in reverse engineering the missing drivers and stuffs we wouldn't be expecting any stable ICS ROMs here.
@onebornoflight
what did I do? Lol I'm no doubleshot developer yet I'm still at the learning stage just owning this device for almost just a week now. Didn't provide any development stuffs yet
Riyal said:
@onebornoflight
what did I do? Lol I'm no doubleshot developer yet I'm still at the learning stage just owning this device for almost just a week now. Didn't provide any development stuffs yet
Click to expand...
Click to collapse
You have started contributing - that kernel in the virtuous beta post is a contribution - see you HAVE provided dev type stuff...
Or would you prefer to be unincluded LOL?
And welcome btw!
Sent from my myTouch 4G Slide using xda app-developers app
I used a hasoon toolkit to root my phone and all that clockwork stuff... and the I used a tool to fastboot the cm9 boot.img..and then flashed the cm9 rom by kornyone.. ITS AWESOME... ICS FTW ON MT4GS....Ifeel like I got a new phone the rom is stable there is literally only one thing wrong with it and that's the front camera is upside down when using gtalk vid chat....but that doesn't matter... its still awesomely awesome
Sent from my myTouch_4G_Slide using xda app-developers app
jesusjv95 said:
I used a hasoon toolkit to root my phone and all that clockwork stuff... and the I used a tool to fastboot the cm9 boot.img..and then flashed the cm9 rom by kornyone.. ITS AWESOME... ICS FTW ON MT4GS....Ifeel like I got a new phone the rom is stable there is literally only one thing wrong with it and that's the front camera is upside down when using gtalk vid chat....but that doesn't matter... its still awesomely awesome
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
Crap.... There's a fix for that somewhere in another kernel I think. I can't remember which one though.
Sent from my myTouch 4G Slide using xda developers app
onebornoflight said:
Crap.... There's a fix for that somewhere in another kernel I think. I can't remember which one though.
Sent from my myTouch 4G Slide using xda developers app
Click to expand...
Click to collapse
Its fixed in the latest alphas, should also be fixed in the latest "stable". But run alpha 5 its the most stable. Overall
Sent from my myTouch_4G_Slide using Tapatalk 2