[ROM] [NIghtlies] Disarmed Toaster [CM10/PA/AOKP] - 0.2.0 (Unofficial)

Search This thread

adenoyd

Member
Dec 28, 2010
26
6
bug report sum-up

here are the bugs i'm experiencing with 0.1.6 shooteru, version from september 5th:

- softbuttons reacting (vibrating) on touch when display is turned off
- lockscreen is hanging when trying to answer call
- ringtone and alarm sounds are not looping as they should. i get one single ring only. (is it THAT ring? the one to rule them all?)
- earpiece volume is maxxed out on answering a call, regardless of volume setting. pushing the volume rocker once in any direction reverts volume to pre-set value

i'm not going to talk about camera and 3d here as we all know that stuff is not developed yet.
 
  • Like
Reactions: SecFry

soldierforchrist2

Senior Member
Mar 29, 2011
129
26
Kansas City, MO
Agrabren, I know you're not supporting CDMA, so feel free not to answer this but I think it might apply to GSM too.

I'm running the Sept 5/6th version of 0.1.6. Twice when I plugged my phone in to charge overnight, the next morning it was warm and hadn't charged at all and it reported to me that storage was running low. When I clicked on the notification it showed me my "apps" memory usage page which indicated that I only had a few bytes of free space, although the gray and blue bar at the bottom appeared only about half "full". In this state a lot of apps like Titanium Backup would crash. I tried wiping the Cache and Dalvik cache both times and it didn't help, so I had to just wipe my data partition (and everything else) and start from scratch.

I apologize that I don't have a logcat or anything - I had to wipe my phone and re-install so it could be functional.

Thanks for continuing development on the CDMA version. It seems like you're making good progress and we appreciate both versions!
 

SecUpwN

Senior Member
Jun 12, 2012
2,086
645
DEUTSCHLAND!
secupwn.github.io
Thanks for your answer. My data connection broke over night again. So there was no change of the location or so. But for me the data connection stayed broken and I had to switch on and off airplane mode to get it working again.

Would be nice to know if more people have still the same issue to find a solution.
Can confirm that. What I discovered during my search for a fix was that VODAFONE has currently some slight trouble with their 2G & 3G network stability. That's because they're working on broadening their services while I write this. testman86, are you @ Vodafone? Might not be the fault of this ROM.. :rolleyes:
 

testman86

Senior Member
Mar 23, 2012
351
112
Can confirm that. What I discovered during my search for a fix was that VODAFONE has currently some slight trouble with their 2G & 3G network stability. That's because they're working on broadening their services while I write this. testman86, are you @ Vodafone? Might not be the fault of this ROM.. :rolleyes:

Thanks for your reply.

No, I have o2 Germany. And the funny thing is that a friend of mine has the same phone and the same provider and we were at the same place and my data connection was broken and his not :) He is on stock ICS.
 

agrabren

Inactive Recognized Developer
Mar 28, 2011
1,451
9,516
Weld County, CO
Ok, let me go over a few things real quick, so people know what's happening and why...

1. Data connection - Yes, the GSM build definitely has a problem with data dropping, I've experienced it as well, haven't debugged it yet, but I have some suspicions on it.

2. Kernel issues - This is the tricky one to explain. Both builds (GSM & CDMA) have bugs with their respective kernels, which are different kernels. I'm trying to get this resolved quickly, since development against an unstable ROM is very difficult. Why have I stopped developing my own kernel? Because there are plenty of great kernel developers helping out for both devices, my skills are better served working on the ROM itself. While the pretty picture explaining what a kernel is may give a false representation of respective size, the kernel is by far the smaller component. Further, because the majority of the kernel is pure linux, most changes are directed only at drivers and board configuration, with a few changes going to well-documented interfaces for handling things like CPU frequencies. This doesn't mean kernel development is easy, it means that it has a much tighter area of focus and is 100% open-source. The ROM, on the other hand, has a cascading design which means that a change to one piece (such as audio) has far-reaching affects like camera and graphics. And many of the interconnects are in closed-source components, making it very difficult to debug or fully understand. Since we have quite a few talented kernel developers, I feel my knowledge of the whole stack is better served delivering AOSP instead of kernel improvements for now. And trying to do both at once leads to a lot of feature requests and time sinks on me that could be better used making the ROM better. But that transition has encountered a few minor hiccups and broke Bluetooth, as well as broke some CPU governor controls. This is making ROMs run too fast and cause reboots. So I'm working with the kernel developers to get stable builds that are AOSP-compliant and ready for Jelly Bean. This has to be my #1 focus, because I can't debug broken devices.

