[Q] guys help plz for motoGinger 2.3.4 - Defy General

Hi Guys,
my defy was working smoothly until I enabled vsel through 2ndinit and set the values to [email protected], [email protected], [email protected] and [email protected], Then I installed busybox installer and super manager. And also copied services.jar to system/frameworks. But now my phone takes 5-10 min to boot abd as soon as it boots I get a hell lot of force closes unable to launch any app, the force close keeps getting back one after the other what do u think the prob might be with? I had uninstalled busybox installer before i rebooted, Can that cause such an issue? I even disabled the vsel in boot menu

vikrambharadwaj said:
Hi Guys,
my defy was working smoothly until I enabled vsel through 2ndinit and set the values to [email protected], [email protected], [email protected] and [email protected], Then I installed busybox installer and super manager. And also copied services.jar to system/frameworks. But now my phone takes 5-10 min to boot abd as soon as it boots I get a hell lot of force closes unable to launch any app, the force close keeps getting back one after the other what do u think the prob might be with? I had uninstalled busybox installer before i rebooted, Can that cause such an issue? I even disabled the vsel in boot menu
Click to expand...
Click to collapse
I just want to get my phone back to its shape without erasing, Can I just refalsh the motoGinger.zip in 2ndinit?

Mistake is copied services.jar to system/frameworks.
If you're already running motoGinger 2.3.4. Then of course you can safely reflash it over. Wipe - custom recovery - flash..

vikrambharadwaj said:
I just want to get my phone back to its shape without erasing, Can I just refalsh the motoGinger.zip in 2ndinit?
Click to expand...
Click to collapse
You did not make a nandroid backup before you did this??
If you did make a nandroid backup just restore system and do NOT wipe anything then your system will be fine without losing any data.
(Allready dit that 5 times without any problems or loss of data)

farsight73 said:
Mistake is copied services.jar to system/frameworks.
If you're already running motoGinger 2.3.4. Then of course you can safely reflash it over. Wipe - custom recovery - flash..
Click to expand...
Click to collapse
Yup, its working now just refalshed it and its working now phew..
But for the services.jar file was for 1% battery indicator.. Has it also been integrated in the motoGinger (4th test)?

Related

[Q] Pyromod 1.6 trouble

Hello there everybody. I'm kind of new to modding my T-mobile G2.
I tried running the Pyromod 1.6 on my phone and I followed directions to the T. At first startup everything was running normally. On my previous rom (Villianrom) I used titanium backup to back up all my apps and some data. I was reinstalling my old apps using titanium and then I ran into some issues.
First, I kept getting force close issues with the android media process. I was also unable to download or update any of my apps via the android market.
Second, whenever I tried setting up a widget, I get even more force close issues with the media process and a couple others.
In an attempt to remedy this, I rebooted my phone and now its stuck on the startup of the mod. ( the blue hexagon beehive like flashing and graphic)
I'm not too sure if this is a brick or not and I'm currently just letting it run to see if time is what it needs to start up.
Any help or suggestions would be a great help and appreciated. =)
When it ran the first time it was a really cool mod so i'd like to keep it if possible.
Thanks!
if you can get into recovery i think you are ok, try to wipe cache/dalvik and run fix permissions
You're better off just wiping the phone, reflashing the ROM (and don't flash any other kernels on top of it), and then just select "restore apps with data" from Titanium's batch window.

market keeps force closing! help!!

Hey guys,
Here is the issue. I thought nandroid would restore a total image of the system before i started tinkering with the new fresh 4.0 update. I nandroided my perfectly running fresh 3.5 and upgraded to fresh 4.0
I didnt like fresh 4.0 and decided to go back to 3.5
Well, it restored just fine, I booted up and the GMail and Market app were not working. I tried to clear the cache on both, but it would not clear. I deleted the apps from the system/app folder and flashed the gapps zip thru recovery.
Now gmail works fine, but the market will not launch. it force closes every time.
Ive tried every which way (even tried to install a com.android.vending.apk i foiund) and it jsut wont work.
1) How do I fix the market?
2) Why am I having this issue anyway? I cleared dalvik/cache/factory reset/ then restored the nandroid. Why did it not go back EXACTLY the way it was?
Thanks so much
Abe
-----------------
**** EDIT ****
THANK baby jesus. I downloaded a com.android.vending 2.3.3 and did adb push to the system/app folder. now its working.
still doesnt explain why the nandroid restore let me down. Was not the full on "image restore" i was expecting!

