Related
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...
All, I've gone through many of the forums here and all I am now is confused. Issue: Had CWM and NVFLASH on and Honeycomb on gtab. Some issues, wanted to go back to stock. Followed instructions; however, now it's in a loop. I cannot get to it via PC. Holding power and volume key, see the 3 birds and "recovery key detected, goes to gtablet screen, goes to screen with a box (arrow in it pointing down) and status bar across bottom, goes to w/tap n tap screen, goes to screen with tnt; then reboots through the process again and again. I've spent the past two weeks going through the internet and reading the various methods to unbrick, none work; because I can't get to the internal SD card.
Is there a way to fix this? Is there a way to use the external micro-SD card? Or do I just need to throw this thing away? Any assistance would be appreciated. Oh, I've tried the Code Red and every other unbricking method I came across.
Thank you in advance, Michael
[email protected]
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
nobe1976 said:
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
Click to expand...
Click to collapse
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
There is a way to "install clockwork from external SD" - search that phrase and you should find it.
BTW- If you plan on trashing it, I'll pay for shipping to my house. I'll 'throw it away' for you
new_to-droid said:
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
Click to expand...
Click to collapse
Well all and all I know your fustration. The first link I beleive you are using is the Stock 1.1 from the 3588 branch. That one I used before and had nothing but issues. The best one to use is from the 4349 branch perfered with CWM pre-installed. After flashing that file shut the Tablet off during boot up. Then boot into recovery mode by holding down the volume + while pressing the power button. Do a Wipe Data Factory reset, Clear Cache, and then under advance Wipe Dalvic Cache then go back to main menu of CWM and reboot device. Make sure you don't select reboot recovery since that will not let you boot into anything but CWM. TNT TabUI will then boot up and you chould be good to go.
Thanks...but
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
$$Price?
Sent from my Droid using XDA
new_to-droid said:
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
Click to expand...
Click to collapse
Sorry to see that your experience with your newly found failure did not come with a price of knowledge. Truth be sayed I am no programmer, geek or knowledge of script writing either, but what I can pass along to all new-to-android persons is that your best path is to read and follow instructions to the T or you will end up with a expensive paper wait. The web link I posted above is pretty self explained and I give that man credit because I was a newbie too once. Then somewhere in these forums I found that website and was able to recover from just about anything that happened to my poor Gtab. Hell, I even had to drill a hole in the back of the case just because I wanted more and there was ICS from Team DRH. But truth be said that web link is your path and only path to going back to the stock UI and recovery.
Price
50 plus shipping to us only
new_to-droid said:
50 plus shipping to us only
Click to expand...
Click to collapse
I'll buy it. DIBS EVERYONE!
PM me with your info and I'll have the money sent right away.
Even if I couldn't get it to work, I could use it for parts for my current g-tab.
EDIT: Don't mind my post count. I'm very active on SD, just not here.
Just wanted to mention that I have not been PM'd or replied to. Hope this guy got his tab to work.
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.
Hi all,
I thought this might help ppl, it certainly helped me.
So as I reported earlier mine NT was one of those which wont boot off of the sd unless tethered. I did many things but I THINK (can't be certain) that I did what is mentioned my the guy PHIL here in the below link and it solved it (for until now, for my last 3-4 boots)
Basically, just remove the cord once you see the N sign, timing might be important I don't know.
For reference: http://www.androidfornook.com/forum/thread-98.html
P.S. : Making a separate thread so that ppl can see and get benefited. Sorry if thats against forum rules. Just trying to help
Cheers !
I'm sorry, but I don't really get how this is a solution to the problem that you need to be thethered to boot from sd. In order for you to "remove the cord" it has to be inserted in the first place = you are thethered. Or am I missing something?
Normally what you do with those troublesome ones that needs to be tethered to boot from sd is you turn it off (wich of course you do anyway!), and instead of pressing "power" you insert the powered cable. Once the boot process starts you can either leave the chord in or remove it. It doesn't matter.
Is this something different where you don't need the chord to be connected to the charger? Or is it for a number of Tablets that doesn't boot from sd even when thethered the "normal" way (with the powered chord)?
Sorry, don't mean to be difficult, but I honestly don't get it! I have only had one of the 10 or so NT:s that has passed through my hands with this problem, so I really have very little experience of it and want to learn more!
Edit: I think I maybe get it now. There is a lot of talk about sleep mode and turning off the device and this supposedly allows you to turn on and off the device and it boots into SD until you need to charge it again. Personally I never turn off my devices unless for example on an airplane. It hardly looses any battery in standby as long as wifi is off. A good ROM will not require you to turn it for battery conservation!
asawi said:
I'm sorry, but I don't really get how this is a solution to the problem that you need to be thethered to boot from sd. In order for you to "remove the cord" it has to be inserted in the first place = you are thethered. Or am I missing something?
Normally what you do with those troublesome ones that needs to be tethered to boot from sd is you turn it off (wich of course you do anyway!), and instead of pressing "power" you insert the powered cable. Once the boot process starts you can either leave the chord in or remove it. It doesn't matter.
Is this something different where you don't need the chord to be connected to the charger? Or is it for a number of Tablets that doesn't boot from sd even when thethered the "normal" way (with the powered chord)?
Sorry, don't mean to be difficult, but I honestly don't get it! I have only had one of the 10 or so NT:s that has passed through my hands with this problem, so I really have very little experience of it and want to learn more!
Edit: I think I maybe get it now. There is a lot of talk about sleep mode and turning off the device and this supposedly allows you to turn on and off the device and it boots into SD until you need to charge it again. Personally I never turn off my devices unless for example on an airplane. It hardly looses any battery in standby as long as wifi is off. A good ROM will not require you to turn it for battery conservation!
Click to expand...
Click to collapse
Hi, I see the confusion, what I meant (at least worked for me) is to that as a one time thing.. after that if I switch off switch on it can boot from sd card by pressing the n key on startup, no more need of tethering. I don't know if it'll work with everyone, don't have more such tablets to try on. Give it a shot. Worked for me, I hope this helps
firstdavis said:
Hi all,
I thought this might help ppl, it certainly helped me.
...
Basically, just remove the cord once you see the N sign, timing might be important I don't know.
For reference: http://www.androidfornook.com/forum/thread-98.html
...
Click to expand...
Click to collapse
The "remove the cord on the first boot-screen flash" was identified/posted on XDA at http://forum.xda-developers.com/showpost.php?p=25668292&postcount=13. I had used it successfully when I was running CM7-beta, but I have not been able to get it to work with any CM9 and CM10 SD ROM builds.
digixmax said:
The "remove the cord on the first boot-screen flash" was identified/posted on XDA at http://forum.xda-developers.com/showpost.php?p=25668292&postcount=13. I had used it successfully when I was running CM7-beta, but I have not been able to get it to work when with any CM9 and CM10 SD ROM builds.
Click to expand...
Click to collapse
I didn't know about that thread, still reading all of it.. but just fyi, this method worked for me for CM10.2 (android 4.3 latest ROM)
Hi there,
I've got CM10.2 running on my TF201 (currently on version from 20131211), it all works a lot better than before, thanks for the good work!
I am not allowed to respond in the thread about this rom since I'm to new here, hence in Q&A.
There are two things that I do not yet understand, and haven't found anything on in the entire thread:
the power button doesn't seem to work anymore, I can only reboot via a special app...can I even turn the tablet on again if I turn it off? I don't want to turn it off right now
the buttons in the nav bar are in the middle, how to get them back to the left? especially with the dock attached the center buttons are hard to reach...
Any suggestions/hints/tips/tricks?
more questions
Hi again all,
Like several others also reported, in my case my micro hdmi port no longer seems to work. Has anyone found a workaround for this yet?
And finally, the least of the issues, but I wanted to list it anyway: all of my keys on my dock-keyboard work, except for one: the power-off or lock-button (top row, rightmost button). A long shot perhaps, but could this be related to the other (main) powerbutton not working as it should?
All ideas and suggestions are appreciated,
Cheers,
Peregr1ne
power button works differently
Peregr1ne said:
the power button doesn't seem to work anymore, I can only reboot via a special app...can I even turn the tablet on again if I turn it off? I don't want to turn it off right now
Click to expand...
Click to collapse
Having used it for a while now, I found out that that the hardware power button on the tablet in fact does still work...but it works differently...
Under normal conditions when using my Prime (like now), it does not work: there is no way to "lock", power down, or reboot the tablet with hardware buttons; fortunatly there are apps available to trigger this software-based.
When the tablet is "sleeping" an attached to its dock, folding open the dock wakes the tablet up, and the power button is not required (nor doing anything if pressed).
If the tablet is sleeping but not folded closed or not attached to the dock however, the power button does activate the screen and bring up the login screen.
Anyone any ideas? Is this a setting I can adjust myself? Do I have to install something (a driver of sorts)?
All help is appreciated...
Cheers!
Peregr1ne said:
Having used it for a while now, I found out that that the hardware power button on the tablet in fact does still work...but it works differently...
Under normal conditions when using my Prime (like now), it does not work: there is no way to "lock", power down, or reboot the tablet with hardware buttons; fortunatly there are apps available to trigger this software-based.
When the tablet is "sleeping" an attached to its dock, folding open the dock wakes the tablet up, and the power button is not required (nor doing anything if pressed).
If the tablet is sleeping but not folded closed or not attached to the dock however, the power button does activate the screen and bring up the login screen.
Anyone any ideas? Is this a setting I can adjust myself? Do I have to install something (a driver of sorts)?
All help is appreciated...
Click to expand...
Click to collapse
I surely cannot be the only one facing these issues?
Is there really no one that can tell me has tips for me?
Regarding rebooting, as far as I can remember, the prime will boot if you plug it in to the charger.
Sent from my LG D802
Makrilli said:
Regarding rebooting, as far as I can remember, the prime will boot if you plug it in to the charger.
Sent from my LG D802
Click to expand...
Click to collapse
Ahhh, that is a reassuring thought, thanks!
I have not yet power it down, but I'm sure that will happen sooner or later, good to know it should power up in that case...
Peregr1ne said:
Ahhh, that is a reassuring thought, thanks!
I have not yet power it down, but I'm sure that will happen sooner or later, good to know it should power up in that case...
Click to expand...
Click to collapse
not sure myself, but maybe its the CM10.2 thats causing those problems?
have you tried going back to more of a stock ROM and try?
lil-devil said:
not sure myself, but maybe its the CM10.2 thats causing those problems?
have you tried going back to more of a stock ROM and try?
Click to expand...
Click to collapse
I agree, most likely it has to do with the rom, and I probably should try downgrading to confirm so.
I was hoping to run into someone who had run into the same issue and found a solution.
I'm not allowed to post in threads any place but here - yet...but a few more posts and I can
Peregr1ne said:
I agree, most likely it has to do with the rom, and I probably should try downgrading to confirm so.
I was hoping to run into someone who had run into the same issue and found a solution.
I'm not allowed to post in threads any place but here - yet...but a few more posts and I can
Click to expand...
Click to collapse
i guess just search the thread and read... cause most of those people actually don't go to these question threads
lil-devil said:
i guess just search the thread and read... cause most of those people actually don't go to these question threads
Click to expand...
Click to collapse
erm...I did, I went through all 21 pages...and I didn't find answers to the questions I stated above
Peregr1ne said:
I surely cannot be the only one facing these issues?
Is there really no one that can tell me has tips for me?
Click to expand...
Click to collapse
Same here. Power button and lock button work for some time after reboot. But touchpad disabling does not work at all.
I think I did not see it w/ 10.1 and not with early 10.2.
Touchpad enable/disable works for me, only the lock-button doesn't work.
Peregr1ne said:
Touchpad enable/disable works for me, only the lock-button doesn't work.
Click to expand...
Click to collapse
You'll probably get it to work if you take it away from the dock and use vol down and up buttons for a couple of times. For me it helps and after that the lock works for some time.
Just installed the latest CM 10.2 UNOFFICIAL on Saturday night. Started with the official 4.1.1 JB from ASUS (10.4.2.18), unlocked, made NVFLASH recoveries, flashed TWRP 2.6.3, then flashed the CM ROM. Works great, including the power button. Don't have the keyboard dock, so can't speak to those problems. Only real issue for us was make sure you clear all the stuff before you flash the ROM (and we did it again after as well).
Enjoy.
Cm 10.2 gapps?
ahw609 said:
Just installed the latest CM 10.2 UNOFFICIAL on Saturday night. Started with the official 4.1.1 JB from ASUS (10.4.2.18), unlocked, made NVFLASH recoveries, flashed TWRP 2.6.3, then flashed the CM ROM. Works great, including the power button. Don't have the keyboard dock, so can't speak to those problems. Only real issue for us was make sure you clear all the stuff before you flash the ROM (and we did it again after as well).
Enjoy.
Click to expand...
Click to collapse
Quick question....just unlocked my TP tonight, made all necessary backups, and want to flash the same CM 10.2 that you mentioned. Does the Rom come with GAPPS? I've read in the past that CM Roms don't include GAPPS. If not, how did you install/load them?
Thanks.
You are correct - the CM ROM needs the GAPPS loaded as well. Once I had the recovery module in I loaded the ROM and GAPPS together. The version I used was gapps-jb-20130813-signed.zip. Also it seems that TWRP likes to have the md5 checksums there as well. I seem to recall I got the checksum file for gapps along with the zip, but I had to generate my own for the CM ROM.
Thanks for the response. Downloaded gapps, and will give it a shot. I've got the Flatline recovery utility installed (and not TWRP). Not sure if one is better than the other, graphical presentation aside.
Lavman72 said:
Thanks for the response. Downloaded gapps, and will give it a shot. I've got the Flatline recovery utility installed (and not TWRP). Not sure if one is better than the other, graphical presentation aside.
Click to expand...
Click to collapse
Update: Installed TWRP, flashed CWM 4.3.1 CM-10.2 Cyanogenmod 10.2 Unofficial. So far so good. Haven't really noticed or experienced the "new tablet" feeling that has been mentioned just yet. I'll give it a few days to settle in.