Affichage des articles dont le libellé est seems. Afficher tous les articles
Affichage des articles dont le libellé est seems. Afficher tous les articles

vendredi 27 février 2015

Chrome seems to back history up at Google's, not matter what topic






Playing a lot with my Nexus 6, I came to want to try Chrome out a bit, for a change from Firefox. And I stumbled on what I consider a very big problem.

All my browsers, I set up to clear history, cache, cookies, etc, as soon as I stop using them. Be it for pr0n, bank managing, or mere general hygiene, I just want the browser to start fresh every time I launch it (I only keep bookmarks and some selected passwords).

Now, with Chrome, there doesn't seem to be any real way to wipe all the crap when exiting the browser. So I started playing with deleting of history, recent tabs and cookie files in /data/data/com.android.chrome/app_chrome, triggered by recent app swipe out (process stop) detection in Tasker. And it worked, for some time.

Problem, after having swiped Chrome out, deleted history files, and checked the history and recent tabs indeed seemed wiped, when tapping on the clock history icon, on the lower right part of the empty home page, then tapped on display whole history (translated from my language; YMWV). But OCD striked out, and I went back to the empty home page, to repeat the same process again. And again...

Until I ended up with the history appearing back, out of seemingly nowhere. So I wiped everything in the app itself (clear browser data), which works OK everytime. And now disconnected the phone from data before wiping the history and co files. And then went back to the history icon routine: now, without data, the history doesn't appear back. Then, I activated data anew, went on the repeated history checking, and bang: history appears right back...

So, when one tampers when Chrome history and co files, it seems Chrome restores those from the Internet, most probably from Google. Even though I set web history to off in my Google settings... Also tried History Cleaner Pro for root app, and end up with the same exact behaviour from Chrome. For what is worth, I use latest everything, factory 5.0.1, rooted, up to date Nexus 6.

Seriously: what's that crap?!?! Do you observe the same behaviour? Do you know of a way to teach hygiene to Chrome? Not sure I'll be touching the thing again though, even with a barge-pole... There may be a way to clean Chrome (would it be manually, in the app itself, which works as far as displaying information from previous sessions), but this experience tends to make me believe Chrome will save the history and all kind of crap at Google's, even if it doesn't display it anymore in the browser, even when you ask Google not to manage your history. And I surely won't have that. Back to Firefox, I am.






mardi 24 février 2015

Just Rooted and flashed CloudyG3 1.2 on my D851r and it seems like nothing changed topic






I just rooted, wiped, and flashed CloudyG3 1.2 for my D851r and it seems like i'm not even on a custom ROM. Is it supposed to feel like this? Where is all the power? I don't see any options for customizing my phone with different features. Where is the custom menu in settngs?

Moreover even though i have root access i cannot uninstall certain apps in the settings -> general -> apps. Some apps like LG Smartworld i can only disable but i cant uninstall them. I thought cloudy was supposed to be debloated, why does it include stuff like Music, and LG Smartworld, and QuickMemo+? I only chose to install google apps during the Aroma install, so why do these all still exist and how do i completely uninstall them? (not just disable).

Thanks!






lundi 23 février 2015

[I9305] Seems to have a blown Digitizer topic






I openend a thread over at the main forum for the SGS3 and boomboomer mentioned that it would be better to use this forum for the problem.

-------------

Quote:










Originally Posted by Drake008


I got an I-9305 yesterday.
On this device the touchfunction won't work. I still can use a mouse in recovery. In the OS itself there is now mouse.
I thought the one who got it before me had tampered with the devices internals but the screws are all without any scratches.
Could he/she had flashed something wrong on to this device and if so can it be "repaired"?





------------

Quote:










Originally Posted by boomboomer
(Post 59013143)

If touch doesn't work in both recovery and OS then the digitizer is blown, usually this happens when the kernel for another model is flashed.
There is no cure for a hardware fault, other than replace the screen assembly from a second hand handset or time for a new phone.
i9305 has a separate q&a section, mainly to prevent incorrect flashing.





-----------

How can I be sure to have the right kernel right now on the system? I mean the person who gave me the phone seems to have put a original Samsungrom on it which is stuck at the first setup screen with no mouse support.
As for germany there are 4 different versions for the stock rom. Even in Odin Mode under Current Binary and System Status there is just "Custom" stated.








Attached Thumbnails


Click image for larger version<br/><br/>Name:	whattoload.jpg<br/>Views:	N/A<br/>Size:	132.6 KB<br/>ID:	3179670
 

