[Q] How do I keep Sense from being shutdown due to OOM

Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John
swindelljd said:
Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John
Click to expand...
Click to collapse
with any OTA its recommended to do a factory reset. did you do this? its a pain to loss all your data but it might fix your problems.
sorry i didnt have my morning coffee yet.... If you wiped dalvik then that means you have root. your phone is not shutting down. something is killing rosie (the sense launcher.) and that why the white HTC splash screen comes up again. What rom are you runing? i know its the OTA but is it the RUU or one of the devs roms based off RUU??
swindelljd said:
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
Click to expand...
Click to collapse
If you read his entire post you would know he did a factory reset.
My best guess is to go back to stock sense before the last ota (by rooting and flashing or whatever way you wish..sbf or whatever) then download the ota on your computer and try manually updating your phone..if that doesn't work then I don't know
/Droid3
What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App
RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That worked for me.
synisterwolf said:
... i know its the OTA but is it the RUU or one of the devs roms based off RUU??
Click to expand...
Click to collapse
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Click to expand...
Click to collapse
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
swindelljd said:
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
There's no risk of brick with v6. It just tweaked a couple parts of the kernel.
Sent from my ADR6300 using Tapatalk
swindelljd said:
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.
RMarkwald said:
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.
Click to expand...
Click to collapse
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?
swindelljd said:
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?
Click to expand...
Click to collapse
Yes, that's the app.
Download this app as well: Busybox Installer
It'll tell you what version you have (if you have it), then you can select what version you want to install. No need to adjust where it installs, just leave that at the default, just select version 1.18.2, then hit Install.
I read through the script just to get a sense (no pun intended) of what it was doing and then installed Busybox 1.18.2 and applied setting 11 "Hard to kill launcher" from the script. I've done a bunch of browsing to sites that normally caused Sense to get shut down and so far so good.
I initially installed busybox with symlinks and it the script threw a ton of errors so I reinstalled with symlinks to fix that.
Thanks for all the help. For completeness, here is a link to V6 Supercharger so all the links are in this one thread http://forum.xda-developers.com/showthread.php?t=991276 .
One thing I did have to change because I am running Sense and not a stock android launcher is the name of the launcher process itself.
On line 64, I changed this "pidof com.android.launcher" to this "pidof com.htc.launcher"
will the V6 script it just tells the android memory system to not reclaim memory from the launcher app so it stays on no matter what happens. only way to kill it is to go to settings and FC the launcher. also with the script you cant brick the phone because its not ran till after the phone boots. The term brick means : that the phone will not boot at all. you just have a phone that does nothing at all not even turn on. You can soft brick the phone meaning the software will not boot. all you need to do is make a backup before installing the script and you will always have a way back if anything happens.
for me i run the beta V6 script option under -=*512HP*=- which is more of a balanced one with bullet prof launcher and its is wonderful. but each phone is different so just try them out and see what works for you.
synisterwolf said:
... You can soft brick the phone meaning the software will not boot. ...
Click to expand...
Click to collapse
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
Yeah, you kinda need that one there!
Good job getting it replaced using adb and all, good to hear you figured it out!
swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
yes that will do it. lol i did that a long time ago when i wanted to edit it my fat finger deleted it. now as good practice i always make a copy of it but add .bak at the end of it so if i do delete it i can just replace it before reboot.
I've been using options 1, 8, and 12 in the V6 Supercharger and my phone has been running great. What options did everyone else choose?

[SOLVED] Android is updating message on every restart after kernel upgrade

