[ROM]{4.2.2} Vanir 4.0 - Need help testing

[zard]

Sure,

There are about 3 dozen ways to logcat, but this is my favorite

1) Grab a logcat App
- I prefer Log Viewer in the Play store

2) On Android 4.2.X, you need to move the application to system/data
- The best way is go to Titanium Backup. Long press and hit 'Convert to system app'
- Or use any root explorer and move to system/app

*** You get style points if at this step you queue up the process you are about to log in order to minimize spam in the logger.

3) Open Log Viewer or whatever app
- Hit 'Read'
- Hit the trash button until the log is clear. (Just starting up makes thousands of lines of code)

4) Now navigate to the problem and replicate it.

5) Hit recents and stop the logger. Send it in.

Here goes:

http://db.tt/KnbcrblP = Storage FC

http://db.tt/xhTnJfxN = DPI changed to 160

These are based on 4 Mar.

 

[DHO]

Very nice. Storage logcat is beautiful.

Storage FC is 1 of 2 things. I will test one then the other.

DPI changer log was not as clean, it looks like tab was still booting up so tons of spam. I am still shifting through it but nothing is jumping out. I might need a cleaner one to narrow things down.

 

[zard]

Very nice. Storage logcat is beautiful.

Storage FC is 1 of 2 things. I will test one then the other.

DPI changer log was not as clean, it looks like tab was still booting up so tons of spam. I am still shifting through it but nothing is jumping out. I might need a cleaner one to narrow things down.

For DPI changer log, what was captured includes the changing and reboot. It was only "Stopped" after the reboot. Hope this information helps. On second thoughts, I should have done one that "stops" after the change, before the reboot. I was thinking of the outcome, which should be after a reboot.

 

[DHO]

For DPI changer log, what was captured includes the changing and reboot. It was only "Stopped" after the reboot. Hope this information helps. On second thoughts, I should have done one that "stops" after the change, before the reboot. I was thinking of the outcome, which should be after a reboot.

When you reboot it nuked the logger. Try changing, then stopping and sending. I have the reboot now

Tonight's build should fix the Storage FC issue. (If for any reason it didn;t it make be because I did not clobber the build prior)

 

[DHO]

Also does it work at other DPIs?

It's confirmed working on Grouper, so I know we are soo close. Just need to figure out the slight difference in Tilapia and will be go-to-go!

 

[zard]

Also does it work at other DPIs?

It's confirmed working on Grouper, so I know we are soo close. Just need to figure out the slight difference in Tilapia and will be go-to-go!

Congratulations! Almost done. Tried 160 and default 213 DPI, all working. Version tested is 5 & 6 March 2013.

1. Settings - Storage - FC - Resolved

2. UI Mode - NavBar and SystemBar - Resolved

3. The combined width entries are missing - Resolved

New issues:
1. When opening the built-in browser, error occurs: Connection problem. There was a network error. This seems to happen only with XDA forum. When I tried with other websites, no such error.

2. After boot up, error occurs: Unfortunately, Messenging has stopped. If I open up messenging up, no such error.

Logcat for connection problem is attached.

 

[DHO]

Congratulations! Almost done. Tried 160 and default 213 DPI, all working. Version tested is 5 & 6 March 2013.

1. Settings - Storage - FC - Resolved

2. UI Mode - NavBar and SystemBar - Resolved

3. The combined width entries are missing - Resolved

New issues:
1. When opening the built-in browser, error occurs: Connection problem. There was a network error. This seems to happen only with XDA forum. When I tried with other websites, no such error.

2. After boot up, error occurs: Unfortunately, Messaging has stopped. If I open up messaging up, no such error.

Logcat for connection problem is attached.

Alright now we are making some progress.

I will look at the logcats after work and see if I can find the culprit.

Thanks for your great testing.

 

[DHO]

I might need a bit more in that logcat I know,.. it's a fine balance.

It sounds proprietary related. I did not have time today, but I plan on refactoring them with another repo to ensure I got the best Tegra props.

Also would you find the full MMS app better than the basic one? I can include either, but usually the basic is included with GSM tabs.

 

[zard]

I might need a bit more in that logcat I know,.. it's a fine balance.

It sounds proprietary related. I did not have time today, but I plan on refactoring them with another repo to ensure I got the best Tegra props.

Also would you find the full MMS app better than the basic one? I can include either, but usually the basic is included with GSM tabs.

On the telipia, I don't use the Messenging app at all. The issue is really the error message, which needs to be addressed. Same goes to the network connection error.

 

[DHO]

On the telipia, I don't use the Messenging app at all. The issue is really the error message, which needs to be addressed. Same goes to the network connection error.

I okay, today I reconciled all the proprietary drivers with Codefire. Also been submitting a ton of small bug fixes across the board.

IF any problems with data I could use a longer changelog, I think the error was not fully captured on the last one. If the app is running, you may need to kill it, start logging then open it again.