samedi 21 février 2015

Album art seems funky on lock screen since 5.0 OTA?? topic






They said and claim album art is still on lollipop but what I notice is when I'm playing music and screen turns off when I turn it onto lock Screen to skip tracks from pandora from lock screen there isn't a > play or skip button or album art
It just like a notification just sitting on lock screen

Sent from my SM-G900T using XDA Free mobile app






vendredi 13 février 2015

TWRP seems to have some bugs... topic






Not quite sure exactly what's happening, but it's repeatable and noticeable and for anyone less-tech savvy might convince them they're bricked.

It seems to be when a zip comes with an installer (such as Android Revolution) - once the install starts it's fine as long as I touch the screen every few seconds, however if I don't touch it for a while, say when it's loading system files and then continue on with the installer and get to the end - the installer will exit gracefully then I will see the usual "unlock" for TWRP, and before I can hit it the screen will go completely black.

While it's in this state, the phone will not respond to anything. Even a hard reset (power+down) doesn't do a thing. The only way it signifies it's still alive is by running 'adb devices' when plugged into a computer, then adb reboot.






lundi 9 février 2015

[Q] [CM12] Surfaceflinger seems to block boot process topic






Hi,

I'm trying to port cm12 to htc one v, which doesn't have devs anymore, so I'm asking here.
The phone starts surfaceflinger and shows the bootanimation, then it does nothing:


Code:


