yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] adfree:
http://xdaforums.com/showpost.php?p=54511928&postcount=601

Little progress...

EMMCBOOTplay_v1.tar is with "modified" EMMCBOOT.MBN from I9001...

Tested only with GT-S8600... and Odin...

Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> partition.bin download..
<1> 1/4 Finished.
<1> dbl.mbn download..
<1> 2/4 Finished.
<1> osbl.mbn download..
<1> 3/4 Finished.
<1> EMMCBOOT.MBN download..
<1> 4/4 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!

Visual Change is only replaced Samsung Logo by stupid text...

Look at Picture TestRAW4EMMCBOOT_v1.jpg to know, what is where...

In main it looks...

EMMCBOOT.MBN from I9001, I8150 and so on...

Only 60 KB usefull data... and then only Pics in RAW Format inside...

Files are for study...

Best Regards
[Galaxy S Plus I9001 Android Development] adfree:
Maybe someone with IDA skills or other Reverse E. knowledge could help please little bit about first 60 KB in EMMCBOOT...

Display Init should be inside...

Something about Qualcomm partition table... MIBIB...

This is near end of usefull data...

If you open EMMCBOOT from I9001 in HEX Editor...

You can see near address 0xF100...

Few Bytes later Zeros (00) in my opinion Color black from any first RAW Pic...

You can check this via irfanview for instance...

Best Regards

Edit 1.

Referenceposition: 0x0000CFD8	Filename: target/GT-I9001/init.c
Referenceposition: 0x0000D029	Filename: target/GT-I9001/atags.c
Referenceposition: 0x0000D648	Filename: platform/msm_shared/nand.c
Referenceposition: 0x0000ED82	Filename: app/aboot/odin.c
Referenceposition: 0x0000EE27	Filename: dev/fbcon/fbcon.c
Referenceposition: 0x0000EF58	Filename: dev/keys/gpio_keypad.c
Referenceposition: 0x0000F075	Filename: lib/ptable/ptable.c

Filecount: 7

If you copy human readable text from these 60 KB... you can find things like this...

Taken from I9001 EMMCBOOT:

ERROR: unable to read shared memory for reboot mode
ERROR: unable to read shared memory for power on reason
PC is at
LR is at
mmc init failed!
ASSERT FAILED at
target/GT-I9001/init.c
flash_info
ERROR: Unable to read RAM partition
target/GT-I9001/atags.c
Backlight off
panel_s6e63m0_init
setting_table_write
parameter

Edit 2.

found via Google...

https://github.com/beidl/lk_umia

Some readable infos... :good:

More other LK projects...

https://github.com/travisg/lk

https://github.com/RonGokhale/android_lk_bootloader
[T-Mobile Samsung Galaxy S II SGH-T989] blackangst:
I've only tried a couple JB roms (whitehawkx's) and the problem is when playing visual voicemail it plays over speaker phone. Is anyone using the TMo app successfully with any of the current, stable JB roms?
[T-Mobile Samsung Galaxy S II SGH-T989] jrosetto:
I had an issue with the Visual Voicemail and TMobile couldn't seem to fix it. I switch to google voice which also does voice to text for free and I've been loving it. Seems to work with any ROM.
[T-Mobile Samsung Galaxy S II SGH-T989] blackangst:
How would I incorporate that with my existing number?
[Nexus 4 Q&A, Help & Troubleshooting] wtfshouldidonow:
Hey guys, does anyone know how to set one of the camera filters (e.g. Instant, Punch, Vintage, etc.) to be applied immediately after taking a picture in the stock camera app? :)
[LG Optimus 2x] Engr. GiLyn:
Hey guys, I suddenly got a problem with my connection. My Applications suddenly got a connection problem. I can't access my google play, fb, and other apps that requires internet connection, but I can surf the net using the browser. I also noticed that the wifi symbol at my status bar is gray (which was always blue when connected) but the 2 arrows pointing up and down are visible. This problem just started this morning and I would really appreciate your help. Thanks in advance. :laugh:
[Epic 4G Q&A, Help & Troubleshooting] only1penny:
I have an epic that was working fine. I got a new phone so it sat with the battery dead for a little over a month. Now I gave the epic to my daughter and the battery is all wonky. It will charge up to 100%, but when I take it off the charger it will last anywhere from 20 minutes to 4 hours, which I got the other day with no use and airplane mode on. Now here's the wonky part. It only goes down to around 88% and than goes dead. If I plug it back in it says it has about 80% charge. But if I don't plug it in and just try to turn it back on it acts like it doesn't have enough juice. Now on this phone I'm on cwm 6.8.x or something like that and you can't wipe battery stats so I didn't try that. So I guess my next step would be to flash another recovery and wipe battery stats. I did just flash the peoples ROM 2.2 (I think was the number) just yesterday and wiped everything else for a clean install. Has anyone heard of or experienced this? How can I fix this? Will wiping battery stats work? Also, the battery was great, I could easily get all day out of it with average use just a month ago. Please and thank you.
[Epic 4G Q&A, Help & Troubleshooting] only1penny:
Nothing?
[Epic 4G Q&A, Help & Troubleshooting] nikon120:
This community is very small now since this device is old. You need to have patience regarding replies to threads.

