Develop Bugs

Arnova 10 G2 (RK2918 based tablet)

Hello all
I just bought Archos Arnova 10 G2 few days ago and till now I would say I kinda satisfied with the device. But since we are here on XDA, enjoyment from this device could be even better
I tried to put a custom rom (here) to my device but unfortunatelly I'm not a lucky guy and device didn't boot at all. So I ask uncle Google for help and found this great tool that allowed me to root the tablet easily and put some extra apps into /system/app. I then encounter endless problems with Maket to even get it to work and found a way here (download the attached .zip, copy it to the device and install .apk's in order posted, reboot the device and you have Market and Google apps up and running ). And this is where my problems started to appear...
Market in that .zip is veeery old (v1.82) so I put there new version (3.3.11) and it seems to work well too but just until I try to install some app from Market => FC.
I read something about permisions set wrong or some another component/app is not installed or incompatible with Market 3+ (btw, only version working is 1.82 and 3.3.11 -with problems. Another version give my FC during loading).
So, now to the point I managed to get some feedback from LogCat when Market FC:
Code:
D/Finsky ( 1912): [1] DownloadRestarterRule.run: Recovering from Market exit when restoring / downloading assets.
D/Finsky ( 1912): [1] SanityChecker.run: # LocalAssets corrected : 1
D/Finsky ( 1912): Sanity check took : 24 ms
D/Finsky ( 1912): [1] DownloadTickleReceiver.onReceive: Received tickle.
W/Finsky ( 1912): [1] DownloadTickleReceiver.generatePackageProperties: Received refund period time end string : null
D/Finsky ( 1912): [1] DownloadTickleReceiver.parseObb: Not generating OBB (patch false)
D/Finsky ( 1912): [1] DownloadTickleReceiver.parseObb: Not generating OBB (patch true)
D/Finsky ( 1912): [1] Installer.downloadAndInstallAsset: Downloading and installing Google Docs.
D/Finsky ( 1912): [1] DownloadImpl.setState: com.google.android.apps.docs from null to UNQUEUED.
D/dalvikvm( 1912): GC_CONCURRENT freed 404K, 52% free 2884K/5895K, external 793K/1051K, paused 4ms+3ms
D/Finsky ( 1912): [1] DownloadQueueImpl.add: Download com.google.android.apps.docs added to DownloadQueue
D/Finsky ( 1912): [1] DownloadImpl.setState: com.google.android.apps.docs from UNQUEUED to QUEUED.
I/installd( 60): free_cache(2618907) avail 195815424
D/Finsky ( 1912): [23] DownloadRecords.initializeAndPrune: Pruned 0 old downloads from the cursor.
D/Finsky ( 1912): [1] DownloadQueueImpl.startDownload: Download com.google.android.apps.docs starting
D/Finsky ( 1912): [1] DownloadRestarter.onPostExecute: Recovering restore of com.stumbleupon.android.app
D/Finsky ( 1912): [1] DownloadRestarter.handleObbResumingOrRestart: No OBB's associated to this asset.
D/Finsky ( 1912): [1] DownloadRestarter.restartAssetDownload: Restarting asset download : com.stumbleupon.android.app
E/DatabaseUtils( 269): Writing exception to parcel
E/DatabaseUtils( 269): java.lang.SecurityException: Invalid value for is_public_api: null
E/DatabaseUtils( 269): at com.android.providers.downloads.DownloadProvider.enforceAllowedValues(DownloadProvider.java:686)
E/DatabaseUtils( 269): at com.android.providers.downloads.DownloadProvider.checkInsertPermissions(DownloadProvider.java:624)
E/DatabaseUtils( 269): at com.android.providers.downloads.DownloadProvider.insert(DownloadProvider.java:442)
E/DatabaseUtils( 269): at android.content.ContentProvider$Transport.insert(ContentProvider.java:198)
E/DatabaseUtils( 269): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:146)
E/DatabaseUtils( 269): at android.os.Binder.execTransact(Binder.java:320)
E/DatabaseUtils( 269): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 1912): threadid=21: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime( 1912): FATAL EXCEPTION: download-manager-thread
E/AndroidRuntime( 1912): java.lang.SecurityException: Invalid value for is_public_api: null
E/AndroidRuntime( 1912): at android.os.Parcel.readException(Parcel.java:1322)
E/AndroidRuntime( 1912): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:160)
E/AndroidRuntime( 1912): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)
E/AndroidRuntime( 1912): at android.content.ContentProviderProxy.insert(ContentProviderNative.java:408)
E/AndroidRuntime( 1912): at android.content.ContentResolver.insert(ContentResolver.java:606)
E/AndroidRuntime( 1912): at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:44)
E/AndroidRuntime( 1912): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 1912): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 1912): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1912): at android.os.HandlerThread.run(HandlerThread.java:60)
D/dalvikvm( 1912): GC_CONCURRENT freed 408K, 51% free 3000K/6023K, external 793K/1051K, paused 4ms+3ms
D/dalvikvm( 79): GC_CONCURRENT freed 1041K, 49% free 5163K/10055K, external 1908K/1998K, paused 3ms+12ms
D/dalvikvm( 1912): GC_CONCURRENT freed 540K, 52% free 2994K/6151K, external 793K/1051K, paused 3ms+9ms
D/Finsky ( 1912): [1] Installer.downloadAndInstallAsset: Downloading and installing StumbleUpon.
D/Finsky ( 1912): [1] DownloadImpl.setState: com.stumbleupon.android.app from null to UNQUEUED.
D/Finsky ( 1912): [1] DownloadQueueImpl.add: Download com.stumbleupon.android.app added to DownloadQueue
D/Finsky ( 1912): [1] DownloadImpl.setState: com.stumbleupon.android.app from UNQUEUED to QUEUED.
D/dalvikvm( 269): GC_EXPLICIT freed 58K, 53% free 2654K/5575K, external 793K/1051K, paused 93ms
I/Process ( 1912): Sending signal. PID: 1912 SIG: 9
W/InputManagerService( 79): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 79): Process com.android.vending (pid 1912) has died.
Can somebody advice me in which direction should I look to fix these errors?
Or another thing, /system is not RW on this device, so every change I do I have to flash whole ROM again :/
I tried these command in Terminal Emulator but without luck:
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
Thanks anyone for kick
Regards
Adam

