First off I just have to say that I totally understand the 10 post minimum before posting in the development section but my god is that annoying. I just don't post a lot but have been doing this for over a year now. I very much dislike that I can't post into the CM7 Nightly section about this. ANYWAY with that out of the way....
I have a AT&T SGSII (i777) which at boot up the Samsung splash screen says i9100 which I find odd and I am running CM7.2.0 RC0 (KANG) and the alternat modem i777 UCKJ4. This Nightly saved my battery as it was intended to do so I am grateful for that. I have noticed something that I would like to tell Antinm about though.
When using the Google Music application if my screen rotates I lose the screen. It will rotate but then it will only show the background of the Music app and then if I hit the power button to turn the screen off it will not come back on. The music still plays and the buttons still work (volume) so I don't think it is a hardware lock up but rather something with the display. I have to powercycle the device to get back to normal operation.
Also, I have done everything I should as far as wiping dalvik and cache and reinstalling the ROM/Kenrel/Radio/Recovery etc. It's not a major issue but I just wanted to get it out there in case anyone else is having this peoblem so the devs can look into it is they find it necessary which they may not as I know everyone especially Antinm is working on ICS/CM9. Can I get a woot! for CM9/ICS?!?!
Thanks
Woot
With that out of the way, I can answer the first part. It boots the i9100 screen because the flash counter has been tripped from a non stock kernel being flashed. This most likely happened when you rooted it. Should've went entropy512's route of rooting. A usb jig will bring back stock splash screen and reset the flash counter.
As far as the google music app, so far no issues have been reported on like that. Doesn't mean that rules out it being a cm7 problem.
But to try and rule that out, reflash cm7. It's known for not 'sticking' the first flash. Then wipe everything you can in recovery, minus battery stats of course. Make sure to back up your apps somewhere else so they don't get erased.
Once that's done post if google music app is still giving you issues.
Sent from my páhhōniē
USB JIG
Yo hairy1, it totally worked. I got it from mobiletechvideos.com for $8. Thanks!
Thanks for the update. Glad it worked out.
Sent from my páhhōniē
Related
I have searched and searched, but can not find what seems to be an applicable fix, so here goes.
Ok here is my best description. Equipment: Rooted vibrant. The plot: Rooted. Ran fine for months. Yesterday purchased Rom Manager premium. Installed one of the premium roms. Can't remember the name of the rom. After install everything worked fine except I kept getting the error, "com.google.process.gapps has stopped unexpectedly" so I tried everything I could find related to that problem to fix it, but nothing worked. As a symptom the market, gmail, etc wouldn't work. Anyway I figured I'd just recover the last rom that I backed up and start over. So I did, but now the phone boots, goes to the "draw pattern to unlock screen" and won't recognize the fact that I'm actually drawing the pattern to unlock the screen. The "buttons" on the bottom of the screen recognize my touch (menu, home, search, back) as they darken when touching them.
So there the phone sits on the unlock screen. After a minute or two the screen goes blank, the phone vibrates once, and the unlock screen comes back and won't accept any input.
Is this fix applicable, or would it work in bringing my phone back to me?
http://forum.xda-developers.com/showthread.php?t=848737
I want to make sure as I don't want to further exacerbate the uselessness of my phone. I feel like I've lost a limb with it gone.
Thanks for any help.
Sorry to hear you found the worst gremlin of all. I'll get that from time to time when my phone feels like being stupid. Lucky for me, I can just reboot the phone, and she's back to normal.
As far your situation is concerned, I would probably try to use Odin and flash your phone back to stock so you can build it back up to whatever ROM you're on. This usually happens when you bounce back and forth between a froyo and GB ROM; or a ROM from a different dev that's used a different framework to make all his stuff work.
Jump into the link in my sig, and see if you can find the files you need. Otherwise, shoot me a message so I can link you to the files I use to go back to stock pre-rooted.
Lol, did you try this?
http://forum.xda-developers.com/showthread.php?t=749605
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
younix258 said:
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
OK. The sticky worked. I admit I panicked, but IT WORKS NOW!! I'm just ecstatic! You guys rule.
I guess I was just gun shy. I bricked the snot out of my my-touch a year ago (still doesn't work).
Anyway, on to hacking.
Thanks again!
Awesome! Glad you got it werkin
Next time just try a simple Google search of the error itself.
*EDIT*
If you still have the mytouch I'd be interested in it. PM me if so
Yeah I tried to google the problem, but I was still stuck. None of the fixes seemed to work. Until google led me here.
I do still have the my touch. Mint condition, minus the fact it doesn't work! I'd like to get it working again if possible. Is there a way to odin the my touch? I tried and tried last year when I bricked it, but I never got it to work again. Is there a my touch forum here somewhere named something other than "my touch"?
Sent from my SGH-T959 using XDA App
I was trying out Passion ICS RC1.1 but was unable to maintain a data connection, so I tried to use CWM to restore to my Nandroid of Trigger 3.2 Final. Unfortunately, it looks like due to the GB Bootloader that was a bad idea.
Now when I turn my phone on I just see the name "Adyscorpius" under a green Android, it never progresses beyond that screen. When I try to access download mode to Odin I just see a non-spinning, gray battery icon in the middle of the screen. It never proceeds to the actual charging screen even when plugged into the wall. I tried every combination of Vol +/- & PWR, plus taking the battery out and switching the order of battery or USB connection but no matter what I do I can't get into Recovery/Download.
I ordered a JIG off of eBay but the item description said "If you don't see the 'Triangle Error Message' this jig won't help." I haven't seen any triangles in all of my troubleshooting - just the two screens I mentioned. Am I most likely out of luck?
Wow, that's all it took?
As I was reviewing my own post I had an ephiphony "What if the bootloader changed the default keys for Download mode?" I did a Google search for "Adyscorpius download mode vibrant" and what do you know - it's changed from Vol +/-, to just Vol + & PWR. Tried it and on my first time I got to download mode. Now I feel silly for having spent hours unsuccessfully trying to fix it. Leaving this post in case anyone else runs into the same problem and attempts to search for it.
Be careful with passion, I fried my vibrant on v12
If you ever see the "encryption unsuccessful" message after a reboot, you're screwed, no internal memory, if I were you I'd let the releases go one ahead and stay behind reading EVERYTHING that others are saying.
Sent from my SAMSUNG-SGH-T989 using XDA
Thanks for the heads up. I don't think I'll be leaving Fishmanmod/Bionix-V until I get a new phone when my contract is up for renewal. Passion seemed nice to look at but I was getting less than a third of the battery life that I got with Trigger and I've read Fishmanmod has even better battery than that! Not to mention, no previous ROM I've tried has been quite this smooth before.
Nope, I was wrong
Guess I won't be staying with Fishman. I got so used to being able to use the Camera and Music Player below 15% power that I had forgotten that was a feature exclusive to the Trigger ROM. The buttery smoothness can't quite make up for that. Okay, definitely sticking with Trigger until I get a new phone
If Birgertime happens to stumble across this thread: YOU ROCK!
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to General
Hey guys!
The other day, I picked up an Atrix, mainly to use as an mp3 player so my S3's battery wouldn't drain as much during the day.
So, I took the steps any good android-user would go through. I unlocked the bootloader, rooted, and had Clockworkmod all set up.
This is within 30 minutes of having the phone. During the first while of tinkering with it, I noticed some strange things. There's really too many to list, but I'll try.
The phone at times is completely unresponsive. At seemingly random intervals, the Atrix would freeze, and randomly start selecting things.
For example, whilst using the keyboard, it would stream out random lines of text, like yyyyzzyyzyyzyyzyyyxyyxyyzy. Thinking that it was just a fluke with the rom , I carried on.
Often, the only time I can accurately and reliably select something is immediately after turning the screen off and back on again. And sometimes, that doesn't work either.
Also, there seems to be a 4-5 second latency from pressing the screen, to the device registering it.
Again, at random intervals, the image displayed on the screen begins to shake, and becomes unresponsive. I really wish I could record it happening.
There's also a host of other problems. The wifi hasn't ever worked, and the phone flat out refuses to flash some gapps packages.
So, my Atrix is basically a non-functioning, shivering, nightmare of a phone to work with. None of these issues have been caused by flashing different roms, and I have never touched any of the sbf files.
No matter what I try, it is just unusable. Every thing I have tried has failed, and this phone is out of warranty, so replacement is out of the question. So, is there anything I can do to fix this issue? I really, really need help.
Thanks in advance guys!!
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Newbleeto said:
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hey! Well, I started on the stock ota 2.3.6
Yes, the bootloader is unlocked, cwm is the recovery, and I can get into it. Before flashing, I did wipe dalvik, cache, and factory reset.
The roms I've installed are in this order:
Stock ota 2.3.6, Cyanogenmod 7 2013/1/1 nightly, TopSmart's final release 1.3 rom, and AOKP 4.1.2 from October 17.
The roms flash just fine,and I always use the correct gapps. The problems have persisted through everything I have tried.
Bluetooth does not work, and neither does anything that requires a radio. (Data, calls, wifi, etc)
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
affiatic said:
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
Click to expand...
Click to collapse
I got it used, but it was still in the box, and even had the plastic screen that says "Don't text and drive" on it. The phone had literally never been booted up.
I think I figured out the problem, and will try to post a video of it.
The touchscreen just freaks out when being used. I found this out through the pointer location in the dev tools in Cyanogenmod 7
I'm on cm10 and random touches happen to me. I just lock and unlock the screen to fix. Only happens to me on cyanogen roms.
Sent using tapatalk
Could it be a foreign phone? that would explain the radio not working. The screen breaking and ghost touches sound like the leaked rom/kernel, was it happening with all the roms you installed?
So sometime in the last week or 2, my I9300 started randomly freezing up and/or shutting off by itself.
it's usually a while after booting - i'll come to unlock it, and the LED will be showing Blue. Clicking any of the buttons doesn't do anything, nor does waiting a while.
Holding down the power button for a few seconds boot/reboots the phone though, and it works normally when it starts back up again - although after a while it will die again.
Sometimes it runs for hours, sometimes just minutes.
Occasionally, it will freeze up while i'm actually using it - the screen stays on, frozen in place, but the touchscreen and buttons won't do anything (although oddly, multiple clicks of the home button make the colours invert?).
Anyway, i thought this soundsed a bit like this 'Sudden Death' bug, but how do I know? I installed and ran the eMMC check app and it says:
Phone Model: Samsung GT-I9300
eMMC chip: Type VTu00M, Date 05/2012, CID 15010056545530304df1f900755f5f5f, FwRev oxf1
SGS3 Sudden Death? YES. Insane chip.
My question is - what does this mean? Do i have the problem and just need to make sure i run a kernel with the fix, or is the phone now broken and needs replacing/fixing?
If it does need fixing, do i need to revert it to stock ROM and run triangleaway or anything before i send it in, or is it fine how it is?
It's currently running crDroid 11.1 XXELLC, and it was at the time i started noticing the problem. I'm using Siyah 1.8.9, although i was using an earlier version before (can't remember what).
Same problem here... i don´t know what to do... today i make a lot of things to attempt to restore all but everything fail... i decided to talk with samsung and send the phone to repair, in a few days I hope to come to pick up the phone, I have to say that I had to pay 24 € for the shipping and after playing wait month or month and a half. is frustrating but hopefully come good repair.
One read the SDS thread . Two if you think you have the problem or a problem follow the how to revert to stock post and take to a service centre .
Freeze is more likely rom and or kernel .
???????
although oddly, multiple clicks of the home button make the colours invert AS IT SHOULD .
jje
thanks - have read the SDS thread and the stuff people were talking about there didn't really sound like what's happening for me, which is why i posted this thread.
I also thought that it sounded like the ROM or kernel, which is why I have now tried Siyah, tank, and boeffla kernel latest versions, as well as the foxhound, android revolution, and darky roms.
none have made a difference so far
I'm just looking for some ideas on what to do next - should i try reverting back to an Old rom/kernel, should i try a non-sammy based one, is it possible that my SD card is somehow causing the problem?
i didn't know that the multi-click thing inverted the colours - why does it though? it doesn't seem like something i'd want a shortcut to.
Wipe phone flash stock rom .
jje
Fixed it by moving from ELLA modem & wiping.
This thread is your solution : http://forum.xda-developers.com/showthread.php?t=2091045
so i wiped again and installed the MA2 modem - this made the freezing problem even worse so i wiped again and installed the ELKC modem.
this was on Monday and I hadn't had a single freeze until this morning, when it's frozen 4 times in the space of a few hours.
so i guess i'm flashing back to the factory image...
Lear95 said:
Fixed it by moving from ELLA modem & wiping.
Click to expand...
Click to collapse
So one day out of the blue, my phone starts acting weird. I think hey no big deal, and I just go on to restart the darn thing. When it boots up it acting normal again, but then I start to get a phone call. No big deal I answer it, but when I go to hang up it is still stuck at the point I answered it. With the answer or decline button. I think to myself to reinstall the rom again. Do that same problem still going on... I install another rom same problem two roms later same problem even after flashing a stock rooted rom.. Now here is my real question what do you think is my problem? I went from cm 10.1 working fine, to an older cm10.1 then fresh rom 3.5 then stock. With the stock rom it would boot all the way to the home screen then restart. But on my cm 10 it would boot up fine act normal then when screen timer turned the screen off it would be stuck off not like frozen the lights at the bottom would cut on but not the screen, and I'd also hear it click off.
Any ideas or is this just something for sprint tep to handle?
More information is needed to even begin to answer.
S-on or S-off, recovery version, clean or dirty flash? Take a look at the sticky for rooting and flashing roms to ensure you are doing the right processes etc.
Sent from my EVO using xda app-developers app