Sounds like you need to replace the battery. Look on Amazon and eBay.
[Epic 4G Q&A, Help & Troubleshooting] jeffreyjicha:
I haven't heard of this happening before, nor has it happened to me. Even though some would advise against it, i'd 'calibrate' the battery just to see if that would fix it. If that doesn't fix it, I have no idea.
[Epic 4G Q&A, Help & Troubleshooting] h8it:
From what I recall there was a lot of different opinions about the battery wipe in CWM.

If you google it there should be a video that shows you how to use it. I think you drain the battery until phone shuts off then charge it full, unplug it wait 10 minutes, charge it full, then turn it on and wipe battery stats. Then run phone dead again and charge again. Don't really want to charge it until after running it dead.

I used it a couple of times and it seemed to help but people say it has no affect because the battery stats are in the rom or something like that.

I also have heard that after you load a new rom you have to give it some time and the battery will get better.

I have never experienced what you are so sorry I can't help.

I would guess most would say its the battery buy a new one cause it sounds like the battery is only charging 20%.

I still have my stock battery after almost 2 years. It will get me through the day if I just make phone calls and text, but I have to keep a charger handy if I'm going to use the phone for other things. Sometimes my battery will drop if I reboot. It will be at like 30% and when I reboot it will come on with 15% and tell me to charge it.

They say the 1800ma model will work in this phone and I would check into that if buying a new battery.

Well good luck!
[Epic 4G Q&A, Help & Troubleshooting] only1penny:
The battery was working fine two months ago. That's why its weird to me. Wiping the stats didn't help. I guess a new battery is in order. Grrrrrrrr
[Epic 4G Q&A, Help & Troubleshooting] DynamicN:
If it was the original battery it already has some miles on it and if it sat for a month or two dead in the phone then it's most likely toast. You will get best results with li-ion batteries during the first 300 to 500 charges, so after a year or two the battery will naturally loose it's ability to hold a charge, that's just the nature of the beast. A new battery will do wonders!
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
The percentage that is displayed is usually directly correlated with battery voltage. So 3.200 V would represent 100% and I think it is 2.6 is 0%. So what sounds like is happening is the battery has a bad cell and jumps from say 3V or whatever is 80% right to some voltage below 2.6. A new battery "should" fix this.
[Epic 4G Q&A, Help & Troubleshooting] cybershawngates:
check that 4g isn't on or google talk isn't on. Google now is a big battery waster too. For unexplicable drains, check for a defective battery and if all else fails a clean wipe/install. I've had just about all of these issues on the 4 epic's we own.
[T-Mobile Samsung Galaxy S II SGH-T989] aujbman:
Hey guys, I know there has been a little talk back and forth about this but haven't seen anything too concrete so I just wanted to start this thread to see if there is anyone out there that has run into this same problem and a fix.