3. CDMA Support - I'm not officially supporting CDMA, but that doesn't mean I'm not fixing bugs. You'll notice that I have not created a CDMA thread for this ROM, and that I continually ask for CDMA users to please refrain from asking CDMA-specific questions in this thread. To be nice, I tossed WiMAX into the CDMA Jelly Bean builds, but don't really care to find the long-present bug of why it doesn't report "4G" in the bar. Mostly because my WiMAX coverage here sucks, so it's very hard to debug, and for little benefit. I'm sure it's trivial, but *finding* it isn't. Somewhere, there's a mismatch in how the current signal type is reported.

4. Trolling - Yes, I enjoyed my little explosion, but that doesn't mean it was right. Thankfully, the moderators are kind enough to recognize both that it's my first offense (although second time banned... Anyone who went to last years BBQ may remember the sign-up sheet for being banned. If they do it again, expect me to be banned again this year) and that I do try to contribute to the community. Sprint users in general should take some time reading around in the GSM threads and see how the "other half" acts and responds to developers. I wouldn't have believed the difference if I hadn't come over here myself to help GSM users.

5. Version Numbers - If there's anything important, I rev the version number. Otherwise, it's a pain in the butt and I don't do it. So if you really care for the latest cutting-edge, may not even boot build, you can check the timestamp. But otherwise, if the number hasn't changed, it's not worthy of upgrading.

Hope this helps.
 

ipsuvedi

Senior Member
Feb 9, 2012
1,389
655
Mumbai
You have changed the rom date ...is there any update or bug fix in 07 sept 12...:confused::thumbup::confused::thumbup::confused::thumbup:

Sent from my HTC EVO 3D X515m using xda premium
 

cityeyes

Senior Member
Aug 12, 2009
877
291
Near Chicago
You have changed the rom date ...is there any update or bug fix in 07 sept 12...:confused::thumbup::confused::thumbup::confused::thumbup:

Sent from my HTC EVO 3D X515m using xda premium


He addressed this in the post above yours:

5. Version Numbers - If there's anything important, I rev the version number. Otherwise, it's a pain in the butt and I don't do it. So if you really care for the latest cutting-edge, may not even boot build, you can check the timestamp. But otherwise, if the number hasn't changed, it's not worthy of upgrading.

Edit: Ohhh, I get what you mean - I think someone was on him about dating his new revisions in his thread title. I don't think it's a guarantee that he's updating a new version, but I wouldn't count it out.
 

agrabren

Inactive Recognized Developer
Mar 28, 2011
1,451
9,516
Weld County, CO
He addressed this in the post above yours:



Edit: Ohhh, I get what you mean - I think someone was on him about dating his new revisions in his thread title. I don't think it's a guarantee that he's updating a new version, but I wouldn't count it out.

No new build yet, but to help out with the ROMs thread, I added todays date, since I don't know when I posted the last ROM.
 
  • Like
Reactions: Dnst and scariola

cagaagac

Senior Member
Jan 18, 2008
210
92
Merseburg
No new build yet, but to help out with the ROMs thread, I added todays date, since I don't know when I posted the last ROM.

system settings > about phone > build date
Tue Sept 4

Actually this should be the relevant date :p

BTW: fantastic story about the ROMs name :thumbup:

Sent from my GT-P5110 using xda app-developers app
 
Last edited:

ipsuvedi

Senior Member
Feb 9, 2012
1,389
655
Mumbai
I think everythig goinf fine here...with e3d..cuz
Ubuntuz+Agrabren+helicopter88 and gav-collins = working everything jb for htc evo 3d...even 3d
:thumbup::D:thumbup:
 

SecFry

Senior Member
Jul 12, 2009
162
199
29
Moscow
Alarm sound playing only once

