Related
How is the latest HTC update incorporated into ROMs, specifically non-Sense based ROMs ? I think with Sense-based ones, it's somewhat easier, but for Cyanogen-based ones, I'm completely clueless.
Main reason I ask is because of the silent-call issue. It's supposedly fixed with this update (I don't know for sure though) and it would be real nice to have it incorporated into the CM ROMs. I was hoping that running a CM ROM would avoid this issue, but alas, it doesn't.
hallstevenson said:
How is the latest HTC update incorporated into ROMs, specifically non-Sense based ROMs ? I think with Sense-based ones, it's somewhat easier, but for Cyanogen-based ones, I'm completely clueless.
Main reason I ask is because of the silent-call issue. It's supposedly fixed with this update (I don't know for sure though) and it would be real nice to have it incorporated into the CM ROMs. I was hoping that running a CM ROM would avoid this issue, but alas, it doesn't.
Click to expand...
Click to collapse
i have yet to have any silent call at all on any rom i have ever flashed
When I was running Sense-based ROMs, it was getting to the point that I was ready to return my phone to VZW. When I switched to CM5 ROMs, it was much improved, but still happened on occasion.
hallstevenson said:
When I was running Sense-based ROMs, it was getting to the point that I was ready to return my phone to VZW. When I switched to CM5 ROMs, it was much improved, but still happened on occasion.
Click to expand...
Click to collapse
wish i could offer advice but ive yet to experience it
I'm beginning to think that the silent issue is user error. Maybe a setting or am app that some people use or something. I have never had the issue and I have tested just about every rom.
Sorry off topic.
Sent from my KaosFroyoEris
Speculation is that the new radio may be the "silent call" bugfix. Flash that & see if it helps.
Sent from my Eris using XDA App
PPCGeek01 said:
Speculation is that the new radio may be the "silent call" bugfix. Flash that & see if it helps.
Click to expand...
Click to collapse
That "new" radio has been available from Sprint for more than a few weeks, if not longer, and I can personally attest that it does NOT fix the issue.
i have noticed this issue with my gfs phone. when she answers her phone no one can hear her. shes had this problem on several different roms. i however haven't on any...
I can confirm that the latest fix pushed from VZN has fixed the no-audio bug on my wife's Eris. She was rebooting multiple times a day, and has not since the update!
The real question is can I safely root and load EvilEris 3.0 now without losing the fix??
dman776 said:
The real question is can I safely root and load EvilEris 3.0 now without losing the fix??
Click to expand...
Click to collapse
I think the answer to that is "no".
listyb01 said:
I'm beginning to think that the silent issue is user error. Maybe a setting or am app that some people use or something.
Click to expand...
Click to collapse
Too many people have changed the same setting or added the same app then.... And if that many people have done the same thing "wrong", it still warrants a fix from VZW or HTC.
Havent had the problem with PlainJane2.0, will report if I do though
I've been running non-Sense ROMs since I rooted and haven't had the silent bug yet. I had it a few times after the 2.1 OTA, but nothing since running White Widow 4.5 and now CELB 2.8... hopefully it stays that way
DDustiNN said:
I've been running non-Sense ROMs since I rooted and haven't had the silent bug yet. I had it a few times after the 2.1 OTA, but nothing since running White Widow 4.5 and now CELB 2.8... hopefully it stays that way
Click to expand...
Click to collapse
If you're like me, you just jinxed yourself. I said the same thing -- had the same experience -- for a good while after switching to CM-based ROMs. I posted this and bam ! Started experiencing it again...
hallstevenson said:
I think the answer to that is "no".
Click to expand...
Click to collapse
I can confirm this. The EvilEris 3.0 ROM does not include this bug fix and the bug is still present. The bug ceased for me until I rooted my phone and installed the EvilEris 3.0 ROM.
No one ? The original question still has me wondering....
hallstevenson said:
No one ? The original question still has me wondering....
Click to expand...
Click to collapse
I have been experimenting with the files from the MR4 update in a few ROMs that I have built but I still can not seem to get them to "take". I am not sure if the update is in build.prop or one of the other files included in MR4. I am still looking for any good documentation on how to cook the update in to my ROMs.
There are folks who know how to do it, but I don't know if it's documented anywhere.
Every rom i have used that was made without the July patch has done the glitch. Now that im on a rom with the patch i havent had an issue. Sucks cause i was loving Sense-able, but im getting use to Xtr
SCato said:
Every rom i have used that was made without the July patch has done the glitch. Now that im on a rom with the patch i havent had an issue. Sucks cause i was loving Sense-able, but im getting use to Xtr
Click to expand...
Click to collapse
I know Sense-Able is Sense-based, but is XTR ? If a ROM is not Sense-based or if it's ported from another (HTC) phone without the issue, and therefore no patch has been made, I wonder if it can be incorporated.
What ROM do you like the best? Rate it now in the above Poll.
My apologies if I left anyone's ROM out, post it here if I overlooked any...
PeAcE!
first, I don't even see a poll. And second, well...
I was in the process of drafting it, took me 30sec though... ;-)
no syndicate rom option?
Where's Baked Snack?
I guess I cannot edit the Poll OR delete the post ....
Sorry everyone! Perhaps a moderate/admin can delete this Post/Poll so I can create one with all the ROM's appropriately.
I think it would be EXTREMELY helpful to have an active indefinite Poll for users to grade all these ROM's, it would help in the selection process...
:-(
Heroic is the tits, but Syndicate is rocking hard on my Epic right now.
ccline84 said:
Heroic is the tits, but Syndicate is rocking hard on my Epic right now.
Click to expand...
Click to collapse
Yeah we need to get Syndicate and Baked Snack up there.
i prefer my own rom, with one of the beastly kernels out there, currently hero special kernel
1999TL said:
no syndicate rom option?
Click to expand...
Click to collapse
Yeah, no love for ACS?
Only thing holding me back from Syndicate right now is that every other post in the thread is someone having some issue with the rom. Been monitoring it nonstop, because they seem like they are bringing the premier rom to XDA for the Epic, but not gonna switch from EE until some issues are smoothed out.
muyoso said:
Only thing holding me back from Syndicate right now is that every other post in the thread is someone having some issue with the rom. Been monitoring it nonstop, because they seem like they are bringing the premier rom to XDA for the Epic, but not gonna switch from EE until some issues are smoothed out.
Click to expand...
Click to collapse
All reproducible bugs are fixed in 1.0.1a, except the harmless Airplane Mode FC and the Service Mode FC (which is only seen if you so desire to go there!) - both of which are not present in Fully Loaded, as it includes TouchWiz.
If you read through the thread, almost all of the issues people have had were due to Clockwork, Titanium Backup, or an SD card that needs formatting. Everything else, like I said above, is fixed - and if you do have any issues (which I assure you, we do not anticipate), just post, and we'll help right away.
I think you'll also find that there are plenty of people needing help with issues in other ROM threads.
k0nane said:
All reproducible bugs are fixed in 1.0.1a, except the harmless Airplane Mode FC and the Service Mode FC (which is only seen if you so desire to go there!) - both of which are not present in Fully Loaded, as it includes TouchWiz.
If you read through the thread, almost all of the issues people have had were due to Clockwork, Titanium Backup, or an SD card that needs formatting. Everything else, like I said above, is fixed - and if you do have any issues (which I assure you, we do not anticipate), just post, and we'll help right away.
I think you'll also find that there are plenty of people needing help with issues in other ROM threads.
Click to expand...
Click to collapse
Did that vibrate issue get resolved? May have to flash me a new rom tomorrow.
muyoso said:
Did that vibrate issue get resolved? May have to flash me a new rom tomorrow.
Click to expand...
Click to collapse
That's in the kernel - DevinXtreme is looking at it - and only at 1.6ghz (and even then, only for some people!). See the Xtreme Kernel thread for more. The kernel defaults to 1ghz, and the ROM does not change that. 1.2ghz is known stable (well, so is 1.6 - minus the odd vibration for some) - and Devin is in the process of adding even more steps (1.3/1.4ghz for example if I recall correctly).
muyoso said:
Did that vibrate issue get resolved? May have to flash me a new rom tomorrow.
Click to expand...
Click to collapse
It's worth installing, I personally have my phone clocked at 1.6 when it's plugged in and it's never once not woken up, or vibrated strangely. Then again, when I flashed I formatted my sd, data, dalvik, you name it.
Baked Snack is the only one that I've tried since its been very stable for the most part. Launcher Pro quits on me every now and then but I believe that its a problem with the app itself.
Since the other thread seems to be getting off topic, what topic? Im not sure since there is no development collaboration in the topic...I have created this thread for us to talk about whatever we want (pertaining to this ROM) SO go ahead and cry and whine all you want here, because afterall, thats the topic.
(MOD> PLEASE MOVE THIS TOPIC TO THE CORRECT FORUM, by MISTAKE I ADDED IT HERE)
Thread moved to General.
I'm afraid to see this thread in a day or two.
Anyways, does anybody know where AOSP and his all-knowing powers stand with this? There's plenty of chatter about what version he's on and all, but does anybody know for sure what he has so far?
I say give it some time. It took a while for Froyo to be fully functional. I'm not too keen on rushing the progress.
But as for GB, it looks really neat. Has anybody got any benchmarks data on it and compared it to the latest Froyo release?
i almost got a 5 on linpack, jit enabled. if u enable jit in gb though ive found video playback is screwey and dont work all the time. or maybe thats just the rom itself cause ive been having video playback problems with jit off to
mdhscanes24 said:
Anyways, does anybody know where AOSP and his all-knowing powers stand with this? There's plenty of chatter about what version he's on and all, but does anybody know for sure what he has so far?
Click to expand...
Click to collapse
Haven't been following the IRC. I don't much like the web based one. I follow 3 from Trillian, but I can't access the one he uses (only tried twice).
I do have hunches as to the slience. A lot of things have changed recently I think he might be working out.
-Root issues - being wiped out because of binary update
-ClockworkMOD - change to 3.0.0.2 supporting the new image methods
-gmail - critical to some, he's probably working on this over..
-camera. not critical to next update, but long run would be nice to have working, even to aosp i'm sure.
oohaylima said:
I say give it some time. It took a while for Froyo to be fully functional. I'm not too keen on rushing the progress.
But as for GB, it looks really neat. Has anybody got any benchmarks data on it and compared it to the latest Froyo release?
Click to expand...
Click to collapse
Rest assured I'm not looking to try and rush things. Hell, it's my daily as is.
I have the new 2.6.35 kernel that gnarlyc was working on working on my eris, I am going to post the link to download after I test it on a few of the other roms. I will release the new kernel in a couple days just wanted to let you all know
Thanks gnarlyc http://forum.xda-developers.com/showthread.php?t=992323
for starting this greate WORK!
mjgdroid said:
I have the new 2.6.35 kernel that gnarlyc was working on working on my eris, I am going to post the link to download after I test it on a few of the other roms. I will release the new kernel in a couple days just wanted to let you all know
Thanks gnarlyc http://forum.xda-developers.com/showthread.php?t=992323
for starting this greate WORK!
Click to expand...
Click to collapse
Well, no real need to thank me. I just start projects and hopefully someone else comes along and finishes them! Great job. Thank you. I look forward to flashing this on my kid's Eris.
Oh sure, now you tell me
What are the differences between the old kernel and this one. Also will this be okay to flash on GSB?
Sent from my ERIS using XDA App
mjgdroid said:
I have the new 2.6.35 kernel that gnarlyc was working on working on my eris, I am going to post the link to download after I test it on a few of the other roms. I will release the new kernel in a couple days just wanted to let you all know
Thanks gnarlyc http://forum.xda-developers.com/showthread.php?t=992323
for starting this greate WORK!
Click to expand...
Click to collapse
Congrats!
Is this based on the recent HeroC/DesireC sources, or the older s0be based sources?
Are the updates on github or some other repository site?
jaybob413 said:
Congrats!
Is this based on the recent HeroC/DesireC sources, or the older s0be based sources?
Are the updates on github or some other repository site?
Click to expand...
Click to collapse
Yeah, me too I had been working on the breber github source and finally got a bootable ERIS that I could adb into and captured a dmesg as well. Only thing lacking (small issue), is that none of the buttons worked I had an idea on a fix but lost my dev box and am waiting on a replacement MB to continue.
Question is, how different is the source tree for this kernel from the breber github source? When I used the breber source, I did change many kernel options to build many items as modules (ipv6 etc...) I've used the stock CM7 as the base w/ many mods for our older phones, and was able to reduce the size of the kernel image fairly significantly. Bootup was a bit quicker, but main idea was to remove some options that are rarely used, but still make them available as modules.
I've not tested this kernel yet, but I had to make a lot of mods to the defconfig etc... to get breber to work. 2.6.35 gives us some nice features, such as auto memory compaction / defragmentation etc... In the short time I was able to use it, it appeared to run better than the .29 we've all been using.
has it been a few days yet?
theboo7 said:
has it been a few days yet?
Click to expand...
Click to collapse
Yes, finally I just got it up and running end of last week and have been playing catch-up. I use this box as a mailserver for my domain, so it spent the first 10 hours processing over 49000 messages.
Funny timing though, just compiled .35 and was getting ready to flash it. At this point, I have no idea where I left off Maybe I'll smoke the Eris next....
as long as we get a download link soon
I was hoping we might hear some updates for the people working on this...
It would be a big help if those who have gotten it to boot would post their source so others can help get this to a stable point without having to repeat work. I'd like to see Eris development stay alive even as many, including myself, have moved on to more powerful phones.
MongooseHelix said:
I was hoping we might hear some updates for the people working on this...
It would be a big help if those who have gotten it to boot would post their source so others can help get this to a stable point without having to repeat work. I'd like to see Eris development stay alive even as many, including myself, have moved on to more powerful phones.
Click to expand...
Click to collapse
sounds good to me. I do have my box up and running, just haven't had much time to mess with it. somewhere along the the line, I screwed up my Conf, but I'll get it. It boots, but I've messed up the mtd enumeration, so no init gets started.
Just as an fyi, I'm using breber's github source with the arm 4.4.3 eabi.
Well, the good news is, I'm running 2.6.35 now. But.... the bad news is that it's on a new Moto Razr. However, I'll still be tinkering with the Eris in my spare time.
I've rooted the Razr, but I'll tell you. Getting recovery on it's a booger. Also, the battery is sealed in (I'm sure the 2 small screws at the top allow a lift out and disconnect). But, kinda got nervous for a sec when I tried to boot into recovery and got nowhere with no easy way to pull the batt. Overall, liking the phone a lot.
Now.... If only I can dig up my working config. I have a cloud based backup system that versions stuff. Need to go through and see if I've got something there.
sracer9 said:
Well, the good news is, I'm running 2.6.35 now. But.... the bad news is that it's on a new Moto Razr. However, I'll still be tinkering with the Eris in my spare time.
I've rooted the Razr, but I'll tell you. Getting recovery on it's a booger. Also, the battery is sealed in (I'm sure the 2 small screws at the top allow a lift out and disconnect). But, kinda got nervous for a sec when I tried to boot into recovery and got nowhere with no easy way to pull the batt. Overall, liking the phone a lot.
Now.... If only I can dig up my working config. I have a cloud based backup system that versions stuff. Need to go through and see if I've got something there.
Click to expand...
Click to collapse
Having a current generation phone is quite a change. I am enjoying my gnex a lot and since it doesn't need much modification, I still get to spend a good bit of my dev time with the eris .
Maybe we can talk workshed into messing with this .35 kernel again when you find that config...or he might be burnt out for awhile on the frustrations that are the kernel porting and the tbolt as a whole.
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?
Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.
Try flashing a different kernel as that is what bridges hardware and software.
Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium
uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.
I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.
I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.