This whole problem with callling out and the phone says it is connected but you can't hear anything and it apparently rings on the other side but they can't hear anything either. You end up calling the same person two or three times before you get a good connection. I understand this is a T-Mobile thing, and not a rom specific problem, (although it didn't do this at all when I first got it and had ICS rom on it) so I was wondering if anyone has tried different radios or anything to at least help the problem. I tried switching to the radio I have now ( UVLI1) and it seemed to help for a little while but now it seems to do it every time i either call out or someone else calls in and it's getting really frustrating.

Has anyone came across an adequate alternative or cure for this as of yet?
[T-Mobile Samsung Galaxy S II SGH-T989] richardlibeau:
Try UVLI4 might help you out
[T-Mobile Samsung Galaxy S II SGH-T989] zxstyle07:
+1
[T-Mobile Samsung Galaxy S II SGH-T989] mgeekd:
I too have been having this same issue. I got two Telus original T989D units an have them running on Mobilicity. Additionally, Phone_A immediately gets network upon starting up and the one I'm using, Phone_B takes a good 5 minutes. Both of the specs are the same, and call quality is equally as bad on them. To quickfix the "no sound" problem, I found that rebooting the phone works to re-establish the connection (tested with Phone_A). Phone_B has never had that problem, but again the call quality is very below par. I don't think it's a network issue as I have been on Mobilicity for over a year and was using a Blackberry 9360, and not once had an issue with reception or call quality. As a matter of fact, I never experienced a dropped call until I purchased my current T989. It has come to the point that moving 2 feet in either direction can potentially cause enough interference to drop the call, and I hear what the OP states, it IS frustrating. ROMs and radios were all flashed clean, and phones are unlocked. Both phones are running the following:

ROM: Galaxy SBean Unicef v13.5

Kernel: All-Star (included in AROMA installer)

Radio: UVLI4
[Android Q&A, Help & Troubleshooting] maglev0730:
my screen is not centered after installing pascal kernel for cwm recovery. my alcatel t10 tablet now looks like this
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] parasverm:
Need ink effect for stock odex rom...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ThaiDai:
Buy it in the supermarket next to you

or

Develop it yourself

or

install a deodexed Custom Rom and add the Mod.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] parasverm:
You can reply in pleasent way also instead of taunting
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ThaiDai:
only a response to your

Need ink effect for stock odex rom...

No "please", no "help", no "thanks"

and in the end I gave you a solution: deodexed versions are made because of the feature to add mods
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] salilpune1:
Thaidai is right.. just root ur cell.. and flash any xxlsz rom...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] parasverm:
THANKS BUDDY :thumbup:
[Android Q&A, Help & Troubleshooting] qazed102:
Hi,

I have a Note 2 clone bought from here:

mt6575

Single sim

512MB RAM

2GB ROM

5.2" 800*480

flashed incorrect ROM and it is now dead (I have no backup) :(

my question is anybody know a similar device to download ROM :confused:

Thanks in advance
[HTC Vivid, Raider, Velocity] homeslice976:
Gonna take this one too.
[HTC Vivid, Raider, Velocity] zippox180:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

This is pretty intense man. That's gonna be a lot of work but glad to see it being worked on. From what I have seen the changes from sense 3.6 to 4.1 are not really huge but a lot of people will like this if they don't want jb.
[HTC Vivid, Raider, Velocity] homeslice976:
Yup - and I have some ulterior motives as well. I already have access to a great Sense 4.1 ROM, but I like projects that keep me busy and may benefit others. I don't have unlimited free time though, so I'm really hoping for some community involvement in this one..
[HTC Vivid, Raider, Velocity] yosoywilson78:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

I would love to contribute more, but only thing I can offer is testing. Would be nice to have. What 4.1 ROM do you have?

I unfortunately cannot find any 4.1 ROMs...
[HTC Vivid, Raider, Velocity] homeslice976:
One from a forum/team in the US at which I'm a mod/member. I'm not gonna discuss other 4.1 ROMs here or provide links though.
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

Pm me for the link
[HTC Vivid, Raider, Velocity] yosoywilson78:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

Wasn't asking for links. Just curious. :)
[HTC Vivid, Raider, Velocity] mg2195:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

The menu button can probably be fixed by the keychar/keylayout folders...don't remember the files off the top of my head but that where I fixed the home button for cm10 way back...you'll probably be fine if you just replace the whole folders actually - you may have already tried that though...but its an idea :)
[HTC Vivid, Raider, Velocity] camo_flage:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

Coming from a complete idiot..... why is it that ril doesn't work? The guys down over at the rezound forums fixed ril for sense 4.1 for their device

Sent from my Paranoid HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