after wiping dalvik cache to flash a kernel....
this problem is caused when there are .odex files in /data/app folder than have permissions set so system can no write to them during the optimization process. There may be other causes, but this is the leading cause, i read about 15 threads on this, for alot of people its the app titanium backup odex file that causes the issue but there can be other programs. for these people the fix is uninstall and reinstall titanium backup. for me, i used es file explorer (root req) and i deleted any .odex (in data/app) that i found that didn't have write permissions for the system, i found two odex files that were rw- r-- r-- and deleted them. then i rebooted and the android is upgrading message did not come back (after 2nd reboot) at this point i reinstalled the two apps that had the odex files without w permission for system.
i assume the problem could also be fixed by changing the permissions on the odex files without having to reinstall them, but if the permissions were set like that for a reason, you'll want to set it back to rw- r-- r-- after you stop getting the android is upgrading message at bootup.
cheers guys, just made this thread because the other 15 threads i read on this topic were all lacking in useful information.
note: some outdated versions of ICS are known to have an issue where the system scans EVERY app on EVERY restart, this fix does not fix that. if your phone is rescanning EVERY app and not just the ones with odex w permission off then you need to update your ics version or get a custom rom that is up to date to fix this.
80 views today just gonna bump this once
NEED HELP
KronicSkillz said:
80 views today just gonna bump this once
Click to expand...
Click to collapse
HI,
FIRST OF ALL I AM REALLY THANKFUL TO EVERY MEMBER OF XDA DEVELOPERS. BECAUSE I HAVE LEARNT MANY MANY GOOD THINGS FROM XDA DEVELOPER. I DONT BELIEVE MYSELF AS A DEVELOPER I AM JUST AN ADVANCE USER.
I NEED HELP FROM YOU. I AM USING SONY XPERIA-S CELLPHONE WITH DUAL BOOT MANAGER DEVELOPED BY SENIOR XDA MEMBER letama HERE IS THE DETAILS OF MY DEVICE
MODEL SONY XPERIA-S
DUAL BOOT MANAGER BY letama
NATIVE OS ANDROID 4.0.4 ICS 6.1.A.2.55 STOCK ROOTED
ON LOOP HACK I AM USING ANDROID 4.2.2 CUSTOM ROM PAC VER 20.00
I AM ALSO USING FEW MODS ON STOCK OS LIKE
ACID AUDIO VER 4.00
BEATS AUDIO APPLICATION
BRAVIA ENGINE-2
CYBER SHOT CAMERA 4.72
NOW ABOUT MY PROBLEM. EVERY TIME I REBOOT MY DEVICE WITH NATIVE KERNEL (ICS STOCK) I AM GETTING MESSAGE ANDROID IS UPGRADING AND APPLICATION COUNT UP TO 58. THEN STARTING APPLICATIONS. THEN PHONE WORKS PROPERLY. BUT IT TAKE LONG TIME TO START.
I HAVE THIS PROBLEM SINCE I THINK I USED ABOVE MODS SO NO PROBLEMS WITH DUAL BOOT MANAGER BECAUSE THIS PROBLEM STARTED BEFORE USE OF DUAL BOOT MANAGER. THE CUSTOM ROM IS WORKING FINE AND NO ISSUES
I HAVE TRIED THIS TO SOLVE
FIRST I HAVE CHECKED FILES IN /DATA/APP BUT I HAVE NOT FOUND ANY ODEX FILES IN THIS FOLDER.
THEN I HAVE CLEANED DALVIK CATCH AND ALSO CLEANED DATA IN TWARP RECOVERY
THEN I FLASHED STOCK ICS 6.1.A.2.55 KERNEL
BUT STILL NOTHING WORKED FOR ME. PLEAS HELP ME IN THIS REGARDS. THANKS IN ADVANCE.
first of all there is no need to use all caps, secondly i answered your question in the last comment of my first post.
you need to get a newer version of ics or a custom rom thats been updated to fix this bug that was part with some old stock versions of ics and GB.
if u like the stock rom, just find a custom updated version of ics that has bloatware removed and memory leaks fixed, there is one available for most mainstream devices, the one i use is for my device though and is not supported on your phone.
if u like custom roms get somethign like cyanogenmod last stable release just google cyanogenmod "your phone model here" and it shoudl come up
KronicSkillz said:
first of all there is no need to use all caps, secondly i answered your question in the last comment of my first post.
you need to get a newer version of ics or a custom rom thats been updated to fix this bug that was part with some old stock versions of ics and GB.
if u like the stock rom, just find a custom updated version of ics that has bloatware removed and memory leaks fixed, there is one available for most mainstream devices, the one i use is for my device though and is not supported on your phone.
Click to expand...
Click to collapse
Hi. Thanks for your reply. I found the reseon for my above mantion problem. As I mantion I m using acid audio engine version 4 I have restored my cwm backup which was taken before the installation of acid audio. After restoration android is upgrading msg gone and phone boot normally. Then I tried different versions of acid audio like 5 and the latest 7 but after instalation the problem comes back so there must be something in acid audio package. So plz if u have some time then plz help me in this because apart from problem this audio mod is very nice. I herewith paste the build prop lines which acid audio adds during installation for your reference.
###AC!D Sound Tweaks by R-ikfoot###
#Sony Xloud
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
#Resampling Tweaks
af.resampler.quality=255
af.resample=48000
ro.audio.samplerate=48000
ro.audio.pcm.samplerate=48000
persist.dev.pm.dyn_samplingrate=1
persist.audio.samplerate=48000
persist.audio.pcm.samplerate=48000
persist.af.resampler.quality=255
persist.af.resample=48000
#One X+ Beats
persist.tegra.nvmmlite = 1
persist.audio.SupportHTCHWAEC=1
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
ro.audio.pcm.samplerate=48000
i dont think it has anything to do with what you posted, but im not 100% sure
my comments:
1. why do u need this sound tweak?
2. have u tried the same installation on another rom... everything i've read about rescanning all apps is a problem with stock ics 4.0.4 or some GB stock roms, which is fixed by upgrading to newer stock ics or custom roms.
3. have you contacted the developer of the tweak you are adding and asked him about it? i dont know anything about audio addons because i mostly play music in my car over bluetooth and its always sounded incredible so i've never had a need to tweak it.
4. what lead you to think that the build.prop changes are causing the problem?
5. without knowing what other modifications this audio tweak you are using does it hard for me to even try to figure this out.
6. i dont see why a bunch of audio setting changes would cause your phone to scan all apps every restart...
7. this thread is not meant to deal with this issue caused by things other than dalvik wipe/kernel upgrade/old bug in some versions of GB/ISC
does your acid audio addon or w/e its called make changes to the kernel? if so that is more likely the issue, have u checked permissions of all your files in /app folder
I don't get it. Every single app in my data\app folder is rw-r--r-- Should it be something else??
are you getting the kernel upgrading on every boot?
i think the permission problem is the .odex not the apps, i think its normal for the apps to all be rw r r
i thought it was both app and odex at first but i think just the odex is the issue. not 100% sure, either way if you are seeing the error on boot play with the permissions, or reinstall apps in question if that doesn't work. start with the odex permissions i think you are right and the apps are rw r r by default. therefore that probably isn't the issue.
i just did another kernel upgrade so i tried the method of changing permissions, it doesn't seem as reliable as uninstall reinstall.
when i changed permissions the optimizing of app went away but i still got annoying upgrading message.
i recommend uninstalling and reinstalling any apps that have odex in data/apps folder. i'm still not 100% sure why this fixes it but it does for me.
the permission changes seem like they only fix the issue sometimes
Hi Kronic,
I've got a Nexus 4 on stock and rooted (updated to 4.2.2) and constantly get the "Android is upgrading" on every boot. I've had this issue for sometime now and only every so often will I dedicate time to finding a solution with no avail. I updated a couple of days ago, had to do a factory reset and upon booting up that was the first message.
I had a looked into the data/app file and I do not have a single .odex file, all apk. I do have a strange file in that folder though, sensor_ctl_socket with permissions set to rwx-rw-rw
Thoughts?
its normal for it to happen after a factory reset, you should only look into fixing it if it continues this behavior after multiple reboots
KronicSkillz said:
its normal for it to happen after a factory reset, you should only look into fixing it if it continues this behavior after multiple reboots
Click to expand...
Click to collapse
Hi Kronic, thanks for the reply. Notice the key word EVERY boot/reboot . Granted, I don't have to reboot or power off my phone often BUT when I do it is annoying to see the Android is upgrading message and it takes a while to update all of the apps. (I actually had to reboot a few times while fixing a gallery/camera issue).
I've searched multiple forums/posts/pages for a solution and have found nothing. I tried undoing the Dalvik integration as recommended on this postand that didn't help either.
what version of android are you using, are you possibly using the bugged version? you did a factory reset and you haven't updated right? there was a few versions of android that have this bug and have to be updated to be fixed. aside from that i'm not sure what else it could be, let me know if you've already updated we'll look into some other solutions.
KronicSkillz said:
what version of android are you using, are you possibly using the bugged version? you did a factory reset and you haven't updated right? there was a few versions of android that have this bug and have to be updated to be fixed. aside from that i'm not sure what else it could be, let me know if you've already updated we'll look into some other solutions.
Click to expand...
Click to collapse
Rooted, stock on 4.2.2 (see image attached) Thanks for your help
you might wanna see if reinstalling apps fixes it but its wierd cuz u have a fairly new version of android.
kill .odex junk file
Bammed the "Thanks" button on this post, for solving this nutcracker.
KronicSkillz said:
after wiping dalvik cache to flash a kernel....
this problem is caused when there are .odex files in /data/app folder than have permissions set so system can no write to them during the optimization process. There may be other causes, but this is the leading cause, i read about 15 threads on this, for alot of people its the app titanium backup odex file that causes the issue but there can be other programs. for these people the fix is uninstall and reinstall titanium backup. for me, i used es file explorer (root req) and i deleted any .odex (in data/app) that i found that didn't have write permissions for the system, i found two odex files that were rw- r-- r-- and deleted them. then i rebooted and the android is upgrading message did not come back (after 2nd reboot) at this point i reinstalled the two apps that had the odex files without w permission for system.
i assume the problem could also be fixed by changing the permissions on the odex files without having to reinstall them, but if the permissions were set like that for a reason, you'll want to set it back to rw- r-- r-- after you stop getting the android is upgrading message at bootup.
cheers guys, just made this thread because the other 15 threads i read on this topic were all lacking in useful information.
note: some outdated versions of ICS are
known to have an issue where the system scans EVERY app on EVERY restart, this fix does not fix that. if your phone is rescanning EVERY app and not just the ones with odex w permission off then you need to update your ics version or get a custom rom that is up to date to fix this.
Click to expand...
Click to collapse
Thank you for extremely for this info.... Thought I was gonna have to re flash my phone again
Night_1 said:
Thank you for extremely for this info.... Thought I was gonna have to re flash my phone again
Click to expand...
Click to collapse
then push the thank you button

