Jump to content
  • Advertisement
Sign in to follow this  
Sollum

Question about screwing up your phone with unoptimized code...

This topic is 1409 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Good evening,

My phone is killing me, i have sent it to repair service 3 times and 3 times they replaced motherboard.
Few days i've got it back. It restarts itself and crashes when i try to play my projects or debug them. Now it's stuck in boot loop for the second time.

I have done 1 native android program and 1 with LibGDX API, both published on Google Play. Now i am working on my third game.

Is it possible to screw up your phone by unoptimized code?

 

I am testing my code on tablet and everything works just perfect!

 

 

 

At this point i am just really frustrated and lost. Is it my code or warranty service is unable to fix my damn phone by replacing freagin motherboard 3 times in a row!



Using HTC...

 

Any help would be appreciated...

Edited by Sollum

Share this post


Link to post
Share on other sites
Advertisement

Not through lack of optimizations.

 

In theory the Android OS will keep your app inside a nice little sandbox, that sandbox is self-contained, and the OS can de-prioritize or kill off your sandbox if you start to do things wrong.

 

It is still possible for your app to crash or cause other problems, but those should only trigger after you start your app.

 

 


Now it's stuck in boot loop for the second time.

 

Unless you've done something weird like trying to auto-start your app during the boot cycle, or you are doing things like writing OS mods or custom ROM images, you shouldn't be able to cause a boot loop under the normal course of development.

Share this post


Link to post
Share on other sites

Thank you for reply,

From what i know, i am not doing anything that interferes with OS.

Share this post


Link to post
Share on other sites

Sure you just don't have a lemon for a phone or a bad custom ROM?  At work we using a HTC Desire, Inspire, and One and have never had any issues with them.  Back when we started mobile the Desire got quite a few hard crashes where the battery had to be pulled to reset it.  As frob mentioned, you app is sandboxed on Android so it shouldn't have access to anything it shouldn't unless you are trying to do some kind of rooting stuff yourself.

Share this post


Link to post
Share on other sites

Ill try to take it to a warranty again.

Each time they claim to have fixed it by replacing main motherboard, saying that hardware burnt. Like wtf....

It's HTC One S by the way

Edited by Sollum

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!