Its not fixed because we don't know how to fix it. Smali might as well be russian to me.. so without knowing what I'm looking for its like finding a needle in a haystack. If you can find out what they dis to fix the ril I'm happy to give it a shot
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Nvm...
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

edited: not worth it
[HTC Vivid, Raider, Velocity] camo_flage:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

I don't mean to be a **** as well but its not like the world is gonna end or anything and btw pmd the guy in the rezound forums about the sense ril.

Sent from my Paranoid HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] yosoywilson78:
He is what? 12 or so?
[HTC Vivid, Raider, Velocity] camo_flage:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

Sudden hate much

Sent from my Paranoid HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] homeslice976:
no hate intended. I've been pretty sour with him since his "whoever made this app should die" statement this morning in another thread. That kind of stuff bugs me. Some other stuff too, but it's not worth it at this point. Over it. Anyway, let me know what you hear back about the RIL - meantime, you have a link to his thread or whatever? Yes I could find it - but currently trying to keep 4 brats, I mean kids, under control
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

I'm 14 btw
[HTC Vivid, Raider, Velocity] camo_flage:
Re: [ROM][WiP/PoC] BoRKeD RoM | ALPHA 0.1 [Sense 4.1][4.0.4]

Never mind......

Sent from my Paranoid HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Re: [ROM][WiP] BoRKeD RoM | ALPHA 1.7 [Sense 4.1][4.0.4]

I hope you know what your doing.. I tried some **** and I ended up making it worse xD
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Re: [ROM][WiP] BoRKeD RoM | ALPHA 1.7 [Sense 4.1][4.0.4]

Read your pms lol
[HTC Vivid, Raider, Velocity] Vicpdx18:
Ok so in my total work I did not get video playback to work. Sad face=(, on the bright side I installed the latest Adreno drivers I think 9/10/12(found on youtube) and all is fine not a graphics glitch so far and Block breaker 3 is running without hiccups once I changed the build.prop to a different device name.
[HTC Vivid, Raider, Velocity] nitsuj17:
Assuming you have the right key mappings set in whatever keylayout file this phone uses, and menu works in apps, then yes that's all that's needed for Rosie menu
[HTC Vivid, Raider, Velocity] homeslice976:
I think I found the 2 methods, but implementation isn't as easy as I hoped it would be (have I mentioned I don't understand smali)? If anyone does, and cares to try and figure it out, here's launcher.smali with the 2 new methods @ 22899 and 24989. Unfortunately something isn't right, as Rosie constantly crashes after recompiling.. I did verify that the const variables that were pulling from public.xml in Rosie and com.htc.resources are correct, but on top of that, I really don't know.. I'm gonna go to looking at the camera/video playback for a little, and come back with a fresh mind and maybe figure something new out...

Launcher.smali

Edit: the new methods actually start on lines 21371 and 23328. Don't know where I got the first set ??
[HTC Vivid, Raider, Velocity] :
Re: [ROM][WiP] BoRKeD RoM | ALPHA 1.7 [Sense 4.1][4.0.4]

For video playback I'd take a look at libstagefright
[HTC Vivid, Raider, Velocity] :
Hmm this looks interesting where is the hwcomposer and gralloc libs /lib/hw from? Stock or cm. I'd try using the stock ones and play with media_codecs.xml and media_profiles.xml all from vivido stock
[HTC Vivid, Raider, Velocity] :
could be libomx too
[HTC Vivid, Raider, Velocity] homeslice976:
yup - i've been running circles around libomx, hwcomposer, and gralloc. gralloc.msm8660.so was actually taken from rafy's original 4.0 port. It won't even boot with our's. All of the other hw libs are from the vivid. I've tried using all of the above from rafy's, all of the above from vivid stock, mix/matching them, all with the same result (other than the no boot using our gralloc.msm8660.so). just curious, are the only omx libs you're aware of libmm-omxcore.so, libOmxCore.so, libOmxVenc.so, libOmxDenc.so, and libstagefright_omx.so or am I missing some?
[HTC Vivid, Raider, Velocity] Vicpdx18:
Testing

If you need anything tested I have my vivid ready to go for testing new files or anything else. Im up till 4AM every day so just let me know what i can test out.
[HTC Vivid, Raider, Velocity] :
You could take a look at my git and try those ones video playback works fine for us
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][WiP] BoRKeD RoM | ALPHA 1.7 [Sense 4.1][4.0.4]

