I've installed KennethPenn's ROM for 2.3.4 and loving it, however whenever I try to change my camera to front facing mode, it fails and causes the camera to FC.
Is anyone else seeing this issue or is it possible that I simply have a defective/corrupted com.camera module?
TIA for any advice/solutions.
im runnings kens rom, faux kernal, and front facing camera works fine...have your tried using QIK and see if it fc's?
I hate to say, but it works fine for me also.
No issues with mine either....did you freeze anything?
Sent from my MB860 using Tapatalk
OK...thanks. I'm reflashing the ROM now. I hadn't seen others complain about it, so I figured it was likely just me.
Love 2.3.4!
Hmmm....after fresh flash, I still can't get the front facing camera to work. Fails and FC. I'll have to look into after I restore things.
I just verified that my front facing camera has no issues on KP's 2.3.4 beta 3.
Just tested. Working fine for me on beta 4.5
Sent from my MB860 using XDA Premium App
OK...so apparently I have a corrupted file for my camera app or a hardware issue. Any thoughts on how to repair/replace?
Error: The application Camera (process com.motorola.Camera) has stopped unexpectedly. Please try again.
The regular camera seems to be working fine, otherwise. Just freezes when I go to front cam (same thing happens in QIK), then I get the error.
Used KennethPenn's Rom .... going back to 1.83 safe?
Maybe you missed something. Here are the instructions I followed on 3 occasions now to flash 2.3.4 beta 3:
reboot into CWM
do a complete wipe( this order, DALVIK, CACHE, factory)
install beta 3
do another complete wipe
install the root zip
reboot and quickly press up to start in RSD mode
flash the new radio reboot in CWM
wipe cache and dalvik
Maybe following this procedure will help you.
<edit> If you follow this, and get reboots when installing apps from the Market, what worked for me was boot into CWM, wipe Dalvik, cache, and factory reset, install root.zip again, then wipe Dalvik, cache, and factory reset again, then reboot. Should fix that issue.
I'll give it a try.
I think when I restored from Ti b/u, it just rewrote the fault. I'll uncheck the camera app for the next restore
What do you mean by install beta 3 do wipe then install root.zip ???? I only have beta 4.5.
carlharsch said:
I'll give it a try.
I think when I restored from Ti b/u, it just rewrote the fault. I'll uncheck the camera app for the next restore
What do you mean by install beta 3 do wipe then install root.zip ???? I only have beta 4.5.
Click to expand...
Click to collapse
you shouldn't restore ANY of your system apps from TiBu if going between OS versions.
Well...reinstalled with lots of cache wipes, and first thing I did was (after initial motoblur stuff) to try the camera....no dice. Looks as if it's bad.
I think going back to stock and calling Moto for a replacement might be in order
carlharsch said:
OK...so apparently I have a corrupted file for my camera app or a hardware issue. Any thoughts on how to repair/replace?
Error: The application Camera (process com.motorola.Camera) has stopped unexpectedly. Please try again.
The regular camera seems to be working fine, otherwise. Just freezes when I go to front cam (same thing happens in QIK), then I get the error.
Used KennethPenn's Rom .... going back to 1.83 safe?
Click to expand...
Click to collapse
Why dont you just take the data/app com.motorola.Camera
and the system/app/BlurCamera.apk
and system/app/BlurCamera.odex
from one of these peoples working phones, then paste them into their according directories on your phone. Should fix it.
Edit: also, you will probably need system/framework/com.motorola.hardware.frontcamera
dLo GSR said:
you shouldn't restore ANY of your system apps from TiBu if going between OS versions.
Click to expand...
Click to collapse
Agree with above completely! This is what caused me to have FCs with the contact manager. When I used TiBu to restore, I only restored my apps + data, not system apps. Worked like a charm.
Magnetox said:
Why dont you just take the data/app com.motorola.Camera
and the system/app/BlurCamera.apk
and system/app/BlurCamera.odex
from one of these peoples working phones, then paste them into their according directories on your phone. Should fix it.
Edit: also, you will probably need system/framework/com.motorola.hardware.frontcamera
Click to expand...
Click to collapse
I could try that.
Anyone with a working copy of Ken's 2.3.4 want to email me the files?
carlharsch said:
I could try that.
Anyone with a working copy of Ken's 2.3.4 want to email me the files?
Click to expand...
Click to collapse
I would either pm ken or pm one of the people on the first page ( or all of them! Haha ) asking for the specific files. I would but im on bell.
Cheers
Did you search logcat and dmesg? Probably there is some info about what is the problem.
Enviado desde mi MB860 usando Tapatalk
After several more reinstalls, I "believe" I have it working again.
Related
Hi all,
Myself and @minamiki were having problems downloading from the Market after we downgraded to CM5.0.6/7 after upgrading to Froyo. After numerous attempts, we figured that it was due to Google's servers storing some information that we are on 2.2, and now we're on 2.1 it's just not working. We tried re-checkin, clearing market data, all to no avail. We also downgraded our radio.
Finally, we decided to wipe, and then flash a 2.1 ROM again. This will cause the welcome screen and log-in screen to launch on bootup, thus, re-signing into Google with new info so to speak. Once done, restored our backed up ROM, and Market downloads are working again. I'm on CM5.0.7-T3 running Froyo's radio, and @minamiki is on CM5.0.6 running EPE54B's radio, FYI .
Note: What we assume is purely our guess, but it has worked for us. So, here are the quick steps:
Step 1: Download a 2.1 ROM, such as CyanogenMod 5.0.6 or Enomther's 1.9.2
Step 2: Nandroid backup your current 2.1 setup
Step 3: Wipe, then flash the downloaded 2.1 ROM
Step 4: Upon phone reboot, sign into Google
Step 5: Go back to recovery and restore the nandroid backup
We've confirmed this to work on CM5.0.6 and CM5.0.7-Test3 .
Extra:
We did not try removing and re-adding a Google account without wiping, but that *may* work as well.
bolux said:
There might be a shorter way, go to
SETTING -> MANAGE APPLICATIONS -> GOOGLE APPS and hit CLEAR DATA
that usually forces you to sign in again in market.
I didn't have to use this when i downgraded from Froyo since my Market was working, so it's just a hypophysis.
Click to expand...
Click to collapse
Hope it helps !
Thanks, I was having the same problem and your steps worked for me
vending FC
does it fc when trying to install or just doesnt start download at all ? if it starts but then FC's
do
settings/applications/manage applications/market/uninstall updates
thats what i use to have to do when problems arose but this may be completely different
Wysie said:
Hi all,
Myself and @minamiki were having problems downloading from the Market after we downgraded to CM5.0.6/7 after upgrading to Froyo. After numerous attempts, we figured that it was due to Google's servers storing some information that we are on 2.2, and now we're on 2.1 it's just not working. We tried re-checkin, clearing market data, all to no avail.
Finally, we decided to wipe, and then flash a 2.1 ROM again. This will cause the welcome screen and log-in screen to launch on bootup, thus, re-signing into Google with new info so to speak. Once done, restored our backed up ROM, and Market downloads are working again.
Note: What we assume is purely our guess, but it has worked for us. So, here are the quick steps:
Step 1: Download a 2.1 ROM, such as CyanogenMod 5.0.6 or Enomther's 1.9.2
Step 2: Nandroid backup your current 2.1 setup
Step 3: Wipe, then flash the downloaded 2.1 ROM
Step 4: Upon phone reboot, sign into Google
Step 5: Go back to recovery and restore the nandroid backup
We've confirmed this to work on CM5.0.6 and CM5.0.7-Test3 .
Extra:
We did not try removing and re-adding a Google account without wiping, but that *may* work as well.
Hope it helps !
Click to expand...
Click to collapse
Happened to me too. All I did was flash old radio and all was well. Didn't have to do all the rest.
There might be a shorter way, go to
SETTING -> MANAGE APPLICATIONS -> GOOGLE APPS and hit CLEAR DATA
that usually forces you to sign in again in market.
I didn't have to use this when i downgraded from Froyo since my Market was working, so it's just a hypophysis.
I did flash the old radio, as did @minamiki but it didn't help us. Also, it didn't FC, rather, it hangs at "Starting downloads" . Glad it helped at least one more person!
I have the same problem so will try this now and report back
EDIT: Fantastic, all fixed and working. Thanks
Oh man! This thread is coming in 12 hours too late. I came to the same conclusion as you guys did, wiped, loaded up cyan7test3, logged in, and yes, market was back again. The only difference is, I didn't follow this up with a nand restore, but painstakingly (and painfully) went through a Titanium app restore routine. Everything works now, but man I wish you'd posted earlier
-------------------------------------
Sent via the XDA Tapatalk App
So it seems Google does store some information on what ROM version you're on .
I tried dalvik wipe, clearing market data, removing the market update, etc. none of it worked. Doing a full wipe & reinstall got it going again though, cheers!
I was so happy about not having to wipe, but... this didn't work for me nandroid, wipe, sign in, then market worked. Restored nandroid and market didn't work again...
Any ideas anyone? I really want to avoid the titanium backup method.
Worked for me on Enom 1.9.2
All right, apparently there was something terribly wrong with my market, because titanium backup's restore all data would bring back the unable to download problem too. In the end I had to skip restoring system apps' data.
Did you guys try pushing Vending.apk to /system/app from an update.zip of Cyanogens?
spyz88 said:
Did you guys try pushing Vending.apk to /system/app from an update.zip of Cyanogens?
Click to expand...
Click to collapse
No, but I suppose that would have the same effect as reflashing gapps, which didn't work.
Thanks!
Everything works fine!
Thanks!! This was driving me crazy, followed steps in first post and worked great!
Thanks to the OP for the tips! Worked for me also.
The ONLY thing I did diff was wipe, then flash CM5.0.7-T2, and then GApps AS WELL. After that I did a nandroid restore and all was well!
Cheers,
Ross
worked for me!
thanks
Thank you very much! The instructions worked perfectly!
Although I when I use the dialer and actually begin dialing a number the matched contact appears, I cant see my "contacts" anywhere else -- in the app or in the contacts portion of the dialer.
I saw in the development thread that some people were having this problem, but the only solution seemed to be to watch what you freeze with TiBu. However, I'm on a fresh flash of beta 4.5, and have frozen nothing.
Any ideas? I don't know if this matters, but in settings-->accounts, it shows my Google account, but it is not under "motoblur" accounts.
Thanks in advance.
I had this problem. What I did to fix it was flash a fresh system.img of someone on the same build as me. Sounds like your /system might be fudged.
Find someone using the same kernel&version and try that.
Edit: if nothing else works, a factory reset will work, but that may cause problems, idk ()
Yea did you reset and wipe your data before loading the new rom?
I had same problem when I didn't wipe once I did and reinstalled 2.3.4 it worked fine.
Sent from my MB860 using XDA Premium App
Yeah I wiped furiously when I originally installed it and when I reflashed. Quick question, when you re-install, did you sbf back to 1.8.3, or did you just reinstall the zip with CWM? I just reinstalled the zip so maybe I should try a clean install.
Sent from my MB860 using XDA App
I installed the CM7 rom, everything is working fine that I can tell except when i switch from camera to video camera the app freezes and force closes. I am a noob to the android rooting community, not sure if this is known or not, I have looked around the forum and found some stuff pertaining to different devices but they are also mostly year old posts, this the at&t samsung Galaxy s II forum is fairly new there isnt much that is of help here, any one else experiencing this?
Did you try to wipe cache, and data, then re-flash the rom?
This is the most stable one (just in case) http://download.cyanogenmod.com/get/update-cm-7.1.0-Galaxys2ATT-signed.zip
Yes before I installed any rom, I back up my current, than wipe data and cache and than install the rom, I am also using the correct rom.. by reflashing you mean just installing the rom from sdcard correct?
That's correct. Also, go under Advanced in recovery and clear the Dalvic Cache. It can leave behind tidbits that can cause problems as well.
ZeroIsntTheHero said:
That's correct. Also, go under Advanced in recovery and clear the Dalvic Cache. It can leave behind tidbits that can cause problems as well.
Click to expand...
Click to collapse
Ok, I will try that, now when I do that, I need to install a fresh CM7 rom, not my backup of CM7 correct?
penskyc said:
Ok, I will try that, now when I do that, I need to install a fresh CM7 rom, not my backup of CM7 correct?
Click to expand...
Click to collapse
Ok, so I restored, wipe partition,cache and Dalvic, than restored from a CM7 backup, no dice, i than redid it, wiped everything again, installed from the zip, same problem i freeze when trying to change to video camera in the camera app, is anyone else having this problem? or is video working fine for you guys with an AT&T Samsung Galaxy S II?
penskyc said:
Ok, so I restored, wipe partition,cache and Dalvic, than restored from a CM7 backup, no dice, i than redid it, wiped everything again, installed from the zip, same problem i freeze when trying to change to video camera in the camera app, is anyone else having this problem? or is video working fine for you guys with an AT&T Samsung Galaxy S II?
Click to expand...
Click to collapse
Not having that issue myself with CM7.1
Sent from my SAMSUNG-SGH-I777 using xda premium
Kadin said:
Not having that issue myself with CM7.1
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
very very strange, I mean if I am wiping everything I am technically doing it from scratch correct? or would i possibly benefit from doing a complete factory restore and totally deleting everything (including rom back ups, downloads, titanium backups, etc.)
penskyc said:
very very strange, I mean if I am wiping everything I am technically doing it from scratch correct? or would i possibly benefit from doing a complete factory restore and totally deleting everything (including rom back ups, downloads, titanium backups, etc.)
Click to expand...
Click to collapse
Its very odd to have a problem with the camera, even after re-flashing, and doing all that that you've done. It should've worked. Have you tried flashing a different rom, one other than cm7? Because if it still doesn't work on other roms, then you definitely have a hardware problem with the camera.
b4d455b345t said:
Its very odd to have a problem with the camera, even after re-flashing, and doing all that that you've done. It should've worked. Have you tried flashing a different rom, one other than cm7? Because if it still doesn't work on other roms, then you definitely have a hardware problem with the camera.
Click to expand...
Click to collapse
Ok I just wiped again and installed cognition x2 beta 4, it essentially looks just like my stock samsung but it does read cognition on the about page. Camcorder works fine, only in CM7 when i slide the switch to record video do I have a problem
I am having the same issue with cm7. When I switch to the camcorder the application fc. Is anyone else having this issue.
Try installing the Camcorder Shortcut App
Someone posted a solution to this over on the CM forums ht tp://forum.cyanogenmod.com/topic/32601-camera-keeps-force-closing/page__view__findpost__p__246546
remove the space between the t's (can't post links)
X7- said:
Try installing the Camcorder Shortcut App
Someone posted a solution to this over on the CM forums ht tp://forum.cyanogenmod.com/topic/32601-camera-keeps-force-closing/page__view__findpost__p__246546
remove the space between the t's (can't post links)
Click to expand...
Click to collapse
Thank you for the link!
Step #4 dowloading the camcorder launcher app worked. Opened it one time now I can access my camcorder through the camera app.
Also having the same issue. Will try the CM Forum link.
X7- said:
Try installing the Camcorder Shortcut App
Someone posted a solution to this over on the CM forums ht tp://forum.cyanogenmod.com/topic/32601-camera-keeps-force-closing/page__view__findpost__p__246546
remove the space between the t's (can't post links)
Click to expand...
Click to collapse
Very excited to try this! I am back to stock rom right now, so I will switch roms and let you know!
I have the same issue
abacon15 said:
I have the same issue
Click to expand...
Click to collapse
If you install Camcorder Shortcut App from the market it resolves the issue. Just open the app and use it once and then close out. When you open up the stock camera app the camcorder option should work.
moustro said:
If you install Camcorder Shortcut App from the market it resolves the issue. Just open the app and use it once and then close out. When you open up the stock camera app the camcorder option should work.
Click to expand...
Click to collapse
this worked for me aswell, thank you a million!
I installed the app and it works in that it lets me record video. However, after closing, opening the camera, and trying to switch, it force closes again. Also, on the camcorder shortcut, it is only using my front-facing camera.
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
TeamRainless said:
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
Click to expand...
Click to collapse
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Wanamlite. Latest version. And I sure did...
TeamRainless said:
Wanamlite. Latest version. And I sure did...
Click to expand...
Click to collapse
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
TeamRainless said:
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
Click to expand...
Click to collapse
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
kilometers4 said:
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
TeamRainless said:
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
Click to expand...
Click to collapse
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
TeamRainless said:
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
Click to expand...
Click to collapse
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
kilometers4 said:
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
It absolutely was. But what did it do and how could I fix it?
Hello guys
I need your help here. So I flashed this new ROM, and the Google Push service seemed to have stopped working completely.
1. Gmail not pushing.
2. K9 push not working
3. Google play store not pushing as well
I have played around (sync on,etc) but I can't seem to find what's wrong with it. So I tried to restore a previous Nandroid backup, but the md5 checksum was mismatched!
I then tried to wipe everything, reflash new ROM etc, and yet the Google Push services aren't working as well.
Can anyone help? I am stuck, I can't go back due to md5 checksum error, and I can't move forward because I don't get Google Push services
budisuharto said:
Hello guys
I need your help here. So I flashed this new ROM, and the Google Push service seemed to have stopped working completely.
1. Gmail not pushing.
2. K9 push not working
3. Google play store not pushing as well
I have played around (sync on,etc) but I can't seem to find what's wrong with it. So I tried to restore a previous Nandroid backup, but the md5 checksum was mismatched!
I then tried to wipe everything, reflash new ROM etc, and yet the Google Push services aren't working as well.
Can anyone help? I am stuck, I can't go back due to md5 checksum error, and I can't move forward because I don't get Google Push services
Click to expand...
Click to collapse
go to settings , accounts , Google delete it , then log in again
Yup, done that, still doesn't work. Plus k9 push isn't working either, it seems that the whole push function is completely broken
Sent from my GT-I9300 using xda app-developers app
Push seems an issue with XXDLI8 (at least in HyperGalaxy 1.8), just revert back to XXDLI7.
Yup I read about that too. The thing is I'm still on ICS, and I have never flashed a jb rom before. The error happened when I flashed hyper galaxy 0.7, which is a ics build.
I have given up on that rom, and I'm not on other rom and the push problem persists. I'm not sure what I did wrong, it's like the problem sticks despite me wiping cache, and everything else.
Sent from my GT-I9300 using xda app-developers app
Maybe you can supply some more info, like what ROM and version are yiu using now, which baseband and what install procedure did you follow exactly?
j0ep0 said:
Maybe you can supply some more info, like what ROM and version are yiu using now, which baseband and what install procedure did you follow exactly?
Click to expand...
Click to collapse
Sure, here it goes. I have been flashing ROMs etc since 2010, so I am quite familiar with the concept, but this baffles me, before I can't seem to wipe everything clean and restart from point zero, because the problem sticks even after a new ROM is flashed. Is there more to this? Like modem/baseband etc? Thanks in advance for your help!
Baseband I9300XXLH1
Kernel Siyah s3 v 1.5 beta 4
Build no IMM76D.I9300XXBLG9
WanamLite ROM XXBLG V2.2
Thank you!!!
Ok I got it figured out already.
Previously I was on a full feature rom, then I flashed to a stripped down rom. I was short of a few apps, so i flashed additional apps, extracted from titanium etc, without checking their compatibility etc.
When I flash a new rom after that, I'll restore all system data via titanium, and that's why the problem persists. If I flash a new rom without restoring system data, then it's fine.
It's strange though, you'd think that titanium would be able to pick up on that if they aren't compatible.
Anyway problem solved and thanks for your kind assistance!
Sent from my GT-I9300 using xda app-developers app
well happy that you found out a solution. generally titanium backup is used only for restoring apps not for system settings
jaidev.s said:
well happy that you found out a solution. generally titanium backup is used only for restoring apps not for system settings
Click to expand...
Click to collapse
Yea I realised that with SGS 3. With HTC Desire on Froyo/GB, the issue was nearly non existent, I never had a single issue, be it from Sense to AOSP, back to Sense etc.
Flashing is quite a pain then, if system apps can't be restored via Titanium, having to re apply settings like ringtones, widgets etc?
u can make a nandroid backup and restore
do kernels affect push ?
sorry to bring up an old thread, but i didn't want to open a new one just for this
i've recently flashed Perseus 24.2 over Omega 27.2 and noticed that Push notifications dont work when the phone is sleeping.
to get it working, i have to open up the app (eg. Whatsapp, hotmail) and i get all of them at once.
did a nandroid rollback to stock kernel and it was working fine
Q. is there a specific setting to kernels that may affect push?
probably Android ID problem
i didn't want to open a new thread for same kind of problem.
Problem occured when i fresh install DLIB (with wipes and everything). After installation complete, i've restored apps + systemdata with titanium. While restoring, it asked me to whether use new android id or restore the old one in backup. I choose to restore old one. then problems started.
- I can't use Google Play on the web. It says "there is no phone connected to this google account"
- none of my notifications are working. and i assume it is about android id. (today using Titanium i switched to new android id but nothing changed)
any guesses?