I have been having so many issues with my phone of late, I decided to just throw it back to locked and stock. I am doing the initial bootup after a complete wipe and factory restore to stock ROM, and while it is going through the initial set up, every time it tries to display the softkeys at the bottom of the screen, it pops up with "Unfortunately system UI has stopped", and is preventing me from completing the setup of the device. I am really at my wits end, as the device is now back at square one complete and total stock. Please, if anybody has any ideas, I'd really appreciate your help. I am about 6 months out from the end of my contract, so I'm not really in a position to replace the phone.
To paraphrase Princess Leia, "Help me xda-developers; you're my only hope."
P.S. Can't figure out how to delete the thread - I was able to push my way through the initial setup, and once the system got into the launcher, the softkeys appeared, and so far the phone appears to be working. It's going to be a long 6 months.
P.P.S. Everybody here in these forums is [email protected]#$ing awesome, so please continue to be that way. (At least those that have responded to me have been anyway.)
Nobody shared their experience and tried to help (publicly, at least) maybe because we also have a life outside xda?
Not to mention there's tons of threads discussing more or less the same stuff. And you didn't even provide info on how you're flashing a stock ROM.
Glad you got it covered.
a manta sent this.
Related
Hey all,
I have owned my Tilt 2 for a little over 6 months now and have seemed to have problems with it since day one. Its a little hard to describe the exact issue but I will do My Best.
First of all, I am currently Using the Latest Energy Rom for the Phone from xda developers. I have installed both hot Fixes on my Phone from HTC and I do a hard reset every time I upgrade my rom.
This is a problem I have had since getting the phone and seemed to be present in the Stock Rom that came from ATT so I am not convinced that it is a software problem, but I thought I would get some opinions here first. My Concern is that the phone itself has issues and I may be out of luck because I have had the phone and dealt with the issues for so long.
So, My Biggest problem is one with Freezing. I have to reset my phone at least 5-10 times a day. I always have. Sometimes I even have to remove the battery to get the phone to reset. I do quite a bit of Texting with my phone and the freezing almost always seems to happen after I have sent a text and am trying to get back to the Home/Today Screen. The Phone just sits there, I can hit the end call button as much as I want and it will not go back to the home screen. The Phone is not completely locked tho because most of the time the Calling features still work, and I can even hit the windows button and get into the menu where I can get to task manager or a software reset button. If I try to hit the home Icon tho nothing seems to happen. The Phone just sits there and I have to reset it to get it working again.
This is frustrating me because the phone is not actually frozen, it seem to be stuck thinking but will never come back to life. When the phone works, its works great and does everything I need it to do. The Constant freezing and resets are driving me crazy. Any help or suggestions would be appreciated. I am pretty tech savy and have been installing roms on my phones for a couple years now. Please Help before I toss this thing out the window.
Vgamer4550 said:
Hey all,
I have owned my Tilt 2 for a little over 6 months now and have seemed to have problems with it since day one. Its a little hard to describe the exact issue but I will do My Best.
First of all, I am currently Using the Latest Energy Rom for the Phone from xda developers. I have installed both hot Fixes on my Phone from HTC and I do a hard reset every time I upgrade my rom.
This is a problem I have had since getting the phone and seemed to be present in the Stock Rom that came from ATT so I am not convinced that it is a software problem, but I thought I would get some opinions here first. My Concern is that the phone itself has issues and I may be out of luck because I have had the phone and dealt with the issues for so long.
So, My Biggest problem is one with Freezing. I have to reset my phone at least 5-10 times a day. I always have. Sometimes I even have to remove the battery to get the phone to reset. I do quite a bit of Texting with my phone and the freezing almost always seems to happen after I have sent a text and am trying to get back to the Home/Today Screen. The Phone just sits there, I can hit the end call button as much as I want and it will not go back to the home screen. The Phone is not completely locked tho because most of the time the Calling features still work, and I can even hit the windows button and get into the menu where I can get to task manager or a software reset button. If I try to hit the home Icon tho nothing seems to happen. The Phone just sits there and I have to reset it to get it working again.
This is frustrating me because the phone is not actually frozen, it seem to be stuck thinking but will never come back to life. When the phone works, its works great and does everything I need it to do. The Constant freezing and resets are driving me crazy. Any help or suggestions would be appreciated. I am pretty tech savy and have been installing roms on my phones for a couple years now. Please Help before I toss this thing out the window.
Click to expand...
Click to collapse
It is usually not desired to post the same information twice on different forums. The NRG thread has some responses to THIS EXACT POST that was made there. I know that cut-n-paste is easy, but avoid the temptation.
stevedebi said:
It is usually not desired to post the same information twice on different forums. The NRG thread has some responses to THIS EXACT POST that was made there. I know that cut-n-paste is easy, but avoid the temptation.
Click to expand...
Click to collapse
Will Do, I was just not sure where this questions belonged as I am unclear as to whether this is an NRG issue or a Phone Issue.
I have not had this experience, but I have read a lot of posts in the tilt forums where people complain of slow/laggy behavior using the htc messagaing tabs... I wanted to avoid that, so I just mapped my push-to-talk button to the windows mobile messaging client and use it. You might try doing that, if the HTC is what you are using now...
Off subject (new to this) but you mention "tilt forums" How do I find these s for my tilt phone? Looking for new apps also... I'm old
I'm hoping you Android experts can help me. I need LogCat interpretation. Since updating to 2.2 (not rooted), I've seen my phone go to a white HTC screen followed by a re-start of the home screen. It ends up being on the home screen page I was at, not the "center" one.
This has been happening several times a day, usually when unlocking the phone or exiting from an app. It seems like it's related to receiving some sort of alert while locked or using an app.
I have a LogCat excerpt which I snagged while taking some screen shots with ddms. I was snapping screens from Dolphin. After I was done, I used Dolphin's menu Exit button to stop Dolphin. I got the white HTC screen then the home screen restart. I've attached the relevant LogCat data. Can someone look at this and tell what happened and why the home screen restarted? I am looking for real concrete info. There is a ton of Old Wives' Tales going around about this and I'm not interested that sort of nonsense
PS: I tried to post some context in the form of CODE blocks from LogCat but I got refused because this forum prohibits me from posting "outside links". There is no hyperlinking info in the LogCat info, but...
I am also getting the same issues. Using virtuous 2.5 and BFS#1. If this doesn't get better, I am just going to try a different flash and see how it goes.
Sigh... I was hoping one of the Android jocks here would be able to tell from that LogCat. I see this mentioned in other threads on other forums. But all I have found amounts to old wives' tales.
Sorry I don't know how read those but if your not rooted I don't think it matters anyway because you cannot access those files. I would root the phone Unrevoked forever with s-off and then download rom manager if you have never flashed roms and stuff. from rom manager install your custom recovery and do a nandroid backup. So from this point basically you can do anything short of changing the radio without worries. because if you mess it up just boot into recovery and restore from the nandroid backup. you will be no worse off than you are now. you can download stock 2.2 or even try virtuous 2.6. its awesome and super stable. in fact it runs better than stock did. Anyway good luck all the info you need is on the forum. if you have a question i will try to help but im not a computer programmer but i have been playing with android for about a year.
Jonathan --
I finally went back and looked at this thread. I did root the phone with the Reflash from the #unrevokedtest IRC channel. In fact it went so smoothly, I "gave back" by spending several hours a night for 5 nights helping and encouraging others on IRC. Then I wrote up an article based on the things people had trouble with (see http://bit.ly/aBez98). One of the unrEVOked guys picked it up, made some suggestions, I edited it, and now it's linked in the /topic of the channel. Your suggestion pushed me over the edge.
I am using Auto Memory Manager, which allows you to tune the way the OS prunes tasks. With it set to "Mild" my Sense restarts are a thing of the past.
I'm pretty sure that somehow the HTC Sense "app" is actually getting pruned by the OS, causing it to need to start from scratch when exiting from whatever task needed that extra bit or memory to run. It's not a bug, it's a feature!!!!
Thanks..I'm gonna try this.
I don't like spending hours tweaking task killers and the like.. but if I'm ever showing my phone to someone, I don't want the phone to appear buggy.
On the same token, I'd like to know when this feature is updated to prevent the symptom.. so I can dump the memory manager.
I tested the solution of using Auto Memory Manager configured to Mild for a couple weeks... I don't feel there was any improvement. Anyone else?
I had a strange reset of my phone last night, through what I think was no real action on my part, but I wanted to defer to the experts and see if anyone can help me make sense of this...
Also, as you'll see at the end of my post—if you make it through my rambling—I could find some of the info I seek elsewhere on this, and other forums, but the combination of data would be a difficult scavenger hunt and I thought this thread may help other lite (or lazy) power users with similar issues or info searches in the future...
So I was changing my battery out last night and when I was pulling the dead one out I had accidentally turned the phone on, but was talking to someone at the time and, being distracted, continued pulling the battery.
I got the new one in and turned the phone on to be greeted by what I think is called, and excuse my ignorance on terms as I have had no real interest in rooting to date, the debug screen—white background, cute little android rascals on the bottom, several restart options, etc. I believe I selected 'fast boot', as I think I have done when some random serious of events have greeted me with the 'debug' screen in the past.
All seemed fine and the device started up but it lagged on a black screen with an icon I interpreted as an 'update' icon and a progress bar. When I got to the OS, my settings, screens, apps, etc were reverted to stock conditions. My SD card retained all its contents and I used AppBrain so I was able to get things back to some semblance of normalcy rather quickly, but I am left with so many questions...
I've come up with 3 possible explanations...I made an error on the 'debug' screen, my device had a huge and random hiccup, or there was some strange update last night that, despite my best efforts, I cannot find mention of here or on any other forums.
Some additional info...
-on App Brain site, after linking the reset device back up to my E-mail/account, I have a totally new list named, not by the former 'ADR6300', but by 'HTC Droid Incredible'. This leads me to believe either AppBrain has changed its naming convention for this device since I originally set the app/account up, or there was some strange mystery update.
-I have always updated when prompted so I believe I was running the newest OS and am still on 2.2 now.
I'm not really looking for a solution to the reset, more looking for answers/theories and some preventative measures for reducing possible distress should something similar occur in the future.
-back-up methods...I use Launcher Pro Plus - paid, and just realized I can back-up home screens and settings through the launcher but is there anything else I should be doing?
-break down on that 'debug' screen, best option to choose for various issues, etc.
-has anyone heard of a similar story, update last night, or know the reason for AppBrain's new naming convention for my device?
Any other info, tips, or relevant advice would be much appreciated. As a Web/graphic designer and modern woman I am inquisitive and technical by nature but tend to subscribe to the 'if it aint broke, don't fix it' school of thought unless there is some new feature I hear about or want when it comes to my device. So I am not dense but I definitely don't know everything and I am looking to you, the 'experts' for answers
You held vol - and the pwr button when you turned on the phone. That is what made you go to the bootloader (debug). From there i'm guessing you had the phone do a factory reset, that is why everything went back to how it was when you first bought the phone.
2.2 is the "newest" build available without rooting your device.
Rooting and making a backup through Recovery is the best way (imo) to create a backup.
For what it's worth, I think g00s3y is spot-on
When you get to the hboot screen (the white screen with the Android dudes at the bottom), there should be 5 options:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
FACTORY RESET
Seems most likely that you mistakenly hit the last one rather than the first.
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
patrioticparadox said:
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
Click to expand...
Click to collapse
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware. Make sure you wipe data and dalvik a couple times and go to mounts and storage and wipe system too. Do those a couple times, I always do just to be sure it works. Then after that try to flash another ROM stock or custom doesnt matter. This will help a lot.
Just a recommendation, I use and LOVE Codename Android Rom. Very very fast and stable with a lot of features.
Anyways, post back when you wipe everything out and flash a new ROM on there and let me know the outcome.
nothing yet...
myboyblake said:
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware.
Click to expand...
Click to collapse
Just finished flashing the 4.1.1 back and still the same issue (did all of the data wiping). I'll try a custom ROM now though I doubt its going to make any difference.
What in the world has got a hold of my camera?
No dice
"Unfortunately Talk has stopped responding" on the first screen. "Gallery has stopped responding" when trying to open Camera app.
So despite several wipes and two distinct ROM flashes (used PARANOIDANDROID the second time) my device is still acting up.
Please help me out people. What is causing this error that is lasting across ROM flashes? What can I try to resolve this issue?
Rewiped everything and reflashed PARANOIDANDROID (2.23) just to be sure and still the camera doesn't work
seems like perhaps the registers ended up in an odd state.. know this is for a different phone, but you might give it a shot..
http://www.droidforums.net/forum/dr...amera-app-stoped-working-wont-initialize.html
---------- Post added at 05:03 PM ---------- Previous post was at 04:46 PM ----------
Looks like OMAPFlash can do a full reset on all the camera registers from looking at:
./Targets/Definitions/definitions_omap4.txt
in the OMAPFlash zipfile..
It might be worth a shot..
Slide opultl
No dice... I assume you were referring to clearing the cache and data. I had tried this before but gave it another shot anyways. In case you meant the screenshot part, I did that too and the screenshot captures fine but still the camera does not function. Also holding down the volume down and power keys never shuts the phone off I assume that is device specific (though several seconds after the screenshot captured the screen did flash off then on very quickly). I have tried disabling Gallery and rebooting in the hopes that would free up the hardware. Failed.
I am uber stuck on this.
Why is this persisting across flashes and what can I try to resolve it?
edit: just noticed that the bottom of your post was more info and not a signature. I'll look into that. Ran out of "thanks" for today but I'll get you yours
Since it won't delete....
As an update: I have tried contacting both Verizon and Samsung about the issue. Both recommend returning the device under warranty (as was expected). This would be fine except that I LEARN NOTHING! If the Samsung techies have a protocol/enumeration/anything to discover and resolve the issue then so can I (potentially), which means the general public should have this knowledge too, right? WHAT IS MY NEXT STEP?
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Here's a link, sorry I didn't post soon - I don't check back here often..
patrioticparadox said:
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
Click to expand...
Click to collapse
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
I don't think it going to do a reg reset for the camera by default..
This is from: Targets/Definitions/definitions_omap4.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET 0x4A1000C0
It is pulled in and used by:
Targets/Configurations/configuration_omap4460_tuna_8g.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET needs to set for the correct location -- I have not done any digging, so I don't know what the location is..
Just Found this -- https://github.com/omapconf/omapconf/wiki
omapconf can be used to read/write/modify any register from within Android..
Mach3.2 said:
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
Click to expand...
Click to collapse
Insurance fraud? Um get a life! That's not why their premiums are high you ass! They do it to make more money you jack knob. My company charges $65/yr with a $25 deductible with up to 5 claims a year! That's so much better than asurion. And they give you a piece of **** replacement. Is all about money not the customer...now please me nice. Great ideas come from working together not from being an asshat!
Hi all,
Hopefully someone can shed some light on this and help a tortured soul. By no means am I an Android expert, but I definitely am not a noob. I had an S2 in the past and done plenty of flashing there, and now own a Bell SGH-I747M S3... my precious...
First off I tried a whole bunch of different ROMs, of all flavors (AOSP, AOKP, CM10, PARANOID, and some TW), and a lot of them are awesome. However, I found that after having done so much flashing and customizing using other people's work, it was now time for me and attempt to make my own ROM. I feel I now have the knowledge to do so. Don't get me wrong, I am far from a Dev, and I don't do much coding at all. I found this great suite called Android Kitchen, which pretty much guides you through the steps for making your own ROM, and it's great for learning.
In the end, I was able to come up with a final working version of my own ROM, built from scratch using the original official Bell JB 4.1.1 update file. and I have to say I am quite proud of it, as it has all the apps, features and theming that I want, and works quite well I might add. I get great results performance and battery wise (for my taste and needs) when using my ROM with KToonsez kernel.
BUT!!... as good as I think the ROM is, it is unfortunately not flawless. I do have an issue (the only one I could find so far after 2 weeks using it), and for me it is a BIG issue. Maps/Navigation does not seem to like the ROM/kernel combo on MY phone. I say MY phone because I have setup a friend with pretty much the same thing, and he is not experiencing the same issue.
Here is a description of the problem I get. Let's say I go to my contacts and select one with an address. I will touch the address, then Maps opens no problem, and finds the place, and I also get fast GPS lock, no issues there either. Then I will select Navigate to get a voice turn by turn description while driving. The Nav app starts OK as well and seems to work fine. Then after a few minutes (sometimes 2 sometimes 10), Navigation will shutdown, and I get a pop-up saying "Unfortunately Maps has stopped working...". When I OK that, after a few seconds, Navigation starts talking to me again, although not on screen. Also a Navigation icon will appear in the notification area, and if I hit that it resumes Nav, as if nothing had happened. Another few minutes like that, and then I get the same message again, but this time it crashes for good. ALWAYS!!
Troubleshooting:
- Flashed the ROM/Kernel 3 times now. Always wiping and formatting ALL!
- Cleared cache and data from Android Settings/Applications
- Cleared cache from Maps settings.
- Re-installed Maps
- Wiped phone cache, dalvik cache and fixed permissions from recovery.
- Changed kernel back to stock (that seems to work fine btw,, but I do not want stock kernel, plus the setup I want works well on my friend's S3, same as mine, which I setup myself for him (he's a total noob)).
- Changed kernel again from stock to KToonsez (that also works fine after that, however I get other things that start not working well... too many).
- I always wipe cache, dalvik cache and fix permissions after changing kernels.
I have been poking at this for about a week now, and I am tired! I was hoping someone would have a suggestion, maybe from past experience. The only thing I can think of that is different on his phone and mine is the apps that we restore after installing the ROM and kernel (Titanium Backup, user apps and data only, nothing related to system is touched). I am guessing one of my apps could cause a conflict, but pardon my laziness, but I really do not feel like testing / installing my apps one by one to hopefully without guarantee find a culprit... way too many apps for that So I am testing my luck here on XDA... there are a lot of smart people here
I appologize for the lenghty post, but this way, there is less chance I left anything out... PLEASE HELP!!!
Raz...
Sorry for the bump guys... I was really hoping someone can give some input here. Desperate for a solution here!!
Thanks