Okay, guys. I'm new to this forum (I own the ATRIX since yesterday, so...). I had the HTC Desire, Desire HD and EVO 3D before and never had such problems with them (instead, I used to have other issues such as crappy sound, ghost touching etc.).
Flashed Neutrino GT+ ROM, set the max CPU freq to 1 GHz, instead of 1.45 - I don't feel like I need that extra power (at least not yet, anyway). Flashed the Superuser 3.0.7 pack, flashed several Addons, also set the NitroCharger.sh script on boot... I think I pretty much did everything that mattered.
Oh, I flashed the ROM from the internal sdcard (emmc). I don't get why it's reccomended not to flash from the external sdcard, anyways, but... oh well...
-----
The best way to describe the problem(s) I am experiencing is through this movie I've made. I filmed it with a Nokia 6233, so it's not really high definition, but hey, at least it's 480p, not QVGA . Oh well, you can figure, I suppose / hope.
Okay, the problem is the touch panel is acting weird. When I'm browsing through the app drawer, and I slide my finger across and then stop or do something like that, the app that the finger was on is being launched (like I released my finger = touch ended, registered, whatever).
Also, the left and right sides of the screen seem to be less responsive (you can clearly see that in Multitouch Visualiser), especially as you get closer to the edges. Not ALL THE TIMES, though, but roughly 95%, the problem occurs and... well... the touch goes crazy.
----------------------------------------------------
Can anyone confirm that this is happening to them, and not only to me? Perhaps use Multitouch Visualiser yourself and see if you get the same results?!
VIDEO HERE
Formhault said:
Okay, guys. I'm new to this forum (I own the ATRIX since yesterday, so...). I had the HTC Desire, Desire HD and EVO 3D before and never had such problems with them (instead, I used to have other issues such as crappy sound, ghost touching etc.).
Flashed Neutrino GT+ ROM, set the max CPU freq to 1 GHz, instead of 1.45 - I don't feel like I need that extra power (at least not yet, anyway). Flashed the Superuser 3.0.7 pack, flashed several Addons, also set the NitroCharger.sh script on boot... I think I pretty much did everything that mattered.
Oh, I flashed the ROM from the internal sdcard (emmc). I don't get why it's reccomended not to flash from the external sdcard, anyways, but... oh well...
-----
The best way to describe the problem(s) I am experiencing is through this movie I've made. I filmed it with a Nokia 6233, so it's not really high definition, but hey, at least it's 480p, not QVGA . Oh well, you can figure, I suppose / hope.
Okay, the problem is the touch panel is acting weird. When I'm browsing through the app drawer, and I slide my finger across and then stop or do something like that, the app that the finger was on is being launched (like I released my finger = touch ended, registered, whatever).
Also, the left and right sides of the screen seem to be less responsive (you can clearly see that in Multitouch Visualiser), especially as you get closer to the edges. Not ALL THE TIMES, though, but roughly 95%, the problem occurs and... well... the touch goes crazy.
----------------------------------------------------
Can anyone confirm that this is happening to them, and not only to me? Perhaps use Multitouch Visualiser yourself and see if you get the same results?!
Click to expand...
Click to collapse
The app drawer thing is the manner in which you stop it, to stop the app drawer from scrolling, just give a quick very light tap, it also helps to try and tap between two of the apps, if you're using your right hand try to tap between the 3rd and 4th columns, this way you don't tap any icons. To be honest, I never really have any problems at all. Can you give me DETAILED information on how you flashed the ROM? It could be cause by a mistake in the flashing process.
Erebus671 said:
The app drawer thing is the manner in which you stop it, to stop the app drawer from scrolling, just give a quick very light tap, it also helps to try and tap between two of the apps, if you're using your right hand try to tap between the 3rd and 4th columns, this way you don't tap any icons. To be honest, I never really have any problems at all. Can you give me DETAILED information on how you flashed the ROM? It could be cause by a mistake in the flashing process.
Click to expand...
Click to collapse
I forgot to put the video link in the first topic (I edited it, it is there now).
I put Neutrino GT+ .zip in the emmc (along with all other flashables, actually). I still don't get why it is reccomended to flash from the internal memory instead of an external sdcard. Speaking of internal memory, is it an internal SD card (just like HTC devices with WP7) or NAND?!
Wiped everything in recovery (using the latest RomRacer's CWM). Then, I flashed Neutrino V2.6 GT+.zip, then Lite Gapps, then Deskclock addon, then Languages addon, then Live Wallpapers addon, then Sync addon, then Theme Chooser addon, then TTS addon, then VPN addon. Then rebooted the phone.
The red M logo appeared, and a few seconds after that, it seemed like the phone turned off and turned itself on again (M logo appeared second time, then the boot animation showed up and the ROM booted). I remember that was happening back when I was using CM7 on my old Desire and I was flashing the Gapps right after the ROM. If I were to flash MIUI and then the DarkTremor script (for A2SD), without rebooting in between, the boot splash would appear three times .
Formhault said:
I forgot to put the video link in the first topic (I edited it, it is there now).
I put Neutrino GT+ .zip in the emmc (along with all other flashables, actually). I still don't get why it is reccomended to flash from the internal memory instead of an external sdcard. Speaking of internal memory, is it an internal SD card (just like HTC devices with WP7) or NAND?!
Wiped everything in recovery (using the latest RomRacer's CWM). Then, I flashed Neutrino V2.6 GT+.zip, then Lite Gapps, then Deskclock addon, then Languages addon, then Live Wallpapers addon, then Sync addon, then Theme Chooser addon, then TTS addon, then VPN addon. Then rebooted the phone.
The red M logo appeared, and a few seconds after that, it seemed like the phone turned off and turned itself on again (M logo appeared second time, then the boot animation showed up and the ROM booted). I remember that was happening back when I was using CM7 on my old Desire and I was flashing the Gapps right after the ROM. If I were to flash MIUI and then the DarkTremor script (for A2SD), without rebooting in between, the boot splash would appear three times .
Click to expand...
Click to collapse
Okay, I'm not exactly sure about what the "Internal SD Card" is, but it is not an actual SD card, I do know that.
Are you at all familiar with fastboot? I would assume so, but I would like to know before I go any further.
Yeah, the double boot before the boot animation is normal.
Erebus671 said:
Okay, I'm not exactly sure about what the "Internal SD Card" is, but it is not an actual SD card, I do know that.
Are you at all familiar with fastboot? I would assume so, but I would like to know before I go any further.
Yeah, the double boot before the boot animation is normal.
Click to expand...
Click to collapse
I was assuming it is a SD card, so... Okay, so it is internal memory, so NAND .
I am familiar with fastboot, of course. That's how I was flashing recoveries, radios etc. on the HTC devices : fastboot flash recovery <file.img> etc...
I saw that for Motorola the fastboot commands are a bit different, and this system being somewhat different than it is on HTC devices, I am a bit afraid
Formhault said:
I was assuming it is a SD card, so... Okay, so it is internal memory, so NAND .
I am familiar with fastboot, of course. That's how I was flashing recoveries, radios etc. on the HTC devices : fastboot flash recovery <file.img> etc...
I saw that for Motorola the fastboot commands are a bit different, and this system being somewhat different than it is on HTC devices, I am a bit afraid
Click to expand...
Click to collapse
lol, okay, I'll give you a thanks for that one.
TBH, I don't use the "moto fastboot" commands, you can just use the general fastboot commands, so try this out..
Do a clean install, using fastboot wipe everything:
Code:
fastboot -w
fastboot erase system
fastboot erase preinstall
fastboot erase boot
fastboot reboot (make sure you're pressing the VOL Down button when you press enter)
reboot into recover and erase the Dalvik cache, once all that is done, flash the ROM as usual and see how it goes... Sometimes all you need is a clean install.
That's how most of my problems get fixed.
OK, I am no longer sure if it's a digitizer malfunction.
What I would do is wipe the screen completely clean with a wet PC cloth or something.
Also, try installing a different launcher (Go Launcher, ADW) and check if it does the same thing.
Usually, when the digitizer dies, the symptoms are - digitizer registers random touches without you touching it.
xploited said:
OK, I am no longer sure if it's a digitizer malfunction.
What I would do is wipe the screen completely clean with a wet PC cloth or something.
Also, try installing a different launcher (Go Launcher, ADW) and check if it does the same thing.
Usually, when the digitizer dies, the symptoms are - digitizer registers random touches without you touching it.
Click to expand...
Click to collapse
That sounds like my problem... but to hell with motorola, I'll buy my own digitizer, damned fools sent me a sim locked phone to replace a sim unlocked phone when I am under a carrier that does not have the equipment to support locking the phones to its network...
Erebus671 said:
TBH, I don't use the "moto fastboot" commands, you can just use the general fastboot commands, so try this out..
Do a clean install, using fastboot wipe everything:
Code:
fastboot -w
fastboot erase system
fastboot erase preinstall
fastboot erase boot
fastboot reboot (make sure you're pressing the VOL Down button when you press enter)
reboot into recover and erase the Dalvik cache, once all that is done, flash the ROM as usual and see how it goes... Sometimes all you need is a clean install.
That's how most of my problems get fixed.
Click to expand...
Click to collapse
No fastboot erase data and etc.? Just those? Mmmmkay . Should I do this when the battery is ABSOLUTELY FULL?! Cause yesterday I flashed when the phone was @ ~20%, and today, when the battery reached 15%, it dropped to 4% as I blinked, rofl (fully charged it earlier today).
Erebus671 said:
lol, okay, I'll give you a thanks for that one.
Click to expand...
Click to collapse
read my signature, carefully (I'll edit it to match the current state... soon... some day...)
"I've had the Wildfire, Desire & Desire HD before, so I know flies are not eatable "
God damn it, this post is a fail. Head on to the second page, rofl.
xploited said:
OK, I am no longer sure if it's a digitizer malfunction.
What I would do is wipe the screen completely clean with a wet PC cloth or something.
Also, try installing a different launcher (Go Launcher, ADW) and check if it does the same thing.
Usually, when the digitizer dies, the symptoms are - digitizer registers random touches without you touching it.
Click to expand...
Click to collapse
Erebus671 said:
That sounds like my problem... but to hell with motorola, I'll buy my own digitizer, damned fools sent me a sim locked phone to replace a sim unlocked phone when I am under a carrier that does not have the equipment to support locking the phones to its network...
Click to expand...
Click to collapse
Guys, have you tried Multitouch Visualiser?
I mean seriously... Clean your screen (like I did) with a cloth (not NASA-ultrasmooth-bacteria-remover) and then try it in that program... like I did... see if you get the same outcome...
Formhault said:
No fastboot erase data and etc.? Just those? Mmmmkay . Should I do this when the battery is ABSOLUTELY FULL?! Cause yesterday I flashed when the phone was @ ~20%, and today, when the battery reached 15%, it dropped to 4% as I blinked, rofl (fully charged it earlier today).
read my signature, carefully (I'll edit it to match the current state... soon... some day...)
Click to expand...
Click to collapse
nope.. fastboot -w takes care of that.
The battery thing is simple, once it is fully charged calibrate the battery with a battery calibration app. It's that simple.
I'm not sure what I'm supposed to be reading, the device history? or the thanks message?
---------- Post added at 05:48 AM ---------- Previous post was at 05:46 AM ----------
Formhault said:
Guys, have you tried Multitouch Visualiser?
I mean seriously... Clean your screen (like I did) with a cloth (not NASA-ultrasmooth-bacteria-remover) and then try it in that program... like I did... see if you get the same outcome...
Click to expand...
Click to collapse
I have actually and I've gotten up to 8 fingers on there with fairly accurate precision...
Edit: You'll have to elaborate on the non-eatable flies thing, understand I do not... (I didn't see you point that out until after I posted this)
Erebus671 said:
nope.. fastboot -w takes care of that.
The battery thing is simple, once it is fully charged calibrate the battery with a battery calibration app. It's that simple.
Click to expand...
Click to collapse
I thought the thing with the battery calibration was sorted already (it is a placebo?). Anyway, I'll do that (placebo DOES have effect, rofl).
Erebus671 said:
I'm not sure what I'm supposed to be reading, the device history? or the thanks message?
Click to expand...
Click to collapse
I edited the original post. Oh well, what I meant is... I'm not REALLY a newbie. Not THAT much of a newbie
Erebus671 said:
I have actually and I've gotten up to 8 fingers on there with fairly accurate precision...
Click to expand...
Click to collapse
I can only get FIVE touch points :/
Also, it seems that 5 is the maximum, lol. So how the heck did you get 8 touch points, and even working PERFECTLY :/ https://www.google.ro/search?sourceid=chrome&ie=UTF-8&q=motorola+atrix+multi+touch
-----
WHY WON'T posts merge?! -.-
Formhault said:
I thought the thing with the battery calibration was sorted already (it is a placebo?). Anyway, I'll do that (placebo DOES have effect, rofl).
I edited the original post. Oh well, what I meant is... I'm not REALLY a newbie. Not THAT much of a newbie
Click to expand...
Click to collapse
Uh, no, you're right, the battery life problem was solve, but there is no real solution to the battery calibration issue, that is cause by battery stats remaining over multiple flashes. At least that's how I comprehend it from what I have read in the past. I calibrate my battery on every flash, never once had the problem.
And I edited mine as well, and believe it or not I AM a newbie. I simply seem to not be a newbie (well not a total newbie at least) because I actually follow the first rule of XDA, unlike a lot of the people who have a million questions... Present company excluded... Basically what I just said is, I READ BEFORE I POST. Once again, I will note that I am excluding the present company when I state this.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
Formhault said:
I can only get FIVE touch points :/
Also, it seems that 5 is the maximum, lol. https://www.google.ro/search?sourceid=chrome&ie=UTF-8&q=motorola+atrix+multi+touch
-----
WHY WON'T posts merge?! -.-
Click to expand...
Click to collapse
hmm, I'll have to test again... I'll let you know what I get.
Edit: Okay, you got me, 5 it is. I seem to have forgotten and over guestimated. XD
Okay... I say again : should I flash ONLY when the battery is full? I know it wasn't much of a problem on HTCs... The difference was I had to make a few battery cycles afterwards so the battery percentage is displayed right.
Formhault said:
Okay... I say again : should I flash ONLY when the battery is full? I know it wasn't much of a problem on HTCs... The difference was I had to make a few battery cycles afterwards so the battery percentage is displayed right.
Click to expand...
Click to collapse
It's not all that important to be fully charged... I do it between 25-30% when I really have to...
Off topic... Is it safe to remove the stock messenger app? Or am I being a newbie?
Erebus671 said:
It's not all that important to be fully charged... I do it between 25-30% when I really have to...
Click to expand...
Click to collapse
As I thought .
I was thinking, somewhat, since the Motorola system is a bit different, it may require a battery closer to full... I had the Motorola V360 before and... oh well, if you know what I'm talking about, nuff said
Formhault said:
As I thought .
I was thinking, somewhat, since the Motorola system is a bit different, it may require a battery closer to full... I had the Motorola V360 before and... oh well, if you know what I'm talking about, nuff said
Click to expand...
Click to collapse
Lol, I know what you're talking about... Horrible customer service aside, I am a tried and true moto fan.
Erebus671 said:
Off topic... Is it safe to remove the stock messenger app? Or am I being a newbie?
Click to expand...
Click to collapse
I remember this part from the time I was using CM7 on my Desire. God, at that time, I thought CM7 is the ONLY ROM, lol.
Some people were saying that you need to remove/replace some libraries & some other additional files in order to be able to fully replace the stock Messaging app. I ended up just adding Handcent SMS and using the option from within its Settings menu to disable the stock Messaging app notification.
Of course, I no longer use Handcent. I was, almost a year ago. Now I'll just wait for MIUI to be fully working on the ATRIX then...
Related
I noticed recently after my friend got a fascinate that my phone takes an awfully long time to boot up.
He allowed me to tinker with his phone and pretty much copy my rom, kernal, and the settings that go with it onto it just to see if there was a problem with the combination I was using.
This yielded no difference as my phone will still take about 50 seconds while his takes roughly 20.
The majority of the time it's showing the Samsung logo. The animation process itself goes by just as quickly.
I've wiped both phones completely without getting any different results.
I've found my phone will boot up at the same time as his when both have been brought completely back to stock, but c'mon, is that really an option?
My question is if anybody knows anything else that might cause this? If so, is there a way to fix it?
I'm starting to think it might be a hardware issue as his phone is considerably newer than mine, but I still have a small glimmer of hope.
It's not a huge problem, but it would be nice if I could save time when rebooting my phone.
It's obviously not a hardware issue if you don't get this when you are stock. Not sure if there is anything you can do to speed up the boot process though
Just a thought (though I can be entirely wrong) but try swapping the SD cards from yours and your friends phones, then wipe both (both rooted with the same rom)
I could be wrong but it might be the sdcards causing the difference in speed.
Please post results as I am very curious.
Could always delete the boot animation.
Sent from my SCH-I500 using XDA App
chefthomas99 said:
Could always delete the boot animation.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I don't think that wouldn't really help. The problem with that is the segment with the boot animation actually goes by just as fast on both phones. It's just portion with the Samsung logo that takes forever really... I should probably add that to the OP.
Also, IIRC if I were to delete the boot animation it would just be replaced by either a black screen or the stock animation and it would take just as much time.
*edit* Just for safe measure I deleted the boot animation file and it left me with the scrolling Android logo.
Dalamar1320 said:
Just a thought (though I can be entirely wrong) but try swapping the SD cards from yours and your friends phones, then wipe both (both rooted with the same rom)
I could be wrong but it might be the sdcards causing the difference in speed.
Please post results as I am very curious.
Click to expand...
Click to collapse
That could be. I feel a little dumb for not thinking of it as I have a 32GB card and he still has the 16GB. I'll let you know the next time I see him.
Hey Guys,
I'm having some problems with my screen and have made a quick video to make the problem clear.
http://www.youtube.com/watch?v=6sR3JSElIvM&feature=youtube_gdata
As you can see, it's unresponsive in a horizontal section about 2cm wide near the bottom of the screen - it's almost exactly where the unlock slider resides.
I'm running CM7 weekly 11-15 with the standard CM7 kernel, 01.100.00R radio.
I've tried Aura, CM7 bat2f or whatever, as well as another radio, and the OC kernel, all with the same exact problem, so I don't think it's any of that.
I've tried factory reset, and also formatted the data, system and cache in romracers recovery.
I haven't dropped it or got water damage, it just started happening about 2 weeks ago. The phone is still usable (although annoying), but I wouldn't be able to sell it like this.
Any idea's on what the problem could be, and how I could fix it?
NOTE: I thought I fixed it after 1 of the formats, but when I re-installed apps the problem started again (could have been an ICS theme app for ADW EX), and I haven't been able to replicate it, even without installing any apps.
All suggestions and help is really appreciated
This could help: http://forum.xda-developers.com/showthread.php?t=1131649
Do you remember accidentally partitioning (in cwm) the internal storage? The above will fix it in that case. Good luck
Thanks for the tip, but unfortunately it didn't work.
I tried deep cache erase too with no luck either.
Can anyone point me to a list of commands on how to totally wipe my phone (like full on format in fastboot). I want to try totally wiping everything, data, system, cache, boot maybe, and see if that helps. However I can't find the commands for it.
Thanks heaps!
dbergen said:
Thanks for the tip, but unfortunately it didn't work.
I tried deep cache erase too with no luck either.
Can anyone point me to a list of commands on how to totally wipe my phone (like full on format in fastboot). I want to try totally wiping everything, data, system, cache, boot maybe, and see if that helps. However I can't find the commands for it.
Thanks heaps!
Click to expand...
Click to collapse
Bummer..
Here are the commands mate:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
Perfect! That's a tremendous help to me! I have searched for about 30 mins and couldn't find anything like that.
I will try soon (hanging out with the girlfriend at the moment)
Since that erases the boot, do I need to install a rom before I reboot? Don't wanna brick this thing
Why don't you install the latest fruitcake & start new? Do the above, install the fruitcake, reboot to cwm, clear dalvik & cache, reboot & let the system build up cache for 10-15 minutes.
AHHH! I've done all that now and I'm on the HKTW build of fruitcake... yet the same problem persists.
Have I exhausted all my options? Do you think it's just a screen problem that will need repair under warranty?
dbergen said:
AHHH! I've done all that now and I'm on the HKTW build of fruitcake... yet the same problem persists.
Have I exhausted all my options? Do you think it's just a screen problem that will need repair under warranty?
Click to expand...
Click to collapse
Hm. It certainly sounds like a defect then. Unless someone else has a more educated guess..
Damn it! Looks like I might have to flash it back to stock then.
I was hoping it wouldn't come to this since I had it sent over from the US, so I'll have to post it back for the warranty claim (I'm in Australia), which will be expensive and time consuming I'm sure
Thanks for trying Vangelis
dbergen said:
Damn it! Looks like I might have to flash it back to stock then.
I was hoping it wouldn't come to this since I had it sent over from the US, so I'll have to post it back for the warranty claim (I'm in Australia), which will be expensive and time consuming I'm sure
Thanks for trying Vangelis
Click to expand...
Click to collapse
Then again, if someone can verify it's the screen you could order it off eBay & swap it yourself. It's allegedly very easy.
I've seen a couple of posts about defect screens though; check in the pds thread, I think its a girl called "filmusicat" or so that had a screen issue. Check her profile & see if there isn't any thread she's started about the defect screen she had..
Same issue, got my replacement on wednesday
Sent from my CM860
Oh really Robby! Was it a warranty repair?
I just heard back from Motorola and they advised me to turn it off, then on again, lol
I might try and get it done under warranty, but if they deem it to be misuse then I'll have to pay their repair fee's which I assume will be around $200 (girlfriend had Steak screen repaired for $280).
Otherwise I can just grab a screen on ebay for $70 and do it myself.
Any recommendations?
Grab a cold Fosters before swapping it..? ;-)
Lol, thanks for that mate.
I think I'll take the warranty route. I've found quite a few others with similar problems who got a warranty replacement. One theory is that that glass is squashed down and touching the digitizer.
Now I just need to get rid of the 'unlocked' text on the boot up so they don't void my warranty :S Hopefully it's not too difficult to do
dbergen said:
Lol, thanks for that mate.
I think I'll take the warranty route. I've found quite a few others with similar problems who got a warranty replacement. One theory is that that glass is squashed down and touching the digitizer.
Now I just need to get rid of the 'unlocked' text on the boot up so they don't void my warranty :S Hopefully it's not too difficult to do
Click to expand...
Click to collapse
theres probably a guide or 2 to help you out with that, check the dev section
I actually fried a portion of my screen (the vertical area is now unresponsive) by overheating my CPU on Faux's 1.45 kernel (hold it, dev avengers... I am not blaming Faux). I have to play acrobatics with my screen orientation just to type simple sentences. Really sucks with apps that don't support rotation. There are certain letter-values my blank tiles will never again hold in Scrabble Free.
Oh that sucks dude. It's possible that mine was caused by a similar problem, but I was just running the stock CM kernel at 1ghz, however I did occasionally feel it getting pretty hot.
Couldn't you downgrade yours to stock and then take it in for a warranty replacement?
I pretty much hate my phone at the moment because texting is near impossible
OK so I did the HTCDev unlock perfectly fine, then flashed the Leedroid rom (using cwm) and the kernel (using fastboot), it loaded up and was working great until I made a phone call! Within about 2 minutes of the call it cut out completely (had about 70-75% battery), and I mean it literally just completely shut off and now it won't turn back on. I have done battery pulls, tried a different battery, plugging into charger (but light doesn't even come on!). What is going on?
Sounds like leedroid is your problem
Sent from my PG86100 using XDA
fpineda101 said:
Sounds like leedroid is your problem
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Yeah I guessed that problem is I can't boot the phone at all, so can't get into fastboot or recovery to get rid of it
Atomix86 said:
Yeah I guessed that problem is I can't boot the phone at all, so can't get into fastboot or recovery to get rid of it
Click to expand...
Click to collapse
Weird... Have u tried vol down+power?
What you could try, take the SD card out and use either another phone or sd adaptor and place on it the PG86IMG.zip file (you can find this in one of the root threads)..........try the volume-down, power button method to see if it boots into recovery.........if this works, then it will read the .zip file.
---------- Post added at 08:34 AM ---------- Previous post was at 08:33 AM ----------
of course, after placing the .zip file on the card, put back into your phone before trying to boot into recovery.
wikdNoob said:
Weird... Have u tried vol down+power?
Click to expand...
Click to collapse
Yes it was one of the first things I tried.
ycats said:
What you could try, take the SD card out and use either another phone or sd adaptor and place on it the PG86IMG.zip file (you can find this in one of the root threads)..........try the volume-down, power button method to see if it boots into recovery.........if this works, then it will read the .zip file.
of course, after placing the .zip file on the card, put back into your phone before trying to boot into recovery.
Click to expand...
Click to collapse
I wish I could do that but I can't boot using any button combination at all
the volume-down/power button method, hold them both down simultaneously for awhile................in the past I've had to do this for about a minute to get it to work.............you may have tried that already but doesn't hurt to try again.
ycats said:
the volume-down/power button method, hold them both down simultaneously for awhile................in the past I've had to do this for about a minute to get it to work.............you may have tried that already but doesn't hurt to try again.
Click to expand...
Click to collapse
Counted two whole minutes while holding them down, nothing :/ beginning to regret buying this now.
that sucks.........did you try finding that .zip file, put on the sdcard, then hold down those buttons for awhile? bTW, when you plug in the charger, do you get a red light?
ycats said:
that sucks.........did you try finding that .zip file, put on the sdcard, then hold down those buttons for awhile? bTW, when you plug in the charger, do you get a red light?
Click to expand...
Click to collapse
Yes I tried placing the file on the memory card, no dice. And no I don't get a red light when plugging into charger. It's as if the ROM or whatever the issue is, has completely destroyed it.
Atomix86 said:
Counted two whole minutes while holding them down, nothing :/ beginning to regret buying this now.
Click to expand...
Click to collapse
Sounds like a hardware issue. How long did you have it before unlocking it? Did you even make sure that the phone ran a few days before screwing around with installing a ROM and Kernel?
Would you buy a new car and not break it in before replacing the factory parts with aftermarket parts?
tgruendler said:
Sounds like a hardware issue. How long did you have it before unlocking it? Did you even make sure that the phone ran a few days before screwing around with installing a ROM and Kernel?
Would you buy a new car and not break it in before replacing the factory parts with aftermarket parts?
Click to expand...
Click to collapse
Used it for about an hour as stock, but that is irrelevant. I wasn't "screwing around" either, I have flashed many phones in my time and always follow the guides provided to completion. The car analogy isn't anything like this, rooting or installing a ROM wouldn't cause a hardware issue any different to a stock ROM would.
Atomix86 said:
The car analogy isn't anything like this, rooting or installing a ROM wouldn't cause a hardware issue any different to a stock ROM would.
Click to expand...
Click to collapse
That is halfway correct. But you said in your original post that you installed a kernel. The kernel is what runs the hardware. If the kernel is set to run the phone out of spec, this could cause hardware issues.
Did you change the max CPU? What about undervolting?
tgruendler said:
That is halfway correct. But you said in your original post that you installed a kernel. The kernel is what runs the hardware. If the kernel is set to run the phone out of spec, this could cause hardware issues.
Click to expand...
Click to collapse
The kernel was the leedroid one, but I thought it only started running that if you booted regularly eg not into fastboot?
Atomix86 said:
The kernel was the leedroid one, but I thought it only started running that if you booted regularly eg not into fastboot?
Click to expand...
Click to collapse
If you installed the ROM and Kernel, you were running it when you made the phone call and the phone went dead. Leeroids kernel, even though he is an excellent developer and I am not saying anything bad about him or his work, changes cpu and undervolting settings which could cause issues with the phone. I am not saying that that is what caused your issue, but it could have been your phone not playing nice with the kernel.
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Yep... sounds to me like a hardware failure. Shiat! :-/
tgruendler said:
If you installed the ROM and Kernel, you were running it when you made the phone call and the phone went dead. Leeroids kernel, even though he is an excellent developer and I am not saying anything bad about him or his work, changes cpu and undervolting settings which could cause issues with the phone. I am not saying that that is what caused your issue, but it could have been your phone not playing nice with the kernel.
Click to expand...
Click to collapse
That is very true, I was just hoping that the kernel "boot up" so to speak could be avoided by opening fastboot and flashing a stock rom back. But as you stated perhaps the undervolting has messed something up. Thank you very much for your insight and help.
ycats said:
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Click to expand...
Click to collapse
Funnily enough this is what i'm going to do now, having a quick google search shows a few people suggesting to do this (im not quite sure what it does, something to do with the phone dispersing the charge it has inside it or some such?), so thanks for the suggestion!
Jakedude2011 said:
Yep... sounds to me like a hardware failure. Shiat! :-/
Click to expand...
Click to collapse
Indeed
ycats said:
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Click to expand...
Click to collapse
Holy crap, this actually worked! Now I just have to find a way of removing that nasty kernel xD
AWESOME! I believe the stock kernel would be in that .zip file if it flashed from recovery.
When I first received my Galaxy Player, I was ecstatic; my first Android device! Well that was back in June 2012 and now it's becoming more of a frustration than anything!
I got into the modding scene just like the old days with the Sony PSP so I've rooted the device and flashed many ROMs over the months. I've found some really nice setups and learned a lot. I've ended up with the following setup and I love it:
Galaxy Player 5 International
Kernel: rj's custom kernel for Galaxy Player 5.0 INTL (YP-G70) r14
ROM: G70XXKPH Gingerbread 2.3.6 Stock Firmware
Launcher: Xperia Home 2.2.A.0.14.ra3al.r7
Since the Galaxy Player doesn't have support any variant of ICS with a working camera I went after the best GB ROM I could find. I've tried Chip, Entropy and others but they've all had their problems and I moved on to my current one. I can actually hear the Android tap sounds on this when I touch an icon like in the stock GB ROM! Among other reasons I believe this ROM to be my best option.
As for launchers, I've been through all the popular ones including all of the TouchWiz's, Go Launcher, Holo and now Xperia. This one is absolutely amazing! I love nearly everything about it, especially the animations and layouts! It pairs really nicely with the weather widget app too!
I finally get all of this setup and performing smoothly and quite fast too! But of course there has to be problems ~
The biggest problem is the card reader very often hiccups and thinks the cards are damaged or have been unmounted or removed randomly. This happens with more than 2 of my cards so it's the device itself!
Frequently random crashes where I cannot turn the display or anything on, requires hard reboot.
The camera very occasionally winds up with a disabled touch screen after taking a picture.
The camera often doesn't even load past a black screen with the status bar to the side.
Etc..
I'm starting to think it's best to stick with the Stock ROM and use my favorite Launcher and Kernel and avoid all this hassle! Although I was under the impression that I AM using the stock ROM, minus the tweaks mentioned on the developer's thread. Does anyone know why I'm having all of these problems?
My goal is to get this device back to factory default settings including ROM and Kernel. I just got the thing in a bootloop after flashing the stock ROM via Odin so I'm trying to figure that out. I'm also having difficulty finding the legit stock ROM and possibly Kernel, where could I get those if you don't mind?
SesukaShindo said:
My goal is to get this device back to factory default settings including ROM and Kernel. I just got the thing in a bootloop after flashing the stock ROM via Odin so I'm trying to figure that out. I'm also having difficulty finding the legit stock ROM and possibly Kernel, where could I get those if you don't mind?
Click to expand...
Click to collapse
Latest legit stock ROM is linked from the end of the KPH thread. It includes the kernel.
However, no stock kernel supports the ext4 filesystem. That means if your /data or /cache are formatted to ext4, it cannot read them and bootloops. To fix, either go into recovery and wipe data and cache, or if you have things on there that you don't want to lose, flash Rumirand's kernel again with Odin, go into cwm, and make a nandroid. You will still have to wipe data from "Android System Recovery" after flashing stock, but you will have a backup.
Mevordel said:
Latest legit stock ROM is linked from the end of the KPH thread. It includes the kernel.
However, no stock kernel supports the ext4 filesystem. That means if your /data or /cache are formatted to ext4, it cannot read them and bootloops. To fix, either go into recovery and wipe data and cache, or if you have things on there that you don't want to lose, flash Rumirand's kernel again with Odin, go into cwm, and make a nandroid. You will still have to wipe data from "Android System Recovery" after flashing stock, but you will have a backup.
Click to expand...
Click to collapse
Thanks for the tip! I was wondering how to get back into recovery since holding down and/or home wasn't working at this point. Didn't remember that you could flash r14 with Odin. I'll have to try that!
Do you have any experience with the complaints I have about the device or am I the only one who's device tends to act up this way?
SesukaShindo said:
Thanks for the tip! I was wondering how to get back into recovery since holding down and/or home wasn't working at this point. Didn't remember that you could flash r14 with Odin. I'll have to try that!
Do you have any experience with the complaints I have about the device or am I the only one who's device tends to act up this way?
Click to expand...
Click to collapse
No, I haven't experienced them, but I spend most of my time on ROMs where camera is broken. Your issues sound specific to your device, or to your ROM/kernel. I recommend upgrading to XXKPL, as that may help.
And I believe on International devices recovery is vol UP and home, not down.
Mevordel said:
No, I haven't experienced them, but I spend most of my time on ROMs where camera is broken. Your issues sound specific to your device, or to your ROM/kernel. I recommend upgrading to XXKPL, as that may help.
And I believe on International devices recovery is vol UP and home, not down.
Click to expand...
Click to collapse
That was a typo, I meant to say "Up+Home", Down is download mode lol, woops.
My new setup (before reading your post):
Kernel: r14
Firmware: 2.3.6
Build: GINGERBREAD.XXKPH
What's the difference between XXKPH and XXKPL?
Update: I'm trying to flash XXKPL with Odin but it just makes the device bootloop. I'm even using a .pit named "G70-GalaxyPlayer5.0-8gig-Inter_model_2.3.5" but it just bootloops. So I'm figuring it's due to that file extension situation and I'm trying to figure out how to properly flash this Stock (XXKPL) ROM properly.
Update: Okay! It seems all you need to do is flash rem's r14 kernel and the device boots right up. Shame there's no one click fix to just flash the Stock ROM without issue like with flashing a custom ROM through CWM Recovery Menu.
Now I'm sitting at:
ROM: Stock G70XXKPL
Firmware: 2.3.6
Kernel: Rem's R14
I look forward to the first problem in this setup!
The new JB roms are in Nightly betas. So far all of the things that we are missing from it are Camera (kinda works), functionality for the earphones/headphones (you have to plug in earphones with a mic and then all of the other types work). That's really the only major problems I can remember and they are all close to being fixed.
Sent from my YP-G70 using xda app-developers app
damnyouwaffles said:
The new JB roms are in Nightly betas. So far all of the things that we are missing from it are Camera (kinda works), functionality for the earphones/headphones (you have to plug in earphones with a mic and then all of the other types work). That's really the only major problems I can remember and they are all close to being fixed.
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
That's pretty impressive! I had no idea they were that far along in JB! I could search for it myself but I'd probably find the wrong thing, could you give me a link to this particular JB Project please? I really want to follow and support it!
Ah and of course all day I've been dealing with this device of mine misbehaving! Every time I pull it out of my pocket and try to wake it up it just doesn't respond, no lights no screen, there's nothing. I have to keep hard booting it every few hours!
The worst thing is the camera almost never loads anymore! Either the default or my Camera Zoom FX app. I launch it and it never fully loads up or if it does it either takes 1 pic and then the touch screen doesn't respond. Or it says there's a problem with the SD card like it's missing or damaged so it doesn't save the pictures.
There is always something with this device I'm so annoyed with it -_-. Any help or advice? Because I'm at my whit's end here with ideas!
Update: I'm actually starting to suspect the Xperia S Home Launcher as the problem here. I noticed this did mostly start to get worse when I installed it and so far since I removed every Xperia-related software and went to default TouchWiz that it's performing just fine. I hope it stays this way but what a shame, I really like the Xperia Launcher. Even more than my favorite Go Launcher Ex! D:
Here is JB http://forum.xda-developers.com/showthread.php?t=2077671
Sent from my Nexus 7 using xda app-developers app
DZonikg said:
Here is JB http://forum.xda-developers.com/showthread.php?t=2077671
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for that! I was under the impression that CyanOgen 10.1 was the main JB ROM. Glad I asked lol.
Btw a little update with my Galaxy Player!
The Good:
So far, since I've switched back to TouchWiz and dropped Xperia (sadface), my device has not locked up on me!
The camera also stays functional!
The Bad:
"SD card unexpectedly removed" continues to randomly occur (as I'm writing this)! Why? The card is still in there, I never touched it.
Still, when I power it down, the device sometimes hangs at the black screen and never completes the process!
Must reboot first to connect USB to PC. Even with USB Debugging disabled and Mass Storage selected.
Is this normal? I'm seriously starting to wonder..
SesukaShindo said:
The Bad:
"SD card unexpectedly removed" continues to randomly occur (as I'm writing this)! Why? The card is still in there, I never touched it.
Still, when I power it down, the device sometimes hangs at the black screen and never completes the process!
Must reboot first to connect USB to PC. Even with USB Debugging disabled and Mass Storage selected.
Is this normal? I'm seriously starting to wonder..
Click to expand...
Click to collapse
Is not normal... Never got ext. SD Card unmounted or remove notification in 4 months of use. My advice was to try with another SD Card but you already done this!
Try clean the SD Card socket (blow on it) and push and pop some times the card, just to be sure that there isn't some dirt that make false contact.
If the problem persist i'd suggest to bring at garancy assistence.
Mine takes much time too... it takes more time to turn off that turn on, but after an half minute it vibrate and turn off itself.
zardak said:
Is not normal... Never got ext. SD Card unmounted or remove notification in 4 months of use. My advice was to try with another SD Card but you already done this!
Try clean the SD Card socket (blow on it) and push and pop some times the card, just to be sure that there isn't some dirt that make false contact.
If the problem persist i'd suggest to bring at garancy assistence.
Mine takes much time too... it takes more time to turn off that turn on, but after an half minute it vibrate and turn off itself.
Click to expand...
Click to collapse
I just tried using air pressure to clear out any dirt and no improvements thus far.
Main problems:
Camera works 50% of the time.
SD Card reader randomly claims 'unexpectedly unmounted'.
USB storage randomly stops successfully connecting.
My question now:
I feel like my particular Galaxy Player is a Lemon. What is the manufacture's warranty for this if I bought it from Samsung? What are the chances of me exchanging it or getting it refurbished or w/e after all this modding? (shot in the dark lol)
SesukaShindo said:
I just tried using air pressure to clear out any dirt and no improvements thus far.
Main problems:
Camera works 50% of the time.
SD Card reader randomly claims 'unexpectedly unmounted'.
USB storage randomly stops successfully connecting.
My question now:
I feel like my particular Galaxy Player is a Lemon. What is the manufacture's warranty for this if I bought it from Samsung? What are the chances of me exchanging it or getting it refurbished or w/e after all this modding? (shot in the dark lol)
Click to expand...
Click to collapse
Flash back to stock and they'll never know.
Mevordel said:
Flash back to stock and they'll never know.
Click to expand...
Click to collapse
Lol, stock is KPL right?
SesukaShindo said:
Lol, stock is KPL right?
Click to expand...
Click to collapse
Yes
Sent from my Galaxy Nexus using xda app-developers app
Awesome, then I'll stick to KPL for now. Oddly enough I have this setup:
ROM: KPL
Kernel: Remirand's r14
Launcher: Xperia (i can't help it!)
And so far the only persistent issue is the SD Card "unexpectedly removed" and the occasional need for a hard boot. Hopefully this is the worst of it, aside from the minor nuisance . I think my device will always have those.
similar problems
I have similar SD card problems. I use it primarily as a music player, and at random intervals I'll get messages in the stock music app saying either "This file does not exist", or "This file type is not recognized."
Typically, I have to remove and remount the SD card, sometimes several times, to clear the error.
Ya my problems are all still persisting an really bad now.. Going to send device to samsung through warranty. This is definitely a hardware issue and i cant fix it!
Sent from my YP-G70 using xda app-developers app
SesukaShindo said:
Ya my problems are all still persisting an really bad now.. Going to send device to samsung through warranty. This is definitely a hardware issue and i cant fix it!
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I gave up on it. Returning it to Amazon today.
I'm testing out my Galaxy Tab as a music player...seems to work OK so far.
Hits da Bong said:
Yeah, I gave up on it. Returning it to Amazon today.
I'm testing out my Galaxy Tab as a music player...seems to work OK so far.
Click to expand...
Click to collapse
If only I had these problems within the first 30 days, then I could return it easy to Amazon as well. Hopefully I have success with Samsung Warranty. One annoying thing is I have only 10 days to make sure the device arrives at their site before my claim ticket is canceled so I have to wait to create a new ticket to use it. Such a hassle.
delete this post.
Let's keep it clean and positive in here.
Thanks every one!
http://forum.xda-developers.com/showthread.php?t=2958197
[ROM][CM12][UNOFFICIAL] CyanogenMod 12 BETA - LS990
Loving the 12/03 build, Everything is so smooth.
Testing now will report back later , Thank you! :good:
Only problems I've come across so far is send button in stock messaging app does nothing. Having to use hangouts. And location toggle on power control widget does not work either. Other than that its amazing
SimPup said:
Only problems I've come across so far is send button in stock messaging app does nothing. Having to use hangouts. And location toggle on power control widget does not work either. Other than that its amazing
Click to expand...
Click to collapse
Try this messaging app update. Was updated by Google today. Updating a system app like this (I think my problem was Google Play Music), from gapps 5.0 fixed my issue.
vestaviajag said:
Try this messaging app update. Was updated by Google today. Updating a system app like this (I think my problem was Google Play Music), from gapps 5.0 fixed my issue.
Click to expand...
Click to collapse
Yeah other apps work just fine. Its the stock message app that won't send anything. Not that big of a deal. I like hangouts better anyways. Was just sharing bugs with the rom.
Anyone experiencing the screen coming on in pocket. I have had that issue with all builds of CM and G3. I use nova and greenify to tap to sleep and tap to wake.
HappyFillmore said:
Anyone experiencing the screen coming on in pocket. I have had that issue with all builds of CM and G3. I use nova and greenify to tap to sleep and tap to wake.
Click to expand...
Click to collapse
Lol had 67 pictures of the inside of my pocket yesterday
SimPup said:
Lol had 67 pictures of the inside of my pocket yesterday
Click to expand...
Click to collapse
Well at least I know I'm not crazy. This build is super slick. Super spoiled on the tap to wake and sleep feature.
SimPup said:
Lol had 67 pictures of the inside of my pocket yesterday
Click to expand...
Click to collapse
Hahaha holy crap that's insane!! I am yet to see a case like that in my time with the g3 but if it persists, maybe get a tempered glass to slightly lower the sensitivity of your screen? Or just disabled double tap to wake
clark44 said:
Hahaha holy crap that's insane!! I am yet to see a case like that in my time with the g3 but if it persists, maybe get a tempered glass to slightly lower the sensitivity of your screen? Or just disabled double tap to wake
Click to expand...
Click to collapse
Lol yeah that's the first time it ever happened. There was like 3 hours i didn't check my phone and couldn't figure out why I lost like 25% battery til I got home and seen the pics haha.
Switched to Android after several year with iPhones and long before that I had a HTC evo... (Bleh). Lovin it so far, just few questions with CM12. (hopefully this is the right place)
-does Cm12 support exFat format, I understand TWRP doesn't recognize my sd card due to that, just wondering if CM12 would and recommendation if I should format it to FAT32. ( I have definitely read that if I don't format it to FAT32 the rom won't mount it correctly)
-I am traveling out of town this christmas, usually I would just call sprint to unlock it internationally so I can use a sim card while I'm abroad. If I flash cm12 would this still work or would I have to do some complicated adb shell command and stuff to unlock it myself?
Really appreciate this forum and its awesome, helpful people. Glad I'm in this ship with y'all.
SimPup said:
Lol yeah that's the first time it ever happened. There was like 3 hours i didn't check my phone and couldn't figure out why I lost like 25% battery til I got home and seen the pics haha.
Click to expand...
Click to collapse
I have only had it happen with CM flavors. Stock no issues.
SimPup said:
Lol yeah that's the first time it ever happened. There was like 3 hours i didn't check my phone and couldn't figure out why I lost like 25% battery til I got home and seen the pics haha.
Click to expand...
Click to collapse
Classic lol. Did it happen again?
mm55502003 said:
Switched to Android after several year with iPhones and long before that I had a HTC evo... (Bleh). Lovin it so far, just few questions with CM12. (hopefully this is the right place)
-does Cm12 support exFat format, I understand TWRP doesn't recognize my sd card due to that, just wondering if CM12 would and recommendation if I should format it to FAT32. ( I have definitely read that if I don't format it to FAT32 the rom won't mount it correctly)
-I am traveling out of town this christmas, usually I would just call sprint to unlock it internationally so I can use a sim card while I'm abroad. If I flash cm12 would this still work or would I have to do some complicated adb shell command and stuff to unlock it myself?
Really appreciate this forum and its awesome, helpful people. Glad I'm in this ship with y'all.
Click to expand...
Click to collapse
Whether or not the ROM supports exFat, I would format it regardless so TWRP can access it. It makes it easier on yourself. My logic is; what if this awesome new rom comes out and it doesn't have exFAT support for a while and you really want to access your music and photos? It's just easier to format it to FAT32 and never have that problem. I actually have a link to format it if need be. I'm running Windows 7 on my laptop so my 64gb Micro SD did not have a FAT32 option for formatting by default. I did read that Windows 8 users do not have this issue. I tried three different programs and this was the only one that actually was successful in formatting my card to FAT32: http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm
CM12 does not include activation tools (which is why you don't do an advanced wipe when flashing to this since you need to keep the activation bits from the ROM you are coming from) and as such my feeling is that Sprint won't touch the device for unlocking. Also, the rep likely has no experience with CM so you're better off just putting it on stock to get it properly configured and then flashing back to CM once you've gotten the thing unlocked. I've seen some stuff about build.prop edits and whatnot to run the phone on different carriers without official unlocks but I don't recall seeing definite evidence that it works. You're best off asking someone else about that one.
I'm waiting for CM12 to download myself! I want to join the fun. Is there anything that can be done to improve the slow download speeds for the builds? I've been spoiled for far too long by androidfilehost and the fact that it's taking 45 minutes to download 244MB is killing me. I can wait, I'd just love an alternative if one exists.
outofluck said:
Whether or not the ROM supports exFat, I would format it regardless so TWRP can access it. It makes it easier on yourself. My logic is; what if this awesome new rom comes out and it doesn't have exFAT support for a while and you really want to access your music and photos? It's just easier to format it to FAT32 and never have that problem. I actually have a link to format it if need be. I'm running Windows 7 on my laptop so my 64gb Micro SD did not have a FAT32 option for formatting by default. I did read that Windows 8 users do not have this issue. I tried three different programs and this was the only one that actually was successful in formatting my card to FAT32: http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm
CM12 does not include activation tools (which is why you don't do an advanced wipe when flashing to this since you need to keep the activation bits from the ROM you are coming from) and as such my feeling is that Sprint won't touch the device for unlocking. Also, the rep likely has no experience with CM so you're better off just putting it on stock to get it properly configured and then flashing back to CM once you've gotten the thing unlocked. I've seen some stuff about build.prop edits and whatnot to run the phone on different carriers without official unlocks but I don't recall seeing definite evidence that it works. You're best off asking someone else about that one.
I'm waiting for CM12 to download myself! I want to join the fun. Is there anything that can be done to improve the slow download speeds for the builds? I've been spoiled for far too long by androidfilehost and the fact that it's taking 45 minutes to download 244MB is killing me. I can wait, I'd just love an alternative if one exists.
Click to expand...
Click to collapse
Thant makes sense, guess I will just have sprint unlock it before I flash the ROM. Thanks for answering probably really stupid questions!
In regards to reformatting, I have heard that formatting an exFat to Fat32 will eventually lead to corruption of the SD card later on. That's why I was hesitant.
But for downloading the build, it took longer than usual but nothing crazy like 45 minute... I wasn't on WiFi and it took like 5-10 minute max... Guess I'm just lucky?
mm55502003 said:
Thant makes sense, guess I will just have sprint unlock it before I flash the ROM. Thanks for answering probably really stupid questions!
In regards to reformatting, I have heard that formatting an exFat to Fat32 will eventually lead to corruption of the SD card later on. That's why I was hesitant.
But for downloading the build, it took longer than usual but nothing crazy like 45 minute... I wasn't on WiFi and it took like 5-10 minute max... Guess I'm just lucky?
Click to expand...
Click to collapse
Hmm, I didn't hear anything about corruption.... I should look into that. Worst case it gets corrupted and I just reformat it and start over
Don't be ridiculous! This is XDA. There are only two kinds of stupid questions: The question about ETAs, and the question about something that is clearly stated in the main post. Yours is neither of those so your questions are entirely legitimate.
Lucky... I figured if anything it'd be better for me being that it's now 4am, so server traffic should be lower... I have definitely been downloading this for about an hour now and it's got another 70 or so MB to download. I'm on my home wifi network which hit the speeds you'll see in the image below, WITH the download going on in the background. Normally I'm topping out around 60mbps down. I'll have to wait until tomorrow to flash. Meh. My luck it'll finish and when I check the MD5 it'll be partially corrupted. Hehe
outofluck said:
Hmm, I didn't hear anything about corruption.... I should look into that. Worst case it gets corrupted and I just reformat it and start over [emoji14]
Don't be ridiculous! This is XDA. There are only two kinds of stupid questions: The question about ETAs, and the question about something that is clearly stated in the main post. Yours is neither of those so your questions are entirely legitimate.
Lucky... I figured if anything it'd be better for me being that it's now 4am, so server traffic should be lower... I have definitely been downloading this for about an hour now and it's got another 70 or so MB to download. I'm on my home wifi network which hit the speeds you'll see in the image below, WITH the download going on in the background. Normally I'm topping out around 60mbps down. I'll have to wait until tomorrow to flash. Meh. My luck it'll finish and when I check the MD5 it'll be partially corrupted. Hehe
Click to expand...
Click to collapse
Hmmmm. I just downloaded the 12/4 build again because I accidentally whiped my internal storage and system while restoring to stock to get sprint to unlock (ops). It definitely did not take that long... Lemme test me download speed and report back
Edit:
Erm my wifi DL speed is definitely worse than yours per speed test
Question are you downloading the zip using computer or your phone? (Not sure if that makes a difference, but I'm on my phone)
Still no native mms ... And suddenly can't write to ext sd
whojabacod said:
Still no native mms ... And suddenly can't write to ext sd
Click to expand...
Click to collapse
No MMS here as well. Anyone know what the culprit could be? I have data and it works.
Native mms is a hit and miss for me depending on phone and rom. I didn't even try textra on this rom, because I we having to many issues just trying to call someone. My dialer and contacts FCing in a weird way.
sent from my LG G3