Hi There
I had faced a similar issue this morning. My advise is to install this custom rom and utility 'arctools' to install the google app pack. I did this morning and it worked like a dream.
The link is here
Good luck

Thank for the advice but unfortunatelly I tried put this custom rom to my device for the few times and it just didn't boot (maybe I have some new HW revision?).
But anyway, some guy in the original spanish forum posted updated ROM on page 7 and its working well on my device, only thing missing in RW access on /system

p1ceus said:
I tried to put a custom rom (here) to my device but unfortunatelly I'm not a lucky guy and device didn't boot at all. So I ask uncle Google for help and found this great tool that allowed me to root the tablet easily and put some extra apps into /system/app. I then encounter endless problems with Maket to even get it to work and found a way here (download the attached .zip, copy it to the device and install .apk's in order posted, reboot the device and you have Market and Google apps up and running ). And this is where my problems started to appear...
Click to expand...
Click to collapse
Could you explain what you did with that tool to gain root? Im the thread for the tool it says for step to that I need to "copy the image file into this folder,and rename to wendal.img" What image file do I copy?
I'm not overly concerned about the Market, and I do not want the custom rom that is at arctablet.com because it screws up your storage space among other issues and my tablet work really well right now I just want root. If anyone knows any other ways just to gain root and nothing else it would be greatly appreciated.

Hi,
just DL the official ROM from Arnova, rename update.img to wendal.img and thats it. Then run the Runme.bat with option 1 first and then with option 2. When done, copy wendal_new.img to the root of Arnova internal SD and rename it to update.img before disconnection the USB. After the flash, you should have root (but its just a partial since you cannot write to system parititon :/)

good tablet

p1ceus said:
Hi,
just DL the official ROM from Arnova, rename update.img to wendal.img and thats it. Then run the Runme.bat with option 1 first and then with option 2. When done, copy wendal_new.img to the root of Arnova internal SD and rename it to update.img before disconnection the USB. After the flash, you should have root (but its just a partial since you cannot write to system parititon :/)
Click to expand...
Click to collapse
Any idea if this procedure leaves one able to
1) Use marketenabler to access amazon usa &
2) get a root prompt via terminal ??

sdunne said:
Any idea if this procedure leaves one able to
1) Use marketenabler to access amazon usa &
2) get a root prompt via terminal ??
Click to expand...
Click to collapse
I was able to use the Amazon Appstore if that's what you're talking about. I also have Root Explorer, Titanium Backup, and Rom Toolbox running and get the SU prompt but haven't tried from a Terminal.
Sent from my PC36100 using xda premium

