Team venom will soon be supporting the desire z with the assistance of lms24
ViperZ is based on the other wvga viperRoms on the dhd, vivo, and vivow
We are looking for 5-10 beta testers who can run the rom for a few days prior to release to make sure there are no huge bugs that would prevent a release
Testers should meet following requirements:
Proficient with adb and logcats
Have run sense4 roms on this phone for at least a little while before
Are active forum members (ie didn't join a month ago and have very few posts-
Ethical (won't share beta links with anyone)
Please post here if interested !
Beta should be out this week
Let's do it
Sent from my HTC Vision using xda premium
I can participate too.
I'd be willing to try but I don't have much time in my hands. This is full sense, correct? Also would you prefer us not to use things such as PMR or ROM Cleaner?
I'm willing to participate. i have a spare desire z at home and i used the rom on dhd so i can compare if needer
crestofawave said:
I'd be willing to try but I don't have much time in my hands. This is full sense, correct? Also would you prefer us not to use things such as PMR or ROM Cleaner?
Click to expand...
Click to collapse
yes, please run the rom as close to stock as possible :fingers-crossed:
ok, guys check your inboxes....just run the rom for a day or two, and let me know if there are any serious bugs (bootlooping)
G2 users, you need to be on a Z Hboot
Have fun while you're testing the Rom, guys. Let's hope this runs as great on your phones as on my DZ.
Sent from my HTC Desire Z using xda app-developers app
Smooth installation with aroma. No errors. No bootloops. Also no reboots yet.
Lowmemorykiller works great, even tho there is 50-60 mb free ram, no stutters in games. Actually better gaming then aosp roms.
I went ahead and changed the phone ID from s710e to HTC Desire Z since it bothers me and i do it with every rom before installation. I hope its okay.
All in all great job with the rom.
Don't have time to flash it now will do so later tonight. Looks promising already loved it on dhd
Sent from my HTC Vision using Tapatalk 2
OC settings in venom tweaks not working. or i cant seem to save the new frequencies. they just go back to default when i close the app.
btrst said:
OC settings in venom tweaks not working. or i cant seem to save the new frequencies. they just go back to default when i close the app.
Click to expand...
Click to collapse
ah, i guess torxx didnt remove them before the latest update (i did in viperINC)
good catch, thanks
Something strange,
I tried to enable swap with swap_enabler script but it said swap was already enabled. So i checked with terminal and it shows 122 mb swap space enabled without me enabling it. Strange thing is, my sdcard partitioned for 256 mb swap space. I checked the init.d scripts and none of them has any lines indicating automatic swap enabling. Im really confused here.
Yo, OP send beta towards this way if you don't mind?
I'm off all week and have spare G2 and Always On my phone atleast 18hours of the day literally.
-thanks
Sent from my HTC Vision using xda premium
The PDF Reader app is FC'ing for me. Other than that and what btrst mentioned I haven't had any other issues. The only thing I did was disable CPU Rendering and use CPU Tuner for CPU freq management.
The ROM is between smooth and choppy for me, and has fairly decent performance, things to be expected as we're talking about Sense 4. Quite impressive as far as I'm concerned. I also like the very extensive customizations, especially the Sweep to Unlock.
I can imagine that getting rid of all redundant stuff using ROM Cleaner will increase the ROM's Performance. Thanks for the share
crestofawave said:
The PDF Reader app is FC'ing for me. Other than that and what btrst mentioned I haven't had any other issues. The only thing I did was disable CPU Rendering and use CPU Tuner for CPU freq management.
The ROM is between smooth and choppy for me, and has fairly decent performance, things to be expected as we're talking about Sense 4. Quite impressive as far as I'm concerned. I also like the very extensive customizations, especially the Sweep to Unlock.
I can imagine that getting rid of all redundant stuff using ROM Cleaner will increase the ROM's Performance. Thanks for the share
Click to expand...
Click to collapse
can you logcat the pdf reader fc?
Here you go. (Longer logcat here). I launched the app several times. The longer log is fudged up as I'm running adb from cmd. I managed to salvage a few lines that had to do with the app and make them easier to read. Hope it helps.
Code:
I/Adreno200-EGLSUB( 101): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 101): <GetImageAttributes:1158>: RGBX_8888
I/ActivityManager( 184): Start proc com.htc.pdfviewer for activity com.htc.pdfviewer/.ActPDFReader: pid=9821 uid=10013 gids={2001, 3003, 1015, 1006, 5001}
W/ResourceType( 184): Skipping entry 0x7f04000c in package table 0 because it is not complex!
D/dalvikvm( 102): GC_EXPLICIT freed 38K, 27% free 2802K/3807K, paused 2ms+9ms
D/ConnectivityService( 184): onUidRulesChanged(uid=10013, uidRules=0)
D/dalvikvm( 102): GC_EXPLICIT freed <1K, 27% free 2802K/3807K, paused 3ms+2ms
D/dalvikvm( 102): GC_EXPLICIT freed <1K, 27% free 2802K/3807K, paused 2ms+2ms
I/ActivityThread( 9821): Pub com.htc.provider.pdfviewer: com.htc.pdfviewer.provider.PdfProvider
D/com.htc.pdfviewer.provider.PdfProvider( 9821): onCreate
D/com.htc.pdfviewer.provider.PdfProvider( 9821): AvailableDataDirectorySize 797159424
D/SqliteDatabaseCpp( 9821): Registering sqlite logging func: /data/data/com.htc.pdfviewer/databases/book.db
D/SqliteDatabaseCpp( 9821): DB info: open db, path = /data/data/com.htc.pdfviewer/databases , key = fkko, flag = 6, file size = 5120
D/SqliteDatabaseCpp( 9821): DB info: path = /data/data/com.htc.pdfviewer/databases , key = fkko, handle: 0x1fda9b0, type: w, r/w: (0,1), mode: truncate, disk free size: 760 M
I/ActivityThread( 9821): Pub com.htc.pdfviewer.PdfSuggestionProvider: com.htc.pdfviewer.PdfSuggestionProvider
W/dalvikvm( 9821): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/htc/pdfviewer/JNIHost;
D/AndroidRuntime( 9821): Shutting down VM
W/dalvikvm( 9821): threadid=1: thread exiting with uncaught exception (group=0x40aaf228)
E/EmbeddedLogger( 184): App crashed! Process: com.htc.pdfviewer
E/EmbeddedLogger( 184): App crashed! Package: com.htc.pdfviewer v400371055 (4.0.2215132855.371055.304684)
E/EmbeddedLogger( 184): Application Label: PDF Viewer
E/AndroidRuntime( 9821): FATAL EXCEPTION: main
E/AndroidRuntime( 9821): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 9821): at com.htc.pdfviewer.ActPDFReader.<init>(ActPDFReader.java:577)
E/AndroidRuntime( 9821): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 9821): at java.lang.Class.newInstance(Class.java)
E/AndroidRuntime( 9821): at android.app.Instrumentation.newActivity(Instrumentation.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.access$600(ActivityThread.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
E/AndroidRuntime( 9821): at android.os.Handler.dispatchMessage(Handler.java)
E/AndroidRuntime( 9821): at android.os.Looper.loop(Looper.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.main(ActivityThread.java)
E/AndroidRuntime( 9821): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 9821): at java.lang.reflect.Method.invoke(Method.java)
E/AndroidRuntime( 9821): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
E/AndroidRuntime( 9821): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
E/AndroidRuntime( 9821): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 9821): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load pdfviewer: findLibrary returned null
E/AndroidRuntime( 9821): at java.lang.Runtime.loadLibrary(Runtime.java)
E/AndroidRuntime( 9821): at java.lang.System.loadLibrary(System.java)
E/AndroidRuntime( 9821): at com.htc.pdfviewer.JNIHost.<clinit>(JNIHost.java:768)
E/AndroidRuntime( 9821): ... 16 more
W/ActivityManager( 184): Force finishing activity com.htc.pdfviewer/.ActPDFReader
D/ViewRootImpl( 184): @@@- disable SystemServer HW acceleration
D/OpenGLRenderer( 587): Flushing caches (mode 1)
D/OpenGLRenderer( 587): Flushing caches (mode 0)
D/memalloc( 587): /dev/pmem: Unmapping buffer base:0x58dd8000 size:15052800 offset:13516800
D/memalloc( 587): /dev/pmem: Unmapping buffer base:0x56fbb000 size:4608000 offset:3072000
D/memalloc( 587): /dev/pmem: Unmapping buffer base:0x5a545000 size:6144000 offset:4608000
I/Adreno200-EGLSUB( 101): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 101): <GetImageAttributes:1102>: RGBA_8888
W/ActivityManager( 184): Activity pause timeout for ActivityRecord{40daba60 com.htc.pdfviewer/.ActPDFReader}
thanks, seems to be missing the proper lib
im just gonna remove it from the rom, adobe reader is better (imo)
Just saw the new release for DZ, Thank you guys. I'm finishing downloading and i will share my experience with this rom after installation
desperately waiting for this rom keep up the good work thanks..
ahmedrzvi said:
desperately waiting for this rom keep up the good work thanks..
Click to expand...
Click to collapse
wait no longer! ITS BEEN OUT FOR TWO DAYS!
great for a full sense 4 ROM.
If you really want sense and all its features plus more, this is near perfect
Related
Oct 31 - LeTama has placed a wrapper for TESTING here http://forum.xda-developers.com/showthread.php?t=824413, if you know what your doing go ahead and follow his directions. Otherwise wait for a few fixes to be applied and more detailed directions will be developed so everyone can apply the final fix if there is such a thing.
Please discontinue the the testing from the 29th, thanks for the feedback. I you applied the ppp fix, please reverse the steps and remove. FYI- I just replaced my init.rc with my original one as nothing else calls for the other files. Then you can delete them whenever.
OCT 29 - Ok, LeTama and Cass (DEV's on IRC) have made a rough workaround to detect the data disconnect, when it detects the disconnect it attempts to reconnect or fix the data. I'm testing so far and it appears to work well.
I'm attaching a zip that LeTama posted with the needed files for others to test, this is probably not the final fix, but please post feedback if your feeling brave.
There are 4 files in the zip. The init.rc file contains the service line that you need to copy and paste into YOUR init.rc file. I used WordPad in windows. I then copied the init.rc file over to my SD via WM Activesync to the Android/root/init.rc
The rest of the files need to be copied to Android/root/system/bin/ folder.
Then boot android and test.
Do not copy the files using Droid Explorer as the permissions don't seem to work correctly, I will admit that I tried this method at first and it foobarred my connection.
Good luck....
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Please post your logcat files in this thread as soon as your data disconnects and won't reconnect. So the Devs can take a look and hopefully fix the data issues everyone is having.
Also post your build, sense or no sense, WM build, radio rom,
Otherwise you can toggle airplane mode or data and it should start working again.
EDIT: you can download aLogcat from the market and then just save the log and copy over to your computer then put it here..(actually not here, but in your post..hehe)
UPDATE: I've noticed many cooks have used the required libhtc_ril_wrapper.so file dated 8/19. However there was an update on 8/26 and again today 9/28. The 8/26 fixed some stuff for pppd to work correctly. The 9/28 just added some code for the future NAND to work correctly. I've attached the 9/28 wrapper and have been testing it for the last few hours. So far after reboot, it has been better for me.
The file is located in the root/system/lib folder in android. You can adb push this file or use Droid Explorer or a file manager with SU permissions. Just unzip this file and use one of the mentioned methods to copy it over to Android.
Also you can copy this file in WM to your "Android" folder or whatever folder your build is in, and to the folders (root/system/lib/libhtc_ril_wrapper.so) and when you boot android it should copy the wrapper to the correct folder.
Anyhow, give this a shot and see if it helps. Also check your wrapper and check the properties to see what the date is first, ALSO COPY YOUR CURRENT WRAPPER TO A TEMP FOLDER ON YOUR SD CARD FIRST just in case.
I take no credit for the wrapper as it was the work of other developers and the source is on the git with changes here http://gitorious.org/htc-hd2-android-libraries/libhtc_ril_wrapper
Stuff fixed in wrapper since it was created ....quoted from Git
9/28
-Corrected pppd failure check and introduced NAND boot compatibility.
8/26
- added automatic creation of files needed for pppd to run correctly
- fixed pppd start/stop after wifi activation
- cleaned up code little bit
8/18
-Fixed error with prelinked map while compiling module
8/17
-RIL wrapper for ppp data connection created
NOTE: the attached wrapper may fix the issues people had switching from wifi and back to data. Any wrapper after 8/26 should have the pppd start/stop after wifi activation fix. Should work with Nexus kernel fine.
EDIT: PLEASE PULL LOGCAT WITH SWITCH -b radio.....so logcat -b radio this will pull more detail for connections for devs...
Great.
Sent from my HTC HD2 using XDA App
I am using Mdeejay Evo Sense v1.4 and everything works superb apart from i cant seem to get 3G or H. i only get G and 2G. Anyone know how i can sort this out please???
here is a copy of my logfile
D/alogcat ( 2099): stopping ...
D/dalvikvm( 348): GC_EXPLICIT freed 5861 objects / 278168 bytes in 50ms
D/alogcat ( 2099): stopping ...
D/alogcat ( 2099): paused
D/Sensors ( 232): close_akm, fd=142
D/AK8973 ( 211): Compass CLOSE
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 2->3
D/AK8973 ( 211): Compass Start
D/Sensors ( 232): open_akm, fd=118
I/ActivityManager( 232): Displayed activity com.android.vending/.AssetBrowserActivity: 157 ms (total 157 ms)
D/dalvikvm( 811): GC_EXTERNAL_ALLOC freed 6653 objects / 470200 bytes in 55ms
I/ActivityManager( 232): Displayed activity com.android.vending/.MyDownloadsActivity: 418 ms (total 418 ms)
D/dalvikvm( 811): GC_FOR_MALLOC freed 14390 objects / 858800 bytes in 57ms
D/dalvikvm( 2099): GC_EXPLICIT freed 7589 objects / 1219872 bytes in 102ms
W/KeyCharacterMap( 811): No keyboard for id 0
W/KeyCharacterMap( 811): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/dalvikvm( 811): GC_EXTERNAL_ALLOC freed 5180 objects / 451088 bytes in 41ms
W/KeyCharacterMap( 811): No keyboard for id 0
W/KeyCharacterMap( 811): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/Sensors ( 232): close_akm, fd=118
D/AK8973 ( 211): Compass CLOSE
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 3->2
D/AK8973 ( 211): Compass Start
D/Sensors ( 232): open_akm, fd=122
D/alogcat ( 2099): stopping ...
D/alogcat ( 2099): resumed
I/ActivityManager( 232): Displayed activity org.jtb.alogcat/.LogActivity: 278 ms (total 278 ms)
W/Rosie ( 348): mAddHtcWidgetByOtherActivity = false, mIsOpenSlideWhenLeaveLaunch = true
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 2->4
D/dalvikvm( 811): GC_EXPLICIT freed 6369 objects / 435984 bytes in 116ms
I/ConnLib ( 673): Enter network idle mode
W/KeyCharacterMap( 2099): No keyboard for id 0
W/KeyCharacterMap( 2099): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/alogcat ( 2099): stopping ...
D/alogcat ( 2099): paused
D/Sensors ( 232): close_akm, fd=122
D/AK8973 ( 211): Compass CLOSE
D/Sensors ( 232): open_akm, fd=122
D/AK8973 ( 211): Compass Start
I/ActivityManager( 232): Displayed activity com.android.vending/.AssetBrowserActivity: 128 ms (total 128 ms)
D/dalvikvm( 811): GC_EXTERNAL_ALLOC freed 1848 objects / 132672 bytes in 50ms
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 4->3
I/ActivityManager( 232): Displayed activity com.android.vending/.MyDownloadsActivity: 468 ms (total 468 ms)
D/dalvikvm( 811): GC_FOR_MALLOC freed 7356 objects / 563752 bytes in 46ms
I/ActivityManager( 232): Displayed activity com.android.vending/.TabbedAssetInfoActivity: 474 ms (total 474 ms)
D/dalvikvm( 314): GC_EXPLICIT freed 55 objects / 2264 bytes in 32ms
W/KeyCharacterMap( 811): No keyboard for id 0
W/KeyCharacterMap( 811): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/dalvikvm( 811): GC_EXTERNAL_ALLOC freed 9228 objects / 663360 bytes in 48ms
W/KeyCharacterMap( 811): No keyboard for id 0
W/KeyCharacterMap( 811): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/Sensors ( 232): close_akm, fd=122
D/AK8973 ( 211): Compass CLOSE
D/AK8973 ( 211): Compass Start
D/Sensors ( 232): open_akm, fd=134
I/ActivityThread( 2268): Publishing provider htcbrowser: com.android.browser.htc.util.HTCBrowserProvider
I/ActivityThread( 2268): Publishing provider browser: com.android.browser.BrowserProvider
D/dalvikvm( 2268): GC_EXTERNAL_ALLOC freed 3060 objects / 184344 bytes in 45ms
W/webcore ( 2268): Not supported in this case.
I/ActivityManager( 232): Displayed activity com.android.browser/.BrowserActivity: 2627 ms (total 2627 ms)
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 3->2
I/com_htc_android_iqagent_Controller( 314): submitAL15
D/webkit-timers( 2268): [JWebCoreJavaBridge::resume] >> do resume
D/RequestQueue( 2268): queueRequest to set proxy
D/RequestQueue( 2268): setProxyConfig mProxyHost=null
D/RequestQueue( 2268): setProxyConfig mProxyHost=null
D/RequestQueue( 2268): queueRequest with mProxyHost=null for http://www.google.com/
D/dalvikvm( 2268): GC_FOR_MALLOC freed 6148 objects / 399768 bytes in 63ms
D/dalvikvm( 420): GC_EXPLICIT freed 789 objects / 37280 bytes in 35ms
D/dalvikvm( 2268): GC_EXPLICIT freed 1804 objects / 127176 bytes in 92ms
D/dalvikvm( 2268): GC_EXTERNAL_ALLOC freed 22 objects / 1240 bytes in 89ms
D/LocationManager( 2268): requestLocationUpdates: provider = network, listener = [email protected]
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 2->3
W/Process ( 232): Unable to open /proc/542/status
W/KeyCharacterMap( 2268): No keyboard for id 0
W/KeyCharacterMap( 2268): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 3->2
D/LocationManager( 2268): removeUpdates: listener = [email protected]
D/webkit-timers( 2268): [JWebCoreJavaBridge:ause] >> do pause
D/Sensors ( 232): close_akm, fd=134
D/AK8973 ( 211): Compass CLOSE
D/LocationMasfClient( 232): getNetworkLocation(): Returning cache location with accuracy 668.0
D/AK8973 ( 211): Compass Start
D/Sensors ( 232): open_akm, fd=140
D/alogcat ( 2099): stopping ...
D/alogcat ( 2099): resumed
I/ActivityManager( 232): Displayed activity org.jtb.alogcat/.LogActivity: 246 ms (total 246 ms)
W/Rosie ( 348): mAddHtcWidgetByOtherActivity = false, mIsOpenSlideWhenLeaveLaunch = true
D/dalvikvm( 2099): GC_FOR_MALLOC freed 5858 objects / 482776 bytes in 46ms
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 2->3
D/dalvikvm( 348): GC_EXPLICIT freed 4151 objects / 229096 bytes in 42ms
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 3->4
I/ConnLib ( 673): Enter network idle mode
I/global ( 232): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
I/global ( 232): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
D/BatteryService( 232): isUsbConnected() = false
D/BatteryService( 232): mPlugType = 0
D/UsbConnectedReceiver( 467): action = psclient.intent.action.usb_status
D/UsbConnectedReceiver( 467): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 467): usbCurrentType = 0
D/UsbConnectedReceiver( 467): Current type is same as previous, return!
E/Tethering( 232): attempting to remove unknown iface (usb0), ignoring
D/lights ( 232): set_light_backlight
D/lights ( 232): set_light_backlight
W/KeyCharacterMap( 2099): No keyboard for id 0
W/KeyCharacterMap( 2099): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/alogcat ( 2099): stopping ...
D/alogcat ( 2099): paused
D/Sensors ( 232): close_akm, fd=140
D/AK8973 ( 211): Compass CLOSE
D/AK8973 ( 211): Compass Start
D/Sensors ( 232): open_akm, fd=134
D/LocationManager( 2268): requestLocationUpdates: provider = network, listener = [email protected]
D/RequestQueue( 2268): setProxyConfig mProxyHost=null
D/LocationManager( 2268): removeUpdates: listener = [email protected]
D/webkit-timers( 2268): [JWebCoreJavaBridge::resume] >> do resume
I/HTC_IME ( 313): onCreateInputView
D/dalvikvm( 313): GC_EXTERNAL_ALLOC freed 1176 objects / 55096 bytes in 57ms
W/Resources( 313): Converting to string: TypedValue{t=0x12/d=0x0 a=3 r=0x7f090195}
W/Resources( 313): Converting to string: TypedValue{t=0x12/d=0x0 a=3 r=0x7f090196}
D/dalvikvm( 313): GC_EXTERNAL_ALLOC freed 4174 objects / 276800 bytes in 34ms
D/dalvikvm( 2268): GC_FOR_MALLOC freed 2852 objects / 439000 bytes in 53ms
W/KeyCharacterMap( 2268): No keyboard for id 0
W/KeyCharacterMap( 2268): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/LocationMasfClient( 232): getNetworkLocation(): Returning cache location with accuracy 668.0
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 4->3
D/dalvikvm( 313): GC_EXPLICIT freed 931 objects / 51176 bytes in 51ms
I/com_htc_android_iqagent_Controller( 314): submitAL15
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 3->4
D/dalvikvm( 2268): GC_FOR_MALLOC freed 4468 objects / 465416 bytes in 48ms
D/dalvikvm( 2099): GC_EXPLICIT freed 2290 objects / 139320 bytes in 32ms
W/KeyCharacterMap( 2268): No keyboard for id 0
W/KeyCharacterMap( 2268): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 4->3
D/dalvikvm( 2268): GC_FOR_MALLOC freed 3444 objects / 326728 bytes in 70ms
D/LocationManager( 2268): requestLocationUpdates: provider = network, listener = [email protected]
W/KeyCharacterMap( 2268): No keyboard for id 0
W/KeyCharacterMap( 2268): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/LocationManager( 2268): removeUpdates: listener = [email protected]
D/webkit-timers( 2268): [JWebCoreJavaBridge:ause] >> do pause
D/Sensors ( 232): close_akm, fd=134
D/AK8973 ( 211): Compass CLOSE
D/AK8973 ( 211): Compass Start
D/Sensors ( 232): open_akm, fd=140
D/alogcat ( 2099): stopping ...
D/alogcat ( 2099): resumed
W/ContentService( 232): binderDied() at ObserverNode name contacts
W/ContentService( 232): binderDied() at ObserverNode name system
W/ContentService( 232): binderDied() at ObserverNode name contacts
W/ContentService( 232): binderDied() at ObserverNode name contacts
W/ContentService( 232): binderDied() at ObserverNode name contacts
W/ContentService( 232): binderDied() at ObserverNode name contacts
W/ContentService( 232): binderDied() at ObserverNode name contacts
W/Rosie ( 348): mAddHtcWidgetByOtherActivity = false, mIsOpenSlideWhenLeaveLaunch = true
I/ActivityManager( 232): Displayed activity org.jtb.alogcat/.LogActivity: 606 ms (total 606 ms)
D/LocationMasfClient( 232): getNetworkLocation(): Returning cache location with accuracy 668.0
W/Process ( 232): Unable to open /proc/553/status
W/Process ( 232): Unable to open /proc/708/status
W/Process ( 232): Unable to open /proc/722/status
D/dalvikvm( 2099): GC_FOR_MALLOC freed 3021 objects / 285256 bytes in 135ms
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 3->4
D/WhatsApp( 2332): hv.java:39 app/create/timer/start
I/WhatsApp( 2332): network/info
I/WhatsApp( 2332): NetworkInfo: type: mobile[EDGE], state: CONNECTED/CONNECTED, reason: apnSwitched, extra: mobile.o2.co.uk, roaming: false, failover: true, isAvailable: true, if: ppp0, type: 0, subtype: 2
I/WhatsApp( 2332): NetworkInfo: type: WIFI[], state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false, if: eth0, type: 1, subtype: 0
I/WhatsApp( 2332): NetworkInfo: type: mobile_mms[UNKNOWN], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, if: ppp0, type: 2, subtype: 0
I/WhatsApp( 2332): NetworkInfo: type: mobile_supl[UNKNOWN], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, if: ppp0, type: 3, subtype: 0
I/WhatsApp( 2332): NetworkInfo: type: mobile_dun[UNKNOWN], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, if: ppp0, type: 4, subtype: 0
I/WhatsApp( 2332): NetworkInfo: type: mobile_hipri[UNKNOWN], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, if: ppp0, type: 5, subtype: 0
I/WhatsApp( 2332): NetworkInfo: type: WIMAX[], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false, if: wimax0, type: 6, subtype: 0
I/WhatsApp( 2332): NetworkInfo: type: mobile_wapgateway[UNKNOWN], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, if: ppp0, type: 7, subtype: 0
I/WhatsApp( 2332): NetworkInfo: type: mobile_httpproxy[UNKNOWN], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, if: ppp0, type: 8, subtype: 0
I/WhatsApp( 2332): NetworkInfo: type: mobile_fota[UNKNOWN], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, if: ppp0, type: 9, subtype: 0
I/WhatsApp( 2332): NetworkInfo: type: mobile_admin[UNKNOWN], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, if: ppp0, type: 10, subtype: 0
D/dalvikvm( 2332): GC_FOR_MALLOC freed 5901 objects / 410648 bytes in 29ms
I/WhatsApp( 2332): statistics Text Messages: 47 sent, 44 received / Media Messages: 0 sent (0 bytes), 0 received (0 bytes) / Offline Messages: 9 received (330815 msec average delay) / Message Service: 321855 bytes sent, 76594 bytes received / Cold Sync: 64444 bytes sent, 178653 bytes received / Total Data: 386299 bytes sent, 255247 bytes received
I/WhatsApp( 2332): dbinfo/checkDataBase
I/WhatsApp( 2332): dbinfo/open_existing_db
I/WhatsApp( 2332): current version:2, Appversion:2
I/WhatsApp( 2332): dbinfo/isDBInited:true/total contact:355 | time spent:155
I/WhatsApp( 2332): dbinfo/isMeExist row_id=1 [email protected] key=435-07885240176 phone=2 iswa=false , time spent:13
I/WhatsApp( 2332): app/init/writable-media
I/WhatsApp( 2332): dbinfo/getContactByJID: row_id=143 [email protected] key=747-+2348059800446 phone=2 iswa=true | time spent:3
I/WhatsApp( 2332): dbinfo/getContactByJID: row_id=234 [email protected] key=410-+2348023039540 phone=2 iswa=true | time spent:1
I/WhatsApp( 2332): app/init/timer/stop: 379
I/WhatsApp( 2332): upgrade/source http://beta.whatsapp.com/android/8/
I/WhatsApp( 2332): app/create/timer/stop: 1373
I/WhatsApp( 2332): xmpp/service/create
I/WhatsApp( 2332): xmpp/service/keepalive/stop
I/WhatsApp( 2332): xmpp/service/start
I/SSLSocketFactory( 2332): Using factory [email protected]006e920
D/dalvikvm( 2332): GC_FOR_MALLOC freed 5875 objects / 326816 bytes in 73ms
I/WhatsApp( 2332): xmpp/connection/recv/writer_thread_ready
I/WhatsApp( 2332): device/memory private_dirty=3112kB pss=4820kB shared_dirty=7352kB
I/WhatsApp( 2332): device/memory processes=53 total=321277
I/WhatsApp( 2332): device/battery level=45% health=2 plugged=0
I/WhatsApp( 2332): xmpp/service/network/notice NetworkInfo: type: mobile[EDGE], state: CONNECTED/CONNECTED, reason: apnSwitched, extra: mobile.o2.co.uk, roaming: false, failover: true, isAvailable: true, if: ppp0
I/WhatsApp( 2332): xmpp/service/network/active NetworkInfo: type: mobile[EDGE], state: CONNECTED/CONNECTED, reason: apnSwitched, extra: mobile.o2.co.uk, roaming: false, failover: true, isAvailable: true, if: ppp0
I/WhatsApp( 2332): xmpp/connection/recv/connect
I/WhatsApp( 2332): xmpp/connection/connect
I/WhatsApp( 2332): xmpp/connection/socket/unencrypted
D/dalvikvm( 2332): GC_FOR_MALLOC freed 8259 objects / 452904 bytes in 48ms
I/WhatsApp( 2332): xmpp/connection/socket/connect xmpp-android.whatsapp.net./173.192.219.131
I/global ( 2332): Default buffer size used in BufferedWriter constructor. It would be better to be explicit if an 8k-char buffer is required.
I/WhatsApp( 2332): xmpp/connection/login
D/dalvikvm( 314): GC_EXPLICIT freed 987 objects / 42352 bytes in 82ms
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 4->2
W/KeyCharacterMap( 2099): No keyboard for id 0
W/KeyCharacterMap( 2099): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
I/BatteryStatsImpl( 232): notePhoneSignalStrengthLocked: 2->1
Alright, i have a problem with 3G and H - shows full bars, can make calls normally, but absolutely no internet. I have to go to to airplane mode, and after i come back from it - works fine for a few hrs. And it dies eventually, so I have to do it again.
Using Mdeejay evo sense 1.5, radio 2.14, and VBNROM. Help
Awesome find on the ril wrapper - gonna give it a go and see if it helps. Did you compile this or did you get it from somewhere else?
This is weird, a ton of people all at once today started having connection issues. Im in the same boat, i always have great connection without a problem. I normally never see Edge, but today something different is happening. I cant keep data for more than 5 to 10 seconds. I had to boot into WinMo to get my data back. Im even using an older build that i KNOW for a fact is 100% functional with a data connection.
noellenchris said:
Please post your logcat files in this thread as soon as your data disconnects and won't reconnect. So the Devs can take a look and hopefully fix the data issues everyone is having.
Also post your build, sense or no sense, WM build, radio rom,
Otherwise you can toggle airplane mode or data and it should start working again.
EDIT: you can download aLogcat from the market and then just save the log and copy over to your computer then put it here..(actually not here, but in your post..hehe)
UPDATE: I've noticed many cooks have used the required libhtc_ril_wrapper.so file dated 8/19. However there was an update on 8/26 and again today 9/28. The 8/26 fixed some stuff for pppd to work correctly. The 9/28 just added some code for the future NAND to work correctly. I've attached the 9/28 wrapper and have been testing it for the last few hours. So far after reboot, it has been better for me.
The file is located in the root/system/lib folder in android. You can adb push this file or use Droid Explorer or a file manager with SU permissions. Just unzip this file and use one of the mentioned methods to copy it over to Android.
Also you can copy this file in WM to your "Android" folder or whatever folder your build is in, and to the folders (root/system/lib/libhtc_ril_wrapper.so) and when you boot android it should copy the wrapper to the correct folder.
Anyhow, give this a shot and see if it helps. Also check your wrapper and check the properties to see what the date is first, ALSO COPY YOUR CURRENT WRAPPER TO A TEMP FOLDER ON YOUR SD CARD FIRST just in case.
I take no credit for the wrapper as it was the work of other developers and the source is on the git with changes here http://gitorious.org/htc-hd2-android-libraries/libhtc_ril_wrapper
Click to expand...
Click to collapse
Thanks for the updated rill
Trying the new wrapper now...will report back
Update...
I copied my original file and using sufb i put the new file in the folder and rebooted. I then used gscript to change my connection type from rmnet to ppp and rebooted again...after the reboot, I could not get any cell connection at all. I am still using the new wrapper but had to switch back to rmnet...I now have signal and data again.
Is there anything else that I need to do? All of the information in my signature is current with the exception of the radio, I switched back to the 2.12 radio for performance issues.
Yup, mine Bangsters v1.4 also 'died' after installing new RIL - no cell reception.
Nice Find...
Installed and running well.... Will see how it goes during the day
Desire HD Beta, Radio 214.etc.etc
regards
Nic
please don't use adb shell logcat or adb logcat but use this..
adb shell
su
logcat | grep ppp
or try
adb logcat | grep ppp
we will have a direct logcat from ppp issue..my case in the logcat after ppp disconnect and connect again and no data : "tcflush fail wrong file number"
and the main problem is : ppp cant pick up my dns provider, so i add it manual in build.prop, same thing with gateway/broadcast ip, i always got 10.64.64.64 but with that broadcast ip and manual dns my data work..
*trying new ril wrapper in miui rom now..
tested on
MIUI beta 4
r0 Michy kernel
testing.. will report soon
Update:
Not working - no trafic, status connected
ChuckyDroidROM, ★shubCRAFT 1.5★CM6 Final★, hastarin r6..
My cell reception died too after RIL update on CoreDroid 0.4R.
seemed to work ok for me on hyperdroid sense..data working fine...before when i tried it earlier it was choppy
here is my pastebin
http://pastebin.com/k0Fzdt9a
i'm using new ril wrapper, still has data disconnect problem..
the most annoying is when the ppp trying to connect back and then it connected but there are no data flow because there is no ip address..take a look at pastebin, after modem hangup and ppp try to reconnect theres tcflush fail, then theres no ip address..
Sent from my HTC HD2 using XDA App
Thank you. Updating that file so far has fixed my data connection on the miui build.
The new ril looks promising.
Previously in terminal - ifconfig ppp0 always bought error message unknown.
Now it brings up ip etc.
edit: spoke too soon disconnected after phone call.
I have running the new wrapper on mdeejay REVOlution and I seen to be getting better connection. I haven't experience a drop yet.
Sent from my SUPER HTC HD2 using XDA App
I have notice something... I had testing some issues with audio stuttering, and try some changes on my SD. I had my SD formated at 32k. And had some stuttering and ppp problems sometimes. Then i formatted my SD Card with 8k cluster size and the ppp become really severe. I couldnt transfer almost no data. I was able to update weather, go to google.com, but when i go to a page like xda, it give a problem on ppp. Then could not restart ppp. Only by reboot. I think that the SD card speed and cluster size affects not only the stuttering audio but also the ppp issue. I dont know why. I dont think its is cause, but affects. It seems that EVO kernels have some issue with SD read/write that old N1 Kernel dont.
Can you check you speed card and try to format with 64k cluster size to see if it helps?
So far so good on Darkstone desire beta 2,but to early to judge it,i first gonna test it for 1 day.
Now the stupid part,placebo or lucky?:
My signal from receive is also much better,placebo?
I do not have any clue lol
So I have been running noobnl's Andromeda Galaxy ROM, ver 1.1.1a currently, with Phoenix Kernel 1.46. Slightly older stuff, but it's been stable so I haven't bothered upgrading. I have the original version of the market as I never received the update to the new version.
This morning I updated a few apps in the Market without a problem. I went to look for something a few hours later and the Market force closed on me. I rebooted the phone a couple times and still got FCs, so I pulled up alogcat and got the follow error:
Code:
E/Database( 3398): Failure 1 (duplicate column name: auto_update) on 0x1304a8 when preparing 'ALTER TABLE assets10 ADD COLUMN auto_update INTEGER'.
E/AndroidRuntime( 3398): Uncaught handler: thread Thread-9 exiting due to uncaught exception
E/AndroidRuntime( 3398): android.database.sqlite.SQLiteException: duplicate column name: auto_update: ALTER TABLE assets10 ADD COLUMN auto_update INTEGER
E/AndroidRuntime( 3398): at android.database.sqlite.SQLiteDatabase.native_execSQL(Native Method)
E/AndroidRuntime( 3398): at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1722)
E/AndroidRuntime( 3398): at com.android.vending.api.LocalAssetDatabase$DatabaseHelper.onUpgrade(LocalAssetDatabase.java:1293)
E/AndroidRuntime( 3398): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:108)
E/AndroidRuntime( 3398): at com.android.vending.api.LocalAssetDatabase.<init>(LocalAssetDatabase.java:135)
E/AndroidRuntime( 3398): at com.android.vending.ServiceLocator.getLocalAssetDatabase(ServiceLocator.java:101)
E/AndroidRuntime( 3398): at com.android.vending.model.Asset.getLocalInfoForAll(Asset.java:1223)
E/AndroidRuntime( 3398): at com.android.vending.model.LocalAssetCache.buildCache(LocalAssetCache.java:139)
E/AndroidRuntime( 3398): at com.android.vending.model.LocalAssetCache.access$000(LocalAssetCache.java:25)
E/AndroidRuntime( 3398): at com.android.vending.model.LocalAssetCache$1.run(LocalAssetCache.java:75)
E/AndroidRuntime( 3398): at java.lang.Thread.run(Thread.java:1096)
From the error, it sounds like maybe I now got the update but for some reason when the updated Market is trying to install itself behind the scenes, it's failing. Thoughts?
I just tried clearing Davlik to no avail. I'm going to try to restore just the data from a couple day old backup. I took a backup of the phone in this current state already.
gremlyn1 said:
So I have been running noobnl's Andromeda Galaxy ROM, ver 1.1.1a currently, with Phoenix Kernel 1.46.
Click to expand...
Click to collapse
That doesn't quite qualify as "having done nothing to the phone", imho, or am I wrong? Very likely the new market app doesn't like your ROM and is failing to launch after having been updated earlier today. Chances are it will happen again even if you go back.
APOLAUF said:
That doesn't quite qualify as "having done nothing to the phone", imho, or am I wrong? Very likely the new market app doesn't like your ROM and is failing to launch after having been updated earlier today. Chances are it will happen again even if you go back.
Click to expand...
Click to collapse
Sorry, I meant I haven't done anything to it recently. I've been on the same ROM/kernel for at least a month now with no issues, and the Market FC issue is just since this morning.
gremlyn1 said:
Sorry, I meant I haven't done anything to it recently. I've been on the same ROM/kernel for at least a month now with no issues, and the Market FC issue is just since this morning.
Click to expand...
Click to collapse
Yeah, that's when the new market pushed out. Not sure what to tell you though... despite all their shortcomings, this is why I personally stick to stock ROMs - all the caveats for minor improvements and constant instability isn't worth it to me in the long run. I've messed with all sorts of custom ROMs in my life, but ultimately, the thing has to work according to its intended development lifecycle. Of course, to each their own, and I can understand the desire to have something uniquely different, but I've run into more trouble than it's worth. A friend of mine was raving on about CM6 on his original G1... but the thing couldn't answer a phonecall half the time. The irony...
APOLAUF said:
Yeah, that's when the new market pushed out. Not sure what to tell you though... despite all their shortcomings, this is why I personally stick to stock ROMs - all the caveats for minor improvements and constant instability isn't worth it to me in the long run. I've messed with all sorts of custom ROMs in my life, but ultimately, the thing has to work according to its intended development lifecycle. Of course, to each their own, and I can understand the desire to have something uniquely different, but I've run into more trouble than it's worth. A friend of mine was raving on about CM6 on his original G1... but the thing couldn't answer a phonecall half the time. The irony...
Click to expand...
Click to collapse
So the new Market pushed out yesterday morning? I thought it pushed out a couple of months ago and I just never got it...
gremlyn1 said:
So the new Market pushed out yesterday morning? I thought it pushed out a couple of months ago and I just never got it...
Click to expand...
Click to collapse
It did. I never got it that time around. (Ended up installing manually, messed up my device, had to wipe.) The newest version that pushed yesterday includes the "related" tab, and this time more of us seem to have gotten it.
So replacing .apks didn't work out for me, so I started looking at the error message and decided to try to remove the column from the offending .db. I did this successfully and thought it was going to work but then received a whole slew of other error messages... so I tried simply deleting the entire /data/data/com.android.vending folder and VOILA! I not only have a working Market, it updated to the new version finally!
Got repeated FC's in the Updated market App. (running -rooted- stock Rogers Canada ROM minus a few rogers/SE apps) Tried clearing cache; NG. Tried re-installing market app; also NG. Finally removed all updates in Applications/market, reverting to the old version and All's Well...guess I'll wait until they work out the bugs in the new market.
OK this thread is dedicated to developing a WORKING charging battery icon animation. The main problem is this: ASUS' code only allows for still images to be drawn when the battery is charging (specifically when the dock is connected). Applying existing techniques to allow for animation results in the following exception:
Code:
W/dalvikvm( 149): threadid=8: thread exiting with uncaught exception (group=0x401ab760)
E/AndroidRuntime( 149): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime( 149): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) } in [email protected]
E/AndroidRuntime( 149): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:725)
E/AndroidRuntime( 149): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 149): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 149): at android.os.Looper.loop(Looper.java:132)
E/AndroidRuntime( 149): at com.android.server.ServerThread.run(SystemServer.java:608)
E/AndroidRuntime( 149): Caused by: java.lang.ClassCastException: android.graphics.drawable.AnimationDrawable cannot be cast to android.graphics.drawable.BitmapDrawable
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.adjustStatusBarDockLocked(DockManagerService.java:371)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.updateLocked(DockManagerService.java:317)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.updateDockBatteryState(DockManagerService.java:309)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.access$300(DockManagerService.java:55)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService$3.onReceive(DockManagerService.java:229)
E/AndroidRuntime( 149): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:716)
E/AndroidRuntime( 149): ... 4 more
The line in question is the following: "Caused by: java.lang.ClassCastException: android.graphics.drawable.AnimationDrawable cannot be cast to android.graphics.drawable.BitmapDrawable", which is pretty much self-explanatory.
Anyways, I have dug into it more and traced the issue back to the source where I believe it is triggered from. First off, let me explain what I did:
Extracted 'classes.dex' from 'services.jar'
Decompiled 'classes.dex' using dex2jar
Was only able to view the source code with JD-GUI (don't know how to make edits)
Traced the issue to the file \com\android\server\asus\DockManagerService.class
In the 'DockManagerService.class', there are references to BitmapDrawable which I think need to be AnimatedDrawable, since that is what the logcat debug message says above (in the OP). I have no idea what to change it to exactly (let alone recompile it), but I believe this is where we need to look ('...' is edited-out code):
Code:
private void adjustStatusBarDockLocked()
...
...
localImageView.setImageResource(n);
int i1 = this.mDockBatteryLevel;
localImageView.setImageLevel(i1);
Bitmap localBitmap = ((BitmapDrawable)localImageView.getDrawable().getCurrent()).getBitmap();
localRemoteViews.setImageViewBitmap(16908985, localBitmap);
}
Also, near the top of 'DockManagerService.class', there is the following:
Code:
import android.graphics.Bitmap;
import android.graphics.drawable.BitmapDrawable;
import android.graphics.drawable.Drawable;
...not sure if we'd need to add something like 'android.graphics.drawable.AnimationDrawable;' in order to get animations supported?
Anyways, that's about as far as I can get with my current knowledge. If any other experienced dev is out there, it would be super great if they could give their thoughts, suggestions, ANYTHING!
Hopefully after we get to the bottom of this, we'll be able to have animated charging icons which support the ASUS dock.
OH, and forgot to mention that users of the OC kernel by Clemsyn (which is currently NOT built from source, since the 3.1 official ASUS source has not yet been released) do not suffer from this problem, since that OC kernel has broken support for the dock battery level/charging status. It currently only becomes an issue with the Stock 3.1 kernel which is able to correctly read the Dock Status.
Thanks in advance!
This may (or may not) help - but -
Can you locate the source for "BatteryService" and see if anything in there helps?
Also - did the Asus "limited release" for the Dock issues not contain a working Dock Status? If it did, someone may have the files kicking around from that which could have the parts you need in?
I use a widget called "bat stat" that uses animation, but it does not handle the dock (of course). It is small, has great animation and graphics, and is not well know yet it is in the market.
Was thinking to do my own tf version, will let you know if succeeds.
Hope this helps.
=======
UPDATE:
I finished the *graphics* to represent various tablet & dock and charging or discharging states.
I will look at some widget *codes* next.
I'm assuming that, for the most part, the apps on the Market that are designed to "discover" CIQ or traces of it are going to look for any small thing that might be left over from the removals, regardless of whether or not it's actually still part of our ROMs. That said, for all our devs who've put out ROMs that claim to not have CIQ on board, how do we know for sure that it's been removed?
Case in point - I'm currently running ACS ICS v5, and every ACS release that I've been on has claimed to have CIQ removed - yet, I ran 4 different CIQ discovery apps on a whim this morning, and they all claimed to find Carrier IQ on board. Is it just hype, or have we been missing something all along?
/and by "we," I mean, all the devs who work way harder on this stuff than me
//is basically just a ROM slut
From what I've read, the CIQ code is still baked into the kernel. BUT because the guts of CIQ were removed, the code has nothing to talk to.
That may be the culprit being detected. If you are getting other "false positives" then post screen shots of your output.
I am running SRF 1.2 still and from the OP for that ROM states that it is completely removed, not disabled or partitially removed.
"What's the secret sauce? Carrier IQ, the infamous Sprint spyware package, has been completely removed! More details in the second post - you won't believe what we found! Themers and other mod developers take note, many modifications were made to the system in order to achieve this exclusive feature."
When I run Voodoo CIQ app it says.
Carrier IQ has been found and is active
Detection score: 370
Test for: Android logcat debugging log
(LOGCAT, weight 100)
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: D/ ( 9960): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: D/ ( 9960): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/bin/iqmsd
found: /system/lib/libiq_client.so
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
found: system 9960 2376 213724 14076 ffffffff 00000000 S android.iqd
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
Yeah, I guess Voodoo is the one I hadn't run yet - according to that, I'm in the clear:
Voodoo Carrier IQ Detector report:
Build fingerprint:
sprint/SPH-D700/SPH-D700:2.3.5/GINGERBREAD/EI22:user/release-keys
Carrier IQ elements found
− however it seems inactive
Detection score: 170
Test for: Linux kernel interfaces
(KERNEL_INTERFACES, weight 50)
nothing found
Test for: Android logcat debugging log
(LOGCAT, weight 100)
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: D/ ( 2073): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: D/ ( 2073): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: I/ActivityManager( 285): No longer want android.iqd (pid 2073): hidden #16
Test for: Linux kernel drivers
(KERNEL_DRIVERS, weight 50)
nothing found
Test for: System services
(SERVICES, weight 70)
nothing found
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/bin/iqmsd
found: /system/lib/libiq_service.so
found: /system/lib/libiq_client.so
Test for: ROM configs
(ETC_CONFIG, weight 0)
nothing found
Test for: Packages
(PACKAGES, weight 70)
nothing found
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
nothing found
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
Test for: Linux kernel dmesg log
(DMESG, weight 100)
nothing found
Mine had a score of 170 and then re-ran it to show someone that mine is inactive and then the score jumped to 370 and said active. I'm thinking wtf...
when creating the CIQ mod, k0nane had to leave certain directories in order for things to work. They're completely empty of the files that were in them, but their existence will register on the voodoo app until supercurio and k0nane fine tune the detection. CIQ is removed from your phone it you're running a CIQ-free rom. This is says the yellow warning that elements may still exist but CIQ may not be present.
The Root said:
when creating the CIQ mod, k0nane had to leave certain directories in order for things to work. They're completely empty of the files that were in them, but their existence will register on the voodoo app until supercurio and k0nane fine tune the detection. CIQ is removed from your phone it you're running a CIQ-free rom. This is says the yellow warning that elements may still exist but CIQ may not be present.
Click to expand...
Click to collapse
/thread 10char
I trust Konane a lot more than some random app. He is the one that warned us all about this and has made sevetal phones ciq free.
Sent from my Epic on Legend or my Galaxy Tab rooted (feels naked without a ROM)
lancelane said:
I trust Konane a lot more than some random app. He is the one that warned us all about this and has made sevetal phones ciq free.
Sent from my Epic on Legend or my Galaxy Tab rooted (feels naked without a ROM)
Click to expand...
Click to collapse
As do I, believe me. I'm new on the boards, but I've been lurking for at least a year now, and I've never had any reason to doubt our devs' fine work Like I said, I mostly tried out those detection apps on a whim, since I had no reason to believe that CIQ was still active on my ROMs (and obviously it's been a current event of sorts) and it just kind of threw me for a loop when I got the results that I did. Anyway, thanks to the community for such quick answers, hopefully I didn't come off as too hostile in my first post!
rekrdskratcher said:
As do I, believe me. I'm new on the boards, but I've been lurking for at least a year now, and I've never had any reason to doubt our devs' fine work Like I said, I mostly tried out those detection apps on a whim, since I had no reason to believe that CIQ was still active on my ROMs (and obviously it's been a current event of sorts) and it just kind of threw me for a loop when I got the results that I did. Anyway, thanks to the community for such quick answers, hopefully I didn't come off as too hostile in my first post!
Click to expand...
Click to collapse
You must not have read the disclaimer on the app. It says it may report false positives still.
Just saw the details on the new Mi Watch. As an OG Pebble purchaser (and owner of a Pebble Steel) I still like the rectangular form factor. So with a 3100, 1GB of RAM and a 570mAh battery, this thing looks like my perfect next watch. However it is only available In China, has a Chinese UI and no Google Play app store installed. Would any purchaser be able to side load the app store? Or use non-Xiaomi watch faces and apps? Any thoughts ?
I'm very interested in this watch, by the moment there are not much information
Maybe it's possible to install Wear OS apk's by adb
Enviado desde mi Pixel 3a mediante Tapatalk
I think it will be possible to install apps using abd because it based on Android wear so android wear apk is ment to work perfectly I guess
Sideloading apks should be possible. However it is running the chinese version of wear os and it has to be paired with the china android wear os app, too, which doesn't use google play services.
It's hard to say if stuff like gpay will function.
Apparently, the iOS version of wear os does not make this difference though.
Hopefully, sideloading the playstore would do the trick.
If the bootloader can be easily unlocked, we could flash roms or the global version.
with ram 1gb, processor snap wear 3100 + LTE and the price. I think it's great. Just waiting for how to install in global version rom on it
i have it here. tried to install a working music player for the last 4 hours. no luck.
erbsenmatsch said:
i have it here. tried to install a working music player for the last 4 hours. no luck.
Click to expand...
Click to collapse
Damn - sorry to hear that. I was super close to ordering one last week, but held off at the last minute until I could get a better sense for what was possible.
We're you able to get the play store installed, or were you trying to install the music players from apks? What happened when you tried to do the installs?
Hoping you have better luck moving forwards - would love to hear any updates.
1Markymark said:
Damn - sorry to hear that. I was super close to ordering one last week, but held off at the last minute until I could get a better sense for what was possible.
We're you able to get the play store installed, or were you trying to install the music players from apks? What happened when you tried to do the installs?
Hoping you have better luck moving forwards - would love to hear any updates.
Click to expand...
Click to collapse
You can easy install the play store with adb - but it won't work. Google apps witch need to sync your google account won't work too. The Watch want to sync the account with your phone .. but it will fail. All other apps seems to be fine (telegram etc.) . The biggest problem is that you can't use the Latin Gboard so you can only write Chinese :-/
Handwriting won't load other languages.
Another issue for me is, that I need to use my phone with English language .. if I set it to Germany , the watch will be completed in Chinese.
But I can say .. I love this watch
*Update*
Just found the "Wear Keyboard" apk from playstore .. it works, but you can only use "default keyboard language".
Also I managed to get Handwriting working (updated the apk).
Gerrett said:
You can easy install the play store with adb - but it won't work. Google apps witch need to sync your google account won't work too. The Watch want to sync the account with your phone .. but it will fail. All other apps seems to be fine (telegram etc.) . The biggest problem is that you can't use the Latin Gboard so you can only write Chinese :-/
Handwriting won't load other languages.
Another issue for me is, that I need to use my phone with English language .. if I set it to Germany , the watch will be completed in Chinese.
But I can say .. I love this watch
*Update*
Just found the "Wear Keyboard" apk from playstore .. it works, but you can only use "default keyboard language".
Also I managed to get Handwriting working (updated the apk).
Click to expand...
Click to collapse
Will get my hand on it very soon. Will try out things.
Update: got the watch, the chinese WearOS is really annoying, no Google app usable on watch: playstore, keep, google map and the most annoying is the Keyboard (I know imputing on watch is kind of stupid, but I want to do some quick responds if needed.) - English keyboard works partial (using the same wear keyboard above), no solution for other language.
Anyway, let hope there's global rom or some mod available, but I like the screen and the watch .
try bootloader oem unlock
but can't unlock bootloader
Yep, we need an unlocked bootloader !
installed com.android.vending_17.3.27 (Google Play Store) apk via adb
installed com.google.android.gms_19.6.29 (Google Play Services) apk via adb
but logcat still spits errors out, like something's missing or blocked:
Code:
11-30 22:52:51.827 1661 1675 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.os.UpdateLock.UPDATE_LOCK_CHANGED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
11-30 22:52:52.141 6106 6106 W Finsky : [2] dig.a(6): Null bundle, which breaks event chain!. Creating a new logging context.
11-30 22:52:52.203 6106 6114 W System : A resource failed to call end.
11-30 22:52:52.204 6106 6114 W System : A resource failed to call end.
11-30 22:52:52.223 6106 6106 E AndroidRuntime: FATAL EXCEPTION: main
11-30 22:52:52.223 6106 6106 E AndroidRuntime: Process: com.android.vending, PID: 6106
11-30 22:52:52.223 6106 6106 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.vending/com.google.android.finsky.wear.activities.MainActivity}: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.vending/cwc}; have you declared this activity in your AndroidManifest.xml?
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2914)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3049)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1809)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6680)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: Caused by: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.vending/cwc}; have you declared this activity in your AndroidManifest.xml?
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2005)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Instrumentation.execStartActivity(Instrumentation.java:1673)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.startActivityForResult(Activity.java:4587)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at eo.startActivityForResult(PG:4)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.startActivityForResult(Activity.java:4545)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at eo.startActivityForResult(PG:2)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.startActivity(Activity.java:4906)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.startActivity(Activity.java:4874)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at ewx.b(PG:35)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at ewx.a(PG:19)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at com.google.android.finsky.wear.activities.MainActivity.a(PG:5)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at ewx.onCreate(PG:6)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7144)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7135)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2894)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: ... 11 more
11-30 22:52:52.226 6106 6106 W Finsky.CrashDetector: Crash at version: 17.3.27-all [5] [PR] 278037957 cnt=4 ts=1575128953673 cause=RuntimeException fg=false".
11-30 22:52:52.238 1661 1944 W ActivityManager: Force finishing activity com.android.vending/com.google.android.finsky.wear.activities.MainActivity
11-30 22:52:52.342 1661 1675 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
11-30 22:52:52.343 1661 1675 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
11-30 22:52:52.545 1661 3363 W ActivityManager: Scheduling restart of crashed service com.android.vending/com.google.android.finsky.scheduler.JobSchedulerEngine$PhoneskyJobSchedulerJobService in 1000ms
Actually, Google play services and google service framework all are pre-installed on the watch, our biggest problem is same as Tic watch run China wearOS- we can't sync Google service from our phone to watch (due to the wearOS app used to connect the watch is china wearOS app).
And... There's not a way to unlock bootloader of the watch.
---------- Post added at 10:59 ---------- Previous post was at 10:14 ----------
erbsenmatsch said:
i have it here. tried to install a working music player for the last 4 hours. no luck.
Click to expand...
Click to collapse
There's mi music app in mi watch app store, you also need the china mi music app on your phone, can control music app from there.
Spotify control also works.
I have no intention of playing music directly from the watch....
ted presley said:
Actually, Google play services and google service framework all are pre-installed on the watch, our biggest problem is same as Tic watch run China wearOS- we can't sync Google service from our phone to watch (due to the wearOS app used to connect the watch is china wearOS app).
And... There's not a way to unlock bootloader of the watch.
---------- Post added at 10:59 ---------- Previous post was at 10:14 ----------
There's mi music app in mi watch app store, you also need the china mi music app on your phone, can control music app from there.
Spotify control also works.
I have no intention of playing music directly from the watch....
Click to expand...
Click to collapse
It's sounds like on tic watch they also didn't find a way to get google sync working?
Gerrett said:
It's sounds like on tic watch they also didn't find a way to get google sync working?
Click to expand...
Click to collapse
Yep, same annoying Chinese wearOS .... But it's fun if we can find a workaround [emoji28][emoji28].
Sent from my MI 9 using Tapatalk
ted presley said:
Yep, same annoying Chinese wearOS .... But it's fun if we can find a workaround [emoji28][emoji28].
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
Yep, let's find one
Tried to update the Wearos.apk .. but it will failed . No Idea what else we can do with a locked bootloader.
Someone need to unlock it
It seem fastboot oem unlock worksss...
All we need a working TWRP and.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MI 9 using Tapatalk
soralis0123 said:
try bootloader oem unlock
but can't unlock bootloader
Click to expand...
Click to collapse
It wont do anything after you click unlock?
Because there's no TWRP or zip rom yet, I haven't clicked on unlock button (due to a unlock one may break the official firmware update)
ted presley said:
Yep, same annoying Chinese wearOS .... But it's fun if we can find a workaround [emoji28][emoji28].
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
ted presley said:
It seem fastboot oem unlock worksss...
All we need a working TWRP and.....View attachment 4891937
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
It's not working .. I run through the unlock process, but device is still locked
Has anyone the changelog from the system update today?
What a pity to hear. So any notice? The device still be formatted but it's still lock? Or it tell error in unlocking?
Sent from my MI 9 using Tapatalk