@justmpm try it with Android Commander http://androidcommander.com/

Originally Posted by Ammadon

@justmpm try it with Android Commander http://androidcommander.com/

That's a really COOL tool! I was able to get a logcat using JJ v3.0, but nothing with this AOKP build...android commander doesn't even see the device.


Edit: After booting into AOKP, adb doesn't see the device either.....

Originally Posted by justmpm

That's a really COOL tool! I was able to get a logcat using JJ v3.0, but nothing with this AOKP build...android commander doesn't even see the device.


Edit: After booting into AOKP, adb doesn't see the device either.....

this one than
http://de.codeplex.com/releases/view/87215

Originally Posted by funiewski

this one than
http://de.codeplex.com/releases/view/87215

Another good one, thanks....but also didn't work.....bacause adb didn't work, I guess usb debugging isn't checked, so it is going to be hard to pull a logcat thru the usb cable.....

beta 2 released

Originally Posted by championswimmer

beta 2 released

Thanks....just in time, I just got the logcat for beta 1.....I attached it, just in case you need it......it's not really zipped. It was just too big as a text file for the xda uploader to take it.....it is really .txt.....

Originally Posted by justmpm

Thanks....just in time, I just got the logcat for beta 1.....I attached it, just in case you need it......it's not really zipped. It was just too big as a text file for the xda uploader to take it.....it is really .txt.....

thanks a load
that was really helpful of you !!!

Originally Posted by championswimmer

thanks a load
that was really helpful of you !!!

OK...looks like same error with beta 2. I have attached a logcat.

Can you make 1 change to the build.prop?

change: persist.sys.usb.config=mass_storage into persist.sys.usb.config=mass_storage,adb

That will make getting a logcat a lot easier....

Thanks.....

@championswimmer, I looked at logcat... this isnt going to end up well so easily...

I suggest you use already compiled ROM that Supervenom has for ARC... There is no way u can stablize this ROM easily without having a device... i.e blindly..

I can see a lot of access errors... so many framework errors especially of google apps..

... u have to do hit and trial to fix those and might need one dedicated user.. I suggest for the time being remove Googleapps from ur ROM like calender and also Phone.apk, contacts.apk, contactsprovider.apk and telephonyprovider.apk... stabilize the basic ROM then add gapps and phone app..

Originally Posted by jjdoctor

@championswimmer, I looked at logcat... this isnt going to end up well so easily...

I suggest you use already compiled ROM that Supervenom has for ARC... There is no way u can stablize this ROM easily without having a device... i.e blindly..

I can see a lot of access errors... so many framework errors especially of google apps..

... u have to do hit and trial to fix those and might need one dedicated user.. I suggest for the time being remove Googleapps from ur ROM like calender and also Phone.apk, contacts.apk, contactsprovider.apk and telephonyprovider.apk... stabilize the basic ROM then add gapps and phone app..

yes it would have been really helpful have a device in hand

i know i can port, but a ported rom already exists on this forum
i wanted to make a native build

supervenom and me both are working together only.
the anzu builds are coming forth without any problems,
but neo and ray are crashing, we will see further,

rest if anyone wants to port using my builds or supervenom's builds using your patch, then he/she is welcome to do so