• Announcements

    • PaulOBrien

      Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such software Nintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance) CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission) ROMs must give full credit to the original author ISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • PaulOBrien

      Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
weeo

[ DEV ] HTC Sense

227 posts in this topic

My current guess is this error:

E/AndroidRuntime( 755): FATAL EXCEPTION: NetworkLocationProvider

E/AndroidRuntime( 755): java.lang.SecurityException: Neither user 10010 nor current process has android.permission.ACCESS_COARSE_LOCATION.

Crevis, can you make log on non-rebooting backup? Seems like that NetworkLocationProvider has no permission to get network location, but would be nice to see the difference, unluckily I can't reproduce the non-rebooting state.

0

Share this post


Link to post
Share on other sites

My current guess is this error:

E/AndroidRuntime( 755): FATAL EXCEPTION: NetworkLocationProvider

E/AndroidRuntime( 755): java.lang.SecurityException: Neither user 10010 nor current process has android.permission.ACCESS_COARSE_LOCATION.

Crevis, can you make log on non-rebooting backup? Seems like that NetworkLocationProvider has no permission to get network location, but would be nice to see the difference, unluckily I can't reproduce the non-rebooting state.

Thing is, it has that permission so I don't know why its saying it doesn't, and the well the difference is that there are no errors on the backup, I'll make a log if I can't fix it soon.

0

Share this post


Link to post
Share on other sites

Hey The_Crevis. Sorry I couldn't help during the week. I can only help on weekends. So here I am. Let me know if you need anything

0

Share this post


Link to post
Share on other sites

Hey The_Crevis. Sorry I couldn't help during the week. I can only help on weekends. So here I am. Let me know if you need anything

If you read a few posts back, then you see that the current problem is NetworkLocation, if you could help, it would be appreciated.

Crevis:

Those working data must got into your backup somehow. How did you exactly flashed it the time you made the backup? Is it possible that you didn't actually wipe and it's from a previous rom?

0

Share this post


Link to post
Share on other sites

If you read a few posts back, then you see that the current problem is NetworkLocation, if you could help, it would be appreciated.

Crevis:

Those working data must got into your backup somehow. How did you exactly flashed it the time you made the backup? Is it possible that you didn't actually wipe and it's from a previous rom?

Yeah I've read them. What build are we on? Sorry Im still in bed and I can't comprehend anything. Ill get to work after breakfast :-)

0

Share this post


Link to post
Share on other sites

Right, I can only conclude that it is actually the fixed libsurfaceflinger that causes the reboots. This is because on the alpha2 build with the upside down screen, there are no reboots. Then I replace the libsurfaceflinger, make a new build and I get the reboots. I didn't get reboots in the first place with it because I just pushed it to a alpha2 build. Its all very strange :S

0

Share this post


Link to post
Share on other sites

Right, I can only conclude that it is actually the fixed libsurfaceflinger that causes the reboots. This is because on the alpha2 build with the upside down screen, there are no reboots. Then I replace the libsurfaceflinger, make a new build and I get the reboots. I didn't get reboots in the first place with it because I just pushed it to a alpha2 build. Its all very strange :S

I've only had 2 reboots on alpha3... let me look into aswell

0

Share this post


Link to post
Share on other sites

Firstly, today I will update and upload stuff to the project website. Then I can get a fix from some developers from the LG, Samsung ports as I believe they to had this problem.

0

Share this post


Link to post
Share on other sites

hey how did you fix the rosie.apk?bcauz when i try ahdpi launcher it force closes.

thanks in advance.

0

Share this post


Link to post
Share on other sites

hey how did you fix the rosie.apk?bcauz when i try ahdpi launcher it force closes.

thanks in advance.

You will have to ask the_crevis on that one

0

Share this post


Link to post
Share on other sites

OK thanks!!

0

Share this post


Link to post
Share on other sites

I've stopped development for the time being as I don't have enough time atm due to exams. I'll try work on it a bit during the easter break though.

0

Share this post


Link to post
Share on other sites

I've stopped development for the time being as I don't have enough time atm due to exams. I'll try work on it a bit during the easter break though.

I'm on the same boat here. Anyone else care to lead temporarily?

Edited by weeo
0

Share this post


Link to post
Share on other sites

I got some time, although I still have no idea how could libsurfaceflinger cause those errors. :unsure:

Look like I gotta take a closer look at arm reverse engineering.

0

Share this post


Link to post
Share on other sites

I got some time, although I still have no idea how could libsurfaceflinger cause those errors. :unsure:

Look like I gotta take a closer look at arm reverse engineering.

You mentioned earlier that you can't find a decompiler for arm machine code. It pooped in today that on warez forums they distribute games that were modified to work with v6. That mean's that they have a working decompiler.

0

Share this post


Link to post
Share on other sites

You mentioned earlier that you can't find a decompiler for arm machine code. It pooped in today that on warez forums they distribute games that were modified to work with v6. That mean's that they have a working decompiler.

Or they can read the binary :)

Actually even I do know some instructions on x86 without a disassembler, for ex. 0x90 is NOP, which stands for No OPeration, because I used it a lot. I guess if they do it all day they learn it over time too. Now I'm looking at HTE, which as I can see is commonly used for iPhone reverse-engineering (=it can disassemble arm), but when I run it, it just don't recognize any input, neither mouse or keyboard. :( Still looking for a good reverse engineering tool. All I found is setting up GDB remotely over ADB, but that's a no go for me, as I have got one single usb port, and I'm using a usb wifi adapter.

0

Share this post


Link to post
Share on other sites

Maybe if you can get adb over wi-fi to work?

0

Share this post


Link to post
Share on other sites

Maybe if you can get adb over wi-fi to work?

That may work, although I don't like to make things like debugging available over the whole network. Will try to set up wifi via pcmcia adapter, then I should be able to get a backtrace of the crash that causes the reboot, without losing connectivity.

0

Share this post


Link to post
Share on other sites

Or they can read the binary :)

Actually even I do know some instructions on x86 without a disassembler, for ex. 0x90 is NOP, which stands for No OPeration, because I used it a lot. I guess if they do it all day they learn it over time too. Now I'm looking at HTE, which as I can see is commonly used for iPhone reverse-engineering (=it can disassemble arm), but when I run it, it just don't recognize any input, neither mouse or keyboard. :( Still looking for a good reverse engineering tool. All I found is setting up GDB remotely over ADB, but that's a no go for me, as I have got one single usb port, and I'm using a usb wifi adapter.

you can use IDA decompiler!!!

0

Share this post


Link to post
Share on other sites

you can use IDA decompiler!!!

If you pay me a full license, then OK.

:D

Edited by Sulthekk
0

Share this post


Link to post
Share on other sites

If you pay me a full license, then OK.

:D

you can decompile the native libs with the demo version.

0

Share this post


Link to post
Share on other sites

you can decompile the native libs with the demo version.

I already got the free version, it came preinstalled with backtrack. Free is X86 only.

0

Share this post


Link to post
Share on other sites

I'm not a dev, but from which phone is this sense port from?

0

Share this post


Link to post
Share on other sites

I'm not a dev, but from which phone is this sense port from?

Original rom from salsa, framework from desire.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.