[TESTING] - NAND OMGB (1.2.3)

[vzihome]

Originally Posted by argenisaz

Wow, that was harsh, didn't see that one coming.

Sorry for not posting logs, I was out of town and I needed my phone up and running as soon as possible. I don't post frequently but I try to be helpful when I do.

Anyway, I do agree with you, the new acoustic is here to stay and I'm 100% confident that all the wrinkles will be ironed out.

Don't take it personal he does that quite often, he lacks a lil in the people skills department...

Sent from my Touch Pro 2 using Tapatalk

[arrrghhh]

Originally Posted by anish88

I think that he means he had the same problems that I did when I gave you guys logs and vzihome gave you logs. With the whole incoming call volume always being on and having no sound what so ever, in call, ringer, media, or notifications... all not working until restart.

Arrrghhh... did you have luck with the acoustic work??

For the most part, it works great. I posted a log (which doesn't seem to be working...) on a Voice Command issue, and I think I lost all audio once but I didn't get any logs on the problem.... At least not anything that was useful.

Originally Posted by argenisaz

Wow, that was harsh, didn't see that one coming.

Sorry for not posting logs, I was out of town and I needed my phone up and running as soon as possible. I don't post frequently but I try to be helpful when I do.

Anyway, I do agree with you, the new acoustic is here to stay and I'm 100% confident that all the wrinkles will be ironed out.

Originally Posted by vzihome

Don't take it personal he does that quite often, he lacks a lil in the people skills department...

Truth hurts? Seriously guys, if you want to help reverting back to an old build and saying nothing about problems with a new build does nobody any good - especially yourself! So what if we do go full acoustic, then what? Just permanently stay on 12/21? lol. C'mon....

[vzihome]

Originally Posted by arrrghhh

Truth hurts? Seriously guys, if you want to help reverting back to an old build and saying nothing about problems with a new build does nobody any good - especially yourself! So what if we do go full acoustic, then what? Just permanently stay on 12/21? lol. C'mon....

Talk about truth hurting! Look I have posted logs and it seems like they get over looked which is discouraging to say the least. Also barking at people because you can doesn't make it ok, all your doing is discouraging people from getting involved. You never know that person could be the next ACL all they need is to be guided/pointed in the right direction. Besides its not the PPCGeeks way. Sorry I got off topic this my last post on this matter.

Sent from my Touch Pro 2 using Tapatalk

[arrrghhh]

Originally Posted by vzihome

Talk about truth hurting! Look I have posted logs and it seems like they get over looked which is discouraging to say the least. Also barking at people because you can doesn't make it ok, all your doing is discouraging people from getting involved. You never know that person could be the next ACL all they need is to be guided/pointed in the right direction. Besides its not the PPCGeeks way. Sorry I got off topic this my last post on this matter.

ACL is doing his best to analyze logs, but to be honest he's really the only one. There's no other developers working on NAND, it's only him. Cut the dude some slack.... He's not ignoring you, or anyone else for that matter. He's only one man.

Edit - We've all got to pitch in and help him out as best we can - otherwise, how is he going to know what needs to be fixed!??! C'mon guys. We're all in this together.

[[ACL]]

Originally Posted by arrrghhh

ACL is doing his best to analyze logs, but to be honest he's really the only one. There's no other developers working on NAND, it's only him. Cut the dude some slack.... He's not ignoring you, or anyone else for that matter. He's only one man.

Edit - We've all got to pitch in and help him out as best we can - otherwise, how is he going to know what needs to be fixed!??! C'mon guys. We're all in this together.

Thanks arrrghhh.. I try ...

But yea, I try to analyze all logs, but some of them dont show much. There are some crafty devils who are good at this. I'm going to give you guys some advice since the Rhod100 guys set the bar pretty damn high. Think about it, we have a language barrier with most rhod100 users, a device barrier and yet we managed to get them up and running thanks to some good logs (and some creative videos..lol) and 3 or 4 test kernels.

Good logs always make it to the project page. Why? because without them i cant fix anything. Think logically for one second. How would i fix a Rhod100 with a panel that never came with the rhod400? Logs and patience.

Lol, so keep posting and don't loose hope. If you feel I over looked something, just bother me about it again and point out what i may have missed.

case closed and lets move onto new business.

[elesbb]

Originally Posted by vzihome

Talk about truth hurting! Look I have posted logs and it seems like they get over looked which is discouraging to say the least. Also barking at people because you can doesn't make it ok, all your doing is discouraging people from getting involved. You never know that person could be the next ACL all they need is to be guided/pointed in the right direction. Besides its not the PPCGeeks way. Sorry I got off topic this my last post on this matter.

Sent from my Touch Pro 2 using Tapatalk

He's just trying to keep the thread clean, he is not taking anything personal , put yourself in ACL and arrrghhh's shoes , imagine what they are doing . Its all free . They have their own personal lives to deal with . I dont post anything in this thread unless i have something to offer . Not something to complain about . From reading this thread , it seems like EVERYONE just wants the PERFECT build right away . if you(everyone) want the perfect build go do it yourself , if not , then wait for Arrrghhh and ACL to work their magic . Posting logs helps , commenting on certain things helps , but they are only human , give them some time and im very certain , from their previous masterpieces , that they will fix all querks and bugs . Just give them time . Thanks ACL and arrrghhh !

[argenisaz]

Hi folks,

My panel has become unresponsive at times, it doesn't register any touch. It's not permanent. I've rebooted, recalibrated the screen and the condition persists.

I'm attaching logs. I have a RHOD500 running 12/21 without acoustics patch. Waiting eagerly for the next release!

Thanks in advance for your help.

[[ACL]]

Originally Posted by argenisaz

Hi folks,

My panel has become unresponsive at times, it doesn't register any touch. It's not permanent. I've rebooted, recalibrated the screen and the condition persists.

I'm attaching logs. I have a RHOD500 running 12/21 without acoustics patch. Waiting eagerly for the next release!

Thanks in advance for your help.

You have some interesting issues. Well i notice that your device is having a touch time sleeping on the last few lines but then it gets cut off. Now, when it becomes unresponsive, is it a complete lock? where you have to physically reset the device? If so, then there was a kernel panic. A panic will lock up the phone and force you to reset. However, the next step is crucial. When the phone comes back up from the reset, you have to "adb shell" into your phone. then type the following.

cat /proc/last_kmsg > /sdcard/panic.txt

This will create a panic.txt on your sdcard which you can upload to us here. Panics are usually a result of either SMD bugs or possibly something new.

Also there is a CDMA error on the logs.

"01-14 08:35:34.360 E/CDMA ( 221): Wrong network. Can not return a string." I dont think ive ever seen that. Maybe muzling has seen it since he has explored a lot of other cdma issue. Either way that will require some research.

[argenisaz]

Originally Posted by [ACL]

You have some interesting issues. Well i notice that your device is having a touch time sleeping on the last few lines but then it gets cut off. Now, when it becomes unresponsive, is it a complete lock? where you have to physically reset the device? If so, then there was a kernel panic. A panic will lock up the phone and force you to reset. However, the next step is crucial. When the phone comes back up from the reset, you have to "adb shell" into your phone. then type the following.

cat /proc/last_kmsg > /sdcard/panic.txt

This will create a panic.txt on your sdcard which you can upload to us here. Panics are usually a result of either SMD bugs or possibly something new.

Also there is a CDMA error on the logs.

"01-14 08:35:34.360 E/CDMA ( 221): Wrong network. Can not return a string." I dont think ive ever seen that. Maybe muzling has seen it since he has explored a lot of other cdma issue. Either way that will require some research.

The phone doesn't lock up. I can still navigate all menus using the keyboard. But the screen is unresponsive to touch, or it behaves oddly, for example, if I touch an icon on the homescreen to open an app it instead swipes to another homescreen or it ignores my touch.

I rebooted my phone and ran the adb command you suggested, results are attached.

I'd like to inform that I applied a task29 to my phone and started from scratch with the 12/24 build, the screen problem persists.

Thanks for your help!

[[ACL]]

Originally Posted by argenisaz

The phone doesn't lock up. I can still navigate all menus using the keyboard. But the screen is unresponsive to touch, or it behaves oddly, for example, if I touch an icon on the homescreen to open an app it instead swipes to another homescreen or it ignores my touch.

I rebooted my phone and ran the adb command you suggested, results are attached.

I'd like to inform that I applied a task29 to my phone and started from scratch with the 12/24 build, the screen problem persists.

Thanks for your help!

Try the task29. If there was a dirty install there is a chance that some stuff will be broken. Task29 will guarantee a clean delicious install.

since there is no kernel panic and we really cant tell from the logs, then best way to approach this is to see if there is a sequence that reproduces the issue. The only weird thing about your logs is that the phone cant sleep. It could be either wifi being on, data sync or anything that has a wake lock open. Anyways, keep trying dood.