The PRL issue, not because of rom? - Hero CDMA General

I know the PRL issue is fixed, but after all the debate I decided to look at my old thread again
http://forum.xda-developers.com/showthread.php?t=628027
I'm not sure if the people on the old Damage leak where just having a problem with their PRI's or PRl's.
Either way it is interesting that a STOCK phone.
That was nearly never used, had this issue.

chococrazy said:
I know the PRL issue is fixed, but after all the debate I decided to look at my old thread again
http://forum.xda-developers.com/showthread.php?t=628027
I'm not sure if the people on the old Damage leak where just having a problem with their PRI's or PRl's.
Either way it is interesting that a STOCK phone.
That was nearly never used, had this issue.
Click to expand...
Click to collapse
People who had this problem were normally people who flashed "Eris" based roms. Not sure why a stock Phone would not have the right PRL.

Related

How is latest HTC update incorporated into ROMs ?

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.

Increase Signal?

I'm not talking about the image of the signal, I'm talking about the actual signal. My Vibrant seems to be getting horrible reception in places that I normally get great reception. Is there a new radio or a setting somewhere that I can change? I'm getting almost no signal with 3g on, but decent signal with it off.
Thanks in advance.
Minker17 said:
I'm not talking about the image of the signal, I'm talking about the actual signal. My Vibrant seems to be getting horrible reception in places that I normally get great reception. Is there a new radio or a setting somewhere that I can change? I'm getting almost no signal with 3g on, but decent signal with it off.
Thanks in advance.
Click to expand...
Click to collapse
Flash the JI6 radio, i get flawless reception inside buildings etc.
Is there a simple way to do this? Without ODIN?
Someone needs to explain the difference between 3g and edge.
I know that shouldn't make a difference, I'm just saying.
Minker17 said:
I know that shouldn't make a difference, I'm just saying.
Click to expand...
Click to collapse
Yes it will. T-Mobile's edge network is stronger than their 3g network. They basically have two different networks.. unlike ATT.
Is the new J16 radio been packaged to a zip alone?
I would also like to see the JI6 modem packaged in a standalone update zip file. I'd love the update without installing a new buggy rom and I don't trust Odin, already bricked me once.
Bionix 1.5 comes with the JI6 modem and it is not buggy at all. It is very close to stock with minor tweaks for performance. I suggest you use that. I've been using it without flaw.
kangxi said:
Bionix 1.5 comes with the JI6 modem and it is not buggy at all. It is very close to stock with minor tweaks for performance. I suggest you use that. I've been using it without flaw.
Click to expand...
Click to collapse
If people flash that rom or any other rom for that matter won't they still need to odin back to stock to receive updates and 2.2 when it arrives? I myself prefer not to mess with odin either after reading some of the issues on here. Its one of the reasons why I have not flashed any roms and probably won't.
SE7EN- said:
If people flash that rom or any other rom for that matter won't they still need to odin back to stock to receive updates and 2.2 when it arrives? I myself prefer not to mess with odin either after reading some of the issues on here. Its one of the reasons why I have not flashed any roms and probably won't.
Click to expand...
Click to collapse
1. Ppl who have rooted will Most likely have a 2.2 update with dev sprinkles the first few hours after they get the source which someone will dump after getting the OTA or maybe sammy will be nice enough to make it available upon the OTA release.
2. ODIN does more good then harm. It is the only thing that can bring you back from a brick. As long as you read enough & understand what you are doing before being flash happy then you will see how great the development is & you will enjoy its benefits.
SE7EN- said:
If people flash that rom or any other rom for that matter won't they still need to odin back to stock to receive updates and 2.2 when it arrives? I myself prefer not to mess with odin either after reading some of the issues on here. Its one of the reasons why I have not flashed any roms and probably won't.
Click to expand...
Click to collapse
+1 for the JI6 modem!
And yeah it's sort of a given that you will likely have to flash back to JFD to be recognized for an OTA...
Just keep in mind HOW OTA's work. They're generally pushed out in batches of phones rather than all at once. All at once would just be unmanageable. On balance those of us who do routinely use Odin will be able to get the version pushed via OTA quicker than most...primarily because we're an impatient lot.
Even as simple as it is on the Galaxy S phones to do (given you do your homework of course) experimenting with firmwares isn't for everybody...
All~G1 said:
2. ODIN does more good then harm. It is the only thing that can bring you back from a brick. As long as you read enough & understand what you are doing before being flash happy then you will see how great the development is & you will enjoy its benefits.
Click to expand...
Click to collapse
Tell that to my hardware disabled Vibrant that had to get exchanged out because it couldn't be unbricked. Not taking that risk again on a hardware locked Vibrant.
As for Bionix 1.5, I'm using 1.4 but if I understand correctly the BT issue won't be corrected until 1.6.
For some reason with the J16...I'm getting more bars in NYC Subway systems.. I can talk even longer before it cuts off...I know ppl are jealous lol

