Related
bell galaxy s vibrant. i did the #*#*2663*#*# in the dialer and then updated the touchkey firmware and now both touchkeys dont work. tried flashing back to stock ugkg3 with odin. didnt fix. now the phone has ics milestone 5 on it and they still dont work. luckily the nav bar can be used and customized. how can i reenable the buttons?
Try flashing an older from in Odin. Something 2.2 from bell.
Sent from my GT-I9000 using Tapatalk 2
but if flashing back to stock 2.3.3 in odin didnt work why would that? i guess ill try
If not I'd say the buttons are just dead.
Sent from my GT-I9000 using Tapatalk 2
lol why was i able to simply click something that killed my buttons. kinda crappy
Currently I am in your boat as well with those buttons dead, but even though I am on 2.2, my kernel is different (I got other problems, phone won't work with stock kernel), I still can't fix my problem. So, yours might get fixed cause you're on stock on everything, try using 2.2 or lower. It should fix, unlike me.
im not on stock, im on 4.0.4 ice cream sandwhich, aokp milestone 5 rom
you should do the same so u can enable the nav buttons and forget the physical ones. u can have home menu back and multitask on the nav bar, plus the phone runs soooooooooooooooooooooo much smoother, its like i traded an old vibrant for a galaxy nexus
I have this problem before probably a year ago and I fixed it, I think, by first flash the stock 2.2 rom, then after the flash go to that menu again (which caused this trouble) and hit update again.. If it works then flash the 2.3 or better.. This is from my memory from a year or so ago
It is fixable and I got the fix method from this forum.. Forgot exactly which thread since it has been long time.
Good luck!
Sent from my Galaxy Nexus using XDA
Speedum said:
I have this problem before probably a year ago and I fixed it, I think, by first flash the stock 2.2 rom, then after the flash go to that menu again (which caused this trouble) and hit update again.. If it works then flash the 2.3 or better.. This is from my memory from a year or so ago
It is fixable and I got the fix method from this forum.. Forgot exactly which thread since it has been long time.
Good luck!
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Buddy that's what I wrote in my post, but showed the only difference I have is that I have to use custom (speedmod kernel) kernel to boot up otherwise my phone won't start. So, when I get back to everything stock, I will for sure try that number thing again on 2.2 to fix it. Thanks.
i will try too and report
Dit it?
grasshoxda said:
i will try too and report
Click to expand...
Click to collapse
So, dit it work? :fingers-crossed:
Cheers,
AT
Another odd thing I am seeing since the new update, is every time I reboot, if I go into the task manager to see all my open applications... After about a minute or so, I notice there is an app in there that says MIPerroractivity, when I click app info it says it is an app called com.sec.app.MIPErrorNotifier. Why is this automatically open like an app in my task manager when I reboot? Any ody else seeing this?
Sent from my SPH-L720 using Tapatalk 4 Beta
I see this too
Thanks for the reply. Was hoping it wasn't just me. Perhaps someone with more insight could shed some light on this.
Sent from my SPH-L720 using Tapatalk 4 Beta
Same here. Not sure what this is, and if I should just freeze it using Titanium backup. Searched google and the first hit was this post
One of the subsequent posts indicates that this app existed on the S3 late last year too - http://forums.androidcentral.com/sp...ng-galaxy-s3-sprint-version-stock-rooted.html
Same here! I'm wondering if we rename it to .bak at the end if that will affect anything... anyone willing to test that lol?
Joe0113 said:
Same here! I'm wondering if we rename it to .bak at the end if that will affect anything... anyone willing to test that lol?
Click to expand...
Click to collapse
I froze it using Titanium backup. No ill effects so far
QUESTION: Is everyone here running the latest KT Kernel. Bc when I reverted back to the MF9 kernel, I didn't get that anymore...
I am bone stock, haven't even rooted it yet. First time I haven't rooted a phone right out of the gate.
Sent from my SPH-L720 using Tapatalk 4 Beta
Same here just updated this morning. Bone stock and not rooted. Shows up after every reboot.
I did the update myself not via ota. Did everyone else here do it that way? Or did you receive the update via ota?
Maybe its somehow related to the way sprint is rolling out the update?
Sent from my SPH-L720 using xda app-developers app
Did mine ota
Sent from my SPH-L720 using Tapatalk 4 Beta
Happy I found this thread! Thought it was only me. I flashed the MF9 zip, and I'm using KT kernel.
The thing running doesn't really bother me, I'd just like to know what it's for. I kill it every time I reboot anyway
Semtronix said:
Happy I found this thread! Thought it was only me. I flashed the MF9 zip, and I'm using KT kernel.
The thing running doesn't really bother me, I'd just like to know what it's for. I kill it every time I reboot anyway
Click to expand...
Click to collapse
You didnt odin the modem tar?
galaxy s4
johnfred1987 said:
You didnt odin the modem tar?
galaxy s4
Click to expand...
Click to collapse
Should I have? I used Odin to get to stock MDL, then flashed the MF9 zip in recovery. Nothing else. Why would I need to flash the modem if the modem is in the OTA?
Semtronix said:
Should I have? I used Odin to get to stock MDL, then flashed the MF9 zip in recovery. Nothing else. Why would I need to flash the modem if the modem is in the OTA?
Click to expand...
Click to collapse
Did the same thing.
I also get this PITA notice.
Only thing I have been able to find so far is it appears to have something to do with "Mobile IP ERRor".
I will not claim to know what this means.
I have noticed that I have no cell service while roaming at home anymore.
Hopefully, this is because I am slightly (1/4 mile) outside of the official roaming service area.
I am hoping I can reset the phone profile once I get back into Sprint's network later today.
I am also not sure if this is related to MY upgrading to MF9 using the manual ZIP from SD card method and not waiting for the official OTA update.
I already posted that I did the ota stock non rooted and it appears for me.
Sent from my SPH-L720 using Tapatalk 4 Beta
After a bit of review
Ok, so I've been doing a little testing this AM to see if I could get to the bottom of this error.
After rebooting, locking and unlocking a ton of times I've decided its related to wifi connecting on the initial boot.
After a while I started noticing a pattern in relation to the toast message that pops up when it initially connects to wifi and the error showing up.
To confirm my theory, I removed the local wifi at my office, and on reboot, no error.
I have zero clue on how to fix the issue, but just wanted to point any devs looking into this in the right direction.
Additional notes, I'm stock, not rooted, and updated via the sdcard method.
skitzo2000 said:
Ok, so I've been doing a little testing this AM to see if I could get to the bottom of this error.
After rebooting, locking and unlocking a ton of times I've decided its related to wifi connecting on the initial boot.
After a while I started noticing a pattern in relation to the toast message that pops up when it initially connects to wifi and the error showing up.
To confirm my theory, I removed the local wifi at my office, and on reboot, no error.
I have zero clue on how to fix the issue, but just wanted to point any devs looking into this in the right direction.
Additional notes, I'm stock, not rooted, and updated via the sdcard method.
Click to expand...
Click to collapse
I believe you are absolutely correct in your assumption. I can replicate this as you say. Also, I am completely stock, unrooted and gained the update via OTA.
I did crawrj mf9 update for rooted mf9 and not haveing the issues only had to clear my google account (data) check out his thread maybe there that ll help yall
galaxy s4
Has anyone totally deleted it (not freeze it, but DELETE IT) from system/apps ??
$20 via paypal to the person who can get me up and running again.
GPS is very important for my line of work, and I'm trying not to panic.
I'm on MK2. I've been using stock and SHOstock ROM flawlessly since getting the phone just before Christmas. I've NEVER had any GPS issues. Ever.
I decided to flash the Safestrap version of Hyperdrive on ROM Slot 1, along with MK2 kernel module. Installed fine. I flipped back to STOCK rom(SHOstock), until I had time to mess with the new ROM. On the way home from work, I realized I had no GPS.
Using GPS Tools and GPS Fix apps, no satellites showing at all.
I've done everything I can think of, including using ODIN to flash back to stock MK2. Still no dice.
Can anyone give a guy a hand? I'm currently running stock and have re-rooted using saferoot(the same way I rooted previously).
Thanks in advance!
Dlnp22 said:
GPS is very important for my line of work, and I'm trying not to panic.
I'm on MK2. I've been using stock and SHOstock ROM flawlessly since getting the phone just before Christmas. I've NEVER had any GPS issues ever.
I decided to flash Safestrap version of Hyperdrive on ROM Slot 1, along with MK2 kernel module. I flipped back to STOCK rom(SHOstock), until I had time to mess with the new ROM. This was all yesterday, at work(shh!). On the way home, no GPS.
I've done everything I can think of, including using ODIN to flash back to stock. Still no dice.
Can anyone give a guy a hand? I'm currently running stock and have re-rooted using saferoot(the same way I rooted previously).
p.s.- I've checked location services..everything's checked.
Thanks in advance!
Click to expand...
Click to collapse
I've used this app in the past on my GS3 but it might work here.
https://play.google.com/store/apps/details?id=com.cochibo.gpsstatus&hl=en
Also This post (on another forum was quite informative and it's worth a shot)
http://androidforums.com/samsung-galaxy-s4/761247-gps-fix-dummies-guide.html
There used to a method that involved the service menu on the GS3 but I'm not sure if it still applied
hednik said:
I've used this app in the past on my GS3 but it might work here.
https://play.google.com/store/apps/details?id=com.cochibo.gpsstatus&hl=en
Also This post (on another forum was quite informative and it's worth a shot)
http://androidforums.com/samsung-galaxy-s4/761247-gps-fix-dummies-guide.html
There used to a method that involved the service menu on the GS3 but I'm not sure if it still applied
Click to expand...
Click to collapse
Yes, I've had that message forum(2nd link) saved for some time now. I've done everything in that thread and used the GPS app tools, and nothing has helped. Can't locate ANY satellites.
Dlnp22 said:
Yes, I've had that message forum(2nd link) saved for some time now. I've done everything in that thread and used the GPS app tools, and nothing has helped. Can't locate ANY satellites.
Click to expand...
Click to collapse
No possbility of a hardware issue ?
hednik said:
No possbility of a hardware issue ?
Click to expand...
Click to collapse
Nothing has happened to the phone(no drops/spills/etc). It started right after flashing the new ROM, so I'm fairly certain it has to be related.
Did u try flashing older modem / baseband. .... I read that couples people confirmed by using MDL modem. .... check your PM....
Swyped from MK2 Dark Venomous X1
ted77usa said:
Did u try flashing older modem / baseband. .... I read that couples people confirmed by using MDL modem. .... check your PM....
Swyped from MK2 Dark Venomous X1
Click to expand...
Click to collapse
Ted, per our extended private message convo on Friday, thanks for giving me a good shove in the right direction!
Dlp22, I have the same problem, did you solve it?
any suggestion!
I had the same problem after upgrading to MK2, almost on the verge of getting rid of GS4 and switching to another device. But for now, I have fixed it by installing Hyperdrive RS13 using Safestrap on Stock slot (did take a backup of the stock slot before wiping it out)...
on the latest d802 4.4.2 custom roms and kernels i get a lot of freezes.
it will freeze in the middle of an animation and will take some seconds up to some minutes and then working normal again.
sometimes i have to hard-reboot to get out of freeze / lag.
on older 4.4.2 slimroms i never had this behavior, only since some weeks with new roms / kernels.
i`ve tried every rom / kernel combo but sooner or later i will get a freeze again.
could a revert to stock and re-rooting / flashing custom rom maybe a solution? i`m afraid to do this because of the long time to backup my 32gb data.
what are your experiences with the latest 4.4.2 roms and kernels? did you find a solution for this with any combo or fixes?
help would be appreciated.
push! no one else with same problems? maybe i got a hardware defect?
paratox said:
push! no one else with same problems? maybe i got a hardware defect?
Click to expand...
Click to collapse
The only thing I can say is I own the VS980 version of the device and i've tried every single 4.4 rom offered on this sight and have the same issue with all. Most of the time i'm using the device and it freezes, sometimes reboots, and sometimes comes out of it after a few minutes. Also not being able to wake the device only seeing a black screen and forced to hard reboot device. 4.3 seems to be a much better with these issues but not completely solved for me. I'm hoping the release of 4.4 source from lg will fix these issues but i'm unsure. So at least your not alone in these problems lol. I've tried multiple kernels and governors etc. Bumping up the min freq on the cpu seems to help and changing to interactive governor but doesn't eliminate the issue just help. I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
flyinj54 said:
I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
Click to expand...
Click to collapse
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
paratox said:
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
Click to expand...
Click to collapse
Yea unfortunately it seems very common among these devices so i'm pretty confident it's a software issue although i'm not 100% sure of that. I ran a flex rom for a few days on 4.2.2 and didn't have any of the same issues.
added a poll as a matter of interest.
omni-ROM, Mokee rom, vanir rom etc.freezing problem still continues.
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
lubirdy said:
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
Click to expand...
Click to collapse
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yes, stock cm kernel.
I'm thinking back now and it did freeze once when first signing into the Google account immediately after flashing the ROM, but nothing after that. So.. nearly spotless
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Best of luck! To be specific, I'm using the snapshot release of cm11... still don't trust the nightly releases
i did a lg flash tool stock restore, factory reset and OTA updates. now the freezes did not come back until now *knock on wood*.
when i did a backup of the sd there was one corrupt media file which was not able to transfer.
maybe the media scanner did go crazy and was the reason for the freezes.
using cm11 m3 on my d802... very little freezes compared to previous nightlies, fingers crossed
I've tried this two times and both I had the same result. I downgraded back to 4.2.2 with the D80110g_00.kdz for the tmobile g2. Then I rerooted it and added philz touch recovery. I flashed with the kitkat baseband in the cloudystock 1.1 fourm, then the rom with the patched 801 kernel after. Everything boot's up ok, and the phone works. But when I turn off the screen and back on its all grayed out with yellow lines. I have the reboot the phone for the screen to show up again. Can someone tell me what I am doing wrong?
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
JPrinceStar said:
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
Click to expand...
Click to collapse
baseband stays the same when flashing other roms. Pretty sure the rom zips don't touch baseband unless specified otherwise. Glad it worked for ya btw
Sent from my LG-D801 using xda app-developers app
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
JPrinceStar said:
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
Click to expand...
Click to collapse
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
v2.2v said:
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
batmanonastick said:
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
Click to expand...
Click to collapse
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Did anyone out there figure this out?
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
I think you hit the nail on the head with G build comment. I got my phone about a month ago from TMO and it came pre-installed. I wonder if something in the actual hardware is ever so slightly different with the latest G2s...
I flashed with the C build and it didn't fix it also, guess I'll stay on 4.2.2 till there is a official kitkat root.
Anyone around in this thread with the line problem willing to test a kernel?
mackster248 said:
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
Click to expand...
Click to collapse
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
sam298 said:
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
Click to expand...
Click to collapse
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
v2.2v said:
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
KennyJive said:
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Click to expand...
Click to collapse
JPrinceStar said:
Did anyone out there figure this out?
Click to expand...
Click to collapse
SeVIIn said:
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
Click to expand...
Click to collapse
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
dr87 said:
Anyone around in this thread with the line problem willing to test a kernel?
Click to expand...
Click to collapse
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
mackster248 said:
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
Click to expand...
Click to collapse
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
frettfreak said:
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
Click to expand...
Click to collapse
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
yeah it did ship with KK. pretty sure i have seen the thread regarding the autorec app. But will let you know! Thanks!
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
Mackster I'm on 4.2.2 which is rooted, is there anyway I could use a custom kitkat rom without getting the white lines? I dont want to keep downgrading everytime it happens.