[Q] Freezes and reboots?

Sincs last week my N7100 randomly freezes while using it.
Also, when I activate it (take it out of sleep) I'm asked to enter my SIM-PIN. The phone has been rebooted.
I've been using 'N7100XXDMA6 N7100PHNDMA1' from this site for a while and didn't have any problems.
I think it's being caused by an update of some app or even a newly installed app.
What can/must I do?
Reinstall 'N7100XXDMA6 N7100PHNDMA1'?
Clean install my N7100 (please not )
Find the latest installed apps and remove them (how to find them?)
ffortissimo said:
Sincs last week my N7100 randomly freezes while using it.
Also, when I activate it (take it out of sleep) I'm asked to enter my SIM-PIN. The phone has been rebooted.
I've been using 'N7100XXDMA6 N7100PHNDMA1' from this site for a while and didn't have any problems.
I think it's being caused by an update of some app or even a newly installed app.
What can/must I do?
Reinstall 'N7100XXDMA6 N7100PHNDMA1'?
Clean install my N7100 (please not )
Find the latest installed apps and remove them (how to find them?)
Click to expand...
Click to collapse
Is everything Stock ? ROM? KERNEL ?
aukhan said:
Is everything Stock ? ROM? KERNEL ?
Click to expand...
Click to collapse
I installed the stock rom from http://forum.xda-developers.com/showthread.php?t=1896696 with mobile odin and am using root (titanium backup).
Launcher : Go Launcher Ex (tried the original launcher, same problems)
Haven't been meddeling with the phone itself for some time. Only apps from market.
ffortissimo said:
I installed the stock rom from http://forum.xda-developers.com/showthread.php?t=1896696 with mobile odin and am using root (titanium backup).
Launcher : Go Launcher Ex (tried the original launcher, same problems)
Haven't been meddeling with the phone itself for some time. Only apps from market.
Click to expand...
Click to collapse
is suspect there could be possibilities this may be the victim Go Launcher EX could you uninstall and reboot it and chec?
Did you restore anything from Titanium backup
aukhan said:
is suspect there could be possibilities this may be the victim Go Launcher EX could you uninstall and reboot it and chec?
Did you restore anything from Titanium backup
Click to expand...
Click to collapse
No backups replaced.
Only installed and removed apps.
Removed GO Launcher Ex via:
Applications - Gedwongen stoppen (force) - Gegevens wissen (remove data) - Verwijderen (uninstall)
Rebooted N7100
Ready to test :fingers-crossed:
ffortissimo said:
No backups replaced.
Only installed and removed apps.
Removed GO Launcher Ex via:
Applications - Gedwongen stoppen (force) - Gegevens wissen (remove data) - Verwijderen (uninstall)
Rebooted N7100
Ready to test :fingers-crossed:
Click to expand...
Click to collapse
How is it so far ?
aukhan said:
How is it so far ?
Click to expand...
Click to collapse
It's working atm.
Am putting it aside for a while to see if it reboots again.
ffortissimo said:
It's working atm.
Am putting it aside for a while to see if it reboots again.
Click to expand...
Click to collapse
sure
There hasn't been a reboot yet.
But the phone freezes when trying to open an app, or even de phonebook.
Also my battery is droppen very quick. It has dropped over 60% in 7 hours.
It 'feels' like the phone is busy with something which causes battery and memory drain.
ffortissimo said:
There hasn't been a reboot yet.
But the phone freezes when trying to open an app, or even de phonebook.
Also my battery is droppen very quick. It has dropped over 60% in 7 hours.
It 'feels' like the phone is busy with something which causes battery and memory drain.
Click to expand...
Click to collapse
Install Battery Stats and monitor which app is eating more battery
Battery Stats installed and running.
I removed my SIM and micro-SD and rebooted phone.
It seems to be working better.
SD is back in and it's still working.
Could it be caused by a defective SIM?
ffortissimo said:
Battery Stats installed and running.
I removed my SIM and micro-SD and rebooted phone.
It seems to be working better.
SD is back in and it's still working.
Could it be caused by a defective SIM?
Click to expand...
Click to collapse
no i dont think so
It's getting worse and worse.
I used mobile odin and reinstalled the same rom/kernel/firmware as I had.
Still big problems.
Sometimes it won't even work on the homescreen.
Factory reset, lets see how it's working now.
Maybe no root. Means no Titanium Backup, but that was the only thing I needed root for
ffortissimo said:
Factory reset, lets see how it's working now.
Maybe no root. Means no Titanium Backup, but that was the only thing I needed root for
Click to expand...
Click to collapse
so as if now your on complete stock and no root ?
aukhan said:
so as if now your on complete stock and no root ?
Click to expand...
Click to collapse
I thought so, but found out that I'm still rooted.
I had Google restore all my apps and the problems returned.
Went back to 'factory settings' (with root) and am installing my apps from Titanium Backup manually.
I'm skipping the apps I added last month and it seems to work fine for now.
Very strange.
Ok, this didn't work.
No reboots, but sometimes it still freezes.
But, I can reboot the phone by holding the powerbutton now.
I'm going to try and reinstall the phone like it was when it was new.
But, uhm, how can I do that the best way?
Try to flash another kernel, it was work on me from perseus back to stock kernel
Sent from my GT-N7100 using xda app-developers app
Tried the forlast version, but the phone freezes on configuration after boot.
Damn.
are u using the open source superuser ? cuz it was causing my system to freeze and soft reboot on my N2 and S2 :/
i switched back to supersu and no problem whatsoever since 3 weeks :good:
edit : MA6 is very old base BTW update ur rom to latest build which released today ME6 or MF2
http://www.sammobile.com/firmwares/1/?model=GT-N7100&pcode=0

Categories

Resources