Related
Don't know if the problem is wide spread, or just my bad luck, but everytime I try to install Google Sky Map from the Market, after downloading the app and before going into install my phone reboots.
I've gone from latest Cyan 5.0.7 to leaked froyo FRF50, then FRF72 and now FRF83.
So, to find out whether it's a problem for many people, if you've upgraded to Froyo, try to install Google Sky Map (save all work first and participate in this poll.
ps. Is there any log file I can check via adb?
Had Sky Map since I installed FRF50, no problems.
I have the same problem. It also happened when I tried to install the koi pond LW.
Is it really that big of a problem. Sure it's a little bug, but it doesn't effect the OS or the app permanently. How often do you install SkyMap?
For the record, I've never had a reboot after installing SkyMap or any other app.
anstosa said:
Is it really that big of a problem. Sure it's a little bug, but it doesn't effect the OS or the app permanently. How often do you install SkyMap?
For the record, I've never had a reboot after installing SkyMap or any other app.
Click to expand...
Click to collapse
well, thing is that I can't install SkyMap at all, only option it seems to wipe completely and reinstall Froyo.
I just hope there's some kind of way to remove something manually without complete wipe. I just need some directions, where to look and what to try.
after using logcat on the device during installation of Sky Map here's what happens:
W/dalvikvm( 79): threadid=11: thread exiting with uncaught exception (group=0x4001d7f0)
E/AndroidRuntime( 79): *** FATAL EXCEPTION IN SYSTEM PROCESS: PackageManager
E/AndroidRuntime( 79): java.lang.SecurityException: Requires android.permission.ASEC_CREATE permission
E/AndroidRuntime( 79): at android.os.Parcel.readException(Parcel.java:1247)
E/AndroidRuntime( 79): at android.os.Parcel.readException(Parcel.java:1235)
E/AndroidRuntime( 79): at com.android.internal.app.IMediaContainerService$Stub$Proxy.copyResourceToContainer(IMediaContainerService.java:164)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$SdInstallArgs.copyApk(PackageManagerService.java:5341)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$InstallParams.handleStartCopy(PackageManagerService.java:4956)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$HandlerParams.startCopy(PackageManagerService.java:4815)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$PackageHandler.doHandleMessage(PackageManagerService.java:470)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$PackageHandler.handleMessage(PackageManagerService.java:415)
E/AndroidRuntime( 79): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 79): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 79): at android.os.HandlerThread.run(HandlerThread.java:60)
Click to expand...
Click to collapse
anyone know where I can add permission ASEC_CREATE to make it work?
The problem has to do with /sdcard/.android_secure
Removing teh entire directory solves things for some people, but not for me though. Have also the same problem with androidVNC...
i dont think u need to reboot... i never did
I was able to get it installed again. I turned on USB storage and had the external drive mounted in my OS. I then installed from the market place. I am guessing that forced it to install internally, which worked fine. Up to that point, it kept rebooting my phone every time I tried to install it.
or just unmount the SD card
in Settings->SD card & phone storage, then install the app and then remount the SD card. That worked for me.
Ok. I have put up this thread because I need help with the ROM, I am making.
I posted on other threads to get my answers but all i'm getting is irrelevant information.
I need real help and on topic answers.
I am creating a ROM through Dsixda Kitchen
This is what I've tried so Far
1) After doing all mods, I try to build ROM from working folder.
2) Go to Interactive Mod, convert the update-script to updater script. Sign the ROM.
3) And try to flash it through CWM after wiping data and cache.
4) But i get Error, Status 7. Mount expects 4 args got 3.
I tried getting emmc-update binary and renaming it to update-binary and replace it with Meta-inf\com\google\android\update-binary.
After trying to flash again it gets through cwm but stays stuck at the splash screen.
I tried something else.
1) Don't convert the updater-script to update script at the start.
2) Do mods, and build rom
3) Flash with CWM. No errors.
4) Stuck at splash screen.
Can someone please help me? What am i doing wrong. I know how to mod system, and the apks but no knowledge about Meta-INF. So, i'm a total noob at updater script, update-binary and so on.
I tried something again. Without changing base rom alot. I just changed boot animation. And I get Error Status 7 in CWM.
Please Help. Quick.
Use the update script from some other rom!!
Don't be a noob. Be a newbie..!!
Details here.
Try ketut's script.
side_effect said:
Try ketut's script.
Click to expand...
Click to collapse
I read that in one of Prawesome's threads too. But I can't seem to find his script. Could you please direct me to that script. Its really urgent.
masterex567 said:
I read that in one of Prawesome's threads too. But I can't seem to find his script. Could you please direct me to that script. Its really urgent.
Click to expand...
Click to collapse
BlackHawk rom by ketut.Updater script given in 3rd or 4th post.
Prawesome said:
BlackHawk rom by ketut.Updater script given in 3rd or 4th post.
Click to expand...
Click to collapse
Thanks.
I used it succesfully, but now I have a new problem. I flashed it wiping everything but now it's stuck at the Android Logo Screen.
HERE IS LOGCAT: http://pastebin.com/S94vZX3G
I guess this is the main problem:
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.splitThemePackageLjava/lang/String;Ljava/lang/String;[Ljava/lang/StringI
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.detachThemePathLjava/lang/String;I)Z
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.attachThemePathLjava/lang/StringI
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageCount)I
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageNameI)Ljava/lang/String;
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageIdI)I
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.addRedirectionsNativeI)V
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.clearRedirectionsNative)V
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.generateStyleRedirectionsIII)Z
E/JNIHelp ( 5625): RegisterNatives failed for 'android/content/res/AssetManager'
E/AndroidRuntime( 5625): Unable to register all android natives
I/ServiceManager( 108): service 'media.player' died
I/ServiceManager( 108): service 'media.audio_policy' died
I/ServiceManager( 108): service 'media.audio_flinger' died
I/ServiceManager( 108): service 'media.camera' died
Help me outt pleaase.
masterex567 said:
Thanks.
I used it succesfully, but now I have a new problem. I flashed it wiping everything but now it's stuck at the Android Logo Screen.
HERE IS LOGCAT: http://pastebin.com/S94vZX3G
I guess this is the main problem:
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.splitThemePackageLjava/lang/String;Ljava/lang/String;[Ljava/lang/StringI
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.detachThemePathLjava/lang/String;I)Z
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.attachThemePathLjava/lang/StringI
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageCount)I
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageNameI)Ljava/lang/String;
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageIdI)I
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.addRedirectionsNativeI)V
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.clearRedirectionsNative)V
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.generateStyleRedirectionsIII)Z
E/JNIHelp ( 5625): RegisterNatives failed for 'android/content/res/AssetManager'
E/AndroidRuntime( 5625): Unable to register all android natives
I/ServiceManager( 108): service 'media.player' died
I/ServiceManager( 108): service 'media.audio_policy' died
I/ServiceManager( 108): service 'media.audio_flinger' died
I/ServiceManager( 108): service 'media.camera' died
Help me outt pleaase.
Click to expand...
Click to collapse
What all things did you edit?
Prawesome said:
What all things did you edit?
Click to expand...
Click to collapse
I didn't complete it thoroughly. I wanted to test it when I was halfway done. Anyways:
EDIT: Simplified.
1) Changed Kernel
2) Modded Framework-res.apk and SystemUI.apk
2) Changed Boot Animation
3) Updated Apps
4) Added Tweaks
5) Modified Some Apps
7) Changed System Sounds
11) Added Extra Apps.
14) Tweaked init.d
15) Build.prop tweaked
16) Modded Lockscreen
I'm sure that's it if i haven't forgotten something.
Hi there.... yeah, Im a newb too in this business, but the only one thing that I know, that the DEVS gett pissed off when we report bugs without LOGCATs
We dont understand it but they do SO LETs hear them and do it like we should do it.
Every time when you get into the thread and post something like "aaaaaa, the power button doesent work, or Play Store wont open...", this is just a cup of crapy words for the devs (correct me if Im wrong).
Of course theres a ADB version for doing logs, but I think for the START, this one is just fine.
Click to expand...
Click to collapse
What is logcat?
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you'll find out what apps are doing in the background without you noticing.
Advantages of Logcat
Debugging
Debug your apps. Find error stacktraces. See what your phone is saying about you behind your back. It's all there in the system log, aka logcat!
Click to expand...
Click to collapse
DOWNLOAD APP
I was googleing around and I found the best app for doing it for us newbs.
Download the FREE app called CATLOG.
Click to expand...
Click to collapse
HOW TO USE IT
After you installed it, RUN it and click the options button, there youll get a record options. Click on the record button and let it run in the background. If you had problems with Play Store, just run the PS again and when the ERROR comes, the CATLOG recorder is recording. After you did that, just go back to the app, hit the options key and press STOP RECORDING. There you GO, you have a .txt catlog of your problem.
This is just a example with the PLAY STORE fc...
Use some file manager or something like that so you can go into your sdcard / catlogs / and there should be your TXT saved log. Now just select it, press on share and put it on the FORUM or the DEVs mail. It depends on each developer. (Correct me again if Im wrong.)
Click to expand...
Click to collapse
Hope it helps out!
DO IT PEOPLE !
Heres is the more advanced but not so hard way to LOGCAT!
All credits goes to paxChristos who made this awesome tutorial HOW TO LOGCAT!
Original post: http://forum.xda-developers.com/showthread.php?t=1726238
paxChristos said:
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!)
Click to expand...
Click to collapse
Adding some LogCats for CM10 nightly
Powerbutton
http://forum.xda-developers.com/showpost.php?p=33593548&postcount=1130
no sound - poor in/out sound on CALLs
http://forum.xda-developers.com/showpost.php?p=33630013&postcount=1395
blinking screen on "screen off"
http://forum.xda-developers.com/showpost.php?p=33629455&postcount=1391
Hope it helps!
Good thread.
My favourite app for logs on the go is Lumberjack.
For logcatting at the PC I think "adb logcat" via cmd / terminal is better than an app (see torq1337's second post).
What's important: A normal logcat can be useless in some cases.
For audio, calls and anything else radio related you should add a radio logcat as well. (adb logcat -b radio).
If you got a bsod, kernel panic, or sth else that results in a bsod or phone restarting than you should post the last_kmsg.
Get it with Lumberjack or manually in the Terminal by typing "su" and "cat /proc/last_kmsg > /sdcard/last_kmsg.txt"
Dont forget to logcat
I updated my previous post now.
I am posting again to push this thread as I personally belive that most people are unable to do so because that some people out there in our nation don't have maps and that I belive that our education people who are flashing custom ROMs should know how to give developers some valid feedback - and you can learn how to logcat in 5 minutes.
tonyp said:
I updated my previous post now.
I am posting again to push this thread as I personally belive that most people are unable to do so because that some people out there in our nation don't have maps and that I belive that our education people who are flashing custom ROMs should know how to give developers some valid feedback - and you can learn how to logcat in 5 minutes.
Click to expand...
Click to collapse
Im gonna cry xDxDxDxD
Sent from my LG-P990 using xda app-developers app
Hi, maybe you would like to include my tool as well, AIOlog, as it not only logs logcat(with the -b radio for radio issues as well), but dmesg, kmsg and last_kmsg as well
tonyp said:
If you got a bsod, kernel panic, or sth else that results in a bsod or phone restarting than you should post the last_kmsg.
Get it with Lumberjack or manually in the Terminal by typing "su" and "cat /proc/last_kmsg > /sdcard/last_kmsg.txt"
Click to expand...
Click to collapse
What /proc/last_kmsg? (It doesn't appear to exist, on my phone at least.)
withoutwings said:
What /proc/last_kmsg? (It doesn't appear to exist, on my phone at least.)
Click to expand...
Click to collapse
It would be removed in a restart but still, you can retrieve the /proc/kmsg instead(better than none, I suppose, just more work for the devs )
wcypierre said:
It would be removed in a restart but still, you can retrieve the /proc/kmsg instead(better than none, I suppose, just more work for the devs )
Click to expand...
Click to collapse
No, /proc/kmesg is reset upon a restart. The whole point of last_kmesg is in the case of a crash, it is there upon the next boot so you can find out what happened. But on CM10 it doesn't appear to exist. I read somewhere this could mean the RAM Console isn't set up properly?
Hi,
I've been using cyanogenmod in my p880 for a while now and it worked pretty well until last weekend when it started loosing radio (gsm) signal.
After a while I noticed that when I was home, connected to wifi, it didn't occur.
Testing a little bit I found out that the problem was in the 3g. If I set the phone to use only 2g it works, but when I switch to 3g it looses the radio signal after a minute and does not work again until reboot.
The phone gets hot and the battery consumption increases a lot. In the battery status it shows that the "Phone" app's cpu time in "real time", like 100% usage, even with no calls at all..
I'm currently using nightly builds of CM 11, but I flashed the stable CM10 (with factory reset, data wipe) and the problem persisted. Then I flashed the latest nightly again, after another reset/wipe.
To use logcat I turned on the phone using only 2g, started logcat and when switched to 3g. The complete log can be found here:
https://drive.google.com/file/d/0B29xKdkT5wYzZmhleFZlcUhYc28/edit?usp=sharing
It was the first time I saw a logcat file, so I'm not sure, but I found some relevant things:
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
05-19 17:34:28.273 E/MobileDataStateTracker( 531): default: unknown network type: 0
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.usercfg.default not found in system properties. Using defaults
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.delack.default not found in system properties. Using defaults
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=radioTurnedOff
I hope someone can help me so I can use 3g again...
Thanks
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
So I am not alone
hsafenix said:
Hi,
I've been using cyanogenmod in my p880 for a while now and it worked pretty well until last weekend when it started loosing radio (gsm) signal.
After a while I noticed that when I was home, connected to wifi, it didn't occur.
Testing a little bit I found out that the problem was in the 3g. If I set the phone to use only 2g it works, but when I switch to 3g it looses the radio signal after a minute and does not work again until reboot.
The phone gets hot and the battery consumption increases a lot. In the battery status it shows that the "Phone" app's cpu time in "real time", like 100% usage, even with no calls at all..
I'm currently using nightly builds of CM 11, but I flashed the stable CM10 (with factory reset, data wipe) and the problem persisted. Then I flashed the latest nightly again, after another reset/wipe.
To use logcat I turned on the phone using only 2g, started logcat and when switched to 3g. The complete log can be found here:
https://drive.google.com/file/d/0B29xKdkT5wYzZmhleFZlcUhYc28/edit?usp=sharing
It was the first time I saw a logcat file, so I'm not sure, but I found some relevant things:
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
05-19 17:34:28.273 E/MobileDataStateTracker( 531): default: unknown network type: 0
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.usercfg.default not found in system properties. Using defaults
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.delack.default not found in system properties. Using defaults
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=radioTurnedOff
I hope someone can help me so I can use 3g again...
Thanks
Click to expand...
Click to collapse
+1 here
I believe that it all started around 0427 Nightly, not sure, though.
I thought of switching to 2g network only yesterday after reading an old post in CM forums.
Did not have time to pull a logcat, yet, thanks for sharing! Hope somebody will figure out what the problem can be...
Rudjgaard said:
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
Click to expand...
Click to collapse
My settings are as per wind IT specifications, but I noticed that in CM settings there is much more than specified by Wind, such as apn protocol, apn roaming protocol and bearer, which values are unknown to me. Will investigate on those values.
Tried also with official CM11 stock kernel, with no success.
No, I did not try with no apps installed, I will keep this test as the very last resort. I did not install new apps since when the problem started.
Inviato dal mio GT-P3110 utilizzando Tapatalk
Rudjgaard said:
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
Click to expand...
Click to collapse
I checked the apn settings and they are ok..
It happened with a fresh install as well, when I fleshed CM10.
I didn't try another kernel yet, but Ottonet did and it did not solve the problem
SignalStrength: Hotfix TD-SCDMA
There could be some interesting news for those like me who are affected by network losses when in 3G.
One of the commits that will be compiled in tomorrow nightly amends misbehaviours in Android/telephony/SignalStrength.java
This is "Take 2".
https://github.com/CyanogenMod/andr...mmit/94186f84815c8f179ebee6b1d07b086fd06af489
The first attempt was made (so far as I was able to reconstruct) on April 28th, see here
https://gitorious.org/cyandreamproj...mmit/cbd9cf1fa383ea588a5a445306534c01f8aa1ca8
I believe I've had 3g issues since the end of april.
Now, I'm not android developer at all, and I would not like to arise too much xpectations or to get overexcited about something that has nothing to do with network losses when in 3g, so I would really appreciate if somebody more skilled than me would provide some comment/explanations.
[EDIT] it turned out that it was *today's nightly*, so, if there is some improvement, it can be enjoyed right away.
Downloading...
[EDIT 05232014] No joy. Whataver it did that fix, it did not solve the network loss issue.
Ottonet said:
There could be some interesting news for those like me who are affected by network losses when in 3G.
One of the commits that will be compiled in tomorrow nightly amends misbehaviours in Android/telephony/SignalStrength.java
This is "Take 2".
https://github.com/CyanogenMod/andr...mmit/94186f84815c8f179ebee6b1d07b086fd06af489
The first attempt was made (so far as I was able to reconstruct) on April 28th, see here
https://gitorious.org/cyandreamproj...mmit/cbd9cf1fa383ea588a5a445306534c01f8aa1ca8
I believe I've had 3g issues since the end of april.
Now, I'm not android developer at all, and I would not like to arise too much xpectations or to get overexcited about something that has nothing to do with network losses when in 3g, so I would really appreciate if somebody more skilled than me would provide some comment/explanations.
[EDIT] it turned out that it was *today's nightly*, so, if there is some improvement, it can be enjoyed right away.
Downloading...
[EDIT 05232014] No joy. Whataver it did that fix, it did not solve the network loss issue.
Click to expand...
Click to collapse
Just confirming, I also installed the last nightly (05-24) and the problem persists.
Does anyone think it could be a hardware problem?
hsafenix said:
Does anyone think it could be a hardware problem?
Click to expand...
Click to collapse
Hi..the problem still persists (I'm on Wind). I've always used Vanir, now I switched to official Cyanogen Nightly...still nothing happens
Hi. I had cellular network problems (no signal) in omni ROM and cm official too. Anyone tryed changing base band? I have v20a EUR ... Anyone tryed different?
Inviato dal mio LG-P880 utilizzando Tapatalk
I'm posting some modem.log , hoping it's not against forum rules (can remove if it is)
06-12 15:28:24.105 D/GsmDCT ( 896): overall state is CONNECTED
06-12 15:28:24.105 D/GsmDCT ( 896): startDataStallAlarm: tag=61578 delay=60s
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 0
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): rild: wakelock acquired
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): [UNSL]< _LGE_RESTART_RILD {AT Command Timeout}
06-12 15:30:00.745 D/use-Rlog/RLOG-AT( 151): dlc[12] atchannel: at_send_command_full() end; err:-4
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): [1666]< DATA_CALL_LIST fails by E_REQ_TIMEOUT
06-12 15:30:00.745 D/use-Rlog/RLOG-RIL( 151): dlc[12] lge-ril: requestInterface(DATA_CALL_LIST) invoking *requestFunction(req:57, data: 0x00000000, len:0)...DONE
06-12 15:30:00.745 D/use-Rlog/RLOG-RIL( 151): dlc[12]: lge-ril - requestInterface: Exiting DLC handler, thread - 1074013352. s_dlc_handler_create_tracker - 0x301ff
06-12 15:30:00.755 D/RILJ ( 896): *********RILJ: LgeRestartRild Start
06-12 15:30:00.755 D/RILJ ( 896): ### Show RIL Recovery popup ###
06-12 15:30:00.825 E/RILJ ( 896): Uncaught exception read length=52Exception:java.lang.NullPointerException
06-12 15:30:00.825 I/RILJ ( 896): Disconnected from 'rild' socket
06-12 15:30:00.825 D/PHONE ( 896): [ServiceState] setNullState=1
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] Poll ServiceState done: oldSS=[0 0 home I WIND I WIND 22288 UMTS UMTS CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 home null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=1 mNewMaxDataCalls=1 oldReasonDataDenied=-1 mNewReasonDataDenied=-1
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] RAT switched UMTS -> Unknown at cell -1
06-12 15:30:00.825 D/PHONE ( 896): [ServiceState] setNullState=1
06-12 15:30:00.825 D/PhoneProxy( 896): [PhoneProxy] updatePhoneObject: radioTechnology=0
06-12 15:30:00.825 E/use-Rlog/RLOG-RILC( 151): error on reading command socket errno:104
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] Iwlan feature available = false
06-12 15:30:00.825 D/RilRequest( 896): [5314]< DATA_CALL_LIST error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=null
06-12 15:30:00.835 I/use-Rlog/RLOG-RILC( 151): libril: new connection
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 1
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): [UNSL]< UNSOL_RIL_CONNECTED {7}
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 1
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED {RADIO_SIM_READY}
06-12 15:30:00.835 I/use-Rlog/RLOG-RILC( 151): RIL Daemon version: android lge-ril 1.0
06-12 15:30:00.835 I/RILJ ( 896): Connected to 'rild' socket
06-12 15:30:00.865 D/GsmSST ( 896): [GsmSST] updateSpnDisplay: radio is on but out of service, set plmn='Nessun servizio.'
06-12 15:30:00.865 D/RILJ ( 896): [UNSL]< UNSOL_RIL_CONNECTED {7}
06-12 15:30:00.865 D/RILJ ( 896): [0213]> RADIO_POWER off
06-12 15:30:00.865 D/GsmSST ( 896): [GsmSST] updateSpnDisplay: changed sending intent rule=2 showPlmn='true' plmn='Nessun servizio.' showSpn='false' spn=''
06-12 15:30:00.885 D/RILJ ( 896): [0214]> REQUEST_SET_PREFERRED_NETWORK_TYPE : 0
06-12 15:30:00.885 D/use-Rlog/RLOG-RILC( 151): [1363036565]> RADIO_POWER (0)
06-12 15:30:00.885 D/use-Rlog/RLOG-RILC( 151): [1363036565]< RADIO_POWER fails by E_RAIDO_NOT_AVAILABLE
Inviato dal mio LG-P880 utilizzando Tapatalk
I have additionally extreme battery consumption.
I have this problem too.
With Resurrection Remix (CM 11 based) and Wind IT....
complete logs
Happened today, gathered all the logs i could. Kernel dmesg, modem log And main log.
All with official CM11 from 17/06. But it's the same on other cm11 based.
Time is:
<4>[14:06:18 18:49:45.571] ##@acm_read_bulk !ACM_READY
<4>[14:06:18 18:49:45.581] **************************
<4>[14:06:18 18:49:45.581] !!!!! ts_ldisc_close !!!!!
<4>[14:06:18 18:49:45.581] **************************
<4>[14:06:18 18:49:45.581] ### CP Crash : 1, USB DISCONNECT : 0 ###
I have the same problem as well, it started around 2 - 3 weeks ago, I was on beanstalk 4.4.2, a build from march, if I remember correctly. I had no issues before, but suddenly I lost signal every time on 3G. I tried several Roms with and without the RIL-Patch by Flying_Bear, but nothing helped so far. The only "workaround" is to stay on 2G. I'm starting to get tired of constantly reflashing my phone to try other Roms.
Its strange, that the same error occurred around the same time for so many people. I would like to know if it also happens on stock, or if its a special hardware-revision that fails. My phone version is SWS-Black (Swiss market, but bought in Germany).
It looks like something in the connection behavior got changed. When using earlier nightlies you could observe the phone connecting via HSPA+ (H+) everytime it was possible. But in later builds the phone only connects via HSPA+ if you actively use mobile data and changes back the connection to HSDPA (H) afterwards, thus resulting in constant changes between those network types. I believe this change was included to save battery but it really doesn't if your phone constantly loses connection and you have to reboot. Maybe this change was a global one but as you can see our phone can't handle it. Hopefully demetris can either identify that change and revert it or fix it.
@rob3110 , i understand your frustration, i'm changing ROM too. I also did try EPRJ RIL without success. Now I'm experimenting a RIL from CM 10.2. It seems no Dev is looking into it, it's a pity. I'm trying to analyze error logs but I'm no real Dev... You can post your logs if you like
Inviato dal mio LG-P880 utilizzando Tapatalk
Right now I'm trying the strange bug-fix JustChris20 posted in the EPJR-RIL-fix thread:
http://forum.xda-developers.com/showpost.php?p=53015495&postcount=105
1. install your rom of your choice.
don't modify anything, no ril, nothing...
2. shutdown your system and remove your battery. Now press the power button for 30 seconds. Wait further one minute. Now insert your battery back and start handy. enjoy your network... ?
Click to expand...
Click to collapse
(But without flashing a new Rom) So far I haven't lost connection for the last hours, but it is to early to be certain. I'll have to test it for at least some days or weeks to know, if it helped permanently. Maybe it helps others as well.
Just for interest, what carriers are those on with this error, or what countries are they from? Does it only happen in Europe (I'm from Germany)? If so, what happened, did something change with the hsdpa or hsdpa+ networks? Or does this error occur all over the world?
rob3110 said:
Right now I'm trying the strange bug-fix JustChris20 posted in the EPJR-RIL-fix thread:
http://forum.xda-developers.com/showpost.php?p=53015495&postcount=105
(But without flashing a new Rom) So far I haven't lost connection for the last hours, but it is to early to be certain. I'll have to test it for at least some days or weeks to know, if it helped permanently. Maybe it helps others as well.
Just for interest, what carriers are those on with this error, or what countries are they from? Does it only happen in Europe (I'm from Germany)? If so, what happened, did something change with the hsdpa or hsdpa+ networks? Or does this error occur all over the world?
Click to expand...
Click to collapse
I am having the same troubles and I am also from Germany (carrier: simyo).
I did follow your instructions and will report if it worked or not.
Edit: today I did have another disconnect, so unfortunately this rather easy "fix" didn't work out (at least for me).
Hopefully someone finds another sollution.
rootarded said:
I am having the same troubles and I am also from Germany (carrier: simyo).
I did follow your instructions and will report if it worked or not.
Edit: today I did have another disconnect, so unfortunately this rather easy "fix" didn't work out (at least for me).
Hopefully someone finds another sollution.
Click to expand...
Click to collapse
Yeah, didn't work for me either. I still get those disconnects on 3G. I will ask my carrier (E-Plus) if there was a recent change to the 3G-network that might have brought us this error, but I don't think they will give me a useful answer...
Version for no-BN account devices in post #5
This version of the app is for fully registered devices.
5-14-22: Updated to v1.5. Uninstall any previous version to insure all variables clear.
--removed Google accounts section
--removed Network Location setting (relied on Google accounts).
Over the years a few new "Settings" apps have been cobbled together from the ruins of what B&N left on the device. Starting with the original listing by @Renate NST which revealed the scope of what was hidden on the NST/G, people have rejiggered the app in a number of ways. Each of those attempts relied on actually changing the app or the framework and had limitations as to the type of installation they would run on and things that needed to be added, deleted, disabled, etc.
The Nook Settings app is my effort to create a utility that would encompass all the good ideas and none of the less good. But as I am no Java programmer, that meant Tasker (surprise). The result is a frankenapp, using screens from the B&N Settings app (you can't delete it!) as well as completely original pages I assembled from screen images and many, many invisible overlays to hijack the Back button and the return arrow throughout the app. My goal was to eliminate anything that did not work (USB debugging in the Development section, for example), try to fix what I could (USB debugging, for example!), and add in features that just should be there, mundane things like wallpaper and keyboard changes. I also wanted to re-organize the app in a more traditional way. A few representative screenshots below.
Disclaimers
1. Transitions are sometimes a little scrappy. It all depends on what the device is doing in the background and how difficult the item is to access.
2. Rather than introduce a lot of forking with many permutations, I elected to only separate the NST from the NSTG at first run. As far as accounts go, I included everything from B&N: Shop, Social). There is error trapping, so there should be no issues.
3. My number one goal in herding all these electric sheep was to keep what happens in the Settings app within the Settings app. This proved to be impossible in a few cases (keyboard swap is one) because of the way the native Android system was handling the main window. Those cases are clearly indicated in the app menus as "Exits Settings".
4. This app cannot be totally localized. That is, if you have a different display language (say, German), the parts of the app that are actually parts of the B&N Settings app will be localized, i.e., the phrases will be changed to the language you have selected. However, the custom pages I created are just images with invisible touch overlays so.... If anyone is seriously interested in localizing the app for themselves, they should contact me and we can discuss creating a custom set of images which I will then compile into a custom app.
5. I'm sorry to say that the App Manager was one of most difficult nuts to crack. It is part of the B&N Settings app but has an activity that cannot be opened via shell commands. Somehow ADW Launcher does it, but I was never able to come up with a method. Luckily, Tasker has a generic call to the App Manager and it actually works. Still, it is sluggish on the Back arrow where it must be tested against which screen is being displayed. Just not a happy camper. Be sure not to tap the Back arrow more than once or you'll end up who knows where. Consider it a free lesson in patience
6. This app is only for Portrait orientation. Oh, you can rotate your screen, but all the touch coordinates will be off and images distorted. This is not a priority for me, but I may look at it someday. It requires a redesign and right now, I'm sorta sick of working on this :silly:
Requirements
1. This is a Tasker app and has a dependency on two library files which are part of a GApps installation. If you don't have GApps or one of my other Tasker apps already, you need to copy the two files in the zip as below:
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Set permissions for both files to rw-r--r-- and reboot. Without these files resident, the app will not install.
2. Root/SU. Right off the bat. Many, many shell commands, settings.db, accounts.db, etc. manipulations.
3. Sqlite3 (for the database manipulations), provided in the zip below. If you don't already have it, move the file to /system/bin and set the permissions to rwx r-x r-x.
4. Busybox. If you rooted with NookManager, you already have Busybox installed. A few other special packages probably include it. If you have it, you will find it in /system/xbin. If it's not there, copy the file from the zip to that location and set permissions to rwx-rwx-rwx
5. The original B&N Settings app installed
Edit: 6. I've discovered while working on a no-B&N variant that a kernal enabling multi-touch is needed for some of the "sendevent" sequences to execute. Lacking multi-touch does not mean the app will not function or that you will not be able to access some settings.
Installation
The easy part. This is not a system app, but a user app. Just install as normal. You don't have to disable or remove or change anything. If you don't like it, just uninstall.
On first run the app:
1. determines if you have an NSTG and adjusts the menus accordingly.
2. sets ADB debugging via TCP (for WiFi apps like ADB Konnect); This is the default state for rooting with NookManager. You can change to USB in Developer options.
Just to be clear, in every case in which there is a "return" arrow as part of a Settings screen, its function is identical to the Back button in the status bar (i.e., both have been hijacked).
Problems
If you have some issue and end up crashing the app or exiting unexpectedly (has not happened to me, but.....), there may still be invisible overlays present that will impair the function of your device. The easiest way to deal with these is to repeatedly press the Back button until the main Settings menu appears and then disappears. If there is still an issue, force stopping the app via the App Manager will clear all overlays. A power cycle is the last resort.
Acknowledgement
Wow, this was tough... I'm indebted to the generous folk who hang out at the Google Tasker group. I'm sure they all think I'm daft spending so much time on an Eclair device with an ancient version of Tasker, but they have nonetheless been helpful when I've been stuck.
Wow, @nmyshkin that looks like a bit of work.
On a different theme, I have an Android (Linux) executable for doing settings.
It's handy if you want to set a bunch of devices all the same (and you have root).
Settings are stored in different tables for global, system and secure.
Even worse, individual setting moved among these three categories for different versions of Android.
Even worse, they used to be stored in an SQLite database, then they moved to separate XML files.
Fortunately, if there is a setting "klaatu_barada_nikto" it is unique even though it might be in system or secure depending on Android version.
The executable takes an input file of settings.
Here is an example (just what I had at hand, I'm not saying that these settings are the right one for you (or even me)).
Code:
adb_enabled 1
airplane_mode_on 0
auto_time_zone 0
bluetooth_on 0
development_settings_enabled 1
dim_screen 0
heads_up_notification_enabled 0
immersive_mode_confirmations confirmed
install_non_market_apps 0
lockscreen.disabled 1
mock_location 1
package_verifier_enable 0
screen_auto_brightness_adj -1
screen_brightness 5
screen_brightness_mode 0
screen_off_timeout 1800000
skip_first_use_hints 1
stay_on_while_plugged_in 3
transition_animation_scale 1.0
usb_mass_storage_enabled 0
user_setup_complete 1
verifier_verify_adb_installs 0
window_animation_scale 1.0
wifi_frequency_band 0
If the setting exists, it will be set.
Notice, that you don't have to specify category (global, system, secure) since it can figure that out itself.
(No, I didn't attach the executable. I have to double check it.)
Renate NST said:
Wow, @nmyshkin that looks like a bit of work.
Click to expand...
Click to collapse
Yeah, this is another example of why humans are not allowed to know the future. If they did, they would shy away from attempting many things!
I'd be interested in the executable. From my work on this app I can imagine what it must involve to ferret out the appropriate entries. On the NST, at least, values in settings.db for some things appear to be artifacts only and don't actually seem to have any effect. It just made things more interesting...
nmyshkin said:
I'd be interested in the executable.
Click to expand...
Click to collapse
Well, here it is (in the signature).
Park "setvalues" in an executable directory (like /data or /data/local/tmp), chmod 755 it.
It takes the name of the values file as the only argument.
It's verbose in telling you what was and any changes done.
This also should run on any version of Android and any device.
Custom version for those without B&N account and/or apps
5-11-22: updated to 1.5. Uninstall any previous version to insure all variables clear.
--removed Google Accounts section
--removed Network Location setting (relied on Google Accounts)
This version is only for devices which either bypassed OOBE and then removed all B&N stuff or went through registration and then removed all B&N stuff
I've been playing around with a third (my last one, I swear) device and have finally hit upon the method for removing B&N apps without causing a constant drumbeat of protest in the system. More on that in a future post.
No B&N apps means no B&N account, whether you start with a registered device or skip OOBE, so my Nook Settings app had a lot of fluff in it for such devices. Also, the "About" stuff did not work so there was no information such as serial number, MAC address, etc.
This special version of the app addresses these issues. References to B&N stuff are removed and there is a custom "About" section which includes an editing option for those items the app could not dig up on its own (like your name, if you didn't register). See screenshot below.
Hint: if you skip OOBE, you will need to jot down the serial number, model number, and MAC address for entry into the "About" page. You can find these values on the screen where you elect to skip OOBE. Failing that, they are contained in text files in /rom/devconf
The zip below includes all the stuff from the zip in the OP with an updated custom app. Follow the installation instructions in post #1. If you are updating, you only need to uninstall the previous version and install the new one.
Great job!
The app dosen't install on my rooted NST fw ver.1.2.1 but at least I removed all unnecessary B&N apps. Thanks
kodovoimeji said:
Great job!
The app dosen't install on my rooted NST fw ver.1.2.1 but at least I removed all unnecessary B&N apps. Thanks
Click to expand...
Click to collapse
It should install and run on 1.2.1 without any problems. Did you remember to copy the two maps files? It won't install without those present. Also be sure the permissions for each file are set correctly. If not the installer may register them as MIA and refuse to run.
I'm not sure if the same level of dependency is present at installation for sqlite or busybox, but you do need both (with correct permissions) for some parts of the app to function.
Edit: I can confirm that the app installs and runs with FW 1.2.1, following the directions in the first post.
Hey, I find myself unable to put the com.google.android.maps.jar and com.google.android.maps.xml files in the required locations via ADB push due to the filesystem being readonly, and I'm not sure the safest way to remount readwrite on this device, please could you advise?
alexhorner said:
Hey, I find myself unable to put the com.google.android.maps.jar and com.google.android.maps.xml files in the required locations via ADB push due to the filesystem being readonly, and I'm not sure the safest way to remount readwrite on this device, please could you advise?
Click to expand...
Click to collapse
Did you choose one of the NookManager options with ES File Explorer? If so, you can mount /system as RW from within its Settings and just transfer the files to either your sdcard or /media (the "Nook" drive) and then move them with the file manager from there. You can even set the permissions (long-press on file and select "Properties").
Otherwise...hmm....let me see if I have that bookmarked...
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
I think that's it. Then for permissions:
Code:
adb shell chmod 644 /system/wherever/whatever.xml
(I'm not suggesting it's 644--you'll have to check that.
ES File Explorer is by far the easier method.
nmyshkin said:
Did you choose one of the NookManager options with ES File Explorer? If so, you can mount /system as RW from within its Settings and just transfer the files to either your sdcard or /media (the "Nook" drive) and then move them with the file manager from there. You can even set the permissions (long-press on file and select "Properties").
Otherwise...hmm....let me see if I have that bookmarked...
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
I think that's it. The for permissions:
Code:
adb shell chmod 644 /system/wherever/whatever.xml
(I'm not suggesting it's 644--you'll have to check that.
ES File Explorer is by far the easier method.
Click to expand...
Click to collapse
I went for the classic so no ES here! Just ReLaunchX. The mount command worked, and I can confirm 644 is the correct numeric for the required permissions. Busybox already existed from the root, and I installed sqlite3 with correct permissions, 755.
Copied those 2 google files over, set permissions, rebooted then installed the APK fine.
Sorry for being such a noob here, but how do I now run the app as superuser? Running it without just refreshes the screen (I assume that means it crashed after trying to open?)
Opening the Superuser app shows no apps in list.
alexhorner said:
I went for the classic so no ES here! Just ReLaunchX. The mount command worked, and I can confirm 644 is the correct numeric for the required permissions. Busybox already existed from the root, and I installed sqlite3 with correct permissions, 755.
Copied those 2 google files over, set permissions, rebooted then installed the APK fine.
Sorry for being such a noob here, but how do I now run the app as superuser? Running it without just refreshes the screen (I assume that means it crashed after trying to open?)
Opening the Superuser app shows no apps in list.
Click to expand...
Click to collapse
Sometimes SU is slow to respond. I'd reboot and try again.
No luck waiting or rebooting unfortunately. Superuser has no app list and the screen refresh flashes when trying to launch still
alexhorner said:
No luck waiting or rebooting unfortunately. Superuser has no app list and the screen refresh flashes when trying to launch still
Click to expand...
Click to collapse
Grr...
Ok, I've shut down my PC for the day. Let me try a clean install of the app tomorrow and refresh my memory on exactly what happens. SU can really be a pain on this device sometimes.
alexhorner said:
No luck waiting or rebooting unfortunately. Superuser has no app list and the screen refresh flashes when trying to launch still
Click to expand...
Click to collapse
So instead of reading till I get drowsy I have downloaded the zip right on the device! I uninstalled the app and checked Superuser to be sure any entries were gone. Then I extracted the app from the zip and installed it. The moment (or nearly) I tapped the app icon I got the Superuser permission request.
I'm baffled.
nmyshkin said:
So instead of reading till I get drowsy I have downloaded the zip right on the device! I uninstalled the app and checked Superuser to be sure any entries were gone. Then I extracted the app from the zip and installed it. The moment (or nearly) I tapped the app icon I got the Superuser permission request.
I'm baffled.
Click to expand...
Click to collapse
Well...
I opened ADB connect, as I knew that asked for super user too. It did, I accepted and it launched fine. I went back to ReLaunchX and decided to look at Superuser now. It won't open at all.
Okay, fine, I'll reboot the device.
Nope, still won't open.
So I decided to open ADB Connect again. Well now that's broken too! It gives me a black screen, so I decided to tap back. Nope. Okay, I'm stuck now.
After a few seconds I get "Sorry! Activity ReLaunchX (in application ReLaunchX) is not responding. [Wait] [Force Close]
I have since forced closed, uninstalled the settings app and rebooted. Superuser still broken. ADB works once and then subsequent times black screens me.
Edit: Got a logcat of superuser:
Spoiler: Logcat Superuser
Code:
D/AndroidRuntime( 1529): Shutting down VM
W/dalvikvm( 1529): threadid=3: thread exiting with uncaught exception (group=0x4001b210)
E/AndroidRuntime( 1529): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 1529): java.lang.NullPointerException
E/AndroidRuntime( 1529): at com.noshufou.android.su.PinnedHeaderListView.configureHeaderView(PinnedHeaderListView.java:153)
E/AndroidRuntime( 1529): at com.noshufou.android.su.AppListActivity$AppListAdapter.onScroll(AppListActivity.java:326)
E/AndroidRuntime( 1529): at android.widget.AbsListView.invokeOnItemScrollListener(AbsListView.java:741)
E/AndroidRuntime( 1529): at android.widget.AbsListView.handleDataChanged(AbsListView.java:3181)
E/AndroidRuntime( 1529): at android.widget.ListView.layoutChildren(ListView.java:1488)
E/AndroidRuntime( 1529): at android.widget.AbsListView.onLayout(AbsListView.java:1314)
E/AndroidRuntime( 1529): at com.noshufou.android.su.PinnedHeaderListView.onLayout(PinnedHeaderListView.java:123)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1119)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.layoutVertical(LinearLayout.java:998)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.onLayout(LinearLayout.java:918)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1119)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.layoutVertical(LinearLayout.java:998)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.onLayout(LinearLayout.java:918)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.view.ViewRoot.performTraversals(ViewRoot.java:996)
E/AndroidRuntime( 1529): at android.view.ViewRoot.handleMessage(ViewRoot.java:1633)
E/AndroidRuntime( 1529): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1529): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1529): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 1529): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1529): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1529): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 1529): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 1529): at dalvik.system.NativeStart.main(Native Method)
I/ActivityManager( 790): Removing old ANR trace file from /data/anr/traces.txt
W/ActivityManager( 790): Send CRASH intent: true
I/Process ( 790): Sending signal. PID: 1529 SIG: 3
D/EPD#ActivityManager( 790): resetRegion 4
D/NATIVE-EPD( 790): epd_reset_region: 0x10
D/EPD#ActivityManager( 790): resetRegion 5
D/NATIVE-EPD( 790): epd_reset_region: 0x20
D/EPD#ActivityManager( 790): resetRegion 6
D/NATIVE-EPD( 790): epd_reset_region: 0x40
D/EPD#ActivityManager( 790): resetRegion 7
D/NATIVE-EPD( 790): epd_reset_region: 0x80
D/DeviceManagerBroadcastReceiver( 949): action (com.bn.devicemanager.ACTION_HANDLE_CRASH)
I/dalvikvm( 1529): threadid=7: reacting to signal 3
I/dalvikvm( 1529): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 1529): Sending signal. PID: 1529 SIG: 9
I/ActivityManager( 790): Process com.noshufou.android.su (pid 1529) has died.
I/WindowManager( 790): WIN DEATH: Window{4a0ebc98 com.noshufou.android.su/com.noshufou.android.su.Su paused=false}
I/UsageStats( 790): Unexpected resume of com.gacode.relaunchx while already resumed in com.noshufou.android.su
W/InputManagerService( 790): Window already focused, ignoring focus gain of: [email protected]
V/Activity( 1225): performResume()
Most disturbing, as Jeeves would say.
Here's where my lack of depth shows. I can see there is trouble in the logcat. The word "CRASH" being a clue. But as to the rest..not so much.
I would, at this point, uninstall and reinstall SU--you can get the apk from your NookManager card.
I've got a fairly busy day but my aim is to back up one of my devices, revert it to an unrooted, registered state, root with the "classic" package and try to reproduce your situation. That's one step short of converting to UK and going through the entire process. Which I hope not to do.
nmyshkin said:
Most disturbing, as Jeeves would say.
Here's where my lack of depth shows. I can see there is trouble in the logcat. The word "CRASH" being a clue. But as to the rest..not so much.
I would, at this point, uninstall and reinstall SU--you can get the apk from your NookManager card.
I've got a fairly busy day but my aim is to back up one of my devices, revert it to an unrooted, registered state, root with the "classic" package and try to reproduce your situation. That's one step short of converting to UK and going through the entire process. Which I hope not to do.
Click to expand...
Click to collapse
The reinstall has certainly fixed Superuser, however, no luck with NookSettings still even after another reinstall. I feel reverting to UK on your device wouldn't particularly help you, however going from stock to rooted might. I am wondering at this point if that might do me any good.
It clearly shows a lack of resilience of Superuser although the instigation lies elsewhere.
There is absolutely no reason that an app should bomb doing a layout.
Personally, I've never liked su. All I need in life (before the advent of system as root) is a rooted adbd.
alexhorner said:
The reinstall has certainly fixed Superuser, however, no luck with NookSettings still even after another reinstall. I feel reverting to UK on your device wouldn't particularly help you, however going from stock to rooted might. I am wondering at this point if that might do me any good.
Click to expand...
Click to collapse
I have just found a new APK for Superuser, 3.0.7 which I have attached in both the unextracted ZIP form and the extracted APK form. Source is https://forum.xda-developers.com/t/app-superuser-2-3-6-1-now-on-the-market-2010-09-05.682828/page-49
Not sure it will be of much help, but it certainly works with ADB Konnect perfectly fine.
Still no luck with NookSettings. I decided to logcat that too, here it is:
Spoiler: NookSettings Logcat
Code:
I/ActivityManager( 790): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.home.nmyshkin.settings/net.dinglisch.android.tasker.Kid }
I/ActivityManager( 790): Start proc com.home.nmyshkin.settings for activity com.home.nmyshkin.settings/net.dinglisch.android.tasker.Kid: pid=3357 uid=10019 gids={}
E/TC ( 1023): KPICollector: 1634321461142 platform process_start {"processName":"com.home.nmyshkin.settings"}
I/dalvikvm( 3357): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38)
E/TC ( 1023): KPICollector: 1634321461231 ActivityManager background {"component":"com.gacode.relaunchx/.AllApplications"}
E/TC ( 1023): KPICollector: 1634321461238 ActivityManager foreground {"component":"com.home.nmyshkin.settings/net.dinglisch.android.tasker.Kid"}
I/dalvikvm( 3357): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=56)
D/dalvikvm( 3357): GC freed 10007 objects / 357744 bytes in 64ms
D/dalvikvm( 3357): GC freed 10130 objects / 380968 bytes in 61ms
D/dalvikvm( 3357): GC freed 11236 objects / 402944 bytes in 41ms
D/dalvikvm( 3357): GC freed 7376 objects / 183336 bytes in 57ms
I/global ( 3357): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 3357): GC freed 10826 objects / 521112 bytes in 53ms
D/LocationManager( 3357): Constructor: service = [email protected]
D/dalvikvm( 3357): GC freed 1646 objects / 200792 bytes in 44ms
D/dalvikvm( 3357): GC freed 116 objects / 120272 bytes in 44ms
I/global ( 3357): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
E/dalvikvm( 3357): Could not find class 'com.google.android.maps.GeoPoint', referenced from method net.dinglisch.android.tasker.hf.a
W/dalvikvm( 3357): VFY: unable to resolve new-instance 279 (Lcom/google/android/maps/GeoPoint;) in Lnet/dinglisch/android/tasker/hf;
D/dalvikvm( 3357): VFY: replacing opcode 0x22 at 0x0005
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/hf;.a code (52 bytes)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
I/dalvikvm( 3357): Could not find method com.google.android.maps.GeoPoint.getLatitudeE6, referenced from method net.dinglisch.android.tasker.hf.a
W/dalvikvm( 3357): VFY: unable to resolve virtual method 1180: Lcom/google/android/maps/GeoPoint;.getLatitudeE6 ()I
D/dalvikvm( 3357): VFY: replacing opcode 0x6e at 0x000a
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/hf;.a code (116 bytes)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
I/dalvikvm( 3357): Could not find method com.google.android.maps.GeoPoint.getLatitudeE6, referenced from method net.dinglisch.android.tasker.hf.b
W/dalvikvm( 3357): VFY: unable to resolve virtual method 1180: Lcom/google/android/maps/GeoPoint;.getLatitudeE6 ()I
D/dalvikvm( 3357): VFY: replacing opcode 0x6e at 0x0009
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/hf;.b code (72 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/ht; (280)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/ht;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/ht; (280)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/ht;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
E/dalvikvm( 3357): Could not find class 'net.dinglisch.android.tasker.MyMapView', referenced from method net.dinglisch.android.tasker.ql.a
W/dalvikvm( 3357): VFY: unable to resolve check-cast 472 (Lnet/dinglisch/android/tasker/MyMapView;) in Lnet/dinglisch/android/tasker/ql;
D/dalvikvm( 3357): VFY: replacing opcode 0x1f at 0x000b
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/ql;.a code (264 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lnet/dinglisch/android/tasker/MyMapView;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
I/dalvikvm( 3357): Could not find method net.dinglisch.android.tasker.MyMapView.getContext, referenced from method net.dinglisch.android.tasker.ql.a
W/dalvikvm( 3357): VFY: unable to resolve virtual method 3189: Lnet/dinglisch/android/tasker/MyMapView;.getContext ()Landroid/content/Context;
D/dalvikvm( 3357): VFY: replacing opcode 0x6e at 0x0001
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/ql;.a code (117 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lnet/dinglisch/android/tasker/MyMapView;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lnet/dinglisch/android/tasker/MyMapView;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
E/dalvikvm( 3357): Could not find class 'net.dinglisch.android.tasker.MyMapView', referenced from method net.dinglisch.android.tasker.ql.a
W/dalvikvm( 3357): VFY: unable to resolve new-instance 472 (Lnet/dinglisch/android/tasker/MyMapView;) in Lnet/dinglisch/android/tasker/ql;
D/dalvikvm( 3357): VFY: replacing opcode 0x22 at 0x0013
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/ql;.a code (96 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: returning Ljava/lang/Object; (cl=0x0), declared Landroid/view/View; (cl=0x0)
W/dalvikvm( 3357): VFY: rejecting opcode 0x11 at 0x001c
W/dalvikvm( 3357): VFY: rejected Lnet/dinglisch/android/tasker/ql;.a (Landroid/content/Context;I)Landroid/view/View;
W/dalvikvm( 3357): Verifier rejected class Lnet/dinglisch/android/tasker/ql;
W/dalvikvm( 3357): Exception Ljava/lang/VerifyError; thrown during Lnet/dinglisch/android/tasker/md;.<clinit>
D/AndroidRuntime( 3357): Shutting down VM
W/dalvikvm( 3357): threadid=3: thread exiting with uncaught exception (group=0x4001b210)
E/Settings( 3357): 13.11.02#MyUEH: error: exception in thread main: java.lang.ExceptionInInitializerError
E/Settings( 3357): 13.11.02#: error: Caused by:
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.md.<clinit>(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.vh.b(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.vh.a(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.vh.d(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.Kid.onCreate(Unknown Source)
E/Settings( 3357): 13.11.02#: error: android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 3357): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 3357): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.vh.b(Unknown Source)
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.vh.a(Unknown Source)
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.vh.d(Unknown Source)
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.Kid.onCreate(Unknown Source)
E/AndroidRuntime( 3357): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 3357): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime( 3357): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime( 3357): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime( 3357): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime( 3357): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3357): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 3357): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 3357): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3357): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 3357): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 3357): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 3357): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 3357): Caused by: java.lang.VerifyError: net.dinglisch.android.tasker.ql
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.md.<clinit>(Unknown Source)
E/AndroidRuntime( 3357): ... 17 more
I/ActivityManager( 790): Removing old ANR trace file from /data/anr/traces.txt
W/ActivityManager( 790): Send CRASH intent: true
I/Process ( 790): Sending signal. PID: 3357 SIG: 3
D/EPD#ActivityManager( 790): resetRegion 4
D/NATIVE-EPD( 790): epd_reset_region: 0x10
D/EPD#ActivityManager( 790): resetRegion 5
D/NATIVE-EPD( 790): epd_reset_region: 0x20
D/EPD#ActivityManager( 790): resetRegion 6
D/NATIVE-EPD( 790): epd_reset_region: 0x40
D/EPD#ActivityManager( 790): resetRegion 7
D/NATIVE-EPD( 790): epd_reset_region: 0x80
D/DeviceManagerBroadcastReceiver( 949): action (com.bn.devicemanager.ACTION_HANDLE_CRASH)
I/dalvikvm( 3357): threadid=7: reacting to signal 3
I/dalvikvm( 3357): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 3357): Sending signal. PID: 3357 SIG: 9
I/ActivityManager( 790): Process com.home.nmyshkin.settings (pid 3357) has died.
V/Activity( 1225): performResume()
D/EPD#ActivityResume( 790): resetRegion 4
D/NATIVE-EPD( 790): epd_reset_region: 0x10
D/EPD#ActivityResume( 790): resetRegion 5
D/NATIVE-EPD( 790): epd_reset_region: 0x20
D/EPD#ActivityResume( 790): resetRegion 6
D/NATIVE-EPD( 790): epd_reset_region: 0x40
D/EPD#ActivityResume( 790): resetRegion 7
D/NATIVE-EPD( 790): epd_reset_region: 0x80
D/EPD#ActivityResume( 790): Disable EPD for 350ms!!!!!!!!
I/UsageStats( 790): Unexpected resume of com.gacode.relaunchx while already resumed in com.home.nmyshkin.settings
D/ReLaunchApp( 1225): --- onResume(AllApps)
W/InputManagerService( 790): Window already focused, ignoring focus gain of: [email protected]
I/DeviceManagerHandler( 949): HandleMessage(): msg.what (1)
I/global ( 949): Default buffer size used in BufferedWriter constructor. It would be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 949): GC freed 4915 objects / 501464 bytes in 41ms
I/LogcatProcessor( 949): LOG END MARKER - 1634321464060
alexhorner said:
I have just found a new APK for Superuser, 3.0.7 which I have attached in both the unextracted ZIP form and the extracted APK form. Source is https://forum.xda-developers.com/t/app-superuser-2-3-6-1-now-on-the-market-2010-09-05.682828/page-49
Click to expand...
Click to collapse
I have tried other SU apps in the past but they were always complaining about updating binaries (not going to happen). But if you have something that works, good.
That logcat seems to point to the two maps files that are expected by Tasker or any of its kid apps (like Nook Settings). So much stuff about maps, like it can't find what it wants. I've never seen anything like that on my devices (not that I sit around watching logcats scroll by all day). Check that both files are in the proper places. The jar file belongs in /system/framework and is rw-r-r (or 644, as you said). The xml file is in /system/etc/permissions and is also rw-r-r.
In short, if the old SU popped up with ADB Konnect, it's probably not the problem. The Nook Settings app itself is not the problem. I have it running on three devices and the fresh install last night went without a hitch. I've tested it on both FW 1.2.1 and 1.2.2.
Getting one of my Nooks ready for a backup now.