Went back to DI18 (F) DK28

Im so sick of DK28 and all of its issues. I just went back to DI18 Epic Experience. So much more smoother. No lag. No cant hear when calling glitch. No gallery problems. No force closes. No random reboots. NOTHING!! Just a nice smooth phone that I can use and that is reliable!!!!!! Im done with the whole leaked version thing. I wont flash my phone again until the official froyo comes out for the Epic. Good night DK28!!
I did. Well I was an idiot and bricked my phone and was lucky enough to get it replaced without the $100 deposit (thank you Dustin). I planned on rooting and flashing asap until I literally was about to connect the usb cable into my pc. For now I am staying stock. I may Z4 it to get rid of some stock apps but I am taking a break from the ROM/Modem flashing and theming stuff. My new Epic is running WAY better now then my old one was on DK28. I mainly wanted flash 10 but once I got it I never used it. I thought it would be great for watching HULU in between class or when I take the bus to work but my battery life was only 4hrs and I never could fix it no matter what recommendation I tried. Now my battery lasts all day again. We will see what I do in another week or 2 though lol.
youngpro83 said:
Im so sick of DK28 and all of its issues. I just went back to DI18 Epic Experience. So much more smoother. No lag. No cant hear when calling glitch. No gallery problems. No force closes. No random reboots. NOTHING!! Just a nice smooth phone that I can use and that is reliable!!!!!! Im done with the whole leaked version thing. I wont flash my phone again until the official froyo comes out for the Epic. Good night DK28!!
Click to expand...
Click to collapse
Did you try the "Truly Epic Rom" I was on the same boat as you, and was about to switch till I gave that ROM try....Its rocks!!! and its silky smooth!!
Erica8123 said:
I did. Well I was an idiot and bricked my phone and was lucky enough to get it replaced without the $100 deposit (thank you Dustin). I planned on rooting and flashing asap until I literally was about to connect the usb cable into my pc. For now I am staying stock. I may Z4 it to get rid of some stock apps but I am taking a break from the ROM/Modem flashing and theming stuff. My new Epic is running WAY better now then my old one was on DK28. I mainly wanted flash 10 but once I got it I never used it. I thought it would be great for watching HULU in between class or when I take the bus to work but my battery life was only 4hrs and I never could fix it no matter what recommendation I tried. Now my battery lasts all day again. We will see what I do in another week or 2 though lol.
Click to expand...
Click to collapse
Yeah I hear ya!! Hopefully they will come out with the official froyo so I can actually have a decent phone with froyo that actually works without all the head aches.
youngpro83 said:
Im so sick of DK28 and all of its issues. I just went back to DI18 Epic Experience. So much more smoother. No lag. No cant hear when calling glitch. No gallery problems. No force closes. No random reboots. NOTHING!! Just a nice smooth phone that I can use and that is reliable!!!!!! Im done with the whole leaked version thing. I wont flash my phone again until the official froyo comes out for the Epic. Good night DK28!!
Click to expand...
Click to collapse
From what I've experienced, there really aren't any issues with DK28 that aren't already in 18. Every Rom I've tried recently (Quantum, Bonsai, Midnight) has been silky smooth and I haven't gotten any FCs, calling glitches or anything you've experienced.
I just think its odd that people blame all their problems on the build. Its understandable if everyone is having the same issues as you, but when you're the odd one out, doesn't that mean you're the one thats the problem?
riceknight said:
From what I've experienced, there really aren't any issues with DK28 that aren't already in 18. Every Rom I've tried recently (Quantum, Bonsai, Midnight) has been silky smooth and I haven't gotten any FCs, calling glitches or anything you've experienced.
I just think its odd that people blame all their problems on the build. Its understandable if everyone is having the same issues as you, but when you're the odd one out, doesn't that mean you're the one thats the problem?
Click to expand...
Click to collapse
Well when Im looking through the threads and Im reading the titles that people post who are experiencing the same issues as I am and many others on this site, then I would assume its the build and not just one particular person. Not to mention its a leak.....Its not even an official release so for you to sit here and claim that it is more STABLE than the STOCK BUILD or anywhere close, you sound like a fan/groupie of DK28 rather than a person who is speaking from knowledge. There are more people on this thread than me who have been experiencing more than a few issues with the "leaked" froyo. When dialing out and sometimes the call not going through or you can talk but cant hear is a KNOWN ISSUE with the "BUILD" that even the devs are curious about. Never had an issue like that on the stock BUILD. Anyways like I said F DK28.
For me, Quantum 2.1 is more stable than the stock ever was. It's not fanboy speak, it's that we know what we're doing and it's pretty obvious that Froyo is much faster. Maybe Froyo doesn't work as well on older revisions of the Epic hardware, I know I got mine in December rather than when it was first released. But for me, it is much better than the crappy stock rom which is bloated with Sprint garbage.
Do we all care about if someone flashes back. It seems like posts like this keep clutterng up the forums. It makes it really difficult to search. Who cares u went back to stock. Mod please delete thread.
Sent from my viperROM rooted ext4 epic 4g
So what your telling me is that the pre-release version of a ROM is more buggy and less stable then a final product. Got ya.
MedicStuder said:
Do we all care about if someone flashes back. It seems like posts like this keep clutterng up the forums. It makes it really difficult to search. Who cares u went back to stock. Mod please delete thread.
Sent from my viperROM rooted ext4 epic 4g
Click to expand...
Click to collapse
Get off his case. He's sharing his experience on DK28 vs DI18 in case some DI18 users were still on the fence as to whether or not they want to jump to a buggy 2.2.1 build. There's a lot of hate going around these forums and it's the response like what you just gave thats give people a poor outlook of our community.
Personally I've experienced both sides of the argument. I went with DK28 first and killed my gps, flashed back to DI18 and went with ACS for 3 weeks. Got sick of 2.1 and really wanted some 2.2 features back so I went with midNIGHT and a 2.3 theme.
Thanks for your thoughts OP, I share the same concerns but found some of the buggy issues of DK28 to outweigh the bugs and lack of features of DI18. I actually think its funny though because a buggy DK28 makes me want a real stable froyo build even more than being on eclair made me want a 2.2 update lol
snowmanwithahat said:
Get off his case. He's sharing his experience on DK28 vs DI18 in case some DI18 users were still on the fence as to whether or not they want to jump to a buggy 2.2.1 build. There's a lot of hate going around these forums and it's the response like what you just gave thats give people a poor outlook of our community.
Personally I've experienced both sides of the argument. I went with DK28 first and killed my gps, flashed back to DI18 and went with ACS for 3 weeks. Got sick of 2.1 and really wanted some 2.2 features back so I went with midNIGHT and a 2.3 theme.
Thanks for your thoughts OP, I share the same concerns but found some of the buggy issues of DK28 to outweigh the bugs and lack of features of DI18. I actually think its funny though because a buggy DK28 makes me want a real stable froyo build even more than being on eclair made me want a 2.2 update lol
Click to expand...
Click to collapse
Exactly! I have been flashing my phone since I had my Touch Pro so I know all about leaks and the benefits they bring to a hardcore phone user like myself. I enjoyed DK28 for sometime now and it seems like the more people do to it the more some things stop working. I just got to the point where I was just tired of constantly updating the ROM with the newer version because the dev "FIXED" another DK28 issue. I appreciate all of their hard work. I even donated to a few of them because they made me love my Epic again with all these new EXT4 and no journaling mods. My phone has never been so fast and snappy......But at the end of the day when I need to use my phone I dont need it to do a random reboot or even worse miss a call because the other person cant hear me which is a very common problem some users are having. Although now that I am back on the DI18.......Its hard to find all those cool mods that I have been so used to. lol. Decisions decisions.
snowmanwithahat said:
Get off his case. He's sharing his experience on DK28 vs DI18 in case some DI18 users were still on the fence as to whether or not they want to jump to a buggy 2.2.1 build. There's a lot of hate going around these forums and it's the response like what you just gave thats give people a poor outlook of our community.
Personally I've experienced both sides of the argument. I went with DK28 first and killed my gps, flashed back to DI18 and went with ACS for 3 weeks. Got sick of 2.1 and really wanted some 2.2 features back so I went with midNIGHT and a 2.3 theme.
Thanks for your thoughts OP, I share the same concerns but found some of the buggy issues of DK28 to outweigh the bugs and lack of features of DI18. I actually think its funny though because a buggy DK28 makes me want a real stable froyo build even more than being on eclair made me want a 2.2 update lol
Click to expand...
Click to collapse
If he wanted to share his experience then he should have searched for one of the other threads that has already been started about this topic instead of starting yet another one.
Sent from my viperROM rooted ext4 epic 4g
youngpro83 said:
Well when Im looking through the threads and Im reading the titles that people post who are experiencing the same issues as I am and many others on this site, then I would assume its the build and not just one particular person. Not to mention its a leak.....Its not even an official release so for you to sit here and claim that it is more STABLE than the STOCK BUILD or anywhere close, you sound like a fan/groupie of DK28 rather than a person who is speaking from knowledge. There are more people on this thread than me who have been experiencing more than a few issues with the "leaked" froyo. When dialing out and sometimes the call not going through or you can talk but cant hear is a KNOWN ISSUE with the "BUILD" that even the devs are curious about. Never had an issue like that on the stock BUILD. Anyways like I said F DK28.
Click to expand...
Click to collapse
Way to get defensive without backing your claims. There are also much more than a few people who aren't experiencing the same problems you are. I've never even heard of the dial out bug nor experienced it in any flash. If you don't want to work to get a good beta experience, why are you even on XDA and flashing in the first place? I find that DK28 isn't perfect, but its still leaps and bounds better than stock.
You have problems? Try to get them fixed, reflash or ask some questions on the Q&A. Don't just blame it on the build. Basic rule of thumb? If majority don't have the same problem you're having, double check what you've done or reflash.
NYYFan325 said:
So what your telling me is that the pre-release version of a ROM is more buggy and less stable then a final product. Got ya.
Click to expand...
Click to collapse
These are Samsung builds so I don't thinks there's really a difference between a alpha/beta/RC and a final build!
juise said:
These are Samsung builds so I don't thinks there's really a difference between a alpha/beta/RC and a final build!
Click to expand...
Click to collapse
Riiiiiiiiiiiight
To use the OS "windows" as an analogy for you...
How do you think the bugs get found and fixed? When Vista (or any OS for this matter) was in Beta 1 / Beta 2 stage... guess what? It had MORE BUGS / glitches then the version that was released to the public. When it went to RC stage, it had less bugs then the beta. When it went to RTM (the version released to the public) it had less buts the beta and the rc.
Nothing will ever be 100% bug free, but to say you dont think there is a difference between alpha/beta/rc and final builds is very VERY naive of you.
P.S. if you were being sarcastic, my bad lol
Actually MS betas don't work that way, they release betas and continue to fix the bugs they are allowed to fix and run 100000 regression scripts and if any regressions are found they actually unfix the bug and attempt a different fix for it.
Eventually they end up releasing a few release candidates and end up picking the least buggy of these to promote to RTM.
I have a number of friends who work as SDE/Ts for MS, this is how it goes.
Also -- it's very possible that an updated code branch has more bug fixes than bugs introduced on smaller projects (like Android customizations) versus something huge like Windows.
riceknight said:
You have problems? Try to get them fixed, reflash or ask some questions on the Q&A. Don't just blame it on the build. Basic rule of thumb? If majority don't have the same problem you're having, double check what you've done or reflash.
Click to expand...
Click to collapse
Seriously? Don't you think if the build was so perfect, Sprint would have released it by now?
Fact: There are bugs in DK28. Congrats that you aren't experiencing them.
I personally experience the calling out bug, but not the GPS bug. My accelerometer was jacked up for a while when I moved to DK28 until I found a good workaround (and no, the simple "recalibrate in the terminal method" didn't work). HOWEVER, the benefits to me are greater than the disadvantages of having these bugs in DK28.
This is a forum - the OP was sharing his experience. What kind of forum would it be if no one was able to share there personal experiences with the phone we all have?
Cut the guy some slack.
abrognlie said:
Seriously? Don't you think if the build was so perfect, Sprint would have released it by now?
Fact: There are bugs in DK28. Congrats that you aren't experiencing them.
I personally experience the calling out bug, but not the GPS bug. My accelerometer was jacked up for a while when I moved to DK28 until I found a good workaround (and no, the simple "recalibrate in the terminal method" didn't work). HOWEVER, the benefits to me are greater than the disadvantages of having these bugs in DK28.
This is a forum - the OP was sharing his experience. What kind of forum would it be if no one was able to share there personal experiences with the phone we all have?
Cut the guy some slack.
Click to expand...
Click to collapse
So... you had a bug and you looked around and found a way to fix it. Congrats. Thats exactly what my advice was.
I've had FC problems on prior Rom flashes before. I reflashed and took my time to fix it. My phone runs smoothly now. I could just Odin DI18 and blame it all on DK28, but like most people, I took the time to get it right. If it were an OTA upgrade, you could blame it on the build, but its a Rom, so take the time to get it running and like you said yourself, there are plenty of people to help with good workarounds.
I don't understand all the pandering and hand holding thats encouraged in these forums. You encourage whining and then complain when there is so much of it. How about encouraging these same people to go out and improve their phones instead of coddling them?
+1 Theres so many resources and answers theres no reason to not have a sweet running,personalized non buggy phone on dk28

Would be a good idea no?

Should'nt we all start posting annoying threads on Facebook to Motorola and the MS2?.. I already started see here -> http://www.facebook.com/topic.php?uid=121867580498&topic=20102
If we all do that.. they maybe atleast see it.. and think 0,0001 second about it.. thats better than nothing..!!!!
I wist it'd be that simple. With the first Milestone they've proven that they don't know what support is.
I seriously doubt it will have any effect. We all know about the MP3 problems and wrong keyboard layout... The device has been on the market for about six months and there's still no sign of a fix for those problems. Kind of annoying, having a euro sign on the keyboard, but not being able te use it.
...and Motorola knows about those issues. They simply choose not to fix them.
these two bugs are not present in custom firmware argent2stone...
try it
I already fixed those problems in the stock ROM for now I actually quite like Blur, so I don't need it (partially) removed. Unless Argen2Stone performance is undeniably better than Stock. Furthermore I don't know if it fixes the AAC problems, so I don't feel like reinstalling it now...
Still, that isn't the point. It's about the fact Motorola should've pushed a fix for those issues. They're minor, highly annoying and not everybody wants to root their phone to fix such issues.
w0ndersp00n said:
Still, that isn't the point. It's about the fact Motorola should've pushed a fix for those issues. They're minor, highly annoying and not everybody wants to root their phone to fix such issues.
Click to expand...
Click to collapse
Absolutely. +1

Did anyone with multitouch download a new ROM?

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.

Categories

Resources