Well I have the R29xxImageTools v2.1, the Rockchip_Batch tools v1.4 and the Setup_google_app.rar file.
I've exploded the original update.img, overlaid system with the 4 subdirs from within the google rar and repacked the image, renamed the wendal_new.img to update.img and reflashed it.
Tablet just sits at arnova splash screen after a yellow recovery message. (this is the same message whether the flash ultimately works or not)
If I don't hack around with the exploded system image, other than what the lua script does itself then the tablet reflashes successfully and comes up, albeit with a non functioning marketplace.
Any idea what I'm doing wrong ??

Hi, try different gapps. It happend to me also, then I DL different zip with google apps and it was working.

try this rom with arctool v0.57 http://www.arctablet.com/blog/forum/arnova-10-g2/arnova-10-g2-improved-custom-firmware-update/

Anybody know how many mAmps the battery is on the Arnova 10 G2? I'm trying to better calibrate Battery Left Pro widget.

finless bob version 1.3
here is version 1.3 by finless bob
http://dl.dropbox.com/u/17806868/arnova10g2_v1_3_market.zip
how to install can be found here
http://www.freaktab.com/showthread....stom-ROM-by-Finless-Version-1-3&p=428#post428

finless bob version 1.3
please delete

another rom arnova 10 g2
http://www.arctablet.com/blog/archos...d-app-storage/
use arctools 0.57 to install google apps
http://www.multiupload.co.uk/EA51XONM9S link for arctools 0.57

I wonder how we can get finless to come over to xda?

laserman123 said:
I wonder how we can get finless to come over to xda?
Click to expand...
Click to collapse
Finless wants to stick to his site, since he supports several different machines, but is okay with us redirecting those looking for his ROMs there.
His current ROM is 1.4, includes the tools for flashing it and the marketplace and all gapps, and is located here. It is currently my daily on the tablet.

I am actually a good member here on XDA. So I am here.
Feel free to ask quetions
Bob

nice to see you on here finlessbob, nice rom you have made i am using it myself.
I also have to add it actually makes a base tablet run really great, plus the arnova hase some good connection capabilities that more expensive tablets lack.
Just need an arnova 10g2 section in development now to make things perfect

finlessbob said:
I am actually a good member here on XDA. So I am here.
Feel free to ask quetions
Bob
Click to expand...
Click to collapse
Hello bob. I've just bought a arnova preloaded with your rom however I'm unsure of the version of atm I'm without a computer.
Basically I've installed magic locker on the device but now everytime I boot I get FC on magic locker and cannot get past the screen.
I've tried to factory reset but it sends me into recovery and I cannot select any options.
I just wanted to know if I could fix this without a computer?
Join me on dropbox http://db.tt/aijaD3Wr
Follow me on Twitter _H88RRY_

[Guide] How To Logcat

I think this one is definitely needed for this forum as i am seeing more and more users ask how to logcat. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.

Great job brother!!You are in the right path for RC :beer::thumbup:
Sent from my Galaxy Nexus using xda app-developers app

keep going on my friend...:good:

Khizar said:
I think this one is definitely needed for this forum as i am seeing more and more users ask how to logcat. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.
Click to expand...
Click to collapse
I'm happy very happy ... I have little exp with log cat this is my guide ....
Very good another user of Ak team near RC
Sent from my Galaxy Nexus using xda app-developers app

One doubt, I've downloaded catlog and make it run but I don't know where the txt files are stored or what can I do to recover them.
Also the problem I'm experiencing is a random reboot so even if I have catlog running when the reboot occurs, will I be able to recover the log or it will be lost?
Sorry for the noob question but I'm pretty lost here...

binlalo said:
One doubt, I've downloaded catlog and make it run but I don't know where the txt files are stored or what can I do to recover them.
Also the problem I'm experiencing is a random reboot so even if I have catlog running when the reboot occurs, will I be able to recover the log or it will be lost?
Sorry for the noob question but I'm pretty lost here...
Click to expand...
Click to collapse
catlog should have its own folder in data/media where it saves the txt files...

[Tutorial] How To Logcat

Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: CatLog or aLogcat
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator:
Open your terminal app;
Type:
Code:
su
logcat > /sdcard/logcat.txt
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html

Nice guide.

gonna bookmark this Thanks!

[Q&A] [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)

