Hi Guys,
My TF700 has frozen on the CHROMI-X Asus bootup screen, and rather than wipe I wanted to know if there was anything to get it back on the road before I do that.
Many Thanks
Not nearly enough information for even a wild guess!
Rom/recovery /bootloader
What were you doing
Any sudden reboots
The more you tell us, the better your chances to get a meaningful answer....
Sent from my DROID4 using Tapatalk
berndblb said:
Not nearly enough information for even a wild guess!
Rom/recovery /bootloader
What were you doing
Any sudden reboots
The more you tell us, the better your chances to get a meaningful answer....
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I followed these steps when I flashed it, and it has been fine for a week:
http://forum.xda-developers.com/showthread.php?t=2223492
My daughter had been trying to use it and it had just hung, which it was still doing since I flashed it, although it was loads better than it had been with the stock ROM on.
It didnt really reboot, but like I said it occasionally froze, which it had done and so I tried to power cycle it, and then this happened.
IndieAce said:
I followed these steps when I flashed it, and it has been fine for a week:
http://forum.xda-developers.com/showthread.php?t=2223492
My daughter had been trying to use it and it had just hung, which it was still doing since I flashed it, although it was loads better than it had been with the stock ROM on.
It didnt really reboot, but like I said it occasionally froze, which it had done and so I tried to power cycle it, and then this happened.
Click to expand...
Click to collapse
I can get it into TWRP, but just wanted to know the best steps to get it back up and running without it taking too much time.
IndieAce said:
I can get it into TWRP, but just wanted to know the best steps to get it back up and running without it taking too much time.
Click to expand...
Click to collapse
If you have a good backup from TWRP, it should take only about 3 minutes to restore... Most of the time, users have a data corruption on their device. If it is the case, you must format your data partition and restore only your data from your backup. It should be back up and running again within 3 minutes. I think that it is the fastest way. Good luck..:fingers-crossed:
It would be really helpful if you could capture a logcat of the booting process other wise I can only recommend you wipe from TWRP and then reinstall. Obviously you will lose everything if you do this. Which is why you should always keep a nandroid backup in TWRP handy. I have no idea why it stopped booting without the logcat.
If nobody knows how to do a logcat there is Google for that But obviously drivers and adb are needed.
Once the device is plugged in to computer, power on device and wait for it to start looping at the splash screen image.
Give it another say 2 minutes minimum for ADB to kick in (it takes some time on the device when a boot loop occurs for logcat to start logging)
After about two minutes,
type adb devices
to ensure the device is listed.
Then type
adb logcat -v time > Bootloop.txt
wait about a good 3 - 5 minutes to allow EVERYTHING to be logged,
then press CTRL+C on the keyboard to stop the capturing process. then post the Bootloop.txt (it is in the directory where you launched the terminal window)
IndieAce said:
I followed these steps when I flashed it, and it has been fine for a week:
http://forum.xda-developers.com/showthread.php?t=2223492
My daughter had been trying to use it and it had just hung, which it was still doing since I flashed it, although it was loads better than it had been with the stock ROM on.
It didnt really reboot, but like I said it occasionally froze, which it had done and so I tried to power cycle it, and then this happened.
Click to expand...
Click to collapse
Friend! We would really like to help you. But without the necessary information you keep us in the dark!
If your tablet froze after installing CROMi-X, you did something wrong from the very beginning.
Tell us which Rom and version you had and have now, which boot loader version you have, which recovery and version.
And if you can manage, grab that logcat in adb and post the file.
Right now you are telling us: I have a car, it's making a funny noise and is not running well.
What are we supposed to do with that?
Sent from my K00C using Tapatalk
sbdags said:
It would be really helpful if you could capture a logcat of the booting process other wise I can only recommend you wipe from TWRP and then reinstall. Obviously you will lose everything if you do this. Which is why you should always keep a nandroid backup in TWRP handy. I have no idea why it stopped booting without the logcat.
Click to expand...
Click to collapse
Thanks for getting back to me.
I have attached the logcat - if you feel anything else will help - please let me know.
Cheers
IndieAce said:
Thanks for getting back to me.
I have attached the logcat - if you feel anything else will help - please let me know.
Cheers
Click to expand...
Click to collapse
Thank you for that! Which kernel were you using btw?
I think I can see the problem but don't know what causes it. @elesbb @_that any ideas?
Code:
01-18 10:25:10.000 E/AndroidRuntime( 2887): *** FATAL EXCEPTION IN SYSTEM PROCESS: UI
01-18 10:25:10.000 E/AndroidRuntime( 2887): java.lang.NullPointerException
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.media.AudioManager.registerRemoteControlDisplay(AudioManager.java:2172)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at com.android.internal.policy.impl.keyguard.KeyguardTransportControlView.onAttachedToWindow(KeyguardTransportControlView.java:247)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.View.dispatchAttachedToWindow(View.java:11933)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2415)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2422)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2422)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1192)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:989)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4351)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.Choreographer$CallbackRecord.run(Choreographer.java:749)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.Choreographer.doCallbacks(Choreographer.java:562)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.Choreographer.doFrame(Choreographer.java:532)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:735)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.os.Handler.handleCallback(Handler.java:725)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.os.Handler.dispatchMessage(Handler.java:92)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.os.Looper.loop(Looper.java:137)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.os.HandlerThread.run(HandlerThread.java:60)
01-18 10:25:10.130 E/AndroidRuntime( 3159): FATAL EXCEPTION: main
01-18 10:25:10.130 E/AndroidRuntime( 3159): java.lang.RuntimeException: Unable to start receiver com.asus.services.firmware.PreBootUpdateManager: java.lang.RuntimeException: Package manager has died
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.app.ActivityThread.handleReceiver(ActivityThread.java:2383)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.app.ActivityThread.access$1500(ActivityThread.java:141)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1310)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.os.Handler.dispatchMessage(Handler.java:99)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.os.Looper.loop(Looper.java:137)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.app.ActivityThread.main(ActivityThread.java:5039)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at java.lang.reflect.Method.invokeNative(Native Method)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at java.lang.reflect.Method.invoke(Method.java:511)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at dalvik.system.NativeStart.main(Native Method)
01-18 10:25:10.130 E/AndroidRuntime( 3159): Caused by: java.lang.RuntimeException: Package manager has died
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.app.ApplicationPackageManager.hasSystemFeature(ApplicationPackageManager.java:296)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at com.asus.services.firmware.FWScalar.isDeviceSupported(FWScalar.java:115)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at com.asus.services.firmware.PreBootUpdateManager.onPreBootCompleted(PreBootUpdateManager.java:121)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at com.asus.services.firmware.PreBootUpdateManager.onReceive(PreBootUpdateManager.java:79)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.app.ActivityThread.handleReceiver(ActivityThread.java:2376)
01-18 10:25:10.130 E/AndroidRuntime( 3159): ... 10 more
01-18 10:25:10.130 E/AndroidRuntime( 3159): Caused by: android.os.DeadObjectException
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.os.BinderProxy.transact(Native Method)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.content.pm.IPackageManager$Stub$Proxy.hasSystemFeature(IPackageManager.java:2858)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.app.ApplicationPackageManager.hasSystemFeature(ApplicationPackageManager.java:294)
01-18 10:25:10.130 E/AndroidRuntime( 3159): ... 14 more
01-18 10:25:10.130 E/AndroidRuntime( 3159): Error reporting crash
01-18 10:25:10.130 E/AndroidRuntime( 3159): android.os.DeadObjectException
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.os.BinderProxy.transact(Native Method)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:3344)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
01-18 10:25:10.130 E/AndroidRuntime( 3159): at dalvik.system.NativeStart.main(Native Method)
sbdags said:
I think I can see the problem but don't know what causes it. @elesbb @_that any ideas?
Click to expand...
Click to collapse
Is it something I can likely put right or is it a no go?
IndieAce said:
Is it something I can likely put right or is it a no go?
Click to expand...
Click to collapse
Well a format of /data in TWRP will definitely fix it but then you'll lose everything on the internal sd card.
You may be able to do this if you don't have a backup - it may not work as it may just backup the corrupted file(s). But you have nothing to lose.
In TWRP go to the backup menu - make sure you change from internal to external storage so it uses your micro sd for the backup. Also make sure you have a copy of CROMI-X to flash on the micro sd as well..
1. Do a back up to sd and make sure data and system are selected. You can choose the other if you want but they are not important
2. Wipe Menu and chose the format data partition
3. Enter yes to continue
4. After the format finishes go back home and restore
5. Restore the backup (or previous good backup)
6. Try booting - it may bring everything back to life
7. If it doesn't go back to TWRP and format data again
8. Flash CROMi-X and you'll have a working ROM but obviously you will have lost everything.
9. If you used titanium backup to make backups at any point you can obviously restore individual apps from that to get some stuff back
Steps 7, 8 will always get you back up and running.
When you have a working ROM always make some backups
sbdags said:
Thank you for that! Which kernel were you using btw?
I think I can see the problem but don't know what causes it. @elesbb @_that any ideas?
Code:
01-18 10:25:10.000 E/AndroidRuntime( 2887): *** FATAL EXCEPTION IN SYSTEM PROCESS: UI
01-18 10:25:10.000 E/AndroidRuntime( 2887): java.lang.NullPointerException
01-18 10:25:10.000 E/AndroidRuntime( 2887): at android.media.AudioManager.registerRemoteControlDisplay(AudioManager.java:2172)
01-18 10:25:10.000 E/AndroidRuntime( 2887): at com.android.internal.policy.impl.keyguard.KeyguardTransportControlView.onAttachedToWindow(KeyguardTransportControlView.java:247)
...
Click to expand...
Click to collapse
Hmm... the lockscreen media controls (the play/pause/next/previous buttons) are trying to register with the audio manager and this fails... that seems to be a consequence of this error (or an earlier instance of the same error):
Code:
01-18 10:26:25.830 F/SystemServer( 3997): BOOT FAILURE starting Audio Service
01-18 10:26:25.830 F/SystemServer( 3997): java.lang.ArithmeticException: divide by zero
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.rescaleIndex(AudioService.java:767)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.access$3900(AudioService.java:103)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService$VolumeStreamState.setAllIndexes(AudioService.java:2906)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.checkAllAliasStreamVolumes(AudioService.java:588)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.createStreamStates(AudioService.java:610)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.<init>(AudioService.java:502)
01-18 10:26:25.830 F/SystemServer( 3997): at com.android.server.ServerThread.run(SystemServer.java:636)
The source code for rescaleIndex is:
Code:
private int rescaleIndex(int index, int srcStream, int dstStream) {
return (index * mStreamStates[dstStream].getMaxIndex() + mStreamStates[srcStream].getMaxIndex() / 2) / mStreamStates[srcStream].getMaxIndex();
}
So apparently mStreamStates[srcStream].getMaxIndex() is zero. This is in line with the preceding log entries too:
Code:
01-18 10:26:25.820 W/AudioPolicyManagerBase( 3748): initStreamVolume() invalid index limits for stream 3, min 0, max 0
01-18 10:26:25.820 W/AudioPolicyManagerBase( 3748): initStreamVolume() invalid index limits for stream 4, min 0, max 0
01-18 10:26:25.820 W/AudioPolicyManagerBase( 3748): initStreamVolume() invalid index limits for stream 5, min 0, max 0
By the way - the beginning of the log is missing - it would be better to start logging immediately when the boot process starts. Why did you give that "wait 2 minutes" advice? Usually "adb logcat" should wait for the device to become available anyway and then start logging immediately.
_that said:
Hmm... the lockscreen media controls (the play/pause/next/previous buttons) are trying to register with the audio manager and this fails... that seems to be a consequence of this error (or an earlier instance of the same error):
Code:
01-18 10:26:25.830 F/SystemServer( 3997): BOOT FAILURE starting Audio Service
01-18 10:26:25.830 F/SystemServer( 3997): java.lang.ArithmeticException: divide by zero
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.rescaleIndex(AudioService.java:767)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.access$3900(AudioService.java:103)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService$VolumeStreamState.setAllIndexes(AudioService.java:2906)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.checkAllAliasStreamVolumes(AudioService.java:588)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.createStreamStates(AudioService.java:610)
01-18 10:26:25.830 F/SystemServer( 3997): at android.media.AudioService.<init>(AudioService.java:502)
01-18 10:26:25.830 F/SystemServer( 3997): at com.android.server.ServerThread.run(SystemServer.java:636)
The source code for rescaleIndex is:
Code:
private int rescaleIndex(int index, int srcStream, int dstStream) {
return (index * mStreamStates[dstStream].getMaxIndex() + mStreamStates[srcStream].getMaxIndex() / 2) / mStreamStates[srcStream].getMaxIndex();
}
So apparently mStreamStates[srcStream].getMaxIndex() is zero. This is in line with the preceding log entries too:
Code:
01-18 10:26:25.820 W/AudioPolicyManagerBase( 3748): initStreamVolume() invalid index limits for stream 3, min 0, max 0
01-18 10:26:25.820 W/AudioPolicyManagerBase( 3748): initStreamVolume() invalid index limits for stream 4, min 0, max 0
01-18 10:26:25.820 W/AudioPolicyManagerBase( 3748): initStreamVolume() invalid index limits for stream 5, min 0, max 0
By the way - the beginning of the log is missing - it would be better to start logging immediately when the boot process starts. Why did you give that "wait 2 minutes" advice? Usually "adb logcat" should wait for the device to become available anyway and then start logging immediately.
Click to expand...
Click to collapse
Yeah thought it might be useful to capture the log not too soon. Didn't realise it cuts off if waits too long.
OP did you change the Max number of volume steps in cromi control?
sbdags said:
Yeah thought it might be useful to capture the log not too soon. Didn't realise it cuts off if waits too long.
OP did you change the Max number of volume steps in cromi control?
Click to expand...
Click to collapse
Do you mean change the volume?
If you do then I did install Volume+ if thats what you might mean.
I am now flashing it again as the first steps failed, so I have lost everything, but thats my own fault for not taking a copy.
I have learnt from this mistake.
Which Kernel would you recommend?
IndieAce said:
Which Kernel would you recommend?
Click to expand...
Click to collapse
_that v4 is rock solid. Any of the _that kernels for that matter....
But if you don't want to overclock, go for v4
berndblb said:
_that v4 is rock solid. Any of the _that kernels for that matter....
But if you don't want to overclock, go for v4
Click to expand...
Click to collapse
I dont know what your or sbdags thoughts are on this but I was thinking of running from a high speed sd card (something like the sandisc extreme 64gb) at some point as I had read somewhere that they improve speed, so I will flash it again soon (obviously taking a backup this time, lol).
I am not sure I will overclock it, but it was quite laggy, but I am wondering if that was anything to do with setting up 3 user profiles (myself, the missus, and daughter).
Would I benefit from overclocking slightly?
Many Thanks
IndieAce said:
I dont know what your or sbdags thoughts are on this but I was thinking of running from a high speed sd card (something like the sandisc extreme 64gb) at some point as I had read somewhere that they improve speed, so I will flash it again soon (obviously taking a backup this time, lol).
I am not sure I will overclock it, but it was quite laggy, but I am wondering if that was anything to do with setting up 3 user profiles (myself, the missus, and daughter).
Would I benefit from overclocking slightly?
Many Thanks
Click to expand...
Click to collapse
Ah don't get the extreme series it won't work. Also multi user makes the tab very laggy. Nothing I can do about that other than recommend you only have one user. Sorry.
IndieAce said:
I dont know what your or sbdags thoughts are on this but I was thinking of running from a high speed sd card (something like the sandisc extreme 64gb) at some point as I had read somewhere that they improve speed, so I will flash it again soon (obviously taking a backup this time, lol).
I am not sure I will overclock it, but it was quite laggy, but I am wondering if that was anything to do with setting up 3 user profiles (myself, the missus, and daughter).
Would I benefit from overclocking slightly?
Many Thanks
Click to expand...
Click to collapse
3 people - one tablet. That works for you guys??????? Wow!
It would be a sure setup for domestic violence in my house
sbdags said:
Ah don't get the extreme series it won't work. Also multi user makes the tab very laggy. Nothing I can do about that other than recommend you only have one user. Sorry.
Click to expand...
Click to collapse
I read somewhere that the extreme one will work, but doesnt support the fast speeds (but is quicker than the ultra), is that not correct?
I there a way I can have 3 profiles, but actually log out of each profile, because as I understand it at the moment each profile is taking up memory, if they have been logged into since the device was power cycled is that correct?
Just had to help to cook tea, but now back on the tablet, and have chosen the Hunds one - let me know if anyone thinks I have made a bad choice?
Many Thanks
Related
Hello all,
In my noobishness I tried to install the HtcMusic.apk from the Hero ROM onto a G1 running the Google Ion ROM. Well it gave me a MISSING_SHARED_LIBRARY error so in my ignorance I thought that I would be able to find whatever libraries were missing and transfer them to the Ion build and reflash the update.zip. The update flashed but the apk still cannot be installed. Do I have the concept of libraries wrong here and should just realize that it's not possible without doing other things or am I still missing libraries that should be transferred?
Thanks =)
thelamacmdr said:
Hello all,
In my noobishness I tried to install the HtcMusic.apk from the Hero ROM onto a G1 running the Google Ion ROM. Well it gave me a MISSING_SHARED_LIBRARY error so in my ignorance I thought that I would be able to find whatever libraries were missing and transfer them to the Ion build and reflash the update.zip. The update flashed but the apk still cannot be installed. Do I have the concept of libraries wrong here and should just realize that it's not possible without doing other things or am I still missing libraries that should be transferred?
Thanks =)
Click to expand...
Click to collapse
just adp push the libHtcMusic_jni.so from /system/lib and the HtcMusic.apk to /system/apps and you'll be set.
so i was missing a lib because the update.zip i downloaded doesn't have that...the search begins
Can't find this .so too.
Lib
this one is from a 6.0
And you think this would work for it?
Bcause this lib isn't requiered in the hero build.. *irritated*
Ok I did
Code:
adb remount
adb push libhtcmusic_jni.apk system/lib
adb install HtcMusic.apk
I still get the shared library error, maybe I have to push it to somewhere else or update.zip with the library included?
First Post:,
I've actually been working on this too. I've managed to get it to install. I followed another thread, pushing some stuff from /system/etc/permission and Platform.xml for the HTC stuff. I used the same lib a1t linked (although pulled mine right from the rom).
Although when running it on the phone I get this fun little log message:
Code:
E/dalvikvm( 347): Could not find method android.provider.DrmStore.getDrmConstra
int, referenced from method com.htc.music.MusicUtils.getDrmStatus
W/dalvikvm( 347): VFY: unable to resolve static method 403: Landroid/provider/D
rmStore;.getDrmConstraint (Landroid/content/ContentResolver;Landroid/net/Uri;I)L
android/provider/DrmStore$DrmConstraint;
W/dalvikvm( 347): VFY: rejecting opcode 0x71 at 0x00aa
W/dalvikvm( 347): VFY: rejected Lcom/htc/music/MusicUtils;.getDrmStatus (Landr
oid/content/Context;Landroid/net/Uri;)I
W/dalvikvm( 347): Verifier rejected class Lcom/htc/music/MusicUtils;
D/AndroidRuntime( 347): Shutting down VM
W/dalvikvm( 347): threadid=3: thread exiting with uncaught exception (group=0x4
000fe70)
E/AndroidRuntime( 347): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime( 347): java.lang.VerifyError: com.htc.music.MusicUtils
E/AndroidRuntime( 347): at com.htc.music.HtcMusic.onStart(HtcMusic.java:
338)
E/AndroidRuntime( 347): at android.app.Instrumentation.callActivityOnSta
rt(Instrumentation.java:1205)
E/AndroidRuntime( 347): at android.app.Activity.performStart(Activity.ja
va:3490)
E/AndroidRuntime( 347): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2240)
E/AndroidRuntime( 347): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2284)
E/AndroidRuntime( 347): at android.app.ActivityThread.access$1800(Activi
tyThread.java:112)
E/AndroidRuntime( 347): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1692)
E/AndroidRuntime( 347): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 347): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 347): at android.app.ActivityThread.main(ActivityThrea
d.java:3948)
E/AndroidRuntime( 347): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 347): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 347): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:782)
E/AndroidRuntime( 347): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:540)
E/AndroidRuntime( 347): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 60): Sending signal. PID: 347 SIG: 3
I/dalvikvm( 347): threadid=7: reacting to signal 3
I/dalvikvm( 347): Wrote stack trace to '/data/anr/traces.txt'
W/ActivityManager( 60): Launch timeout has expired, giving up wake lock!
Not in the loop as far as the HTC builds go, but there'ls definitely something I'm missing. android.provider is in the sdk, but the DRM stuff isn't (or doesn't seem to be). I tried pushing a few more things to the phone, hoping for a solution, but I ran out of room, I don't have the new SPL.
I can't really tell the problem from looking at this ( I'm kind of inexperienced in the way of Java/Android Application Dev.). Did you push the whole entire library from the HTC Hero ROM or rather the libs that aren't in the Haykuro/JF 1.51
sherlok said:
First Post:,
I've actually been working on this too. I've managed to get it to install. I followed another thread, pushing some stuff from /system/etc/permission and Platform.xml for the HTC stuff. I used the same lib a1t linked (although pulled mine right from the rom).
Although when running it on the phone I get this fun little log message:
Code:
E/dalvikvm( 347): Could not find method android.provider.DrmStore.getDrmConstra
int, referenced from method com.htc.music.MusicUtils.getDrmStatus
W/dalvikvm( 347): VFY: unable to resolve static method 403: Landroid/provider/D
rmStore;.getDrmConstraint (Landroid/content/ContentResolver;Landroid/net/Uri;I)L
android/provider/DrmStore$DrmConstraint;
W/dalvikvm( 347): VFY: rejecting opcode 0x71 at 0x00aa
W/dalvikvm( 347): VFY: rejected Lcom/htc/music/MusicUtils;.getDrmStatus (Landr
oid/content/Context;Landroid/net/Uri;)I
W/dalvikvm( 347): Verifier rejected class Lcom/htc/music/MusicUtils;
D/AndroidRuntime( 347): Shutting down VM
W/dalvikvm( 347): threadid=3: thread exiting with uncaught exception (group=0x4
000fe70)
E/AndroidRuntime( 347): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime( 347): java.lang.VerifyError: com.htc.music.MusicUtils
E/AndroidRuntime( 347): at com.htc.music.HtcMusic.onStart(HtcMusic.java:
338)
E/AndroidRuntime( 347): at android.app.Instrumentation.callActivityOnSta
rt(Instrumentation.java:1205)
E/AndroidRuntime( 347): at android.app.Activity.performStart(Activity.ja
va:3490)
E/AndroidRuntime( 347): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2240)
E/AndroidRuntime( 347): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2284)
E/AndroidRuntime( 347): at android.app.ActivityThread.access$1800(Activi
tyThread.java:112)
E/AndroidRuntime( 347): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1692)
E/AndroidRuntime( 347): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 347): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 347): at android.app.ActivityThread.main(ActivityThrea
d.java:3948)
E/AndroidRuntime( 347): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 347): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 347): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:782)
E/AndroidRuntime( 347): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:540)
E/AndroidRuntime( 347): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 60): Sending signal. PID: 347 SIG: 3
I/dalvikvm( 347): threadid=7: reacting to signal 3
I/dalvikvm( 347): Wrote stack trace to '/data/anr/traces.txt'
W/ActivityManager( 60): Launch timeout has expired, giving up wake lock!
Not in the loop as far as the HTC builds go, but there'ls definitely something I'm missing. android.provider is in the sdk, but the DRM stuff isn't (or doesn't seem to be). I tried pushing a few more things to the phone, hoping for a solution, but I ran out of room, I don't have the new SPL.
Click to expand...
Click to collapse
looks like you're missing the DRM stuff.
libdrmdec_jni.so
libdrmdec.so
libdrm1_jni.so
libdrm1.so
and probably the DrmProvider.apk
If you get this working, def let us know. the music player from that rom is sexy.
I've actually been working on this too. I've managed to get it to install. I followed another thread, pushing some stuff from /system/etc/permission and Platform.xml for the HTC stuff. I used the same lib a1t linked (although pulled mine right from the rom).
Click to expand...
Click to collapse
Hmm what files from system/etc/permissions did you push all of them or just Platform.xml and com.Htc.framework.xml? Cause as far as i know that's the only difference I have from whatt you've been doing except I pushed all of the libraries.
Any of you guys have luck porting the white clock over to Ion? From Hero build or JF? I can get the white notifications, but the clock refuses to budge. Unfortunately my normal goto guy is a bit under the weather.
blackeyedbrian said:
looks like you're missing the DRM stuff.
libdrmdec_jni.so
libdrmdec.so
libdrm1_jni.so
libdrm1.so
and probably the DrmProvider.apk
If you get this working, def let us know. the music player from that rom is sexy.
Click to expand...
Click to collapse
Ok i decided to play with this a little bit.
the method "getDrmConstraint" that is missing, is part of /system/framework/framework.jar on the hero rom. how to get that working on the other builds? i have no idea =D
Anyone got it working now?
Still workin on it, I'm trying to figure out what needs to be transferred. I'm thinking about just transfering all the files that have different file sizes (might check the sums too). I'll get back once I find out.
Edit: Just saw the framework.jar; the files have a difference of 2 mill in file size....
Edit2: Restarted phone after push, it's installed now
thelamacmdr said:
Still workin on it, I'm trying to figure out what needs to be transferred. I'm thinking about just transfering all the files that have different file sizes (might check the sums too). I'll get back once I find out.
Edit: Just saw the framework.jar; the files have a difference of 2 mill in file size....
Edit2: Restarted phone after push, it's installed now
Click to expand...
Click to collapse
so u pushed the lib, apk, n what else? would you mind just clarifying how u got it to work?
I didn't get it to work yet but I did manage to install it, I'm trying to find the location of class com.htc.widget. If anyone can please point it out it would be much appreciated. Once I figure out what I did and then do it again I'll post how to do it.
So far I transferred all of the HTC made libs, platform.xml, com.htc.framework.xml, and libhtcmusic_jni.so
For obvious reasons I won't post the Hero Rom (to get the libs from) and I'm not sure if I'm going too far just trying to use the Music app.
sorry for double post
check the diffs between the two images, this file will show the differences and files that only appear in one image but not the other.
update --> ion
updatehero --> hero
*i removed ringtones and notifications ogg mp3 just to focus on the rest
How did you manage to get this text file? I've been doing it manually....comparing the two zip files.
EDIT: Ok logcat shows
Code:
Could not find class 'com.htc.widget.AboutDialog$Builder', referenced from method com.htc.music.BaseHtcMusic.onCreateDialog
this is followed by a series of verify errors. These classes are located in a lib somewhere I'm assuming?
EDIT2: No longer have class errors, pushed files from system/framework
now receive error
Code:
E/dalvikvm( 330): Could not find method android.provider.DrmStore.getDrmConstra
int, referenced from method com.htc.music.MusicUtils.getDrmStatus
My EVE seems to does this every couple days and then I have to wipe everything of the phone using "Fastboot -w". But I'd like to figure out why this is happening so I'm starting to log stuff using logcat through adb.
Here is what I think may be the issue but you tell me. I'm totally new to trying to debug this thing.
This is a series of Errors that occur when the android loop screen locks up and restarts the boot loop.
E/AndroidRuntime( 6118): java.lang.IllegalStateException: Cannot broadcast before boot completed
E/AndroidRuntime( 6118): at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:10389)
E/AndroidRuntime( 6118): at android.app.ApplicationContext.sendStickyBroadcast(ApplicationContext.java:930)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService.sendConnectedBroadcast(ConnectivityService.java:483)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService.handleConnect(ConnectivityService.java:568)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService.access$500(ConnectivityService.java:48)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService$MyHandler.handleMessage(ConnectivityService.java:714)
E/AndroidRuntime( 6118): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 6118): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:91)
E/AndroidRuntime( 6118): Crash logging skipped, no checkin service
E/installd( 1067): eof
E/installd( 1067): failed to read size
E/appproc ( 6155): Can't open data/nv/command
Can you provide more of the logcat? Particularly what comes before the error. Or even make a file of the whole process and upload the file?
Also, does this happen with one particular ROM or have you tried various ROMs?
That isn't all for the errors though so maybe I should just post the whole log as a link to the file.
I hope someone has some idea about this cause reloading everything on the phone is getting tiresome.
I haven't really tryied that many other roms. I did try the new Rogers beta rom (V10G_00.kdz) but I think it still did it.
Here is one of two logs that I recorded at boot time. They look pretty much the same.
View attachment log.txt
Thanks for all your help.
Note in this next log the lgesystemd error at the end is another area where the android loop starts over.
View attachment Log1.txt
Could this be a currupt firmware seeing as how it seems like its an LG process freezing up?
mazen912 said:
hello
i ported aosp 2.3.7 but can't boot after 2 weeks of trying
please dev's check it
thanks
Click to expand...
Click to collapse
MOD EDIT: Removed link since it destroys recovery...
ATTENTION! THIS SEEMS TO DESTROY THE RECOVERY!!!
I tried to reboot into feamod but this does not work. Using Odin right now to get back to a booting state.
Be careful!
Quoting from the Cyanogenmod Porting thread so I do not need to spam it.
As he wrote, it does not boot.
That's what my logcat spits out:
Code:
W/dalvikvm( 460): threadid=1: thread exiting with uncaught exception (group=0x4
0015560)
E/AndroidRuntime( 460): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 460): java.lang.UnsatisfiedLinkError: Cannot load library: li
nk_image[1962]: 458 could not load needed library 'libsystem_server.so' for 'l
ibandroid_servers.so' (link_image[1962]: 458 could not load needed library 'li
bcameraservice.so' for 'libsystem_server.so' (link_image[1962]: 458 could not
load needed library 'libseccameraadaptor.so' for 'libcameraservice.so' (link_ima
ge[1962]: 458 could not load needed library 'libcamera.so' for 'libseccameraad
aptor.so' (reloc_library[1311]: 458 cannot locate '_ZN7android7Overlay5setFdEi
'...
E/AndroidRuntime( 460): ))))
E/AndroidRuntime( 460): at java.lang.Runtime.loadLibrary(Runtime.java:45
5)
E/AndroidRuntime( 460): at java.lang.System.loadLibrary(System.java:554)
E/AndroidRuntime( 460): at com.android.server.SystemServer.main(SystemSe
rver.java:624)
E/AndroidRuntime( 460): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 460): at java.lang.reflect.Method.invoke(Method.java:5
07)
E/AndroidRuntime( 460): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:839)
E/AndroidRuntime( 460): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:597)
E/AndroidRuntime( 460): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 460): Sending signal. PID: 460 SIG: 9
I/Zygote ( 458): Exit zygote because system server (460) has terminated
E/AndroidRuntime( 460): Error reporting crash
E/AndroidRuntime( 460): java.lang.NullPointerException
E/AndroidRuntime( 460): at com.android.internal.os.RuntimeInit$UncaughtH
andler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 460): at java.lang.ThreadGroup.uncaughtException(Threa
dGroup.java:854)
E/AndroidRuntime( 460): at java.lang.ThreadGroup.uncaughtException(Threa
dGroup.java:851)
E/AndroidRuntime( 460): at dalvik.system.NativeStart.main(Native Method)
There seem to be some missing / not found files.
Hmm interesting development but I guess if he uses boot.img and recovery.img from Cyanogenmod port it could work?
broodplank1337 said:
Hmm interesting development but I guess if he uses boot.img and recovery.img from Cyanogenmod port it could work?
Click to expand...
Click to collapse
well we will never discover it if nobody will test it...
maybe I will do it, if I find the time for it.
stay tuned =)
ok guy's
it is just trying i'm not a dev guy
about recovery problem it is easy no need to use odin
when your phone not able to boot go to adb and push feamod recovery to sdcard
then
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
adb reboot recovery
---------- Post added at 06:19 PM ---------- Previous post was at 06:14 PM ----------
i hope some one explain from wintel_mac logcat
what i should to do to fix it?
i'll test it right now
unfortunally it doesn´t work ;(
i tried it with skywalkers kernel, cm dev boot img and it wouldn´t boot...
mazen912 would you kindly ask if skywalker will help you out?
the hope dies at last....
what kernel did you use??
nail16 said:
what kernel did you use??
Click to expand...
Click to collapse
the one which mazen put in and skyhigh v1.3
i use https://github.com/abbradar
to porting but i will change the kernel
mazen912 said:
ok guy's
it is just trying i'm not a dev guy
about recovery problem it is easy no need to use odin
when your phone not able to boot go to adb and push feamod recovery to sdcard
then
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
adb reboot recovery
Click to expand...
Click to collapse
I came up with that also, but as sdcard was not mounted (since vold is not executed at this early boot stage) I was not able to do that. However I did not check if /data was already there, I think it must have been there. And it should be RW.
So push it do /data if you experience the same problem and dd it with if=/data/recovery.img and it should work.
But of course Odin worked, too.
pffff... I can't download it! Every time download stops to 1% (because of very low speed (3-6kbs per second))
Please, someone pm me another download link if it is not big trouble. Thank's
geo_xar said:
pffff... I can't download it! Every time download stops to 1% (because of very low speed (3-6kbs per second))
Please, someone pm me another download link if it is not big trouble. Thank's
Click to expand...
Click to collapse
it is useless don't bother yourself
logcat attatched i hope some one can help me
Stock Android 4.4.3 KTU84L for HTC One M7
-Made from full system/boot dump of Google Play Edition HTC One 4.4 KTU84L.H4
-Rooted with SuperSU 1.94 by Chainfire
-Busybox installed
-Odexed (for ART compatibility and possible minor OTA support)
Requirements
-GSM HTC One (m7ul/m7tmo/m7att)
-Latest Custom Recovery with 4.4 support (TWRP 2.6.3.3+, CWR 6.0.4.3+)
-S-OFF (SuperSID or GoogleSID)
Features
-Stock Android 4.4.3 w/ Google Apps
-ART capability
-Tap to Pay (Google Wallet)
-Beats Audio toggle in sound settings
Credits
-Chainfire, for SuperSU 1.94 (working on 4.4.3)
Changelog
-Android 4.4 features can be found (here)
Screenshots
{
"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"
}
Instructions
-Do a factory reset (unless coming from previous GPe ROM, then just wipe cache/dalvik)
-Install with TWRP or CWR
Downloads
MD5 (bigxie_m7_GPe_KTU84L_odexed-unsigned.zip) = 128abf3d8906b20cd03c374dbc7e1d25
http://www.androidfilehost.com/?fid=23501681358542399 - AFH
https://mega.co.nz/#!DMkD3QIZ!O8CJXzRACE5_QVAh6sUSywkaJHrqizQHSEYnjOm2f7g - Mega
Older Version Downloads
MD5 (bigxie_m7_GPe_KRT16S_odexed-signed.zip) = 5c9f5c46921e0824dcd75db3927f92a0
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_KRT16S_odexed-signed.zip - Goo.im
https://mega.co.nz/#!3BtCBD6T!ViZfS1MwhR4ttcPEkB3XrDVv9Asardy4e01UJO-5ZB0 - Mega
Radio
http://www.mediafire.com/download/hl9lphiibp51i1w/RadioUpdate_4T.21.3218.21_10.16.1718.01L.zip
MD5 (bigxie_m7_GPe_JWR66V_odexed-signed.zip) = bac188e3b7df88cac7285e2b5e1950e7
https://mega.co.nz/#!DBNGCRRT!fPOi00s-e47XkpODR6uhHCVo7hRyuKVM-iRWIUfWldw
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_JWR66V_odexed-signed.zip
Deodexed version - provided by Whitehawkx
http://goo.im/devs/Whitehawkx/m7/m7_GPe_JWR66V_deodexed-signed.zip
Radio - GE_Radio_4A.18.3263.15_10.38h.1157.04L.zip
https://mega.co.nz/#!HdwxkQqC!TgSeIFmErtLL8iJkpzdR5ThAPn8S0U5BmoEZKrJ_87w
faux123 Google Edition Kernel - Use this if you want additional features such as logo2menu, sweep2wake, etc.
http://forum.xda-developers.com/showthread.php?t=2255900
MD5 (bigxie_m7_GPe_odexed_stock-7-7-13.zip) = 1d36d5a70703018b4fa4ed4f97cbeba4
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_odexed_stock-7-7-13.zip
https://mega.co.nz/#!HJ8jlBJB!OJd7Sl7LrAJC2d6VT4SpJhoxGRpGbn1bE-Dl9TB7lfI
Deodexer - Requires flashing ROM first!
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_deodexer.zip
Radio
http://goo.im/devs/bigxie/m7/Radio_4A.17.3250.14_10.39.1150.04L.zip
Tbalden Google Edition Kernel - Use this if you want additional features such as logo2menu, sweep2wake, etc.
http://forum.xda-developers.com/showthread.php?t=2307371
MD5 (bigxie_m7_GPe_odexed_tbalden.zip) = 42bb792149e08188030271c745223a61
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_odexed_tbalden.zip
ROM Mirrors - Mirrors are appreciated and I will try to update the OP with them as promptly as I can
http://www.4shared.com/zip/4MTwPwsZ/bigxie_m7_GPe_odexed_tbalden.html
https://mega.co.nz/#!F5FWSDyI!SZjiLxEn2QZ_5iciXc9EQUaiKDBYClohVkId-jRxqBo
http://www.uploadmagnet.com/b9vw9c8xa5kv/bigxie_m7_GPe_odexed_tbalden.zip
http://d-h.st/knJ
https://mega.co.nz/#!tJFQFIab!PcsmZHK8HszM9E9jzXAZyw6jNgYLWE6M6cj3lLmwSYw
http://www.uploadmagnet.com/zbwqv5zjoz1s/bigxie_m7_GPe_odexed_tbalden.zip
http://mirror.lag.re/bigxie_m7_GPe_odexed_tbalden.zip
http://htcfanboys.com/download/theDroidfanatic/?action=list&file=5474
Frequently Asked Questions + Other Resources
Frequently Asked Questions
Q: Where's my lock screen?
A: For some reason, HTC chose to disable it by default. Go into security settings and enabled slide, pin, whatever. While you're in there, you may want to enable lock screen widgets as well.
Q: How do I get that sweet launcher from the Nexus 5? I thought that came with KitKat?
A: It's currently only for Nexus 5, however it will install just fine on this ROM. Get it here.
The following questions are quite outdated and will be hidden:
Q: Can so and so feature from Sense be ported to this ROM?
A: Most likely no, you'll have to find a third party solution in the Play Store, or if none exists, live without the feature or return to Sense.
Q: Does the IR blaster work?
A: Yes, it is working as of the 4.3 update!
Q: How do I remove the 3-dot legacy menu?
A1: Download TricksterMod Kernel app from the Play Store, scroll to Specifics, 'Screen Wake Control', switch on 'Disable 3Dot Menu', hit the check mark at the top right, and reboot your phone.
A2: Alternatively, if you know how to edit your build.prop with Root Explorer or something comparable, add "qemu.hw.mainkeys = 1" to the bottom of the file, save and reboot.
Q: Is the included kernel the official GPe ROM kernel?
A: Yes, it is the stock kernel with the ramdisk edited to be debuggable and insecure.
Q: Is the camera quality better or worse than Sense?
A: The OS gets the exact same raw data from the sensor in this ROM as it does in Sense, so the difference is in post processing. It is generally agreed that the photos are comparable to Sense except in really low light, where Sense's post processing is a little bit better.
Q: I don't have an English keyboard? How do I proceed?
A1: As a workaround, you can use the Korean keyboard to type English to get far enough into the Play Store and download an alternative keyboard.
A2: Alternatively, if you know how, you can switch your CID to GOOGL001 and the keyboard should show up now.
Q: How do I take a screenshot?
A: Press and hold power + volume down (at the same time) and don't let go until the screenshot animation and sound play (it will be obvious, takes perhaps a little over 1 second of holding down the buttons).
Q: Has anyone made such and such theme/mod/feature?
A: It would be prudent to check the correct respective forum first (i.e 'Themes and Apps' for themes, 'Original Development' for kernels, etc.)
Q: Can this get OTA updates directly?
A: No.
Q: Is Google Wallet compatible?
A: Not at the moment, and most likely it won't ever be as the HTC One is missing the hardware secure element required by Wallet.
Videos - These are outdated as of 8/5/13 (for the 4.2.2 build only, but may still have pertinent info!)
Installation by Devicecustomizer
Review by Devicecustomizer
Review by krazygreen
When will we be able to FULLY convert to a Google Edition and receive OTA updates etc.?
barkmarkin said:
When will we be able to FULLY convert to a Google Edition and receive OTA updates etc.?
Click to expand...
Click to collapse
Probably when devs start receiving the device from Google Play
Link is up, please mirror, thx!
barkmarkin said:
When will we be able to FULLY convert to a Google Edition and receive OTA updates etc.?
Click to expand...
Click to collapse
Really? The device itself isn't even in the hands of people who ordered it, and we only just got a hold of a system dump today. Slow down and calm down.
mine will complete soon. OP can I mirror it?
ultimatepichu said:
mine will complete soon. OP can I mirror it?
Click to expand...
Click to collapse
Yes, please.
Make sure the md5 checks out before you reup.
MD5 (bigxie_m7_GPe_odexed_tbalden.zip) = 42bb792149e08188030271c745223a61
bigxie said:
Yes, please.
Click to expand...
Click to collapse
I'll just make a torrent lol, if you're okay with that. Seems like the only way to manage the demand currently.
Did you manage to fix the data usage bigxie? I'm looking into but won't if you found the cause
Nice to see this happening so fast! HTC is going the easiest way, Sense and Google Edition can use the same kernel
tischn said:
Thank you soo much. I will flash it as soon as i'm at home.
and p.s. You have written the wrong date in the Title.
Click to expand...
Click to collapse
It's definitely June 28th in China
bbedward said:
Did you manage to fix the data usage bigxie? I'm looking into but won't if you found the cause
Click to expand...
Click to collapse
Nope, seems like the entire entry is just missing from Settings. Not sure, but it may be a bug with the GPe ROM? I mean IR isn't working yet either, they might have rushed this (as the One GPe was announced later than the GS4).
Here's the exception, when launching data usage, for reference.
Code:
W/dalvikvm( 4350): threadid=1: thread exiting with uncaught exception (group=0x41e1eba0)
E/EmbeddedLogger( 728): App crashed! Process: com.android.settings
E/EmbeddedLogger( 728): App crashed! Package: com.android.settings v17 (4.2.2-eng..20130622.034104)
E/EmbeddedLogger( 728): Application Label: Settings
D/InputManager( 728): setFocusedApplication Exception: java.lang.NullPointerException
E/AndroidRuntime( 4350): FATAL EXCEPTION: main
E/AndroidRuntime( 4350): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings$DataUsageSummaryA
ctivity}: java.lang.IllegalStateException: Bandwidth module disabledE/AndroidRuntime( 4350): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2463)
E/AndroidRuntime( 4350): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2520)
E/AndroidRuntime( 4350): at android.app.ActivityThread.access$600(ActivityThread.java:162)
E/AndroidRuntime( 4350): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1366)
E/AndroidRuntime( 4350): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4350): at android.os.Looper.loop(Looper.java:158)
E/AndroidRuntime( 4350): at android.app.ActivityThread.main(ActivityThread.java:5751)
E/AndroidRuntime( 4350): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 4350): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 4350): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1083)
E/AndroidRuntime( 4350): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:850)
E/AndroidRuntime( 4350): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4350): Caused by: java.lang.IllegalStateException: Bandwidth module disabled
E/AndroidRuntime( 4350): at android.os.Parcel.readException(Parcel.java:1442)
E/AndroidRuntime( 4350): at android.os.Parcel.readException(Parcel.java:1388)
E/AndroidRuntime( 4350): at android.net.INetworkStatsService$Stub$Proxy.openSession(INetworkStatsService.java:180)
E/AndroidRuntime( 4350): at com.android.settings.DataUsageSummary.onCreateView(DataUsageSummary.java:302)
E/AndroidRuntime( 4350): at android.app.Fragment.performCreateView(Fragment.java:1785)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:887)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1059)
E/AndroidRuntime( 4350): at android.app.BackStackRecord.run(BackStackRecord.java:682)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1437)
E/AndroidRuntime( 4350): at android.app.Activity.performStart(Activity.java:5174)
E/AndroidRuntime( 4350): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2436)
E/AndroidRuntime( 4350): ... 11 more
W/ActivityManager( 728): Force finishing activity com.android.settings/.Settings$DataUsageSummaryActivity
I cant help it but asking for someone please report battery life with BetterBatteryStat once done downloading & testing.
thanks for your time guys.
I hope they included flash to focus this time.
This is using a custom kernel and not the stock HTC kernel. Does that mean we don't have a boot.img dump from the GE?
Since this is using a compiled kernel does it still have the same glitches as the existing AOSP roms? My understanding was most of the bugs were in the kernel at this point.
Specifically I'm referring to:
- A2DP packet loss and disconnects
- poor bluetooth connectivity (long time to switch devices and having to toggle bluetooth on/off to reconnect)
- Call audio not working over bluetooth
- poor GPU performance compared to Sense
bbedward said:
Here's the exception, when launching data usage, for reference.
Click to expand...
Click to collapse
Code:
java.lang.IllegalStateException: Bandwidth module disabled
?????????? Well there's your problem.
where should i upload to? I'm doing 4shared and dev-host now...
bbedward said:
Here's the exception, when launching data usage, for reference.
Code:
W/dalvikvm( 4350): threadid=1: thread exiting with uncaught exception (group=0x41e1eba0)
E/EmbeddedLogger( 728): App crashed! Process: com.android.settings
E/EmbeddedLogger( 728): App crashed! Package: com.android.settings v17 (4.2.2-eng..20130622.034104)
E/EmbeddedLogger( 728): Application Label: Settings
D/InputManager( 728): setFocusedApplication Exception: java.lang.NullPointerException
E/AndroidRuntime( 4350): FATAL EXCEPTION: main
E/AndroidRuntime( 4350): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings$DataUsageSummaryA
ctivity}: java.lang.IllegalStateException: Bandwidth module disabledE/AndroidRuntime( 4350): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2463)
E/AndroidRuntime( 4350): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2520)
E/AndroidRuntime( 4350): at android.app.ActivityThread.access$600(ActivityThread.java:162)
E/AndroidRuntime( 4350): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1366)
E/AndroidRuntime( 4350): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4350): at android.os.Looper.loop(Looper.java:158)
E/AndroidRuntime( 4350): at android.app.ActivityThread.main(ActivityThread.java:5751)
E/AndroidRuntime( 4350): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 4350): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 4350): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1083)
E/AndroidRuntime( 4350): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:850)
E/AndroidRuntime( 4350): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4350): Caused by: java.lang.IllegalStateException: Bandwidth module disabled
E/AndroidRuntime( 4350): at android.os.Parcel.readException(Parcel.java:1442)
E/AndroidRuntime( 4350): at android.os.Parcel.readException(Parcel.java:1388)
E/AndroidRuntime( 4350): at android.net.INetworkStatsService$Stub$Proxy.openSession(INetworkStatsService.java:180)
E/AndroidRuntime( 4350): at com.android.settings.DataUsageSummary.onCreateView(DataUsageSummary.java:302)
E/AndroidRuntime( 4350): at android.app.Fragment.performCreateView(Fragment.java:1785)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:887)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1059)
E/AndroidRuntime( 4350): at android.app.BackStackRecord.run(BackStackRecord.java:682)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1437)
E/AndroidRuntime( 4350): at android.app.Activity.performStart(Activity.java:5174)
E/AndroidRuntime( 4350): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2436)
E/AndroidRuntime( 4350): ... 11 more
W/ActivityManager( 728): Force finishing activity com.android.settings/.Settings$DataUsageSummaryActivity
Click to expand...
Click to collapse
Wait, so you already have it? Would you make a mirror for us please ?
ultimatepichu said:
where should i upload to? I'm doing 4shared and dev-host now...
Click to expand...
Click to collapse
MEGA.CO.NZ plzzzzz
So every 10 minutes my Z5 flashes a red LED 4 times and then reboots itself. I'm rooted and running AndroPlus Kernel v2, xposed installed. Any idea what could be causing this?
ChrissehB said:
So every 10 minutes my Z5 flashes a red LED 4 times and then reboots itself. I'm rooted and running AndroPlus Kernel v2, xposed installed. Any idea what could be causing this?
Click to expand...
Click to collapse
Downoald and Install the PC Companion (for drivers) then Flashtool.
Download original FTF file image from General section and flash it
Okay I reflashed without wiping data partition and it's still happening. If I boot into safe mode it stops happening so it's something I have installed but I can't find what. I've uninstalled everything that I've recently installed and can't figure it out. Any ideas at all?
EDIT:
I managed to fix this issue so I'm posting for anyone who may have the same issue in the future. I went through all different troubleshooting steps, booting safe mode, without sim card, without microsd. And without microsd it was perfectly fine. I managed to boot into safe mode and transferred all apps stored on the sd card to the phone and it's working perfectly again. I'm not sure which app was causing it to reboot every 10 minutes but something was.
i removed my last 2 installed apps. reflashed kernel and wipe dalvik and cache partition. seem to be fixed the problem for me ( no reboot last 2 hours)
What, exactly, does the 4 red blinks and reboot mean?
My Z5 did this once, but I've had it for a few months now. Completely stock.
I had a Z4 Tablet which did this all the time from brand new. Even did it on first boot, then randomly, several times a day. I tried reflashing it a couple of times, but it kept doing it. O2 replaced it, and the new one has never done it.
But, I still don't know what it means?
ok problem not fixed but i got a crash dump, could someone help me with that ?
the probleme started in the last 5 days.
Logcat Log
--------- beginning of crash
02-04 17:52:51.982 E/AndroidRuntime( 2330): *** FATAL EXCEPTION IN SYSTEM PROCESS: NetworkPolicy
02-04 17:52:51.982 E/AndroidRuntime( 2330): java.lang.IllegalArgumentException: tried recording negative data
02-04 17:52:51.982 E/AndroidRuntime( 2330): at android.net.NetworkStatsHistory.recordData(NetworkStatsHistory.java:304)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at android.net.NetworkStatsHistory.recordHistory(NetworkStatsHistory.java:377)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at android.net.NetworkStatsHistory.recordEntireHistory(NetworkStatsHistory.java:353)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.server.net.NetworkStatsCollection.recordHistory(NetworkStatsCollection.java:224)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.server.net.NetworkStatsCollection.read(NetworkStatsCollection.java:288)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.server.net.NetworkStatsCollection.read(NetworkStatsCollection.java:262)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.server.net.NetworkStatsRecorder$CombiningRewriter.read(NetworkStatsRecorder.java:303)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.internal.util.FileRotator.readFile(FileRotator.java:372)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.internal.util.FileRotator.rewriteSingle(FileRotator.java:242)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.internal.util.FileRotator.rewriteActive(FileRotator.java:184)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.server.net.NetworkStatsRecorder.forcePersistLocked(NetworkStatsRecorder.java:240)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.server.net.NetworkStatsRecorder.maybePersistLocked(NetworkStatsRecorder.java:227)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.server.net.NetworkStatsService.advisePersistThreshold(NetworkStatsService.java:665)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at com.android.server.net.NetworkPolicyManagerService$14.handleMessage(NetworkPolicyManagerService.java:2137)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at android.os.Handler.dispatchMessage(Handler.java:98)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at android.os.Looper.loop(Looper.java:211)
02-04 17:52:51.982 E/AndroidRuntime( 2330): at android.os.HandlerThread.run(HandlerThread.java:61)
02-04 17:52:51.985 E/GTalkService( 8508): connectionClosed: no XMPPConnection - That's strange!
------------system_app_crash.txt ----------------
Process: com.android.settings
PID: 13810
Flags: 0x40c8be45
Package: com.android.settings v22 (5.1.1-1)
Build: Sony/E6653/E6653:5.1.1/32.0.A.6.200/2002872085:user/release-keys
UUID: dad9c001-b7ec-4d32-8ce8-f8305e3d76c1
java.lang.RuntimeException: An error occured while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:304)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:355)
at java.util.concurrent.FutureTask.setException(FutureTask.java:222)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.IllegalArgumentException: tried recording negative data
at android.os.Parcel.readException(Parcel.java:1559)
at android.os.Parcel.readException(Parcel.java:1505)
at android.net.INetworkStatsSession$Stub$Proxy.getSummaryForAllUid(INetworkStatsSession.java:257)
at com.android.settings.net.SummaryForAllUidLoader.loadInBackground(SummaryForAllUidLoader.java:62)
at com.android.settings.net.SummaryForAllUidLoader.loadInBackground(SummaryForAllUidLoader.java:27)
at android.content.AsyncTaskLoader.onLoadInBackground(AsyncTaskLoader.java:312)
at android.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:69)
at android.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:57)
at android.os.AsyncTask$2.call(AsyncTask.java:292)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
... 3 more