Hi,not all know,that stock 3rd htc kernel and its kernel source have multitouch bug.So i created a petition for htc,that will be sended if we will become inaf signs.
If you are in,just follow link below and sign
http://www.ipetitions.com/petition/incredible-s-touch-screen-fix/
How would that work? HTC cant fix it, i thought kernels are google?
Sent from one of the few remaining Incredible S'
Piccilino said:
How would that work? HTC cant fix it, i thought kernels are google?
Sent from one of the few remaining Incredible S'
Click to expand...
Click to collapse
Nah HTC fubar'd the source for ICS on our device (others too iirc) so any kernel compiled from HTC's source will have the issue unless its patched.
The kernels we have are HTC's work, I think forked from google android ICS (hence being 3.0.x)
Piccilino said:
How would that work? HTC cant fix it, i thought kernels are google?
Sent from one of the few remaining Incredible S'
Click to expand...
Click to collapse
Htc's phone, their responsibility and also their job to provide both kernel and kernel source.
Sent from my Incredible S using xda app-developers app
yep.htc fault
Splux said:
Htc's phone, their responsibility and also their job to provide both kernel and kernel source.
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
+1
Stupid HTC. First they stop developing for our phone then stops other people developing for our phone.
Sent from one of the few remaining Incredible S'
Just signed
kernel
I have the same problem, but my problem is with the kernel 3.0x,
so the problem is Sd card unexpectedly removed for every rom who has kernel 3.0x,
all started when i got ota ics,
htc repair center say's i have to replace motherboard for 250$, but i know, that the problem is in kernel 3.0x.
Is this multi-touch issue related to the input delay that is present on most of the Sense based roms? The only exception to this is the chinese kang kernel, where I beleive the input delay is fixed. The problem I have is that I'm not very excited by the Sense's UI. I've noticed that the 2.6.4 hacked ICS-JB kernel seems to have this input delay fixed, or greatly reduced... Is it possible to get the patches/changes we need from there?
I just got my hands on a Galaxy S1, and despite the crappy camera, lower RAM and lack of a flashlight, the seemingly perfect touch input is something that I'm very torn over. Now I'm in a position of giving my Inc S to one of my relatives, or the Galaxy S1. I love the community for the Inc S and am very excited by the progress made to JB since December but am extremely tired of not being able to play all games, or wait for my keyboard to catch up with what I've typed because of this F#[email protected]#ing input lag. Anyone have any opinion on the things I've discussed or have something to add to it? I've got a week to decide what I like better...
Before someone mentions not experiencing any input lag: There is a selectable option in developer options, called "Show Touches". If you have this enabled, and try moving your finger around your screen in various patterns, you'll notice that the white circle trails behind where your finger is by a large amount. If you try this on other phones, the distance at which the white circle trails behind your finger is greatly reduced. There are also situations where tapping the screen rapidly in different areas is occasionally completely ignored.
jancis201991 said:
I have the same problem, but my problem is with the kernel 3.0x,
so the problem is Sd card unexpectedly removed for every rom who has kernel 3.0x,
all started when i got ota ics,
htc repair center say's i have to replace motherboard for 250$, but i know, that the problem is in kernel 3.0x.
Click to expand...
Click to collapse
No one reported about that probelm,I don't think it's kernel issue,tru to format your sd card or use another if you can
so i'm from russian forum,it's big and no one repoted about it
TheMegosh said:
Is this multi-touch issue related to the input delay that is present on most of the Sense based roms? The only exception to this is the chinese kang kernel, where I beleive the input delay is fixed. The problem I have is that I'm not very excited by the Sense's UI. I've noticed that the 2.6.4 hacked ICS-JB kernel seems to have this input delay fixed, or greatly reduced... Is it possible to get the patches/changes we need from there?
I just got my hands on a Galaxy S1, and despite the crappy camera, lower RAM and lack of a flashlight, the seemingly perfect touch input is something that I'm very torn over. Now I'm in a position of giving my Inc S to one of my relatives, or the Galaxy S1. I love the community for the Inc S and am very excited by the progress made to JB since December but am extremely tired of not being able to play all games, or wait for my keyboard to catch up with what I've typed because of this F#[email protected]#ing input lag. Anyone have any opinion on the things I've discussed or have something to add to it? I've got a week to decide what I like better...
Before someone mentions not experiencing any input lag: There is a selectable option in developer options, called "Show Touches". If you have this enabled, and try moving your finger around your screen in various patterns, you'll notice that the white circle trails behind where your finger is by a large amount. If you try this on other phones, the distance at which the white circle trails behind your finger is greatly reduced. There are also situations where tapping the screen rapidly in different areas is occasionally completely ignored.
Click to expand...
Click to collapse
it's not only sense based rom's issue
you can test unofficial cm10,v1 have multitouch issue too,can't say something about later versions.
2.6.x kernel just doesn't have that multitouch bug,i think it's one more reason why all CM rom's were based on it,even 3.x kernel source was released
saneksem said:
it's not only sense based rom's issue
you can test unofficial cm10,v1 have multitouch issue too,can't say something about later versions.
2.6.x kernel just doesn't have that multitouch bug,i think it's one more reason why all CM rom's were based on it,even 3.x kernel source was released
Click to expand...
Click to collapse
No, we had CM9/10 ROM's based on the 2.6.x kernel because no one managed to get it booting with a 3.x kernel until very recently.
Splux said:
No, we had CM9/10 ROM's based on the 2.6.x kernel because no one managed to get it booting with a 3.x kernel until very recently.
Click to expand...
Click to collapse
ok,thx for information)
saneksem said:
No one reported about that probelm,I don't think it's kernel issue,tru to format your sd card or use another if you can
so i'm from russian forum,it's big and no one repoted about it
it's not only sense based rom's issue
you can test unofficial cm10,v1 have multitouch issue too,can't say something about later versions.
2.6.x kernel just doesn't have that multitouch bug,i think it's one more reason why all CM rom's were based on it,even 3.x kernel source was released
Click to expand...
Click to collapse
I have formated sd card, i have bought two new one's(same problem), and when i put files bigger then 4gb and try to run game, game starts and i get back to home screen and in notification bar shows sd card removed unexpectedly.
Everything works flalwless on every rom who uses gingerbread (hacked) kernel, on 3.0x kernel roms the problem starts all over again.
Even if you get 10 million in petition htc will not fix this. Sorry to burst your bubble.
Evilus said:
Even if you get 10 million in petition htc will not fix this. Sorry to burst your bubble.
Click to expand...
Click to collapse
why you think so?
saneksem said:
why you think so?
Click to expand...
Click to collapse
Because we tried this for kernel 3 and in the end htc said nothin.
Sent from one of the few remaining Incredible S'
Piccilino said:
Because we tried this for kernel 3 and in the end htc said nothin.
Sent from one of the few remaining Incredible S'
Click to expand...
Click to collapse
after becoming signs i will send it to htc offices,did you make it?
saneksem said:
after becoming signs i will send it to htc offices,did you make it?
Click to expand...
Click to collapse
Nope i just signed.
Sent from one of the few remaining Incredible S'
There's a multi touch fix available in the unofficial CM10 thread. OP says it is for both sense and cm/AOKP ROMs. I've flashed it on ARHD and it runs just fine. That is if you are s-off and rooted.
Dead cookies leave no trails...
Related
Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.
sniffle said:
Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.
Click to expand...
Click to collapse
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?
Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?
avlfive said:
Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?
Click to expand...
Click to collapse
No they are not. It shows all the known issues from the dl link posted above
bravo1234 said:
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?
Click to expand...
Click to collapse
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.
joebob296 said:
No they are not. It shows all the known issues from the dl link posted above
Click to expand...
Click to collapse
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.
avlfive said:
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.
Click to expand...
Click to collapse
Those are all a must for me at least
Sent from my DROIDX using XDA App
I don't understand the gps issue or the camera issue. If there was fine GPS and a camera i would love the fact it is AOSP however not that i use them all that often but if i loaded it i would inevitably need one or both. and its still beta if you can't get a totally stable and working froyo rom how will you ever get the GB stable. Will the kexec(?) be used to use custom kernels to make the gps and camera work?
I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App
Funnyface19 said:
I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
same here. it's been reported in other obsidian forums too. i was able to get around it by using an older version of market. i installed cm gapps instead of obsidian gapps. The cm gapps had a version of market from 2 month ago. everything worked fine. then i updated my market to 2.2.11 and the "There's not enough room..." error message was right back again.
other than that, i really love how clean and fast this rom is. thanks a ton cvpcs and best of luck with the cyanogenmod team.
any pics of the drop down toggles???
tttuning said:
any pics of the drop down toggles???
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=RbKJy6MPUz0
cvpcs said:
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.
Click to expand...
Click to collapse
what...? What!? That is completely wrong... Nothing says you have to upgrade the kernel... unless Gingerbread uses modules not currently in the present kernel, which I can pretty much guarantee it will... Your statement could hold true for something such as minor update like 2.2 to 2.2.1 as we saw earlier, but would very like cause many things to not work come gingerbread. A good example is the previous hacked upgrades of 2.1 to 2.2 back before the proper kernels were released (specifically in memory of the HTC Incredible) sure, 2.2 could run without the proper kernel, of course your WiFi wouldn't work, GPS didn't work, if you tried to run the 720p camera it would crash, as well as several others that I cannot remember as of this moment. The kernel is not "just a low level piece of software" it is the backbone of your entire system, especially when it comes to the system talking with the hardware itself.
I think Taco that you should reread CVPS post. It stated this...
"nothing says that when you upgrade an android version you MUST upgrade the kernel as well"
Which is what you said was wrong, then said the same thing following it.
So how is the rom working for everyone? or it's pretty much dead..
ram130 said:
So how is the rom working for everyone? or it's pretty much dead..
Click to expand...
Click to collapse
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.
JagoX said:
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.
Click to expand...
Click to collapse
Well that sucks ..development on this phone is so slow..
The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App
ksizzle9 said:
The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
The X development has all but ceased from what I can see. Such a bummer since I'm stuck with it for another year and a half. Hopefully we can see a few updates to some ROMs once gingerbread rolls around for the phone, but after that I don't see much reason for hope.
True...so what was the most annoying issue with this rom? Im thinking about flashing it. Im on 3.4.2 now.
Also you can sell your DX on swappa.com then pay the difference and get a htc.
I'm curious...what is everyone's ICS distro of choice for the Nexus One?
i.e. BCM / TexasIce / MIUI
No bashing allowed...only critical conversation please!
I'm using BCM as I like to have the Cyanogenmod features.
+1 for BCM9
BCM is running pretty smooth and with good features.
Sent from my Nexus One using xda premium
BCM
Bravo CM9
Sent from my Nexus One using xda premium
Damn.
That's a lot for BCM.
I'm currently running TexasIce. No problems. Smooth as silk.
What does BCM have over TexasIce? Have they fixed the video camera FC?
CyanogenMod 9 I don't care about the video camera, rarely use(d) it.
tommert38 said:
CyanogenMod 9 I don't care about the video camera, rarely use(d) it.
Click to expand...
Click to collapse
Gotcha.
So what does BCM have over TexasIce? I'm in no way trying to poke holes in anybody's preferrence. If anything, I'm looking for a reason to flash BCM here. Is BCM basically just TexasIce with the CM9 toolbox? Is one any more "AOSP"-ish than the other?
As I said, BCM has CyanogenMod 9 over TexasICS. I got really used to CM7, and CM9 is no different (some functionality is still missing though). I tried TexasICS a few times, but I feel like BCM fits my needs more than TexasICS. I don't have anything against TexasICS, and I don't think people should see these 2 ROMs as opponents.
tommert38 said:
As I said, BCM has CyanogenMod 9 over TexasICS. I got really used to CM7, and CM9 is no different (some functionality is still missing though). I tried TexasICS a few times, but I feel like BCM fits my needs more than TexasICS. I don't have anything against TexasICS, and I don't think people should see these 2 ROMs as opponents.
Click to expand...
Click to collapse
I got you bro, but my question is still pretty unanswered.
To begin with, I'll say that I LOVE the CM team and all their work. The CM ROMs are minimalist, yet customizable, ultimately providing an android experience that's unadulterated by even the slightest carrier modifications. Plus it's tailored for the power user.
I know this, but that's not quite what I'm looking for in the answer.
I'm simply wondering, besides being associated with the cyanogenmod team, is BCM more stable/closer to being a complete, bugless AOSP distribution of ICS than TexasIce?
I gather that they have not fixed the video camera FC- something that's not a big deal to me.
For example, this is the list taken directly from the TexasIce thread of things that are NOT working:
Gapps might not work properly (search the thread for fixes before posting issues)
USB: MTP / PTP / Tethering
wifi ad-hoc (might work)
Builtin alarm clock app doesn't work 100% of the time.
Click to expand...
Click to collapse
*Anything in blue doesn't really bother me...and the gapps issue is an old wive's tale
I'm curious about whether the stock alarm clock app is buggy in BCM as well, though.
While it's not on the list, an FC when hitting 'record' in the stock video camera app is the only other major issue. Apparently this is due to having to fix something with the stagefright video encoder
What I'm wondering is- Has BCM fixed ANY of these things as of right now? Or are both ROMs on the 'same page'?
The Gapps that I installed with BCM are all working 100%. Never had any FC or freeze. The USB issues I wouldn't know because I never use it for anything other than ADB/Fastboot. Wifi idem dito. Alarm clock is working 100% for me, never missed any early class. I don't believe I've read anything about the alarm clock not working in the BCM thread
Also, I believe BCM doesn't have the Screen of Death which some TexasICS users are experiencing. But it's the same with every ROM: it can work perfectly on one Nexus One, while it sucks on the other.
tommert38 said:
The Gapps that I installed with BCM are all working 100%. Never had any FC or freeze. The USB issues I wouldn't know because I never use it for anything other than ADB/Fastboot. Wifi idem dito. Alarm clock is working 100% for me, never missed any early class. I don't believe I've read anything about the alarm clock not working in the BCM thread
Also, I believe BCM doesn't have the Screen of Death which some TexasICS users are experiencing. But it's the same with every ROM: it can work perfectly on one Nexus One, while it sucks on the other.
Click to expand...
Click to collapse
Awesome bro that's what I'm looking for.
Ultimately, I've got no real allegiance to one brand or the other. As I said, I love the CM team and what they do. I'm all about results though, and if they're a bit behind TexasIce than I'm not interested.
By the sound of it, though, this isn't the case. I appreciate your input man.
Just flashed TexasIce ICS yesterday, but it looks like I might be flashing BCM today.
Thanks again for the info bro.
Just wait a few hours and somebody else would recommend TexasICS
Please let us know what you think after you've installed BCM!
xyrovice said:
Awesome bro that's what I'm looking for.
Ultimately, I've got no real allegiance to one brand or the other. As I said, I love the CM team and what they do. I'm all about results though, and if they're a bit behind TexasIce than I'm not interested.
By the sound of it, though, this isn't the case. I appreciate your input man.
Just flashed TexasIce ICS yesterday, but it looks like I might be flashing BCM today.
Thanks again for the info bro.
Click to expand...
Click to collapse
Yeah, likewise, I haven't tried TexasIce, but the known problems listed as being present in TexasIce (aside from video recording), are non-issue in BCM.
One thing I did discover though - if you take TexasIce's latest Kernel (he posted it in a thread) and put that in BCM, BCM becomes just as fast (or faster) than Cyanogen Mod 7! No hindrance on battery life either. I was in shock - a full speed / slick / stable ICS on Nexus One...now if the video recording / camera scanning features were enabled, this would be 100% fully operational.
I have used both.
Both are equally good and stable but I was on Bcm at the end for a while before I switched to sensation xe.
I preferred bcm due to no SoD issues(drewis kernel solved it later on also) , ease of install and configuration also I was having 3-5 random restarts on tesaxice but seldomly had on bcm, once a week if any.
Sent from my Transformer Prime TF201 using Tapatalk 2
tackleberry_crash said:
I have used both.
Both are equally good and stable but I was on Bcm at the end for a while before I switched to sensation xe.
I preferred bcm due to no SoD issues(drewis kernel solved it later on also) , ease of install and configuration also I was having 3-5 random restarts on tesaxice but seldomly had on bcm, once a week if any.
Sent from my Transformer Prime TF201 using Tapatalk 2
Click to expand...
Click to collapse
Really quickly, I know BCM is ported from the HTC Desire/Bravo CM9. Now, I know the Desire and the N1 are almost identical, the only differences being the N1's trackball and capacitive buttons (as far as I know).
So, question: Does the N1 port of the Desire's CM9 distribution have all the N1's hardware working correctly? Trackball wake and notifications? Any/everything else?
Ultimately, even though it's a port, is BCM being developed with the N1 in mind?
Thanks for the info fellas.
+1 BCM with Drew Kernel
xyrovice said:
Really quickly, I know BCM is ported from the HTC Desire/Bravo CM9. Now, I know the Desire and the N1 are almost identical, the only differences being the N1's trackball and capacitive buttons (as far as I know).
So, question: Does the N1 port of the Desire's CM9 distribution have all the N1's hardware working correctly? Trackball wake and notifications? Any/everything else?
Ultimately, even though it's a port, is BCM being developed with the N1 in mind?
Thanks for the info fellas.
Click to expand...
Click to collapse
Yeah it does. Plus if you want to customize anything, you can install Lightflow to do so.
tried them both, but always preferred bcm.
Nobody has tried. Icy 7. Look on drewgaren Web site
Sent from my Nexus One using Tapatalk 2
I was waiting on the sgs4, but after the cringe worthy unveiling last night…Im not 100% sold on it. Even with a nice vanilla rom, the hardware looks a bit boring (yeah, the screen does look nice…plus I bet the cpu+gpu will be awesome)…so my next choice is the HTC One. However, I don’t see any posts talking about Roms (other than stock/sense roms)…is this because its new…or is there an issue and custom vanilla android roms might not come out straight away?
Sorry for all the questions, just want to make sure I know whats what before jumping in (I know for example, the sgs2 couldn’t get JB roms working 100% because it was missing the Sammy HW compressor at one point)
Cheers guys
fracmo2000 said:
I was waiting on the sgs4, but after the cringe worthy unveiling last night…Im not 100% sold on it. Even with a nice vanilla rom, the hardware looks a bit boring (yeah, the screen does look nice…plus I bet the cpu+gpu will be awesome)…so my next choice is the HTC One. However, I don’t see any posts talking about Roms (other than stock/sense roms)…is this because its new…or is there an issue and custom vanilla android roms might not come out straight away?
Sorry for all the questions, just want to make sure I know whats what before jumping in (I know for example, the sgs2 couldn’t get JB roms working 100% because it was missing the Sammy HW compressor at one point)
Cheers guys
Click to expand...
Click to collapse
It's just a matter of time till the No-Sense script (I believe that's what it was called for most htc phones) is adapted for the One.
However, out of the box you should be able to use something like Nova launcher to give you as much vanilla as you can get without rooting.
Hope it helped
aranab said:
It's just a matter of time till the No-Sense script (I believe that's what it was called for most htc phones) is adapted for the One.
However, out of the box you should be able to use something like Nova launcher to give you as much vanilla as you can get without rooting.
Hope it helped
Click to expand...
Click to collapse
Not had an HTC phone since the Sony X1! Thanks for the heads up on the No-Sense script, I found the HTC One M7 multi purpose tool...awesome!
fracmo2000 said:
Not had an HTC phone since the Sony X1! Thanks for the heads up on the No-Sense script, I found the HTC One M7 multi purpose tool...awesome!
Click to expand...
Click to collapse
wouldnt that be a sony then and not a htc lol
strikerdj2011 said:
wouldnt that be a sony then and not a htc lol
Click to expand...
Click to collapse
i think he means since the time of the sony x1
You have to wait for someone to develope AOSP for this device. Typically, you have some one try to get CM going, then you'll get aokp and so on if this device is popular enough.
Sent from my HTC One S using xda app-developers app
strikerdj2011 said:
wouldnt that be a sony then and not a htc lol
Click to expand...
Click to collapse
Would be Sony Ericsson, but the Xperia X1 was build by HTC just Software was SE.
it will need some time until someone figures out how everthing works with snapdragon cpu and until htc delivers some kernel sources... hopefully they will update to 4.2.2 anytime soon with kernel sources to get stable cm10.1
None on the Vivid Roms are anywhere close to stable, and all the dev's are leaving :crying:
I may be misinformed, but there is not a single rom that works flalessly on our devices...
So, this brings me to my question. Is there a UNIVERSAL ROM for ANY ANDROID DEVICE?
No, there is no universal Rom
Why?
-because every android device is completely different from each other...even similar devices have quite a bit of differences-chipsets, manufacturers, drivers, mount points...etc, they all very from device to device
Sent from my HTC PH39100 using Tapatalk 2
get a new phone
Sent from my HTC PH39100 using Tapatalk 4 Beta
skyrocketeer said:
get a new phone
Sent from my HTC PH39100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Just wondering... Would you want to donate one? The only way I got a Vivid is coz I got one in one of those charity secret santa things.
Mihir1997 said:
Just wondering... Would you want to donate one? The only way I got a Vivid is coz I got one in one of those charity secret santa things.
Click to expand...
Click to collapse
Do you dev? considering you just asked for Universal rom, I'm going to assume you don't.
So no
Mihir1997 said:
None on the Vivid Roms are anywhere close to stable, and all the dev's are leaving :crying:
I may be misinformed, but there is not a single rom that works flalessly on our devices...
So, this brings me to my question. Is there a UNIVERSAL ROM for ANY ANDROID DEVICE?
Click to expand...
Click to collapse
i suggest flashing some roms instead of putting dow the forum. some ppl have put alot of work into these roms
Try albinoman's CyanogenMod 10.1 ROM. It's Jellybean 4.2.2 and is stable. Only problem I have is reception bars are inaccurate, but that is a rare problem.
Only other bug I have encountered is reception drops on first boot. Easy fix in the development thread.
KarlKognition said:
Try albinoman's CyanogenMod 10.1 ROM. It's Jellybean 4.2.2 and is stable. Only problem I have is reception bars are inaccurate, but that is a rare problem.
Only other bug I have encountered is reception drops on first boot. Easy fix in the development thread.
Click to expand...
Click to collapse
Hi,
I flashed this Rom, but it seems that the in-call and speaker volume is still very low.
I started from the stock ICS rom, unlocked, rooted, flash boot.img and flash the rom. The volume issue in CM10 is solved in this Rom?
Thanks
friedenhe said:
Hi,
I flashed this Rom, but it seems that the in-call and speaker volume is still very low.
I started from the stock ICS rom, unlocked, rooted, flash boot.img and flash the rom. The volume issue in CM10 is solved in this Rom?
Thanks
Click to expand...
Click to collapse
No its going to plauge this device forever. I am going to try one thing to see if I can make it work .. I found something.. But It most likely wont work and this is sorta off topic to what this started out to be. If you have any questions go ask em in the Development section
KarlKognition said:
Try albinoman's CyanogenMod 10.1 ROM. It's Jellybean 4.2.2 and is stable. Only problem I have is reception bars are inaccurate, but that is a rare problem.
Only other bug I have encountered is reception drops on first boot. Easy fix in the development thread.
Click to expand...
Click to collapse
This is the first Rom that I've flashed and its my daily driver its good enough the call volume is annoying but when I call someone they can't hear me but I can hear them from time to time any idea on why that is?
Sent from my Vivid 4G using xda app-developers app
swordmastr54 said:
This is the first Rom that I've flashed and its my daily driver its good enough the call volume is annoying but when I call someone they can't hear me but I can hear them from time to time any idea on why that is?
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
It is a bug in all of the AOSP based roms. Albinoman released a new build which kinda fixes it. I haven't tested it yet but according to the posts on the thread seems to be working well.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
WildfireDEV said:
It is a bug in all of the AOSP based roms. Albinoman released a new build which kinda fixes it. I haven't tested it yet but according to the posts on the thread seems to be working well.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Click to expand...
Click to collapse
I would like to ask: do you mean the low in-call volume is fixed? I am going to try this rom!
Thanks
friedenhe said:
I would like to ask: do you mean the low in-call volume is fixed? I am going to try this rom!
Thanks
Click to expand...
Click to collapse
its more like "medium" in call volume now.
i m making one!!
a universal rom seems pretty impossible right!! i ll make one fr sure and u all will get that for free right here on xda i jst need time so u jst wait n watch people!!
I need a coustom rom for allwinner a23 it is a chinese tablet
is there have any rom for Walton primo s5. if anyone know plzzz
An old instinct brought me here? Why? Because its possible!
Mihir1997 said:
None on the Vivid Roms are anywhere close to stable, and all the dev's are leaving :crying:
I may be misinformed, but there is not a single rom that works flalessly on our devices...
So, this brings me to my question. Is there a UNIVERSAL ROM for ANY ANDROID DEVICE?
Click to expand...
Click to collapse
What an interesting post that relays something I've been noticing about XDA, it's development and far too many post of someone who asserted they had no problems putting such and such ROM into his device, "Here's the Tutorial" issue I'm having at present.
I have even openly complained about the only thing I was learning how to do here was how to brick devices in every possible way. And the way I found out how to recover from it properly, sure wasn't from them here. A lot of times you can get the official firmware straight from the manufacturer, online. I've been gone 8 to 10 years and what happened? Most of the posts are Ghost-Town status! Back to the point.
I don't see why they can't be universal, really. And it seems as though, that this was overlooked by every single so-called developer out there. How do you make a 64 bit processor with a dual core would be the first clue. You got your phone(modem) and a split partition that the modem may control sometimes but, can be modified. They seem to have decorated the tree, so to speak rather than actually "build" something. Oh it looks nice and all with the tinsel and shinny stuff. But they're in a hurry I guess and missing the reality of it. You can see it with the source code. The story will go that they got a source code, let's say, Android 4.0. Did this, this, this and that and here you go. Woohooo, look what I did. But what did they do? It wasn't really building if you look at it the right way, it's just, decoration. In the beginning you had to stack things, like boxes. one on top of the other. It's kinda like that. Or sideways. Remember the basics. Two core, four core, soon eight. It doesn't really matter when all it is, is some kind of partitioning. What is it all? 64 one way or another. But seperate the two is the first issue. The phones gonna be the phone regardless. Put a switch in for control. Then you're left with the other part to do as you wish. Run a whole different program, on top of the phone program. Eventually you're gonna reach the end of what the phone is capable of. That's a givenIt was remembering the days of TV/VCR repair and how a basic motherboard works. This part controls audio, this part controls video thing. Now you see it? It's the same in an Android isn't it, just smaller of course. And when it dawned on me that this was more than possible and everyone went the other way? Oh boy things are about to get silly around here at XDA. I'm most definately going to take a different look at this now. It wasn't a problem ten years ago once you got the hang of it to flash in a ROM. Everything I see now is. So what happened? Everyone went decorating I guess...
---------- Post added at 03:19 PM ---------- Previous post was at 02:50 PM ----------
mg2195 said:
No, there is no universal Rom
Why?
-because every android device is completely different from each other...even similar devices have quite a bit of differences-chipsets, manufacturers, drivers, mount points...etc, they all very from device to device
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Riiiight chipsets are more about how many GHz the device may use which is usually around 1 to 1.65 GHZ, we want our devices fast. Manufactures? Well they just put the same stuff together in a different way. Drivers and mounts can be put together, same ol USB (with maybe different serials) and even sd card mounts. Really there's not much difference when you look at it as a whole. Refrence
https://www.androidauthority.com/fact-or-fiction-android-apps-only-use-one-cpu-core-610352/
Hi everyone,
I must say that android 4.4 sounds like a great improvement for us as our device is getting older \=
However, I'm afraid that we may not get a stable rom running this version. I mean' we might get some rom that some how runs it, but still as many roms to our device thease days - they are not stable at all.
So what do you think? will we get it or not?
gavraz said:
Hi everyone,
I must say that android 4.4 sounds like a great improvement for us as our device is getting older \=
However, I'm afraid that we may not get a stable rom running this version. I mean' we might get some rom that some how runs it, but still as many roms to our device thease days - they are not stable at all.
So what do you think? will we get it or not?
Click to expand...
Click to collapse
Lol why not @szezso is working on it. We are moving away from CM and going towards something closer to AOSP because of the changes in cm. Fyi.
The CM ROMs by szezso are basically stable..
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Lol why not @szezso is working on it. We are moving away from CM and going towards something closer to AOSP because of the changes in cm. Fyi.
The CM ROMs by szezso are basically stable..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
With this kid ^ as per usual. Szezso is a good dev. Its just another update. Hopefully it is as 'light' as they say. So it runs well.
Sent from my Incredible S S710e using Tapatalk
james1196 said:
With this kid ^ as per usual. Szezso is a good dev. Its just another update. Hopefully it is as 'light' as they say. So it runs well.
Sent from my Incredible S S710e using Tapatalk
Click to expand...
Click to collapse
I'll find out soon when Google/HTC decide to release kit kat for N7 and One Google edition
poondog said:
I'll find out soon when Google/HTC decide to release kit kat for N7 and One Google edition
Click to expand...
Click to collapse
My Nexus 5 will have it
Sent from my Incredible S S710e using Tapatalk
I'm sorry but I don't think szesco's roms are stable enough. I do appreciate his and contribution of course but since he doesn't have much time and also has many projects simultaneously, it results with poor stability and discontinued projects.
I'm using lacost rom and that one also is very poor like many other. It seems like it's better to use Android 2.3 based roms.
gavraz said:
I'm sorry but I don't think szesco's roms are stable enough. I do appreciate his and contribution of course but since he doesn't have much time and also has many projects simultaneously, it results with poor stability and discontinued projects.
I'm using lacost rom and that one also is very poor like many other. It seems like it's better to use Android 2.3 based roms.
Click to expand...
Click to collapse
What do you define by stable...
Cuz the way I define stable is good enough to be a daily driver with the RARE random rebooting.
072665995 said:
What do you define by stable...
Cuz the way I define stable is good enough to be a daily driver with the RARE random rebooting.
Click to expand...
Click to collapse
What rom do you use? I think I would define such a rom as stable too.
With lacost rom I'm experiancing every day (and sometimes more the once) situations were an app stops to respond or something and the whole phone get stuck, nothing responses. sometimes I have to wait, sometimes I have no other option but to remove the battery.
gavraz said:
What rom do you use? I think I would define such a rom as stable too.
With lacost rom I'm experiancing every day (and sometimes more the once) situations were an app stops to respond or something and the whole phone get stuck, nothing responses. sometimes I have to wait, sometimes I have no other option but to remove the battery.
Click to expand...
Click to collapse
You can't compare ROM stability to app stability. I've seen lots of cases where apps just stop responding and that really doesn't have much to do with the ROM being unstable.
With the phone getting stuck from time to time, I experience no such problem or VERY RARELY on each AOSP ROM here. Sometimes, you may lose responsiveness but you can just lock your screen and then unlock it and that will fix it.
4.4 for HTC S2 will be dream coming true especially for phone with low memory.
JB from sezscoz is stable.. But i do find a lag in scrolling or navigating to diff app or setting etc..
Well, 4.4 is basically 4.3 with a couple of changes, and it was also designed to run on 512mb of ram, so if we got 4.3, i dont see a limitation on 4.4
Press "thanks" if I helped you out!
LamboBull said:
Well, 4.4 is basically 4.3 with a couple of changes, and it was also designed to run on 512mb of ram, so if we got 4.3, i dont see a limitation on 4.4
Press "thanks" if I helped you out!
Click to expand...
Click to collapse
It would be quite different taking into account its 'More' Pure AOSP rather than CM. It does look a bit different and apparently far 'lighter'.
Sent from my Incredible S S710e using Tapatalk
072665995 said:
You can't compare ROM stability to app stability. I've seen lots of cases where apps just stop responding and that really doesn't have much to do with the ROM being unstable.
With the phone getting stuck from time to time, I experience no such problem or VERY RARELY on each AOSP ROM here. Sometimes, you may lose responsiveness but you can just lock your screen and then unlock it and that will fix it.
Click to expand...
Click to collapse
Oh of course, I know. It isn't a specific app, sometimes it's the chrome sometimes whatsapp or Trebuchet launcher sometimes I don't even know what app causes it.
Something with the rom isn't right... the whole phone just stops responding.
I had love to use that AOSP rom, any recommendations on a specific one?
gavraz said:
Oh of course, I know. It isn't a specific app, sometimes it's the chrome sometimes whatsapp or Trebuchet launcher sometimes I don't even know what app causes it.
Something with the rom isn't right... the whole phone just stops responding.
I had love to use that AOSP rom, any recommendations on a specific one?
Click to expand...
Click to collapse
I recommend CyanVivoX. Very stable and pretty much no bugs.
072665995 said:
I recommend CyanVivoX. Very stable and pretty much no bugs.
Click to expand...
Click to collapse
CM build are very nice, but battery optimizations are bad.
On Sense roms my phone is working about 3-4 days!
And CM roms kill my IncS battery for 1-2 days