I am totally stock, unrooted.It all started after I turned on Google Now. I was trying it out for a few days, didnt like it so I turned it off. After that, I noticed a considerable dip in battery life. After checking with better battery stats app I found that the phone would no longer go into deep sleep and the culprit was "mhl-kernel-wakelock". I have tried everything to get rid of this wakelock.
I have tried: phone reboot, battery pull, wipe data from all media player apps and usb service, deleted all my apps, reinstalled them. I tried a full data wipe/reset and wiped cache.I tried charging my phone while off. I deleted all my media off of my sd card and got a new sd card. I tried connecting to windows based pc. Nothing works, the wakelock remains.
I have never used my note 2 to connect to the tv or anything like that. Also my usb functionality no longer works. It wont talk to the computer. The phone will charge though. I have searched google extensively and there is very little information regarding this wakelock. I'm afraid it might be at the hardware level. The only other thing I can think of is buying an MHL cable to HDMI and hook it up and hopefully when I disconnect it it will shut off the MHL mode that it is stuck in. Obviously I could also root and flash a ROM with a different kernel, but I really enjoy stock and the spen features etc.
If anyone has any suggestions im wide open. Thanks
EDIT (2/1/13): I also realized that when I tried Google Now was around the same time that my house lost power during the night and the power flickered WHILE my phone was charging from the wall outlet. I initially attributed the problem to Google Now, while in actuality it makes much more sense that a power surge fried my USB port on my phone.
I know this probably isn't the answer you were hoping for but I think it might be a good idea to go ahead and, assuming you're comfortable doing this, root and unlock your device. I recommend you try out Jelly'Beans' Build 4 ROM. It has all the great features of stock with the bonus of being much lighter on your phone (smaller system ROM file) and you can set it up to look like AOSP Jelly Bean. Or if you really don't want that look and prefer TouchWiz, you can do that too.
I would do this anyway as imho, it's better to be unlocked and free for the remainder of days you own this device, rather than get an OTA and lose the possibility of unlocking ever again.
And this has a good chance to resolve your situation as you would be totally wiping the system partition and chances are thats where the issue is.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
droidstyle said:
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
Click to expand...
Click to collapse
Thanks.I already tried this several times. I tried it from the OS and from the recovery. I also lost my usb functionality so im not even sure if I can flash a new rom with odin.
I think I'm screwed. I can't even access the hidden menu from the dialer pad to attempt change the USB mode. It looks like a hardware failure, even though I haven't done anything out of the ordinary. It would explain why its stuck in MHL mode with the constant wakelock (despite multiple factory resets and data wipes). and why no USB ( tried 3 different cables) cable or any number of computers (3 different computers) cannot recognize, connect, or exchange information with it via USB. This blows.
I registered with Samsung and am trying to fill out a service request through their website, but it just says the troubleshooting guide is unavailable right now and it won't let me get past that step to actually request a service repair. FTW
Just an update in case anyone has this problem. I was able to get the battery drain under control. However, I'm not absolutely sure which setting it was, but under screen settings it was either auto-rotate or screen timeout, but I pretty much changed them all back to default, rebooted and changed them back to the way I liked them. For some reason it disengaged the MHL mode that it was stuck on. This is even after 3 factory resets and data wipes.. all it took was to switch one of those on and off.
The other problem I had was that my USB hub quit working, although it would charge, but not communicate with any computer. After a couple more days though, it stopped working altogether. It wouldn't charge my phone or do anything. I tested my charger and cord with another phone and computer it works/charges flawlessly.
After that, I took it into Verizon (crossing my fingers, since I got my Note II on release day with no insurance... so way passed the 14 day return period) and told them that I did get my phone back in late November, but I had never tried to plug it into my computer since I got it (even though I had and new about this problem for awhile) so I told them it was probably defective from the release date, I just didn't know about it. Long story short, after talking with 3 of the reps and them mindlessly googling dead-end solutions that I had already tried, the manager issued DOA on my device and shipped me a new Note II for free.
F yeah... very happy at this point. The new one I got is not a refurb, runs flawlessly. I rooted, unlocked, and running Clean ROM... all right before the OTA hit.
facing same problem with mhl wake lock and my n7100 note 2 is not detected any more when connecting to PC
Related
Soo I have a Galaxy S II I9100. And it was great until something happened. Lord knows what happened to it. But I was running the latest version of Sensation ROM (1.6) smoothly. Then yesterday all of the sudden my phone kinda stops working more or less. The screen became unresponsive at times, the screen would activate on its own and then I would not be able to use it. After taking the battery out and restarting it things were OK for about 5 minutes.
Then after trying to open any sort of applications the Voice Command app would start and I wouldn't be able to exit out of it. After mashing the home button I could get out of it and then trying to open anything would result in a black screen (status bar active at top). So I figured maybe something went wrong with the software. I happened to have an update .zip of Sensation from 1.5 to 1.6, so I reflashed. This did not really help out. Even plugging in the USB cable was a 50/50 chance, Windows would tell me that the device is seemingly defective and sometimes it would work. But then trying to open USB Mass Storage was a big headache as well.
So I let it sit the night and then this morning I used Odin to flash a stock kernel. This seemed to help out somewhat, it made the system more stable and usable for a little bit. In the meantime I went to the so called "Samsung Cell Phone Service Center" in my city which turned out to be some repair shop for iPhones (go figure). After elaborately explaining my problems they said "must be a software issue". Which it is't. Anyways in the meantime I called Samsung America for direction, after talking to 3 different CS reps they referred me to call Samsung UK because that's where the phone was manufactured.
After that I did a factory reset and that made the issues even worse.
So I'm at a cross roads. I am probably going to be putting a call into Samsung UK tomorrow to try and figure something out.
Do a FULL wipe in CWM and then flash a stock rom. See if that helps. If not, then it's a hardware problem.
I had done that and then flashed a stock ROM which removed CWM, root, and the Sensation ROM. While that seemed to have helped, it would still randomly reboot (fewer than now) and the same issues persisted but less frequently. In the SGS2 stock recovery mode I did factory reset and wiped all data and cache and the problems are back and more frequent. I did take the phone to the beach but it was in a bag wrapped in a shirt..
could that have somehow caused this issue with the hardware?
I'm thinking that this is a hardware issue.
Yes, I think it is. One thing that comes to mind, did your modem change when flashing different roms? If not try a different modem. Otherwise it's really a hardware problem.
Hi,
Recently installed Cyanogenmod on my new Galaxy S2, I couldn't get the stable version to install and after googling several threads on XDA recommended using a nightly build so I went ahead and downloaded the latest one at the time (April 19th release). All was fine, a couple of small bugs but nothing I couldn't work around. The only thing really bothering me was being unable to add a Facebook account.
Yesterday I decided to update to the latest version to see if that release had addressed the Facebook issue. It wouldn't allow me to connect to Wi-Fi, or add a Google account so I restored a backup from a couple of days before and thought nothing of it. Last night when I plugged my phone in it wouldn't charge, I thought I'd knocked the plug out of the wall and I was tired so I just went to sleep. I woke up this morning and my phone was dead and I can't do anything to get it to charge. I have checked the charger with another phone and it's working fine.
I have borrowed someone else's battery and I am able to turn on the phone, but nothing I have tried so far will get it to recognise a charger. I have tried:
resetting battery stats in CWM
resetting cache (both Dalvik and normal)
restoring to an earlier backup
reinstalling CM9 (the 19th April release that worked for me before)
finally restored my phone to stock using my initial backup, but still no joy
After all the above the problem continues. The really odd thing is that it will charge via USB from my PC, or at least it displays a charging animation - no change in battery level reading after 45 mins. It plays the USB plugged/unplugged sound on the PC and phone around every 30 seconds. So after all that my questions are:
1/ Is this a likely to be a Cyanogenmod issue or a hardware fault that coincidentally developed at the same time?
2/ Any suggestions to fix this?
Please let me know if you need any more info, thanks in advance for help.
Diberlee
[EDIT] I'm unable to get the phone to connect to the PC in download mode, I can get into Odin on the phone but it won't connect to the PC.
m8 post in cm9 thread,ull get good help.....if ur not on cm9 then flash again stock rom or c with diffrent usb cable.
After a full factory reset this issue sorted itself out. Guess the simplest solution is sometimes the best =)
Thanks for taking the time to read all the same.
diberlee said:
After a full factory reset this issue sorted itself out. Guess the simplest solution is sometimes the best =)
Thanks for taking the time to read all the same.
Click to expand...
Click to collapse
Yes and a point to bear in mind many user go down the long and winding road just to get to starting point of factory reset .
jje
Well, first of all, I should start by greeting the community, as this is my first post. So, yeah, hey everybody, been reading the forum for quite a while now, and it's been of a great help
Now, to the problem - this morning I noticed that my sgs2 had turned itself off. I didn't suspect the phone to be bricked or something as this happens from time to time when using custom roms. I tried turning it back on, it booted up, showed my kernels logo (DorimanX, not sure for the version though), so I put my phone in my pocket. After half an hour or so, I wanted to make a call, but I noticed that my sgs2 still hadn't booted up. So I tried restarting my phone using the power button, but instead of restarting it just turned off and I hadn't been able to turn it on since - it's bricked
I've heard of phones getting bricked while flashing a new rom or kernel, but never had I thought it could happen on simply booting up...
I did some research on bricked SGS2 and here's what I have done so far:
I've tried booting up in recovery/download modes, but that doesnt work.
I've tried soft/hard resetting my phone - still no luck.
I've also tried making an USB Jig, didn't work though. I'm not quite sure if my self-made jig works in the first place, as I did mess up the micro usb connector pretty bad while soldering resistors to pins. I'll try that one again with a different jack later and will keep you updated on weather it worked or not.
So, my question is, if my second try at making a USB Jig fails, is JTagging my only chance on reviving the phone? I guess that a MOBO change would probably help.
Another question is, if JTagging is my only chance, wouldn't it be easyer to just replace the bricked NAND chip? Then again, even though I have all kinds of soldering equipment accessible and also have the skills to do it, I have no idea where it's located on the mobo... Some info on that would also be much appreciated.
I havent flashed a new rom for quite a while now, last time I did it was when the latest version of Resurrection Remix was released.
My CPU wasn't overclocked - it was underclocked to 1GHz.
I was using DorimanX kernel.
Thanks in advance
jankanolv said:
Well, first of all, I should start by greeting the community, as this is my first post. So, yeah, hey everybody, been reading the forum for quite a while now, and it's been of a great help
Now, to the problem - this morning I noticed that my sgs2 had turned itself off. I didn't suspect the phone to be bricked or something as this happens from time to time when using custom roms. I tried turning it back on, it booted up, showed my kernels logo (DorimanX, not sure for the version though), so I put my phone in my pocket. After half an hour or so, I wanted to make a call, but I noticed that my sgs2 still hadn't booted up. So I tried restarting my phone using the power button, but instead of restarting it just turned off and I hadn't been able to turn it on since - it's bricked
I've heard of phones getting bricked while flashing a new rom or kernel, but never had I thought it could happen on simply booting up...
I did some research on bricked SGS2 and here's what I have done so far:
I've tried booting up in recovery/download modes, but that doesnt work.
I've tried soft/hard resetting my phone - still no luck.
I've also tried making an USB Jig, didn't work though. I'm not quite sure if my self-made jig works in the first place, as I did mess up the micro usb connector pretty bad while soldering resistors to pins. I'll try that one again with a different jack later and will keep you updated on weather it worked or not.
So, my question is, if my second try at making a USB Jig fails, is JTagging my only chance on reviving the phone? I guess that a MOBO change would probably help.
Another question is, if JTagging is my only chance, wouldn't it be easyer to just replace the bricked NAND chip? Then again, even though I have all kinds of soldering equipment accessible and also have the skills to do it, I have no idea where it's located on the mobo... Some info on that would also be much appreciated.
I havent flashed a new rom for quite a while now, last time I did it was when the latest version of Resurrection Remix was released.
My CPU wasn't overclocked - it was underclocked to 1GHz.
I was using DorimanX kernel.
Thanks in advance
Click to expand...
Click to collapse
What happens when you plug the charger. Does it charge?
pasanjay said:
What happens when you plug the charger. Does it charge?
Click to expand...
Click to collapse
I guess the battery is charging, as it heats up, but I don't see the charging animation. Also my PC won't see that a USB divice of any kind is connected.
jankanolv said:
I guess the battery is charging, as it heats up, but I don't see the charging animation. Also my PC won't see that a USB divice of any kind is connected.
Click to expand...
Click to collapse
order an usb jig and try. If it does not work send it to a repair center
Very similar happened to me a couple of days ago. Sgs2 crashed and wouldn't boot. I was also running dorimanx kernel, under clocked at 1ghz.
Originally I managed to get to download mode (not recovery mode). Kernels wouldn't flash via odin. I also tried using samsung kies to flash stock without success.
I tried the solution for nand bricked phones in this forum, however, this appears to have hard bricked the phone, since it failed to flash and now the phone does nothing (other than get hot when it is plugged in.) Nothing shows on screen. The PC does not recognise the device.
None of the threads I've read seem to offer a solution to this - any ideas? I guess I need to try a service centre, but thought I'd mention since I had same configuration as jankanolv, which of course may just be a coincidence...
birdr said:
Very similar happened to me a couple of days ago. Sgs2 crashed and wouldn't boot. I was also running dorimanx kernel, under clocked at 1ghz.
Originally I managed to get to download mode (not recovery mode). Kernels wouldn't flash via odin. I also tried using samsung kies to flash stock without success.
I tried the solution for nand bricked phones in this forum, however, this appears to have hard bricked the phone, since it failed to flash and now the phone does nothing (other than get hot when it is plugged in.) Nothing shows on screen. The PC does not recognise the device.
None of the threads I've read seem to offer a solution to this - any ideas? I guess I need to try a service centre, but thought I'd mention since I had same configuration as jankanolv, which of course may just be a coincidence...
Click to expand...
Click to collapse
Sounds familliar, lol. Anyways, did you use USB Jig to get to download mode? Or you just managed to boot it up on it's own?
I am really confused right now, because I'm pretty sure this can't be a hard brick as nothing has went wrong while flashing something on the device - it just bricked itself...
I've just get in the forum a few minutes ago only to find somoene with this symptoms, and i wasn't in here for too long and voilá...
Since yesterday my SGII, with no problems to this date, went in reboot mode for a few times.
I have no clue what is going on, but im sure something is.
i'll wait to see if theres anyone else complaining about it.
cheers
Hmm... Looks like a lot of people are getting this "brick" lately.
Maybe we all used some kind of app that bricked the phone on bootup?
Well, I tried to make another Jig, didn't work... This time though, I screwed my resitors up...
Another thing - is it really relevant to have exactly 301kOhm resistance between pins 4 and 5? As far as I know, it just kind of short circuits some pins on MOBO, which tells the phone to boot up in download mode. But I might be wrong...
Btw, sorry for the double post.
Same Problem
Hi,
I just face the same problem today,
now my S2 not working and just heat up.
this only happened after the original update done to my S2 - Android 4.1.2 - 2 days ago.
any help please
heat up....near the rear camera heat up?
Sent from the little guy
Mine gets hot near the camera. Nothing shows on screen.
In answer to jankanolv's questions:
- originally I could get to download mode via pressing home/power/volume down. (Not any more following failed flash). I've not tried a USB jig.
- my crash which started the situation occurred while I was listening to tune in radio pro app.
Well guys....near camera heating + no boot/dl/recovery = claim warranty saying that you factory reset the phone, 4.0.4 was laggy.
Sent from the little guy
was going to post a thread asking for help for what appears to be a similar problem
mine got stuck in a bootloop after pulling the battery, tried flashing new software in recovery then tried through odin but kept failing, now its bricked.
does nothing, wont go into either download or recovery mode so looks like its off to the service centre with it.
ahmadmetwally said:
Hi,
I just face the same problem today,
now my S2 not working and just heat up.
this only happened after the original update done to my S2 - Android 4.1.2 - 2 days ago.
any help please
Click to expand...
Click to collapse
Yessss! good to know I'm not the only one facing this issue.
I posted a thread about this yesterday but it is all the way down in page 3 already:
http://forum.xda-developers.com/showthread.php?t=2192996
I tapped on the "sync" toggle on the notification shade and my phone just turned itself off.
Recovery and download mode were accessible though.
Thanks for the help.
I went to Samsung to get them to fix based on the factory reset while on stock 4.04 premise, but they were having none of it, and wanted to charge me to investigate the problem. Once out of warranty period, it seems it doesn't matter if their software can brick your phone!
I found a local phone fixing service in Hong Kong which investigated, diagnosed as a motherboard failure (which I suspect my problem genuinely was given how firmware flashes were failing), and replaced + fitted for 700hkd, (approx 90usd). The guy did it in front of me within 10 mins. "Andy Telecom" in Mongkok, on +852 9237 9237 in case someone else has the same issue locally.
Well, outta warranty...that's another story. You only get 1-2 years to brick your device
Glad you had it fixed for 90 bucks, some service centers charge around 150.
Sent from the little guy
Well, I finally managed to make a working USB Jig, tried it on Galaxy Ace, worked like a charm.
What confuses me right now, is that my sgs2 has drained all the battery, even though it was switched off for about 2 days. I'm charging the device right now, and I will keep you updated on weather my jig works..
Sorry for double-posting again on an old thread, just wanted to let you guys know - I took the phone to warranty service and they changed the mobo. I didn't have to pay anything and everything is working normally. Of course all data on sd card is now lost for good, lol.
So if you hard brick your device so badly it even won't respond to usb jig and you still have your warranty active, don't bother trying to revive your phone - just take it to warranty service
I guess they couldn't see the odin download count so they cant void my warranty, he he he ]
So I'm having a strange issue. I've already checked multiple threads, here and on other forums, most notably this one: http://forums.androidcentral.com/samsung-galaxy-note-2/263592-note-2-wont-charge.html
I read every post and no one has my exact issue. So here's the story:
I smashed my screen to bits on concrete, but I have the insurance so Asurion sent me another one. I'm not certain it's refurbished but It did not come in the same packaging my original one from the VZW store did so I'd say it probably is.
I made a backup of my rom using TWRP (Clean Rom VZW Edition - JB 4.1.1)
Then I got my new phone out and checked it and it was running the vramc3 version, so i tried to root/unlock/install recovery via the NoYou exploit. This failed due to driver issues, then after that was sorted out, failed again due to a partitioning issue. ("error: partition 60 blah blah...") So I tried to odin back to stock without realizing the newest firmware had to be flashed using the alternate stock rom for unlocked bootloaders (even though mine was not unlocked) so i flashed that and it worked, i was on the original stock firmware again. however the older version of the exploit for the stock firmware did not work (i'm assuming because the bootloader wasn't actually rolled back even though the firmware was) so i downloaded the ota updates and got back to vramc3 and tried the NoYou exploit again and it worked, so i had root, recovery, and an unlocked bootloader.
Because my old phone and new phone have different serial numbers, I modified the folder name and .log file entries of the TWRP backup of the old serial number to be the new phone serial number. This worked and my phone was restored. For 3 days it charged just fine, and then last night and all throughout today, I've been testing it after noticing it doesn't charge when connected to an a/c outlet, and does not recognize a connection to my pc..... SOMETIMES. Sometimes it works right away, other times it takes 10 minutes of being plugged in before it recognizes it. and other times it'll sit for an hour and never figure it out. All without me moving it around too, i really don't see how it could be a cable connection issue. I tried my old phone on the old and new samsung official a/c charges and both work flawlessly every time, so i'm certain the cables are good.
So i did some more testing. I tried doing a factory reset with the rom still installed. Still had charging issues. I tried wiping everything except my external sd card and installing the latest version of the rom which is based on the vramc3 update (fresh install, not using my backup), still doesn't always charge...
I didn't yank the cable out, drop the phone, or mishandle it in anyway in the past 3 days, and the leads for the usb connection on the phone don't appear to be damaged. I also tried moving the cable around the connection while plugged in to see if something wasn't making contact and it didn't make a difference. I also now have 2 batteries, both hold a charge perfectly fine, and charge perfectly fin in the old phone so I don't think it's related to them either, and I have tried the new phone with both batteries. So here's the question....
Is this a firmware issue, or a usb port issue? I still have the old phone and if it's a usb port issue i'll just swap it with the old one, but i'd prefer not to take it apart until someone more qualified to speak on the matter tells me that it's the problem, haha.
And if it's a firmware issue, what the hell do i do? since I have recovery operational, i was going to try a few other roms just to see if anything changes while i'm waiting for replies.
Pleeease help, as you can probably tell by the length of this post, this is driving me insane.
TallgeeseIV said:
So I'm having a strange issue. I've already checked multiple threads, here and on other forums, most notably this one: http://forums.androidcentral.com/samsung-galaxy-note-2/263592-note-2-wont-charge.html
I read every post and no one has my exact issue. So here's the story:
I smashed my screen to bits on concrete, but I have the insurance so Asurion sent me another one. I'm not certain it's refurbished but It did not come in the same packaging my original one from the VZW store did so I'd say it probably is.
I made a backup of my rom using TWRP (Clean Rom VZW Edition - JB 4.1.1)
Then I got my new phone out and checked it and it was running the vramc3 version, so i tried to root/unlock/install recovery via the NoYou exploit. This failed due to driver issues, then after that was sorted out, failed again due to a partitioning issue. ("error: partition 60 blah blah...") So I tried to odin back to stock without realizing the newest firmware had to be flashed using the alternate stock rom for unlocked bootloaders (even though mine was not unlocked) so i flashed that and it worked, i was on the original stock firmware again. however the older version of the exploit for the stock firmware did not work (i'm assuming because the bootloader wasn't actually rolled back even though the firmware was) so i downloaded the ota updates and got back to vramc3 and tried the NoYou exploit again and it worked, so i had root, recovery, and an unlocked bootloader.
Because my old phone and new phone have different serial numbers, I modified the folder name and .log file entries of the TWRP backup of the old serial number to be the new phone serial number. This worked and my phone was restored. For 3 days it charged just fine, and then last night and all throughout today, I've been testing it after noticing it doesn't charge when connected to an a/c outlet, and does not recognize a connection to my pc..... SOMETIMES. Sometimes it works right away, other times it takes 10 minutes of being plugged in before it recognizes it. and other times it'll sit for an hour and never figure it out. All without me moving it around too, i really don't see how it could be a cable connection issue. I tried my old phone on the old and new samsung official a/c charges and both work flawlessly every time, so i'm certain the cables are good.
So i did some more testing. I tried doing a factory reset with the rom still installed. Still had charging issues. I tried wiping everything except my external sd card and installing the latest version of the rom which is based on the vramc3 update (fresh install, not using my backup), still doesn't always charge...
I didn't yank the cable out, drop the phone, or mishandle it in anyway in the past 3 days, and the leads for the usb connection on the phone don't appear to be damaged. I also tried moving the cable around the connection while plugged in to see if something wasn't making contact and it didn't make a difference. I also now have 2 batteries, both hold a charge perfectly fine, and charge perfectly fin in the old phone so I don't think it's related to them either, and I have tried the new phone with both batteries. So here's the question....
Is this a firmware issue, or a usb port issue? I still have the old phone and if it's a usb port issue i'll just swap it with the old one, but i'd prefer not to take it apart until someone more qualified to speak on the matter tells me that it's the problem, haha.
And if it's a firmware issue, what the hell do i do? since I have recovery operational, i was going to try a few other roms just to see if anything changes while i'm waiting for replies.
Pleeease help, as you can probably tell by the length of this post, this is driving me insane.
Click to expand...
Click to collapse
This topic can be closed now. I looked up a video (http://www.youtube.com/watch?v=FfvOTFssDMM) of the swapping process and saw how easy it is, so i just went ahead and tried it, and it totally worked, so now it's charging fine again. Thank you to anyone who viewed this and hopefully this can help someone in the future.
I didn't read all of that. I was at a concert last night. But here what I know about the not charging thing.
In my experience
1.all the good galaxy phones do it.
2. Its not that it wasn't charging. Its that vzw turned the power up on the modems. If your in a low service or weak signal area your phone will actually drain the batter faster then you can charge it.
So if you notice this is happening. Switch your phone into airplane mode. Or turn off mobile data and let it charge for a while.
I have read about a few case's where the usb ports where disconnected. But I think the crazy fast radio battery drain is way more common.
I don't know if its the same for other carriers but I know a note guy a s4 guy and 2 other note 2 guys we all had the same problem with it.we are all Verizon too.
The original modem flash helps a lot but the 2nd one that went out ota is stronger in weak signal areas so we all use it and turn off our data if it gets to much.
[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Q&A for [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
gpz1100 said:
I gave up trying to calibrate my compass. I have issues with it in any rom including stock TW. Some of these chips are just broken.
Click to expand...
Click to collapse
After trying many of the suggestions on this thread to fix the compass (my GPS lock is fine), I thought I might have messed up the hardware somehow. However, last night I flashed the 7/12 KT GE kernel, and the compass now correctly points in the right direction.
Germany?
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
TheSt33v said:
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
Click to expand...
Click to collapse
Well in case anyone is curious, this ROM gives me great cell service (full signal on Vodaphone.de) but no data in Munich. I tried airplane mode, disabling/enabling data roaming several times and setting the network mode to GSM preferred, but no luck. Flashing the latest release of Hyperdrive ROM allowed me to use data. Oh well.
flashing google edition on verizon s4 on nc5
I'm a noob and can't figure out if i can use safestrap to flash the dandvh google play edition rom.
verizon galaxy s4 on nc5 build, rooted with towel root and running safestrap 3.75
Viper Audio Working?
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Hi everyone, hoping you all can help me with a problem I'm having with my phone. First, some specs:
ROM: Danvdh GPE 9/30
I am one of those lucky MDK users, I got the phone in May 2013 and rooted early
I had been running the NC5 modem for a while now with no issue. The problem started after I flashed the NG6 modem (from Surge1223's thread) in TWRP. Just fyi, here are the steps I took to flash the modem. Within TWRP, I flashed the zip file, cleared Dalvik/cache, then rebooted.
Almost immediately I started getting random reboots. It rebooted twice, then seemed to settle down, so I decided to wait a day or so to see what my phone would do. Sadly enough, it started rebooting again, so I gave up last night and reflashed the NC5 modem in TWRP using the same method as before. The phone was fine after that, until this afternoon. About an hour ago, my phone froze, and rebooted, but the screen cut off at the Samsung custom padlock boot screen. It seems to be off at this point, but I can't power on the phone without pulling the battery. After pulling and replacing the battery, the phone powers on by itself, but again cuts off at the Samsung boot screen, about 3-4 seconds into the boot process. I've tried booting into TWRP and download mode, with the screen turning off and the device seemingly freezing after 3-4 seconds. I'm at a loss as to what to do at this point.
I'm at work right now, but when I get home, I will see if Odin3 can make some sort of contact with the phone. Any help in the meantime would be greatly appreciated!
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Alxoom33 said:
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Click to expand...
Click to collapse
I would love to, but I can't.
I put a video up on Youtube showing what the phone is doing right now. I don't have 10 posts yet, so I can't post links, but if you go to youtube.com then add "/watch?v=3ey5xD9LodY" at the end of the URL, you can see what the phone is doing.
It is the only thing the phone will do. I've tried doing a hard reset by holding the power button, but nothing happens. All I can do is pull the battery and start this process again. If I hold the correct button combos, I can begin to boot into TWRP or download mode, but the phone cuts off/freezes like clockwork after 3 seconds.
I tried to get Odin3 to recognize the phone, but my desktop doesn't recognize that anything is plugged in when I connect my phone to it, so Odin3 by extension doesn't see anything.
Did you install the Samsung apps on your computer? You need them for the computer to recognize your phone.
To hard boot into recovery you need to hold power button and volume up at the same time, then let go of power button once blue writing appears on upper corner of phone.
Sent from my Xoom Wifi using Tapatalk
I'm sure I have. I've been able to send adb commands to the phone in the past. Now however, my PC doesn't even see that a device has been connected to it (nothing shows up in the device manager, not even an unrecognized device).
The phone will no longer charge when I plug it into an AC adapter either (or at least the LED no longer lights up indicating it's charging).
I have tried booting into recovery several times. Each time, it will begin to boot into TWRP, the blue text, "RECOVERY BOOTING...", will display, then immediately afterwards, the screen will cut off and the phone will freeze, just like in the Youtube video I posted.
I'm afraid the thing is bricked...
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
marioluigi64 said:
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
Click to expand...
Click to collapse
Have you tried a different USB cable/transformer? It sounds like you might just have a charging issue. Not enough juice to get it started.
Allowing a battery to cool down will give it more usable power, which as it heats back up will deplete again. This sounds like your situation... Power off for a few, restart it has enough to begin booting, then depleted again.
The phone cannot run on USB alone it needs the battery to sustain it's operation.
I have tried 3 USB cables, 2 AC adapters, and 2 PCs.
When this started on Friday, my phone was hooked up to my PC at work and showing about 50% battery, but it's possible something went wrong with the battery and it's stopped delivering any significant amount of power or accepting a charge.
So it turns out it wasn't the rom or new modem that was the problem, my battery has decided to kick the bucket. I tried my roommate's battery in my phone and it booted right up as if nothing was ever wrong! Strange that an OEM battery would just die like that, but I suppose that does happen from time to time. Thanks for the help!
matycakes said:
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Click to expand...
Click to collapse
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
TheSt33v said:
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
Click to expand...
Click to collapse
Yeah, I have tried reinstalling it, and I am using the latest version of the app. The fact that you haven't had any issues is encouraging. I'll continue to troubleshoot and see what I can find.
I keep getting this (in CWM touch)
Flashing Google Play Edition
Android 4.4.4
Enjoy!
format() expects 5 args, got 4
E: Error in /storage/sdcard1/danvdh-GE-4.4.4-09-30-2014-VZW.zip
(status 7)
installation aborted
Is it just a bad DL?
EDIT: Tried a new DL, same issue. I want to get this fixed asap
Is cm11 theme manager included in this rom?
brd912 said:
Is cm11 theme manager included in this rom?
Click to expand...
Click to collapse
It is not.