Code:
V/OMXCodec(14517): [OMX.google.vorbis.decoder] FILL_BUFFER_DONE(buffer: 0x419be668, size: 4096, flags: 0x00000000, timestamp: 1461405 us (1.46 secs))
V/OMXCodec(14517): [OMX.google.vorbis.decoder] Calling fillBuffer on buffer 0x41cafec0
V/OMXCodec(14517): [OMX.google.vorbis.decoder] EMPTY_BUFFER_DONE(buffer: 0x41b883e8)
V/OMXCodec(14517): [OMX.google.vorbis.decoder] FILL_BUFFER_DONE(buffer: 0x41cafec0, size: 4096, flags: 0x00000000, timestamp: 1503900 us (1.50 secs))
V/OMXCodec(14517): [OMX.google.vorbis.decoder] Calling fillBuffer on buffer 0x413aa830
V/OMXCodec(14517): [OMX.google.vorbis.decoder] Calling fillBuffer on buffer 0x413eb5e8
V/OMXCodec(14517): [OMX.google.vorbis.decoder] EMPTY_BUFFER_DONE(buffer: 0x4156be38)
V/OMXCodec(14517): [OMX.google.vorbis.decoder] FILL_BUFFER_DONE(buffer: 0x413aa830, size: 3400, flags: 0x00000000, timestamp: 1503900 us (1.50 secs))
V/OMXCodec(14517): [OMX.google.vorbis.decoder] EMPTY_BUFFER_DONE(buffer: 0x419e8a38)
V/OMXCodec(14517): [OMX.google.vorbis.decoder] FILL_BUFFER_DONE(buffer: 0x413eb5e8, size: 0, flags: 0x00000001, timestamp: 1461405 us (1.46 secs))
V/OMXCodec(14517): [OMX.google.vorbis.decoder] No more output data.
V/OMXCodec(14517): [OMX.google.vorbis.decoder] There is no more output data available, not calling fillOutputBuffer
V/OMXCodec(14517): [OMX.google.vorbis.decoder] There is no more output data available, not calling fillOutputBuffer
V/OMXCodec(14517): [OMX.google.vorbis.decoder] There is no more output data available, not calling fillOutputBuffer
V/OMXCodec(14517): [OMX.google.vorbis.decoder] There is no more output data available, not calling fillOutputBuffer
V/OMXCodec(14517): [OMX.google.vorbis.decoder] seeking to 0 us (0.00 secs)
V/OMXCodec(14517): [OMX.google.vorbis.decoder] flushPortAsync(0): we own 4 out of 4 buffers already.
V/OMXCodec(14517): [OMX.google.vorbis.decoder] flushPortAsync(1): we own 4 out of 4 buffers already.
V/OMXCodec(14517): [OMX.google.vorbis.decoder] FLUSH_DONE(0)
V/OMXCodec(14517): [OMX.google.vorbis.decoder] FLUSH_DONE(1)
V/OMXCodec(14517): [OMX.google.vorbis.decoder] Finished flushing both ports, now continuing from seek-time.
F/OMXCodec(14517): frameworks/av/media/libstagefright/OMXCodec.cpp:3554 CHECK(mState == EXECUTING || mState == RECONFIGURING) failed.
F/libc    (14517): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 31803 (OMXCallbackDisp)
I/DEBUG   (  130): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   (  130): Build fingerprint: 'htc_europe/htc_shooteru/shooteru:4.0.3/IML74K/351412.1:userdebug/test-keys'
I/DEBUG   (  130): pid: 14517, tid: 31803, name: OMXCallbackDisp  >>> /system/bin/mediaserver <<<
I/DEBUG   (  130): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
D/MP-Decision(  789): UP Nw:2.700000 Tw:180 rq:3.900000 seq:199
I/DEBUG   (  130):     r0 00000027  r1 deadbaad  r2 0000005a  r3 00000000
I/DEBUG   (  130):     r4 00000000  r5 428ff874  r6 00000004  r7 428ffe88
I/DEBUG   (  130):     r8 42223f08  r9 413eb3e8  sl 401f6a19  fp 00100000
I/DEBUG   (  130):     ip fffd2940  sp 428ff870  lr 40168df1  pc 401654b2  cpsr 60030030
I/DEBUG   (  130):     d0  455845203d3d2065  d1  7c20474e49545543
I/DEBUG   (  130):     d2  65746174536d207c  d3  4f434552203d3d20
I/DEBUG   (  130):     d4  3ce3d87a8d64d7f1  d5  308c2308302318fd
I/DEBUG   (  130):     d6  37e11b82f7afe64f  d7  0000000079d92275
I/DEBUG   (  130):     d8  0004c92e1bea8530  d9  7fffffffffffffff
I/DEBUG   (  130):     d10 0000000000000000  d11 0000000000000000
I/DEBUG   (  130):     d12 0000000000000000  d13 0000000000000000
I/DEBUG   (  130):     d14 0000000000000000  d15 0000000000000000
I/DEBUG   (  130):     d16 4e4952554749464e  d17 656c696166202947
I/DEBUG   (  130):     d18 3fdffffffffff07f  d19 3fe0000000000000
I/DEBUG   (  130):     d20 3fe00000000007c1  d21 d66f658da0e083ef
I/DEBUG   (  130):     d22 fdc7aa4dbf2fce6c  d23 708719b13a9b7838
I/DEBUG   (  130):     d24 3ff009bb63fc01c8  d25 0000000000000000
I/DEBUG   (  130):     d26 0000000000000000  d27 0000000000000000
I/DEBUG   (  130):     d28 0000000000000000  d29 0000000000000000
I/DEBUG   (  130):     d30 0000000000000000  d31 0000000000000000
I/DEBUG   (  130):     scr 20000010
I/DEBUG   (  130):
I/DEBUG   (  130): backtrace:
I/DEBUG   (  130):     #00  pc 000184b2  /system/lib/libc.so
I/DEBUG   (  130):     #01  pc 0000dc44  /system/lib/libc.so (abort+4)
I/DEBUG   (  130):     #02  pc 000040fd  /system/lib/libcutils.so (__android_log_assert+88)
I/DEBUG   (  130):     #03  pc 00077f59  /system/lib/libstagefright.so (android::eek:MXCodec::drainInputBuffers()+40)
I/DEBUG   (  130):     #04  pc 0007bdd3  /system/lib/libstagefright.so (android::eek:MXCodec::onCmdComplete(OMX_COMMANDTYPE, unsigned long)+1394)
I/DEBUG   (  130):     #05  pc 0007c2bd  /system/lib/libstagefright.so (android::eek:MXCodec::onEvent(OMX_EVENTTYPE, unsigned long, unsigned long)+28)
I/DEBUG   (  130):     #06  pc 0007c57d  /system/lib/libstagefright.so (android::eek:MXCodec::on_message(android::omx_message const&)+60)
I/DEBUG   (  130):     #07  pc 0007cc2d  /system/lib/libstagefright.so
I/DEBUG   (  130):     #08  pc 0000c6fd  /system/lib/libstagefright_omx.so (android::eek:MXNodeInstance::onMessage(android::omx_message const&)+48)
I/DEBUG   (  130):     #09  pc 0000ad63  /system/lib/libstagefright_omx.so (android::eek:MX::CallbackDispatcher::loop()+110)
I/DEBUG   (  130):     #10  pc 00010f4b  /system/lib/libutils.so (android::Thread::_threadLoop(void*)+114)
I/DEBUG   (  130):     #11  pc 00010ab1  /system/lib/libutils.so
I/DEBUG   (  130):     #12  pc 000130f4  /system/lib/libc.so (__thread_entry+48)
I/DEBUG   (  130):     #13  pc 00012850  /system/lib/libc.so (pthread_create+180)
I/DEBUG   (  130):
I/DEBUG   (  130): stack:
I/DEBUG   (  130):          428ff830  00100000
I/DEBUG   (  130):          428ff834  00000000
I/DEBUG   (  130):          428ff838  401916c4  /system/lib/libc.so
I/DEBUG   (  130):          428ff83c  41a57a70  [heap]
I/DEBUG   (  130):          428ff840  401916c4  /system/lib/libc.so
I/DEBUG   (  130):          428ff844  00000001
I/DEBUG   (  130):          428ff848  401917b8  /system/lib/libc.so
I/DEBUG   (  130):          428ff84c  40191718  /system/lib/libc.so
I/DEBUG   (  130):          428ff850  00000000
I/DEBUG   (  130):          428ff854  40168df1  /system/lib/libc.so (_fwalk+32)
I/DEBUG   (  130):          428ff858  00000001
I/DEBUG   (  130):          428ff85c  428ff874
I/DEBUG   (  130):          428ff860  00000004
I/DEBUG   (  130):          428ff864  428ffe88
I/DEBUG   (  130):          428ff868  df0027ad
I/DEBUG   (  130):          428ff86c  00000000
I/DEBUG   (  130):     #00  428ff870  428ffe88
I/DEBUG   (  130):          428ff874  fffffbdf
I/DEBUG   (  130):          428ff878  428ff874
I/DEBUG   (  130):          428ff87c  00000001
I/DEBUG   (  130):          428ff880  40626349  /system/lib/libstagefright.so
I/DEBUG   (  130):          428ff884  00000009
I/DEBUG   (  130):          428ff888  428ff8a4
I/DEBUG   (  130):          428ff88c  40626349  /system/lib/libstagefright.so
I/DEBUG   (  130):          428ff890  00000001
I/DEBUG   (  130):          428ff894  4015ac48  /system/lib/libc.so (__pthread_clone)
I/DEBUG   (  130):     #01  428ff898  401a1c25  /system/lib/libcutils.so
I/DEBUG   (  130):          428ff89c  401a2101  /system/lib/libcutils.so (__android_log_assert+92)
I/DEBUG   (  130):     #02  428ff8a0  428ffcb4
I/DEBUG   (  130):          428ff8a4  6d617266
I/DEBUG   (  130):          428ff8a8  726f7765
I/DEBUG   (  130):          428ff8ac  612f736b
I/DEBUG   (  130):          428ff8b0  656d2f76
I/DEBUG   (  130):          428ff8b4  2f616964
I/DEBUG   (  130):          428ff8b8  7362696c
I/DEBUG   (  130):          428ff8bc  65676174
I/DEBUG   (  130):          428ff8c0  67697266
I/DEBUG   (  130):          428ff8c4  4f2f7468
I/DEBUG   (  130):          428ff8c8  6f43584d
I/DEBUG   (  130):          428ff8cc  2e636564
I/DEBUG   (  130):          428ff8d0  3a707063
I/DEBUG   (  130):          428ff8d4  34353533
I/DEBUG   (  130):          428ff8d8  45484320
I/DEBUG   (  130):          428ff8dc  6d284b43
I/DEBUG   (  130):          ........  ........
I/DEBUG   (  130):
I/DEBUG   (  130): memory near r5:
I/DEBUG   (  130):     428ff854 40168df1 00000001 428ff874 00000004  ...@....t..B....
I/DEBUG   (  130):     428ff864 428ffe88 df0027ad 00000000 428ffe88  ...B.'.........B
I/DEBUG   (  130):     428ff874 fffffbdf 428ff874 00000001 40626349  ....t..B....Icb@
I/DEBUG   (  130):     428ff884 00000009 428ff8a4 40626349 00000001  .......BIcb@....
I/DEBUG   (  130):     428ff894 4015ac48 401a1c25 401a2101 428ffcb4  H..@%..@.!.@...B
I/DEBUG   (  130):
I/DEBUG   (  130): memory near r7:
I/DEBUG   (  130):     428ffe68 00000000 0000001e 00000000 00000001  ................
I/DEBUG   (  130):     428ffe78 00000001 4273fdb0 404d7010 41a55010  ......sB.pM@.P.A
I/DEBUG   (  130):     428ffe88 4089f09a 40162a21 4156bf4c 4156bf40  ...@!*.@L.VA@.VA
I/DEBUG   (  130):     428ffe98 428ffea8 408a27a4 408a27a4 401f6f4d  ...B.'.@.'.@Mo.@
I/DEBUG   (  130):     428ffea8 4156bf40 413eb400 4156bf40 413eb3d0  @.VA..>A@.VA..>A
I/DEBUG   (  130):
I/DEBUG   (  130): memory near r8:
I/DEBUG   (  130):     42223ee8 42223f00 401600f8 4156b1c8 42223f00  .?"B...@..VA.?"B
I/DEBUG   (  130):     42223ef8 41cadc88 4015f854 42223f00 4156b1c8  ...AT..@.?"B..VA
I/DEBUG   (  130):     42223f08 00000016 00000000 00000000 00000000  ................
I/DEBUG   (  130):     42223f18 4155bf30 00000000 00000000 00000000  0.UA............
I/DEBUG   (  130):     42223f28 00000000 00000000 00000000 00000000  ................
I/DEBUG   (  130):
I/DEBUG   (  130): memory near r9:
I/DEBUG   (  130):     413eb3c8 00003d67 0000001b 00000002 00000003  g=..............
I/DEBUG   (  130):     413eb3d8 4156bf68 00000000 006e0061 0000003b  h.VA....a.n.;...
I/DEBUG   (  130):     413eb3e8 40648348 419e8904 00000000 00000000  H.d@...A........
I/DEBUG   (  130):     413eb3f8 41b89000 00008000 00001000 00000000  ...A............
I/DEBUG   (  130):     413eb408 00000000 00000000 41a23f00 413b8c10  .........?.A..;A
I/DEBUG   (  130):
I/DEBUG   (  130): memory near sl:
I/DEBUG   (  130):     401f69f8 d0020f00 f8c99905 20011000 e8bdb00d  ........... ....
I/DEBUG   (  130):     401f6a08 bf008ff0 0000006f 00005b57 00005b66  ....o...W[..f[..
I/DEBUG   (  130):     401f6a18 e890b5f7 68c400e0 ec7ef7fb 463a2000  .......h..~.. :F
I/DEBUG   (  130):     401f6a28 f7fb4601 4821ede8 44784921 f7fb4479  .F....!H!IxDyD..
I/DEBUG   (  130):     401f6a38 4820ede8 78034478 2f09b16b f7fbdd03  .. HxD.xk../....
I/DEBUG   (  130):
I/DEBUG   (  130): memory near fp:
I/DEBUG   (  130):     000fffe0 ffffffff ffffffff ffffffff ffffffff  ................
I/DEBUG   (  130):     000ffff0 ffffffff ffffffff ffffffff ffffffff  ................
I/DEBUG   (  130):     00100000 ffffffff ffffffff ffffffff ffffffff  ................
I/DEBUG   (  130):     00100010 ffffffff ffffffff ffffffff ffffffff  ................
I/DEBUG   (  130):     00100020 ffffffff ffffffff ffffffff ffffffff  ................
I/DEBUG   (  130):
I/DEBUG   (  130): memory near sp:
I/DEBUG   (  130):     428ff850 00000000 40168df1 00000001 428ff874  .......@....t..B
I/DEBUG   (  130):     428ff860 00000004 428ffe88 df0027ad 00000000  .......B.'......
I/DEBUG   (  130):     428ff870 428ffe88 fffffbdf 428ff874 00000001  ...B....t..B....
I/DEBUG   (  130):     428ff880 40626349 00000009 428ff8a4 40626349  Icb@.......BIcb@
I/DEBUG   (  130):     428ff890 00000001 4015ac48 401a1c25 401a2101  ....H..@%..@.!.@
I/DEBUG   (  130):
I/DEBUG   (  130): code around pc:
I/DEBUG   (  130):     40165490 e000b164 6823461c d1fb2b00 68e3e026  d....F#h.+..&..h
I/DEBUG   (  130):     401654a0 4a17b123 447a2401 47986014 20274911  #..J.$zD.`.G.I'
I/DEBUG   (  130):     401654b0 70082400 eaf8f7f4 f7f52106 a902ec38  .$.p.....!..8...
I/DEBUG   (  130):     401654c0 f04f2006 460a5380 94029304 f7f59403  . O..S.F........
I/DEBUG   (  130):     401654d0 4629e816 20024622 e81ef7f5 eae4f7f4  ..)F"F. ........
I/DEBUG   (  130):
I/DEBUG   (  130): code around lr:
I/DEBUG   (  130):     40168dd0 41f0e92d 4c0b2600 447c4680 68a56824  -..A.&.L.F|D$h.h
I/DEBUG   (  130):     40168de0 e0076867 300cf9b5 dd022b00 47c04628  gh.....0.+..(F.G
I/DEBUG   (  130):     40168df0 35544306 d5f53f01 2c006824 4630d1ef  .CT5.?..$h.,..0F
I/DEBUG   (  130):     40168e00 81f0e8bd 00028726 43f0e92d fb01461f  ....&...-..C.F..
I/DEBUG   (  130):     40168e10 f8dff602 b0878058 44f8460c 8000f8d8  ....X....F.D....
I/DEBUG   (  130):
I/DEBUG   (  130): memory map around fault addr deadbaad:
I/DEBUG   (  130):     becbf000-bece0000 [stack]
I/DEBUG   (  130):     (no map for address)
I/DEBUG   (  130):     ffff0000-ffff1000 [vectors]
I/BootReceiver( 8047): Copying /data/tombstones/tombstone_00 to DropBox (SYSTEM_TOMBSTONE)
I/ServiceManager(  126): service 'media.audio_flinger' died
I/ServiceManager(  126): service 'media.player' died
I/ServiceManager(  126): service 'media.camera' died
I/ServiceManager(  126): service 'media.audio_policy' died
W/AudioSystem( 8181): AudioFlinger server died!
W/AudioSystem(31230): AudioFlinger server died!
W/IMediaDeathNotifier( 8181): media server died
W/IMediaDeathNotifier(31230): media server died
E/MediaPlayer(31230): error (100, 0)
W/AudioSystem( 9146): AudioPolicyService server died!
E/MediaPlayer(31230): Error (100,0)
E/AlarmClock(31230): Error occurred while playing audio.
E/MediaPlayer(31230): stop called in state 0
E/MediaPlayer(31230): error (-38, 0)
W/AudioSystem( 9146): AudioFlinger server died!
W/AudioSystem(30904): AudioFlinger server died!
W/IMediaDeathNotifier(30904): media server died
I/ServiceManager(31230): Waiting for service media.audio_flinger...
W/AudioSystem(24736): AudioFlinger server died!
W/AudioSystem( 8047): AudioPolicyService server died!
W/AudioSystem( 8047): AudioFlinger server died!
D/MP-Decision(  789): DOWN Ns:2.100000 Ts:270 rq:0.700000 seq:297 (Up time:1088)
D/ThermalDaemon(  791): CPU[1] offline
I/ServiceManager(31230): Waiting for service media.audio_flinger...
E/AudioService( 8047): Media server died.
I/ServiceManager( 8047): Waiting for service media.audio_flinger...
I/ServiceManager(31230): Waiting for service media.audio_flinger...
I/ServiceManager( 8047): Waiting for service media.audio_flinger...
I/ServiceManager(31230): Waiting for service media.audio_flinger...
I/ServiceManager( 8047): Waiting for service media.audio_flinger...
I/ServiceManager(31230): Waiting for service media.audio_flinger...
I/ServiceManager( 8047): Waiting for service media.audio_flinger...
Actually there was a recent gerrit change that was merged - http://r.cyanogenmod.com/#/c/22806/
In agrabren github it shows that last sync was month ago. Maybe sync today? :D
 

gav83collins

Senior Member
I keep getting stuck at boot, I then tried flashing Su zip , and it got to android is optimizing apk, then android loading and it froze, I used the gapps from helicopters jb, so I think it maybe that, I'm downloading your gapps now, if successful il be booting into and out of 5 diff roms



Edit.....nope, just realised there the same gapps, il try again in 15 mins when I get home
 
Last edited:

metamasterplay

Senior Member
Mar 20, 2011
351
120
Casablanca
I keep getting stuck at boot, I then tried flashing Su zip , and it got to android is optimizing apk, then android loading and it froze, I used the gapps from helicopters jb, so I think it maybe that, I'm downloading your gapps now, if successful il be booting into and out of 5 diff roms



Edit.....nope, just realised there the same gapps, il try again in 15 mins when I get home

You have to clear cache &dalvik

Sent from my HTC EVO 3D X515m using xda app-developers app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 215
    CyanogenMod 10 - Disarmed Toaster - Rearmed

    Current version: 0.2.9


    elW6.png


    This is an un-official ROM, and not directly supported by the CyanogenMod team.

    Background Information:
    While working on Devil Toast, it occurred to me that I enjoyed having "names" for the different ROMs, instead of just calling them "CM9", "CM10", etc... But then, what was I going to call Jelly Bean? And while I greatly appreciate all the help ToastCFH has given me in the Android community, it didn't make sense to continue naming my ROMs after him. Then it struck me, "Disarmed Toaster". The name originally came from Microsoft (I'm sure they're thrilled to have named an Android ROM) and their absolutely insane "Random Naming" scheme in the XBOX 360. My wife couldn't think up a nickname (if any of you can't guess what my nick is, you have a *serious* issue with pattern recognition) so the XBOX 360 suggested some for her. The one that caught her attention was "Disarmed Toaster". What exactly is an armed toaster? Do we need to start warning people of the dangers of armed toasters? Are they rising up against us? So after some mild chuckles, she selected it as her name. No, she doesn't play online. No, neither of us have a Gold account. We play "Ticket To Ride" on it, that's about it. So when I got Jelly Bean to boot for the first time and actually function, the first change I made was to name it "Disarmed Toaster", after the woman who really is the most important person in my life. When it became evident that I took Devil Toast as far as it was going to go without some serious code writing (for this unfamiliar, this is the act of writing source code. I don't do any smali hacking or binary swapping from other developers to make these ROMs), I decided it was time to cut over to Jelly Bean. So here it is, a pre-Alpha Jelly Bean ROM, named "Disarmed Toaster"

    Code:
    #include 
    /*
     * Your warranty is now likely void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * spontaneous combustion, your wife/girlfriend wanting
     * to have my babies, or any other host of cosmic penalties
     * which may befall you, your family, or your phone.
     *
     */

    What works:
    • Phone
    • Wifi
    • Camera
    • USB Mass Storage
    • Bluetooth
    • GPS
    • Car Dock
    • Google Now
    • Mutli-touch

    What doesn't work:
    • Anryl Kernel is missing (you can select it, but the actual boot image is missing from the package)
    • PDroid app is missing (you can download it from XDA). Framework is still properly installed.
    • Vanilla Kernel may or may not actually boot. It didn't boot for me, but mileage may vary?
    • Vanilla Kernel missing multi-touch patch
    • Random data drops
    • 3D
    • HDMI output

    Downloads:
    ROM: http://goo.im/devs/agrabren/cm10/shooteru
    Mirror: http://dl.nemec.co/agrabren/cm10

    GAPPS: http://goo.im/gapps/gapps-jb-20120726-signed.zip

    Kernel: Vanilla Kernel
    Toolchain: GCC ARM version 4.6
    Source: https://github.com/agrabren/android_kernel_htc_shooter.git

    Kernel: CoolExe ShooterU Kernel
    Toolchain: Linaro
    Source: git://github.com/Coolexe/shooteru-ics-crc-3.0.16-e733189.git

    Kernel Flashing:
    This ROM uses extra information contained in the boot.img file which standard mkbootimg doesn't understand and discards. To change the kernel, please download the unpackbootimg and mkbookimg tools located on goo.im next to the ROM itself. These are linux-only tools for the moment, but should unblock people from creating boot.img files which are compatible with Disarmed Toaster.

    Special Thanks:
    First, and most importantly, my wife Courtney, who this build is named after
    CoolExe and MikeC84 for offering me the ability to prepackage their kernels in the installer
    ToastCFH, who helped me learn both Linux and Android, as well as contributed largely to all HTC product development in CM
    Anryl, who has helped me along in the GSM community
    Binux-Project, for the amazing 3D Boot Animation
    TeamWin, cause I still love those guys
    DigitalHigh, who got me back into this stuff
    And HTC, makers of a great phone that failed only because of marketing and software...

    Version History
    0.2.0
    • Camera fixes
    • Bluetooth
    • AOKP added to ROM
    • Kernels included in AROMA Installer
    0.1.6
    • Fixes in build process, switch to Anryl and MAC Kernels
    0.1.5
    • Internal bugfixes, integration of latest codebases
    0.1.4
    • Fixed WiFi
    • Fixed Phone Audio
    0.1.3
    • Fixed Google Now
    • Broke Phone Audio (See a recurring trend?)
    • Broke WiFi
    • Fixed multi-touch
    0.1.2
    • Fixed issue with phone audio
    • Verified USB Mass Storage and GPS
    • Broke Google Now / mic
    0.1.1
    • Fixed mic issue when not in phone call
    • Fixed headset issue
    0.1
    • Pre-alpha builds
    106
    Bugfixes completed for next release
    • No video from YouTube or Gallery
    • PDroid 2.0 and V6 Supercharger patches for all three ROMs

    Bugs blocking next minor release

    Bugs blocking next major release
    • AOKP bootloops
    • Tile Rendering has corruption (visible in YouTube video playback)

    Planned Development: This list is subject to change
    0.4:
    • WiFi Tethering
    0.5:
    • 3D Camera and Gallery
    0.6:
    • YouTube 3D
    0.7
    • Battery Improvements
    75
    I'm actually working on the 3D camera at the moment. :) Why? Because I miss the 3D part of the EVO 3D. I'm not nearly as focused on my own "ROM" at the moment as I am creating the patches required to get all ROMs supported. I will, obviously, end up uploading my own ROMs for people to try and play with. But first, I want to get this feature working. :)

    It's a bit harder, Qualcomm took down some of the source code we used in the past. Good thing I'm stubborn. ;)
    72
    Flash a sense Rom and see if that makes a difference. If it's Sprint (CDMA), update your PRL and profile while you're there.

    New development well be on 4.2.1, since that's the code I'm now most familiar with. I thought I knew android before I started on Thor. I was wrong. But I'm coming back with new abilities and more understanding. I program Java now too! So no part of the system is off limits to me!

    Sent from my Nexus 7 using xda premium
    70
    Yes, still working on it. Work is, of course, still very hectic at the moment. But I'm also trying to get 4.2.2 fully building and functional. That's not a small task (sadly) but I'll get it working. Once we have something stable, I can put some nice touches on things like the LEDs. And I'm still in the process of learning more and more about the internals of Android and its architecture. That experience is invaluable for adding features like 3D support. So don't take my lack of updates as nothing happening, it's just nothing to release yet.