[Q&A] [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Q&A for [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

alarm clock
Recently discussed the problem that the included headphones alarm clock rang only from external speakers. Now it rings only from the headphones. But it would be optimal to it when headphones are connected rang simultaneously and external speakers and headphone out. So it is correct and it is so sold on the official firmware.
Sorry for my bad English.

Del
---------- Post added at 03:30 AM ---------- Previous post was at 03:24 AM ----------
Hi, will snapshot m12 for LTE?

Do you just dirty flash the nightlife? I tried going the update route but it doesn't work.

Hi all!
First of all thank you for the Roma and the whole tutorial is perfect on my side on my "tab pro lte"
I would like to know how to overclock the processor above its Standard power?
sorry for the mistakes, I'm French and I use google translation ... oO
thank you!

No mobile data
Thanks to the dev for his continuous efforts on this rom, keep up the good work. However, i noticed that mobile data doesn't work for 2g networks. I've tried using the "preferred network type" and even changing the sim but it still won't work. When i get into 3g or LTE zonse the mobile data begins to work. Please could you suggest a fix. I'm currently limited to 2g so it would be a big help. Thanks

Any hints on building CM12 for this device ? I'm willing to do it if there is any documentation help.

Firmware crude

CM-12 test
Deleted

DensonX said:
Sorry if this is off-topic, but I have seen a lot of people requesting CyanogenMod 12 for this device. I managed to build CM-12 for the mondrianlte, however it does not flash on my device. I get an error saying E: error executing binary in zip. I suspect this may be due to the fact that I have a european Tab Pro, so if anyone with a US Tab Pro LTE wants to try to install it here's a file. https://drive.google.com/file/d/0Bxf2YUR9_3hDX3JUbnJYbWVfTTA/view?usp=sharing
Do NOT forget to backup before attempting to install this, as it likely will not work.
Also if anyone knows how to solve my problem with flashing this please let me know.
Click to expand...
Click to collapse
Please do not post links to other builds in my thread. Especially ones that you can't even flash because it doesn't work for you!
This only adds confusion.
I will try to release something soon. It may have a broken camera (the camera is broken on picassolte and if I can't figure it out I'll have to just leave it broken for both mondrianlte and picassolte for now) but otherwise has been working well for me on picassolte.

SM-T325, CM12 and encryption
Hello,
First Thank you crpalmer for your great work on mondrianlte. I've been using for roughly one month and did not encounter any serious issue, it is working so much better than stock Samsung ROMs ! I only got into problems when trying to encrypt the tablet (with cm-12-20150321-UNOFFICIAL-mondrianlte).
Once the process was started it rebooted very quickly and got stuck on the boot cyanogenmod screen. A forced off/on cycle was able to restore the tablet normal operation, but it had not been encrypted.
Relevant portions of the adb log seem to be :
(just after the beginning of the encrytion process)
Code:
E/Cryptfs ( 243): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
D/Cryptfs ( 243): Just asked init to shut down class main
and later when the tablet reboots :
Code:
D/Cryptfs ( 243): unmounting /data succeeded
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 243): Loading keymaster app failed
E/Cryptfs ( 243): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 243): Failed to init keymaster
--------- beginning of crash
F/libc ( 243): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 315 (vold)
F/libc ( 243): Unable to open connection to debuggerd: Connection refused
I/Vold (26973): Vold 2.1 (the revenge) firing up
D/Vold (26973): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold (26973): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs (26973): Check if PFE is activated on Boot
E/Cryptfs (26973): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs (26973): Error getting crypt footer and key
files /vendor/firmware/keymaster/keymaster.* have permission 644, user/group root, and are symlinks into /firmware/image/. In /firmware/image/, keymaste.* files have permission 440, user system, group drmrpc. Based on the QSEECOMAPI errors above, I am unable to determine whether these access rights are correct. I assume that even if they were, some incorrect SElinux configuration could cause access problems ?
Is anyone able to figure out what is happening ? Is it useful that I post a full log of the process ?

[Q] Rom Bootlooping cause of systemservice SIGABRT

Hi Guys,
I'm trying to port to Android 5.0 to a new device (BQ Aquaris E5 4G) and I can't make it fully boot. I'm always hitting this error :
Code:
pid: 634, tid: 634, name: servicemanager >>> /system/bin/servicemanager <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I can't give you ADB Logcat as logcat doesn't seams to work (adb works fine, I can browse adb shell and so on). It kept giving me this error : "logcat read failure: No such file or directory"
The only thing I've got is some tombstone files witch all look similar (please see one attached)
If you could give me an hint that would be great
I tried to change the kernel also but everytime I boot it (using fastboot boot newboot.img) I get a dark blinking screen.
Thanks and merry christmas!

Thread closed as duplicated with https://forum.xda-developers.com/android/help/rom-bootlooping-cause-systemservice-t2984083