--------- beginning of main
I/lowmemorykiller( 1680): Using in-kernel low memory killer interface
I/cm      ( 1696): ____ _  _ ____ _  _ ____ ____ ____ _  _ _  _ ____ ___
--------- beginning of system
I/Vold    ( 1682): Vold 2.1 (the revenge) firing up
D/Vold    ( 1682): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 1682): Check if PFE is activated on Boot
I/cm      ( 1697): |    \_/  |__| |\ | |  | | __ |___ |\ | |\/| |  | |  \
E/Cryptfs ( 1682): Bad magic for real block device /dev/block/platform/msm_sdcc.2/by-num/p26
E/Cryptfs ( 1682): Error getting crypt footer and key
I/cm      ( 1698): |___  |  |  | | \| |__| |__] |___ | \| |  | |__| |__/
I/SurfaceFlinger( 1687): SurfaceFlinger is starting
I/cm      ( 1701): Welcome to Android 5.0.2 / CyanogenMod-12-20150209-UNOFFICIAL-alpha_0.4-primou
I/SurfaceFlinger( 1687): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL  ( 1687): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL  ( 1687): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL  ( 1687): loaded /system/lib/egl/libGLESv2_adreno200.so
D/Vold    ( 1682): Volume sdcard0 state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 1682): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 65, PARTN 1
D/Vold    ( 1682): Volume sdcard0 state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/Adreno200-EGL( 1687): <qeglDrvAPI_eglInitialize:269>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051_msm8960_JB_VANILLA_CL2997615_release_AU (CL2997615)
I/Adreno200-EGL( 1687): Build Date: 04/11/13 Thu
I/Adreno200-EGL( 1687): Local Branch:
I/Adreno200-EGL( 1687): Remote Branch: quic/mako_jb_mr1
I/Adreno200-EGL( 1687): Local Patches: NONE
I/Adreno200-EGL( 1687): Reconstruct Branch: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051 +  NOTHING
I/gralloc ( 1687): using (fd=13)
I/gralloc ( 1687): id          = msmfb40_0
I/gralloc ( 1687): xres        = 480 px
I/gralloc ( 1687): yres        = 800 px
I/gralloc ( 1687): xres_virtual = 480 px
I/gralloc ( 1687): yres_virtual = 2400 px
I/gralloc ( 1687): bpp          = 32
I/gralloc ( 1687): r            =  0:8
I/gralloc ( 1687): g            =  8:8
I/gralloc ( 1687): b            = 16:8
I/gralloc ( 1687): width        = 52 mm (234.461533 dpi)
I/gralloc ( 1687): height      = 88 mm (230.909088 dpi)
I/gralloc ( 1687): refresh rate = 52429280.00 Hz
D/CALCFPS ( 1687): DEBUG_CALC_FPS: 0
D/CALCFPS ( 1687): period: 10
D/CALCFPS ( 1687): ignorethresh_us: 500000
D/CALCFPS ( 1687): DEBUG_CALC_FPS: 0
D/CALCFPS ( 1687): period: 10
D/CALCFPS ( 1687): ignorethresh_us: 500000
E/SELinux ( 1681): avc:  denied  { add } for service=display.hwcservice scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:system_server_service:s0 tclass=service_manager
I/Adreno200-C2D( 1687): <c2d_wrapper_init:126>: C2D2 initializing z180 version: libc2d2_z180.so
I/Adreno200-C2D( 1687): <c2d_wrapper_init:183>: C2D2 wrapper initialized successfully
I/hwcomposer( 1687): Initializing Qualcomm Hardware Composer
I/hwcomposer( 1687): MDP version: 400
I/hwcomposer( 1687): DYN composition threshold : 2.000000
I/hwcomposer( 1687): hwc_device_open: Faking Hardware VSYNC
I/SurfaceFlinger( 1687): Using composer version 1.0
I/hwcomposer( 1687): Initializing UEvent Listener Thread
I/hwcomposer( 1687): Initializing VSYNC Thread
W/SurfaceFlinger( 1687): no suitable EGLConfig found, trying a simpler query
I/SurfaceFlinger( 1687): EGL information:
I/SurfaceFlinger( 1687): vendor    : Android
I/SurfaceFlinger( 1687): version  : 1.4 Android META-EGL
I/SurfaceFlinger( 1687): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_lock_surface EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_EXT_create_context_robustness EGL_ANDROID_image_native_buffer EGL_ANDROID_recordable
I/SurfaceFlinger( 1687): Client API: OpenGL_ES
I/SurfaceFlinger( 1687): EGLSurface: 8-8-8-8, config=0x4
I/SurfaceFlinger( 1687): OpenGL ES informations:
I/SurfaceFlinger( 1687): vendor    : Qualcomm
I/SurfaceFlinger( 1687): renderer  : Adreno (TM) 205
I/SurfaceFlinger( 1687): version  : OpenGL ES 2.0 V@6.0 AU@04.02.02.60.051 (CL@2997615)
I/SurfaceFlinger( 1687): extensions: GL_EXT_debug_marker GL_AMD_compressed_ATC_texture GL_AMD_performance_monitor GL_AMD_program_binary_Z400 GL_EXT_robustness GL_EXT_texture_format_BGRA8888 GL_EXT_texture_type_2_10_10_10_REV GL_NV_fence GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_depth24 GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_get_program_binary GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_vertex_type_10_10_10_2 GL_OES_vertex_array_object GL_QCOM_alpha_test GL_QCOM_binning_control GL_QCOM_driver_control GL_QCOM_perfmon_global_mode GL_QCOM_extended_get GL_QCOM_extended_get2 GL_QCOM_tiled_rendering GL_QCOM_writeonly_rendering GL_AMD_compressed_3DC_texture GL_EXT_texture_filter_anisotropic
I/SurfaceFlinger( 1687): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger( 1687): GL_MAX_VIEWPORT_DIMS = 4096
E/cutils-trace( 1687): Error opening trace file: No such file or directory (2)
D/SurfaceFlinger( 1687): Set power mode=2, type=0 flinger=0x40662000
D/SurfaceFlinger( 1687): SF. shader cache generated - 26 shaders in 684.494873 ms
D/libEGL  ( 1787): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL  ( 1787): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL  ( 1787): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL( 1787): <qeglDrvAPI_eglInitialize:269>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051_msm8960_JB_VANILLA_CL2997615_release_AU (CL2997615)
I/Adreno200-EGL( 1787): Build Date: 04/11/13 Thu
I/Adreno200-EGL( 1787): Local Branch:
I/Adreno200-EGL( 1787): Remote Branch: quic/mako_jb_mr1
I/Adreno200-EGL( 1787): Local Patches: NONE
I/Adreno200-EGL( 1787): Reconstruct Branch: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051 +  NOTHING
E/cutils-trace( 1787): Error opening trace file: No such file or directory (2)
E/BootAnimation( 1787): couldn't find audio_conf.txt
W/BootAnimation( 1787): Audio service is not initiated.
D/BootAnimation( 1787): Use save memory method, maybe small fps in actual.
D/BootAnimation( 1787): Use save memory method, maybe small fps in actual.


I can kill surfaceflinger, and zygote starts, but then dex2oat fails.

This is my first android rom and I just wanna know how I may find the problem.

If you want, you can look at my device tree on github: https://github.com/AndroidPrimou/and...ee/cm-12.0-new, https://github.com/AndroidPrimou/and...ee/cm-12.0-new
Kernel: https://github.com/rastomanchik/andr...nel_htc_primou

Please help, I'm completely clueless :)