Here goes:
http://db.tt/KnbcrblP = Storage FC
http://db.tt/xhTnJfxN = DPI changed to 160
These are based on 4 Mar.
Here goes:
http://db.tt/KnbcrblP = Storage FC
http://db.tt/xhTnJfxN = DPI changed to 160
These are based on 4 Mar.
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.
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.
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)
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.
Attachments
Last edited:
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.
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.
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.
I might need a bit more in that logcat
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.
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.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
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.2
Will test and let you know.
Feedback:
1. APN is working now.
2. PIE is working now, but not much use since the options available is similar to navigation bar, unless the purpose is to disable navigation bar. I installed a PIE app from Google Play and that was able to add in applications to the PIE control.
Hopefully you can work on the other two soon. FYI, there is another rom that was just realised, AOKP official, and that has the full tablet mode working, ie status bar is below.
Sent from my GT-N7105 using Tapatalk 22
Fantastic! Hopping over to download.
Update :
Looks like nothing has changed.
1. Bluetooth still can't turn on
2. Tablet mode at 160 and Nexus 7 mode at 213, status bar and notifications bar still stays at the top.
3. Under settings, display, navigation bar, advanced settings, after the "Navigation bar width" section where there is some explanation of combined width help, there's a whole lot of missing settings:
a. Combined bar width port
b. Combined bar width land
After Nav button transparency, missing settings:
a. NAVBAR HIDE OPTIONS
e. Hidden Navbar Enable
4. APN still needs to be done manually, ie it's not automatically done. I didn't try to do it manually though, but I believe if done manually, it will work since the first nightly I tried works.
Sent from my Nexus 7 using Tapatalk HD1I 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.
