Hi!
I have been using for two years three different versions of the same GPS navigation application ( 8.xxx, 9.xx.3 and 9.xx.8) on a Samsung Galaxy i5500 ( stock ROM: Eclair 2.1 and then Froyo 2.2).
Yesterday I have noticed that this app ( vers 9.xx3) has some errors: autorotation didn’t work and some buttons were almost outside of the display area (looks like display area shrunk). I reinstalled the app. Nothing changed.
I uninstalled v 9.xx3 and I installed v9.xx.8. After installing, at the first use, there is a configuration wizard. At the end of that wizard, the app freezes or closes. Two days ago, this version ran smooth. I reinstalled app. Nothing happened.
Factory data reset. I have installed v 9.xx.3 , 9.xx.8. Nothing changed.
I have tried vers 8.xxx. Good news: That version worked well.
Factory data rest once again. Wipe data/wipe cache/wipe dalvik cache/format system/format cache. I have installed v 9.xx.3 , 9.xx.8. Nothing changed.
I have checked with Display Metrics Info the screen resolution. It is all right: 240 x 320.
I have flashed with Odin stock ROM
I5500XFJPZ_I5500OXFJPN_CNX.
Nothing changed.
I have tried custom ROMs:
BluedroidMod-2-20130508-1.5.8-galaxy5
CyanogenMod 7.2.0+ Galaxy5 Port
CyanogenMod 7.1……
JellyBread v4.5
New Experince version 4.0
Exactly the same situation:
8.xxx OK,
9.xx.3 autorotation didn’t work and some buttons were almost outside of the display area
9.xx.8 freezes / closes at the end of the configuration wizard.
I didn’t notice any other errors. Any other apps seems to work well.
I don’t know if it is important:
I have used CWM 5.5.0.4.
If I upgrade to CWM 6.0.1.2, after wipe data/wipe cache/wipe dalvik cache, the phone froze at android logo ( but one explanation could be, maybe, the incompatibility EXT4 – RFS file system).
Also, I have tried to flash CyanogenMod 10.1 Galaxy5 Port, but it froze at CyanogenMod logo.
So, could someone explain to me what is happen?
Is there a software or a hardware problem?
If it is a software problem, why does it occur in so many ROMs? Which is the “software piece’ that is unchanged by flashing different ROMs?
What could I do?
Any advice will be appreciated!
P.S.
If it does matter, the app I have talked about is IGO Primo.
9.xx.3
myuplbox.com/file/download/645579
9.xx.8
share-byte.net/uKhgxc
Related
Hi!
I own my Xperia mini pro x10 about 3 month.
Tried more ROM-s, and stopped at CyanoComb v1.2.
Everything was OK till yesterday, when suddenly my hardware keyboard stoped working. Neither of buttion won't responding. I CAN navigate with 3 buttion on face side of phone (back home..) and with volumen up and down.
I tried to make factory restart, then wipe cache, wipe dalvik cache throught recovery, but the situaition is same.
Then I tried to install stock ROM (few of them) and the hardware keyboard problem is still out of function.
Then I tried to format /system partition and installed again stock ROM (again few od them) and same
Whats happend?
Phone wasn't used so frequently that this would happen..
Is really my hardware keyboard died or it is a software problem?
Please help!
ROM - MiniCM7 Pro - V18
I was using v7 previously, was planning on doing a reset but instead i decided to upgrade to v18
wiped davlik cache
did factory reset
installed new rom
Since then any apps i've tried to install from markey, from apk, and through adb cause the phone to reboot...
any ideas?
Looking like it may be a hardware issue... just tried to install GingerDX pro 17 and EVERYTHING force closes... I can't even get through the setup process.
Edit:
Rebbote and got the lock screen, once I unlocked it the first thing that pops up is "complete action using: launcher pro or zeam launcher". both force closes. Screen goes black, and comes back up with "the process cm.google.process.gapps has stopped...."
Firmware update fixed it kind of, got amazon and pandora installed. Amazon Appstore failed at first, however a reboot fixed the install, but force closing every time i open it
Uninstall and Reinstall fixed that... Guess it's just trial and error from this point on
New Update on the issue...
All of a sudden after a reboot, the market and all of the apps I installed since getting MiniCM7 Pro - V18 back have disappeared. Tried to reinstall the ROM and market is still gone
I can attempt to get the market back, just curious if anyone else has had issues similar to this
Wiped davlik cache
factory reset
reinstalled rom
factory reset again
And its working again
I got everything working as intended... then my battery died, and I'm stuck on the Sony Ericsson Screen. At work so I can't do much to fix it, and can't get to the recovery menu.
Hello,
first... im a noob, and have only a little clue about android systems.... i will try my best
second the problem:
I flashed an old S2 with gingerbread with a lot of firmwares and got nearly evry image to wort without NeatRom -> no respons -> recover with odin...
but the problem is that as i select the camera-app the flash-led is going on, and i cant switch it off. its buring the whole time the camera app is active..
with the flashlight-app i can switch it on and off as i like.
this problem exists in RR_JB_V3.1.3_AOKP_4.2.1_I9100 as in pac_i9100_4.2-milestone.1.release_20130806-205645 and in sentinelrom_v4_80_i9100
does anybody know if this is an ROM fault or is it in the cam app?
yours Platonshead
PS: my actual image is the pac one...
Have you bin formatting before flashes? I have used aokp 4.1.2 "my trusty nandroid" as this is perfect rom and faultless and I have used pac 4.2 and that didnt do this either. What I would do Is format system, data, cache, wipe dalvki and then flash rom and see if this fixes this problem.
andrewwright said:
Have you bin formatting before flashes? I have used aokp 4.1.2 "my trusty nandroid" as this is perfect rom and faultless and I have used pac 4.2 and that didnt do this either. What I would do Is format system, data, cache, wipe dalvki and then flash rom and see if this fixes this problem.
Click to expand...
Click to collapse
no i have only made a factory reset, a cache wipe and a dalvki wipe and flashed the roms...
but... today i tried it with formating and got the same problem. (also with pac)
i also tried another firmware: stock pda: I9100XXLPJ with phone: I9100XXLPJ and an unknown CSC whatever that means.....
and there the cam is also showing this strange behaviour.
the funny thing is that i dont think its a hardware problem as i can swich the light on and off as i like per software app.
does anyone know a way to test the hardware-function of the phone just to exclude this source of failure?
thanks sofar
EDIT:
1. my girlfriend just told me that this "feature" was always there and so i think maybe it IS a hardware bug.
2. i just tried to figure out why the app "flashlight" can handle the LED whereas "camera" cant.
i can listen (with a silent room and my ear near the LED) that if i turn on the flashlight, the camera just open up the lens (it just sounds like that) and when i switch it off i hear a similar sound.
-> is the flash somewhat connected to the camera or "exposure" function?
Update 2:
i Tried another camera firmware with *#34971539# (from ocef02 to ocee0? to te??28) but nothing happend. -> also the Version of ROM (GB, ICS) changed nothing...
seems like HARDWARE....
but: I think the flash-LED is mounted on the mainboard. changing the cam-module will not change the LED. right? has anybody solved this type of "damage"?
Hi guys, recently my S3 started to play up on me. The screen started to flicker and would only stop when I touched (and held) the screen. From then, things have gone from bad to worse and the phone now features a completely black screen after it is powered on. Therefore I cannot see the startup animation or anything else (including the home screen etc) but can hear the notifications and vibrations.
I can fortunately use CWM as this is not effected at all and the screen works perfectly fine. I have flashed 3 different roms and wiped my whole device since the problem started hoping it was a software problem.
I have additionaly tried:
- Clear the Dalvick Cache
- Clear cache
- Wipe data/factory reset
- Wipe all SD card data (don't ask)
Hopefully someone can help I would really appreciated it. (Not enjoying using the old Symbian phone atm) :crying:
Thanks
Make sure you are flashing roms meant for your version of the device.Try changing kernel or flash the latest stock firmware available after a factory reset. This should replace every file on your phone. Any problem would be fixed by this. Secondly what CWM do you use? Is it touch? If so does the touch work? Not likely a panel issue if the display is working in CWM, Can be a digitizer issue causing the screen to act up.
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.