• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Rom][5-26-12]Broken Out Spectrum 3.0 w/ Blitzkrieg Kernel

Could be, didn't actually try re-dowloading. I'll wait till MTM updates then reflash that and see. Since none of you had anything similar I won't worry about it

I'm not quite sure what the problem is, but I would try to flash back to v4 then try BO.
 
Does anyone know if someone that has recived the ota v5 update and is running stock has the problem with no bluetooth
 
No one has received the ota. It has been pulled.

I haven't found any official notes about the update being pulled, but I would not be surprised if this issues was found in closed beta testing and there for stopped it from being pushed public. As it is, the update file is still sitting on their server.
 
I haven't found any official notes about the update being pulled, but I would not be surprised if this issues was found in closed beta testing and there for stopped it from being pushed public. As it is, the update file is still sitting on their server.

This screenshot shows that it was put on hold with no date provided. I also assume they found a major flaw that they needed to go back to the drawing board for.
http://i.imgur.com/sMbVA.jpg
 
quick question:
when there's an update, is it required to reflash from stock or can we just flash the update?


CWM will not allow you to take ota's. So you would have to flash back to stock recovery. If your running a custom Rom though, there is no need to take ota's.
 
I very highly doubt that. 32GB is bigger than windows xp, vista, and 7 combined.

you are close, maybe after a clean install with no updates, or on standard edition, but both my windows and vista installs were over 20GB after service pack and update installs (ultimate edition on both, no extra language packs), no extra applications added. And I am just talking about the c:\windows directory. 6 months after install my c:\windows directory in win 7 is 28GB

Windows (since vista) keeps a hidden cache of all the updates in the c:\windows folder in case you delete the normal cache, I assume, since if you delete the cache you can not update any of the installed components as the install packages are required for future updates to install (learned this the hard way). It causes failures with windows update and manually attempting to update giving an error that it cannot find the source file. Examples Ms office and java SE (both a plague on my existence at work, because of severely out of date installs needing to be updated, but the cache was deleted by someone years ago. I cannot even get them to uninstall...)
 
you are close, maybe after a clean install with no updates, or on standard edition, but both my windows and vista installs were over 20GB after service pack and update installs (ultimate edition on both, no extra language packs), no extra applications added. And I am just talking about the c:\windows directory. 6 months after install my c:\windows directory in win 7 is 28GB

Windows (since vista) keeps a hidden cache of all the updates in the c:\windows folder in case you delete the normal cache, I assume, since if you delete the cache you can not update any of the installed components as the install packages are required for future updates to install (learned this the hard way). It causes failures with windows update and manually attempting to update giving an error that it cannot find the source file. Examples Ms office and java SE (both a plague on my existence at work, because of severely out of date installs needing to be updated, but the cache was deleted by someone years ago. I cannot even get them to uninstall...)

Wow. I had no idea it was that big. I just checked my windows folder on my laptop with vista ultimate 64 and it's 25.5 GB Not sure how big windows 7 ultimate 64 is which I have on my desktop because my cpu fan is broke right now and I have it turned off. But yea...I had no idea they were that big now lol. I think I remember xp being around 5GB but it's been 6 years since I've used xp.


But my main point was no way a phone has a 32GB update.
 
are you updating broken out anymore mt, or is this you final build until ICS comes out? Not blaming you if it is I was just wondering if you were still working on it.
 
I think I found the culprit for the random reboots. If you're using ADW and are getting reboots, it's likely ADW throwing java errors: ADW Error - Pastebin.com

Cause :
=======
java.lang.RuntimeException: system server dead?
at
android.appwidget.AppWidgetManager.getAppWidgetInfo(AppWidgetManager.java:332)
at org.adwfreak.launcher.Launcher.a(SourceFile:2537)
at org.adwfreak.launcher.Launcher.a(SourceFile:96)
at org.adwfreak.launcher.fc.handleMessage(SourceFile:3419)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3701)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:895)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:653)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at
com.android.internal.appwidget.IAppWidgetService$Stub$Proxy.getAppWidgetInfo(IAppWidgetService.java:440)
at
android.appwidget.AppWidgetManager.getAppWidgetInfo(AppWidgetManager.java:321)
... 11 more
android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at
com.android.internal.appwidget.IAppWidgetService$Stub$Proxy.getAppWidgetInfo(IAppWidgetService.java:440)
at
android.appwidget.AppWidgetManager.getAppWidgetInfo(AppWidgetManager.java:321)
at org.adwfreak.launcher.Launcher.a(SourceFile:2537)
at org.adwfreak.launcher.Launcher.a(SourceFile:96)
at org.adwfreak.launcher.fc.handleMessage(SourceFile:3419)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3701)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:895)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:653)
at dalvik.system.NativeStart.main(Native Method)
 
are you updating broken out anymore mt, or is this you final build until ICS comes out? Not blaming you if it is I was just wondering if you were still working on it.

Nope, still working on it. Keep bouncing back and forth between kernel tweaks and rom changes until I feel there is enough for a release. I do work on it just about daily, just not feasible to release a build daily lol. Been working on the theme now. Saw that Nitro was going ICS so I had to change what I had done there lol.
 
Nope, still working on it. Keep bouncing back and forth between kernel tweaks and rom changes until I feel there is enough for a release. I do work on it just about daily, just not feasible to release a build daily lol. Been working on the theme now. Saw that Nitro was going ICS so I had to change what I had done there lol.

Can't wait to see it! But I will. I'll be nice and patient. :)
 
Back
Top Bottom