Cool ill try that tonight/tomorrow when I get a moment
[HTC Vivid, Raider, Velocity] Vicpdx18:
Homeslice 976,

If you want to look at a discontinued sense 4.0 port from the first villa c ruu 1.09 leak that is for the vivid here is the link.

Link: http://rootzwiki.com/topic/20401-discontinuedporthtc-vivid-sense-40-portreleasedbroken-ril/

Everything in that rom works on the vivid except RIL.

That project was done by rafyvitto on rootzwiki but is now fully discontinued as of March 2012. Just for fun if you wanna look at it!
[HTC Vivid, Raider, Velocity] ZeRo2o9:
he saw it already ;) lol
[HTC Vivid, Raider, Velocity] camo_flage:
Re: [ROM][WiP] BoRKeD RoM | ALPHA 1.7 [Sense 4.1][4.0.4]

As soon as video playback is fixed call me crazy but it will be my dd x)

Sent from my Paranoid HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] nitsuj17:
if you logcat what happens on rosie crash, would make things a lot easier
[HTC Vivid, Raider, Velocity] homeslice976:
Using all of your libstagefright libs (except libstagefright.so as it wouldn't boot with yours), all your omx libs, your gralloc, and your hwcomposer and still having same issue with video. must still be missing something...

D'oh.

Here it is.. full log

I think this is the relevant part

I/RT ( 1217): ALARM: Device has booted, scheduling an alarm
W/dalvikvm( 728): VFY: Ljava/lang/Object; is not instance of Landroid/content/BroadcastReceiver;
W/dalvikvm( 728): VFY: bad arg 1 (into Landroid/content/BroadcastReceiver;)
W/dalvikvm( 728): VFY: rejecting call to Landroid/content/ContextWrapper;.registerReceiver (Landroid/content/BroadcastReceiver;Landroid/content/IntentFilter;)Landroid/content/Intent;
W/dalvikvm( 728): VFY: rejecting opcode 0x6e at 0x0179
W/dalvikvm( 728): VFY: rejected Lcom/htc/launcher/Launcher;.onCreate (Landroid/os/Bundle;)V
W/dalvikvm( 728): Verifier rejected class Lcom/htc/launcher/Launcher;
W/dalvikvm( 728): Class init failed in newInstance call (Lcom/htc/launcher/Launcher;)
W/dalvikvm( 728): threadid=1: thread exiting with uncaught exception (group=0x40b11228)
E/AndroidRuntime( 728): FATAL EXCEPTION: main
E/AndroidRuntime( 728): java.lang.VerifyError: com/htc/launcher/Launcher
E/AndroidRuntime( 728):	at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 728):	at java.lang.Class.newInstance(Class.java:1319)
E/AndroidRuntime( 728):	at android.app.Instrumentation.newActivity(Instrumentation.java:1039)
E/AndroidRuntime( 728):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2150)
E/AndroidRuntime( 728):	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2278)
E/AndroidRuntime( 728):	at android.app.ActivityThread.access$600(ActivityThread.java:142)
E/AndroidRuntime( 728):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1280)
E/AndroidRuntime( 728):	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 728):	at android.os.Looper.loop(Looper.java:156)
E/AndroidRuntime( 728):	at android.app.ActivityThread.main(ActivityThread.java:5099)
E/AndroidRuntime( 728):	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 728):	at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 728):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
E/AndroidRuntime( 728):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
E/AndroidRuntime( 728):	at dalvik.system.NativeStart.main(Native Method)
E/EmbeddedLogger( 260): App crashed! Process: com.htc.launcher
E/EmbeddedLogger( 260): App crashed! Package: com.htc.launcher v313537553 (3.5.2219272524.459932.365039)
E/EmbeddedLogger( 260): Application Label: HTC Sense
I/RecoverySystem( 260): No recovery log file
W/ActivityManager( 260): Force finishing activity com.htc.launcher/.Launcher
[HTC Vivid, Raider, Velocity] Vicpdx18:
Does anybody know what error this is?

W/System.err( 7433): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)

I saw a couple like it
[HTC Vivid, Raider, Velocity] homeslice976:
not specifically, but it's just a warning (W/)

it is an error in the log I posted above though while Rosie is crashing with the changes I made