I installed faux123's kernel for Gingerbread this morning (I'm running kennethpenn's beta #4.5). Since then, wake on volume only works within the first few seconds after turning off the screen. Because I used WidgetLocker's Easy Wake before, I never did the android.policy.jar tweak. Since it was no longer working, I tried the tweak, but it changed nothing.
Also, I had to reboot a few times to get the new Swype working, and about every other time, my widgets would be lost in both LauncherPro and WidgetLocker.
I'm posting this here instead of in the kernel thread (http://forum.xda-developers.com/showthread.php?t=1156040) because I don't have enough posts yet.
Solution to your problem - Intro to mine
I noticed similar issues with my phone and found it to be an issue with pudding (the unlockable bootloader that u flashed to your phone). This problem was pretty much corrected when I used an older version of pudding available here:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Sorry, couldn't put the actual address because I am a new member
Click the "Unlock SBF File" link. Flash it with RSD lite to replace the old pudding.
It worked for me pretty much except that ADB started to have issues. Any time that I try to debug an APP i made through ADB, i get a connection refused error.
Sounds like this kernel needs some refinement. Anyways, hope this helps.
Cheers!
BE CAREFUL WHEN USING RSD LITE. YOU HAVE THE POTENTIAL TO REALLY MESS UP YOUR PHONE.
Related
It is ok yesterday.
And I installed about 10 apps today and found that it will reboot if I lock the phone (the screen goes dark).
I don't remember the name of those apps.
So, how can I find out the problem of the certain app?
Must I uninstall all the apps to find out the problem?
THX!
If u go to the market and download a app called (instant uninstaller) it lets u choose to show the apps by date installed
Sent from my ADR6400L using XDA Premium App
thx！ let me try it.
So did this fix your issue? I am having the exact same problem.
I'm rooted (using ADB method), running Das BAMF 2.1 with Imoseyon's 2.54test4 kernel .
I can reproduce the a reboot everytime by doing this:
1. With the phone unplugged from the charger, press the lock button so the screen goes off. Once the screen goes off, in about 10 seconds it will reboot everytime.
2. Or, if I leave it set and the screen goes off by itself, it will reboot in about 10 seconds (after the screen goes off) everytime.
If I leave it on the charger, or never let the screen go off, it has never rebooted on me. I got this phone 2 days ago and have been battling it ever since.
UPDATE:
I have eliminated the following as a potential issue.
1. I wiped everything and flashed a new ROM, Kernal, and Radio, and still the exact same results.
2. I tried a new battery, and still the same results.
3. Tried two other kernals with each of the two ROMS, and still the same results.
Out of ideas at the moment.
Thinking of trying to flash back to stock so I can see if it still does it then.... Lost.
Solved my problem for now. Here is what I did.
1. Flashed back to these radios
CDMA: 1.13.605.7
LTE: 1.12.605.6
2. Flashed back to Froyo based ROM, Das BAMF 1.8.
Of course, I wiped everything before doing so. I've been up for about an hour now with my phone resting comfortably with no reboots at all.
Will try again in a few days to flash back to a gingerbread based rom, as I would really like to have Netflix.
If anyone has a gingerbread ROM and radio combo that they have working well together please let me know. You might also shout out which kernal you are using too.
UPDATE:
So I have obviously done some more troubleshooting on this, and I may have something to make sense of.
Since I flashed the GB MR2 radio and ThunderstickGB rom using the kernal provided with it. After bootup, I again had the reboot issues everytime the screen timed out or was locked. Just like before, It would reboot everytime unless the screen was kept on or plugged in to a charger.
I flashed back to the original Froyo radio just to see if that would make a change. Of course, I had no signal, but it would at least tell me if it were the newer MR2 or MR2.5 radios giving me fits. Even with the original radio, it still gave me the same reboots on screen timeout or locked.
So, I started over and this is what finally worked:
Flashed MR2 radio and ThunderstickGB rom again. This time, I flashed the stock GB kernal, instead of using a modified one. Bingo.... no reboots at all.
My feeling is that for some reason, some of the Kernals are undervolting the unit to a point that it shuts off or reboots. I am completely technically illiterate when it comes to the inner workings of Kernals and such, but the one common demoninator between my working Froyo and GB roms was that there was no Governor or Speed Tweak controlling the processor other than what comes in stock form.
Oh and by the way, thanks for eveyone's help with this.... I couldn't have done it without you.
Hey Guys,
Just flashed to 2.3.4 and the pie crust rom. Thanks to all your amazing guides, everything went perfectly.
The only problem is, (besides titanium backup not backing up any of my sms's) that whenever I TRY to select Motorola Phone Portal, it works for a second, then switches back to USB Mass Storage.
Is this a known bug? I would have posted in the Pie Crust rom thread, but I cant since I just created this account.
Thanks for all your help guys!
I am having the same problem with Alien 4 and Crust as well. Putting on Fruitcakes stock stock 2.3.4 to see if that fixes the problem. I like having access to my phone through browser but it's not working on most of the ROMs.
After having no luck with either of the roms, I installed R9 Rom. After installation I gave it around 10 minutes after skipping blur setup to settle down. Once all done, I set mode to Phone Portal and within 2 seconds it was back to USB Storage.
I waited for a minute and click on Phone Portal again and it worked.
It's been on Phone Portal for almost 5 minutes now.
Can anyone else try this on other roms.
1. Click on Motorola Phone Portal (First Option when you connect USB)
2. Try to access through browser and see if it changes to USB mode.
3. Try clicking first option again in a minute and see if it stays in that mode?
Thank you
P.S. I don't want to offend anyone or hate on any ROMs but I should have tested other ROMs thoroughly :facepalm: Can someone please verify if this method works on other ROMs?
Alien v4
No problems with Motorola Phone Portal here though I don't usually use it much.
Shortly after Team DRH's last update for their ICS 1.2 I installed it no problem and it ran for a few weeks. Then I left the tablet alone for a week or so and when I turn it on now the wifi is not working, it just says "turning on wifi" but never actually does. I've followed the reflash instructions here: http://forum.xda-developers.com/showpost.php?p=23147934&postcount=4 and I can re-install ICS endlessly. But even after following those instructions, and even after RayWaldos NVFlash for dummies, it still always says "turning on wifi" but doesn't.
When, during the above flashing, I let the stock tapntap boot, wifi works no problem. It's only when i install a ROM that it stops working. I even tried installing Gtabcombover and it gave me the same "turning on wifi" problem.
I did try searrching the forums, but I see no mention of this anywhere.
Thanks.
If I can be more to the point: does anyone know of a way to completely reflash stock everything? I thought I was doing that, but obviously not enough.
Or do I need to crack open my case and push that Dirty Little reset button?
Slightly Askew said:
If I can be more to the point: does anyone know of a way to completely reflash stock everything? I thought I was doing that, but obviously not enough.
Or do I need to crack open my case and push that Dirty Little reset button?
Click to expand...
Click to collapse
I was able to use the DHR NUFLASH.. It worked real well for me.. download the right file (bootloader 1.1 or 1.2) to your pc, for your g-tab.hook up your USB cable Turn on your tab wile holding your volume (-) key , the logo will come on and then go black. Then go to the nuflash- win file, you downloaded to your pc and run.. The instructions are on the DHR site are vary good I read them a few times before I tried. Its worked great for me.. I'm a noob. Lets just say its just about makes the gtab un-brickable...
Sent from my G Harmony v2.8 using xda app-developers app
graftonrod said:
I was able to use the DHR NUFLASH. . .
Click to expand...
Click to collapse
Well the good news is that after reading your post I went straight to the DRH website and lo and behold they had just posted Beta 1.3 that morning. I redownloaded their Full Stock CWM 5504 NVFLASh file even though I already had it, and the Beta 1.3.
I flashed the stock file and let it boot just like they said but the setup process began a FC loop and would not complete. I simply rebooted and the setup was able to complete. The I installed the Beta 1.3 with no Gapps and it worked like a charm. Wifi was working and everything, except there was no Market. So I did a wipe/FR and installed again this time with Gapps and everything is back, wifi, market, all good. And I have noticed that it all seems to work a ton faster and smoother.
Let me first explain what I did.
1. From stock rom, after doing the root (TWRP recovery), i flashed JellyDaemon v 2.0 listed here http://forum.xda-developers.com/showthread.php?t=2307247 . Used CPU control inbuilt in app to set CPU governer to OnDemand
Fantastic ROM with no problems.
2. After the news of 4.2.1 release came, I started looking for 4.2.1 based roms. I went with StarkHD listed here http://forum.xda-developers.com/showthread.php?t=2212028 . I think my download went wrong and file wasn't downloaded cleanly. I flashed with it. Flash went on successful. Phone got hung at the boot animation. Tried multiple methods to start the ROM. No success. Phone not booting into any ROM.
3. I had stock rom v 0.16 available with so flashed it with SP flash tools. Flash was successful.
4. Downloaded Naturewiz HD listed here http://forum.xda-developers.com/showthread.php?t=2319288 . ROM flashed and phone booted. Restored the apps. Used battery calibration app to calibrate the battery. After this, noticed that every time phone went into standby, it won't wake after that and needed reboot. I thought it to be bug in the rom.
5. Downloaded 4.2.1 based rom listed here http://forum.xda-developers.com/showthread.php?t=2306461 and flashed it. Flash was successful followed by successful TP upgrade. Installed everything. Same problem noticed. Phone won't wake from standby. Needed to be rebooted.
6. I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Any solutions to this? There are no other problems I am facing.
"I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Click to expand...
Click to collapse
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Sent from my CaNvAs HD using xda-developer app.
adizrox said:
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Click to expand...
Click to collapse
Thanks for your reply. I will try your suggestion and see. In the meanwhile, I removed TWRP and flashed CWM 6.0.3.0 and fixed permissions with that. The phone did not reboot on its own for close to eight hours (which it was doing earlier at random). I thought problem was solved. But trying to go through contacts list (DW Contacts), phone rebooted on its own.
Can anyone tell me a method where you do a clean install and bring the phone to a factory fresh state. Something similar to tutorial by team overcome for galaxy tab. Frankly, that seems to be the only possible solution: Get the phone in a completely formatted factory fresh state and then install any other ROM.
SP flash tools
To get your phone to a default factory status. you have to flash the original rom using SP tools. Links to both can be found in the forum.
Finally, tired after numerous attempts, decided to take it to the service center. Asked them to update to 4.2.1. They had the same problem. After flashing, the phone just wouldn't boot past the boot animation.
They kept trying. After two hours, they gave it back to me saying there is a hardware problem which requires a main board change.
I had suspected all along and now I know I was right. I asked them about the time line. The answer I got was even more shocking. Minimum two weeks, but there are lots of hand sets awaiting main board since more than a month
I guess I am better off with current status (Ver .20 installed and rooted).
Seriously, this episode has seriously dented my faith in micromax as a brand. One can buy there phones and be happy with whatever has been packaged. Trying anything new can be dangerous.
Just got a a used Droid X2 and accidentally updated to 2.3.5/1.3.418 now trying to follow these instructions and root it:
[How To] Root DX2 2.3.5/1.3.418 magic md5 method
I installed MotorolaDeviceManager_2.3.9.exe from here:
MY MOTO CARE
Hooked-up the phone which was factory reset, set 'USB debugging', and ran the batch files trying USB connection in both 'PC Mode' & 'Charge Only' and keep getting these errors:
Code:
error: more than one device and emulator
error: device offline
The batch stops at '---Reboot Bootloader---' and nothing happens. I've tried following the instructions to hold volume up while turning off and on, but the phone just hangs at 'Starting RSD protocol support' and the batch stops at '< waiting for device >'.
I've even tried uninstalling and re-installing the Motorola drivers and going through everything again, but no change. Any help?
Thanks!
I just downgraded to Android version 2.3.4/1.3.380 with RSDLite and tried the VooDoo method, but Pete's Motorola Root Tools failed.
The Root Tools program was able to detect the device initially, but none of the commands seemed to have any effect and when it tried to reboot the device nothing happened; it goes through the rest of the steps and then indicates that it failed.
I'm running Windows 7 and even tried a system restore then re-installing the drivers, but no change. When I check the device manager there are no unknown devices or anything like that.
Got it!
Finally tracked down the solution to the error 'more than one device and emulator'
Had to use adb.exe that came in Pete's Root Tools to run the command 'kill-server' in the command window:
Code:
adb.exe kill-server
When I checked
Code:
adb.exe devices
initially there were multiple devices listed, somehow the phone was not disengaging when I was plugging and unplugging it. Running kill-server reset the list so that running the root application could finally identify the phone correctly.
If anybody knows why this was happening and how to prevent it please let me know.
Now I can finally go on to flashing a ROM!
jhsu888 said:
Got it!
Finally tracked down the solution to the error 'more than one device and emulator'
Had to use adb.exe that came in Pete's Root Tools to run the command 'kill-server' in the command window:
Code:
adb.exe kill-server
When I checked
Code:
adb.exe devices
initially there were multiple devices listed, somehow the phone was not disengaging when I was plugging and unplugging it. Running kill-server reset the list so that running the root application could finally identify the phone correctly.
If anybody knows why this was happening and how to prevent it please let me know.
Now I can finally go on to flashing a ROM!
Click to expand...
Click to collapse
Let me know what rom you stick with, I just ordered one 4 days ago and should be getting it today. I'm torn between eclipse(on gingerbread) and Cyanogenmod 10(jelly bean) (i want to be able to call, text and use data reliably, and I like being on the newest version of stuff)
DQEight said:
Let me know what rom you stick with, I just ordered one 4 days ago and should be getting it today. I'm torn between eclipse(on gingerbread) and Cyanogenmod 10(jelly bean) (i want to be able to call, text and use data reliably, and I like being on the newest version of stuff)
Click to expand...
Click to collapse
I actually haven't bothered trying CM10, after I got everything running smooth with Eclipse I just left it at that. I can say that I haven't run into a single issue with Eclipse and I've been using it pretty heavily installing/uninstalling apps and trying all the components including the camera, wifi, led lights, sms and calling - all working solid.
A little off topic, but I also installed a home launcher app and after trying GO Launcher and Holo, I found ADW to have the easiest way for me to manage all the apps in groups and still be highly customizable. GO launcher I found buggy and Holo looked great out of the box, but felt a little limited.
I would also suggest getting the Widget Locker app, it's paid, but worth it to be able to customize the lock screen and get to things like the camera, flashlight, dialer etc quickly from the lock screen. I tried a few of the free ones for that and they were buggy or gave me a flash of the old lock screen, Widget Locker works pretty seamlessly.
Enjoy it!
I am a first owner DX2 owner running CM7. Most of the original owners have all moved on and upgraded. I am waiting until my contract ends to ditch VZW and go to prepaid to save money. But I digress.
You have to be on 2.3.4 to install CM7. This is by far my favorite rom, second to eclipse. It is faster and smoother than eclipse. Eclipse starts to slow down over time.
CM10 also has to be installed from 2.3.4. It's fun to play around with, but at the end of day it is too glitchy and not functionable enough due to the bootloader being locked. So in my opinion, it's best to stick with the gb roms.
Sent from my MB870 using Tapatalk 2
Juice3250 said:
I am a first owner DX2 owner running CM7. Most of the original owners have all moved on and upgraded. I am waiting until my contract ends to ditch VZW and go to prepaid to save money. But I digress.
You have to be on 2.3.4 to install CM7. This is by far my favorite rom, second to eclipse. It is faster and smoother than eclipse. Eclipse starts to slow down over time.
CM10 also has to be installed from 2.3.4. It's fun to play around with, but at the end of day it is too glitchy and not functionable enough due to the bootloader being locked. So in my opinion, it's best to stick with the gb roms.
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
Cm9 wasn't too bad. Its quite a bit more stable then cm10 and now that time has past more apps actually work on it. Give it a try and see how you like it. I couldn't stand the delayed text issue that appears on cm7
Sent from my SCH-I535 using xda premium