Htc bị lỗi android com systemui stopped unexpectedly năm 2024
Sau đó dùng Root Explorer 2.19 down tại:http://up.4share.vn/f/536161606164626b/Root_Explorer_2.19.apk Càii Root Explorer sau đó copy file Contacts vào thư mục system/app . Sau đó set permission cho file contacts.apk giống như mấy file trong system/app. Khởi động lại máy. Nếu còn bị như cũ thì vào Setting>App>All chọn các app nào có từ contact trong đó thì clear data, clear cache. Khởi động lại máy.
22-Mar-17 1:59:53 PM Reading common information 22-Mar-17 1:59:53 PM (bootloader) kernel: lk (bootloader) product: htc_pmeuhl (bootloader) version: 1.0 (bootloader) max-download-size: 1579200000 (bootloader) serialno: FA65SBN00146 (bootloader) current-slot: (bootloader) imei: 354261-- (bootloader) version-main: 2.41.400.5 (bootloader) boot-mode: download (bootloader) version-baseband: 1.0.U010241a@61226 (bootloader) version-bootloader: 1.0.0.0000 (bootloader) mid: 2PS620000 (bootloader) cid: HTC__059 all: Execution time is 15(ms) 22-Mar-17 1:59:53 PM Reading secure flag information 22-Mar-17 1:59:53 PM ... (bootloader) Device security level S-ON 22-Mar-17 1:39:18 PM Phone connected [FA65SBN00146] *** ADB mode 22-Mar-17 1:39:20 PM Please wait, preparing your phone... 22-Mar-17 1:39:25 PM HTC 10 detected 22-Mar-17 1:39:25 PM Android release: 7.1.1 22-Mar-17 1:39:25 PM Working in OS mode 22-Mar-17 1:39:26 PM Checking server connection... 22-Mar-17 1:39:26 PM Communicating with the XTC 2 Clip ... 22-Mar-17 1:40:27 PM Connecting to the server... 22-Mar-17 1:40:28 PM Error: Data format unexpected. Please try again now or contact support. Chia sẻ trang nàyHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails. Already on GitHub? Sign in to your account Closed krasnoj opened this issue Mar 1, 2015 · 23 comments Comments
Hi! Cell phone Android 4.0.3, HTC Rhyme When I start TextSecure the System first crashes with "Default Lock Screen" and then with SystemUI closes unexpectedly (German: "SystemUI wurde unerwarted beendet"). Then the header line including the clock disappears and the SystemUI is started again with the clock. This happens every time I start TextSecure. I already tried to reinstall and reflash the cell phone. But the problem still occurs. If you need any additional information, just tell me what you need. Cheers. The text was updated successfully, but these errors were encountered:
I'm unable to reproduce this and agree that this seems like a ROM bug. If you're running into this issue on a very popular non-stock Android ROM then it might be worth looking into a fix but in general we want to remain focused on compatibility with stock Android.
Hi! I just want to mention that the Bug occurs with the official upgrade for the HTC Rhyme cell phone. So there is no third party software involved. Steps I did: Take HTC Rhyme, upgrade to newest original firmware, activate encryption, install TextSecure. If TextSecure works on any other HTC with encryption enable I agree with closing the bug. In this case I think HTC broke my firmware, but if the problem occurs on all HTC the situation would be different.
thanks for the update @krasnoj, I'll reopen this but still don't have much of an idea how to resolve 0.o
I have the exact same problem on HTC EVO3D stock firmware 4.0.3. Also tried reinstalling but same thing happens while everything else works fine.
Same problem here on a HTC Incredible S, unmodified firmware (Android 4.0.4, HTC Sense 3.6). I've been using TextSecure for quite a while now, and I definitely did not see this in older versions of TextSecure. Maybe for the last six months. Unfortunately, I cannot remember with which version it started.
@swltr could you post a debug log? After the crash from the TS lock screen menu or advanced menu, when you don't use a passphrase
@McLoo Here's a log: https://gist.github.com/anonymous/5457b6f2a0c8bedef8a1 Until now, I noticed these crashes only occasionally when receiving and/or opening messages. Now I also caused a crash of "System UI" by selecting the debug log item in the advanced settings menu, and it seems like I can reproducibly make it crash when pushing the lock button in the notifications list to make TextSecure forget the passphrase. Please note that TextSecure itself does not crash - it keeps running. It's only "System UI" and sometimes "Default lock screen" that seems to be crashed by some interaction with TextSecure.
TestObject has both the HTC Rhyme and Evo 3D, self-assigning this with the intent of at least getting some more debug logs and identifying cause of the error.
test run on unmodified debug build of 27a5b7d, using an HTC EVO 3D from testobject.com. debug log: https://gist.github.com/rhodey/c5b2d82d768dd5f1bad2 this crash occurred without any user interaction, the app was installed by testobject's processes and then opened automatically, and then the crash occurs immediately. debug log should contain everything from boot to crash and after.
@krasnoj, @beanhr a search for htc evo 3d system ui has stopped unexpectedly returns a bunch of results, many claiming that uninstalling updates to the Facebook app or "Face Lock" solve the problem. Could you please try this out and let us know if installing TextSecure still results in a crash? I'm unable to test that case through any of these online test suites. forget that idea, thinking on this again it doesn't seem likely that would solve the issue. relevant parts of the debug log...
at this point I can't think of any way to proceed with this bug except to get our hands on a physical device, root it, and decompile the class if anyone has an affected device and is willing to retrieve this class, please consider this on my wishlist 🎅 rhodey changed the title Crash on Startup SystemUI and DefaultLockScreen HTC bug - "System UI has stopped unexpectedly. Would you like to tell HTC?"
I am affected by this and can't currently use Textsecure. How can I help? My HTC Desire S with Android 4.0.4 and HTC Sense 3.6 used to report the following every time a message was sent or received: "System UI has stopped unexpectedly. Would you like to tell HTC?" After todays deinstall/reinstall attempt it now crashes every time i try to install and register: "Connecting OK, Waiting for SMS verification OK, ...Registering with Server..." "Unfortunately, TextSecure has stopped. Report/OK" (Seems it wants to report to Google.) P.S. I'm not sure I understand what "Upgrade to AppCompat v22.1" means, but it seems it's not a thing I can do?
@tacMable Are you able to use adb in order to get a debug log of the registration crash?
It seems I managed to do that. The output of 'adb bugreport' is about 5MiB in size and it seems there are several credentials in there. Should I use your GPG key from 2007 to encrypt it? Otherwise, I could privately message you an http uri of my dump? Interactions: $adb reboot (device reboots, pin entered, wait some time, touch TextSecure icon) "The default lock screen has stopped unexpectedly, would you like to tell HTC?" / "No" (connect with TextSecure: enter phone number, Register) "connecting... waiting..." "unfortunately, textsecure has stopped" $adb bugreport > bugreport.txt
sure any of those options work for me
@rhodey , I have successfully extracted the class. What exactly would you need? The *.dex? The *.class? The decompiled code? I would really love to see a workaround for this problem...
@pascaldragon , has there been any answer/further interaction regarding this issue? @rhodey or anyone else trying to fix this would need the decompiled code of at least the class |