Related
ROM - Energy.Leo.21916.Sense2.5.Dec.20.7z
ANDROID BUILD - NexusHD2-FRG83D_V1.8_(Froyo 2.2.1).7z
RADIO - 2.10.50.26
I have a problem, my phone is working absolutly beautiful exept for one BIG problem, when i connect my phone to de AC the screen gets disturb, gets all twisty and just like loosing signal in an old Tv; scrambled, and it zooms in and you cant do nothing with it; i have to soft reset to WM; THIS ONLY HAPPENS IN ANDROID;
IT STARTS WHEN I CONNECT MY PHONE TO CHARGE; WHEN I DISCONNECT IT THE PROBLEM DOES NOT GO IMMEDIATELY; i will like to fix this problem with this build because i really like it; if you havent tried it you should !
Try a different charger. You might not have a constant charge which freaks out yourphone.
Sent from my SPH-D700 using XDA App
zenvita said:
Try a different charger. You might not have a constant charge which freaks out yourphone.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
alright; im booting android now to try another charger;
The charger is not causing the problem. The problem is only with android. I have notice that the phone charges and works via USB charging.
at least recommend me a good android build to try out; please.
tried with another android build ( MDJ Revolution HD) and the problem still persist; another observation is that the problem occurs with USB charging too;but only from my PC; with my MAC is charging and works good; EDIT: ISNT WORKING WITH MAC NEITHER! im going to change ROM and see what happens;
----------
MDJ Revolution HD lets you connect you PS3 by wifi Tether with stock ROM the PS3 didnt recognize the network; thats cool
well; i flashed another ROM (Energy.Leo.28244.Titanium.Dec.21) and still having the problem; if it makes it easier i can make a video to show you guys the problem; and i would like to know whats the best ROM for running Android?
-----------------
Another observation is that it does it when its no charging but not as bad; when not charging i just tuch and scroll the menus and that prevents the scrambling and zooming of the screen; Another observation is that when i plugged in fast to AC it gets scrambled; when i insert the plug slowly something called USB debugging turns on and it doent get scrambled rapidly; but in the morning it was all scrambled again.
Another observation; i captured a photo of the screen using an app from the phone; and the photos werent scrambled; im beggining to think that is a hardware problem but i dont know because it only happens in Android maybe a some resolution problem that makes the phone react like this?
Another observation is that it happens too without being connected but very little scrambling;
im going to hard reset my phone and format my SD card;
Hard reset; New ROM; Full formatting the SD card; and the problem still persist. Now it does it when the phone goes to sleep; charging or not; it does it anyway now.
i have updated the Radio to 2.12.50 and still have the problem, i know that theres no interaction with the radio and the screen; but i want to try everything.
come on ! theres a lot of geniuses here ! somebody most know whats wrong;
another observation; it a lot better with the brightness set to 100%. but i cant run with this because im always using my phone; so my battery will drain in less than 5 hours. it get scrambled when i connect it to any source of electricity;
Now runnign NAND and the problem still persist.
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
mohammedmazher said:
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
Click to expand...
Click to collapse
I am facing this only when battery is bellow 15%. If this is the case then just charge it before it goes to 15%.
If that's not the case then you can try installl MAGLDR v1.3
Do you have this issue in Froyo or Gingerbread ROMs? or in both? What version of CWM are you using?
I have the same problem on MIUI since after approximately 1.3.18 (cutover from Froyo to Gingerbread). Also have this problem on CME DHD2 Compact.
It is also an issue if someone tries to call me.
Sometimes, if I try waking the phone from sleep (power button) and it hits the black screen, and I wait long enough, it will wake. But again, the only real fix I know is pulling the battery.
I am running MAGLDR 1.13
Also, another fix that works sometimes is plugging in the phone into a power source e.g. laptop USB port
It's something about light sensor, when you put your screen into a strong light it would be turn "unblack" again. I don't know how to fix it, is this a problem with this hardware because it's broken or my version of LEO doesn't support NAND full functionaly.
Begging for answer!
i know about my poor english
I have this problem too.. running latest Hyperdroid rom by pongster (magdlr version) and it's driving me crazy. Sometimes phone wakes up normally after a call like it shoud, sometimes is stuck with black screen for few minutes, hours even (although i can't wait that long so i pull out battery)..
Back on WinMo everything worked normally, so it's not an hardware issue with proximity/light/whatever sensors
Is there any fix out yet? I googled and searched this forum a lot and haven't found nothing much helpful, ony a couple of threads with bunch of people with same problem like me. An option for disableing those sensors would be just as good, i've tried few apps for keeping the screen awake and none of them actually worked..
Any help is appreciated.. thanks in advance.
Bump!
Anyone? :/
I have the same issue - running Gingerbread, MAGLDR 1.13
Very annoying cause everything else works super.
Temporary solution i use is to use headset / handsfree. Then there is no problem.
So experts on XDA, we are begging for a fix for this!
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
I have had the same thing happen to me but only around 2 or 3 times in a about 3 months of usage. Had it on both CM7 and MIUI Gingerbread ROMs regardless of battery percentage.
MAGLDR 1.13
Some users experience this using SetCPU
if you have a profile for screenoff and it's set to the lowest frequency, try to set the frequency to something above 500 MHz.
If you have smartass set as governor, then even setting the frequency to it's highest (without OC) during screenoff wouldn't change anything in battery performance, but the device will wake up faster.
Your setup works for me as well - until we`ll see a fix for it this will do
Quiethinker said:
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
Click to expand...
Click to collapse
Yup, this worked for my setup to - thanks!
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
xanthrax said:
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
Click to expand...
Click to collapse
(install then enable each one):
Click to expand...
Click to collapse
Incearca Sanity app, cauta pe Market, mie aceste doua nu mo ajutat
with me is so but only if I navigation (Navigon) and to have someone call me and then left the screen black and I can not make
try to change the kernel. that works for me
hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
papaganz said:
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
Click to expand...
Click to collapse
I also try with WinMobile and the problem was still there ...
I think the sensor is broken ....
I will bring my phone to service ... and when i take it back I will tell you whether it is repaired
Solution
I had the same problem with Android roms on my HD2. I saw in an other thread a member (z-o-r-r-o-, thanks btw) wrote "just clean dust on the screen, where sensor is situated". This looked like a joke to me, but it's not. On a review of the phone I found the place of the proximity sensor. This is on the top of your screen next to the speaker, on the left if you look at the screen. I just took off the protection layer of the screen and cleand the sensor and the problem was solved. So I cut of a bit from the protection layer so that the sensors arn't touched by anything.
I think the problem is that this sensor is much more sensitive with android roms.
Hope this works for you to.
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
chota_shivaji said:
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
Click to expand...
Click to collapse
Hi Moderators,
Apologies for posting this thread in this sub-forum. I forgot that question threads should be in Q&A section. Having said that, if its not too much to ask, can you please move this thread to Nexus One's Q&A sub-forum?
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware...
Sent from my GT-S5830 using XDA Premium App
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
shreyasvb said:
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware..
Sent from my GT-S5830 using XDA Premium App
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
b1337 said:
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
chota_shivaji said:
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
Click to expand...
Click to collapse
I tested my Nexus one for past approx ~36 hours. In this time, I was hit by the issue mentioned in this thread twice.
Out of those 2, 1 was probably caused due to a soft reboot as I was able to get some output from cat /proc/last_kmsg but could not save it for sharing. The other one did not had last_kmsg entry so I am not sure what caused the phone to go haywire. The battery charge was ~30% when I booted it next time.
Now, I am on CM 7.x stable + 5.08 radio + Amon_Ra' 2.0.0 recovery and I explicitly have wiped the cache and Dalvik-cache via recovery. Since then, phone seems to be working OK. I will keep this thread updated if I am again able to get into the "Not able to power-on with power button" issue.
Hey czechop,
this post regards to your thread http://forum.xda-developers.com/showthread.php?t=2517735 but since I'm a new XDA user I cannot post to it
Your CM11 for Milestone 2 is really really awesome KitKat performs really great on MS2. Thank you very much!
Since I've installed the ROM two days ago I had only one issue: when I turn Bluetooth on, the WiFi connection is gone for a few seconds. After 5-10 seconds the WiFi connection is established again.
Another issue I've had with all custom ROMs so far (tezet's CM10, your CM10.2 and now your CM11) is the displayed battery level. An example: this morning my MS2 was fully charged. After about 4-5 hours the displayed battery level was 1%. After that the MS2 was normally usable for another 5 hours. After about 10 hours the MS2 automatically shutted down. There is a screenshot of the battery usage attached, shortly before the shutdown (in German, sorry...).
Does anyone of you have the same issue? Is there anything I can do to get a more reliable battery status?
One month ago I bought a new original battery for the MS2, but the behavior is still the same.
By the way: what CPU governor are you guys are using? Which one gives the best compromise between performance and battery life?
> http://forum.xda-developers.com/showthread.php?t=2517735&page=31
I can confirm the problems with Bluetooth headset, too. It's impossible to use at the moment. Sounds like a drunken damaged robot or something
czechop, please beat this annoying robot
A953User said:
Hey czechop,
this post regards to your thread http://forum.xda-developers.com/showthread.php?t=2517735 but since I'm a new XDA user I cannot post to it
Your CM11 for Milestone 2 is really really awesome KitKat performs really great on MS2. Thank you very much!
Since I've installed the ROM two days ago I had only one issue: when I turn Bluetooth on, the WiFi connection is gone for a few seconds. After 5-10 seconds the WiFi connection is established again.
Another issue I've had with all custom ROMs so far (tezet's CM10, your CM10.2 and now your CM11) is the displayed battery level. An example: this morning my MS2 was fully charged. After about 4-5 hours the displayed battery level was 1%. After that the MS2 was normally usable for another 5 hours. After about 10 hours the MS2 automatically shutted down. There is a screenshot of the battery usage attached, shortly before the shutdown (in German, sorry...).
Does anyone of you have the same issue? Is there anything I can do to get a more reliable battery status?
One month ago I bought a new original battery for the MS2, but the behavior is still the same.
By the way: what CPU governor are you guys are using? Which one gives the best compromise between performance and battery life?
Click to expand...
Click to collapse
The problem with the battery depends on the battery. That hasn't anything to do with the Android Version you have installed. If you are able to understand german you can look in a really good MS2 Thread at the "Android-Hilfe" Forum. There is a big explanation about the difficulties finding a really original battery for the MS2.
Your battery is probably a fake :-/
Hey neolovich,
I'm rather sure it's the original battery:
- price: 38 EUR on handyakkus.de
- original packaging, unopened
I have recognized the wide choice of fake batterys during the search for a reliable shop.
But additionally I will check the "Android-Hilfe" forum as soon as I have the time to spare
As I already mentioned it was the same behavior with the original battery (original delivered with the MS2) and the new one: the displayed battery level went down to 1% after 4-5 hours. After that the MS2 was running normally for another 4-5 hours before it was shutting down. So the run-time of the battery was approx. 10 hours. Just the displayed battery level was totally wrong.
Two weeks ago I stumbled across the app "BetterBatteryStats". This app displays useful information like: deep sleep time, awake time, screen on time, ...
Strange to say after installing this app the displayed battery level was okay again... Also the run-time is a little bit better (currently: 40% left after 9 hours). Sounds strange, I know, but after installing this app the displayed battery level is reliable again. I don't unterstand why...
Had same issue with stock battery, see here
http://forum.xda-developers.com/showthread.php?t=1846002
I was running Tezet CM7 at the time. Since then (I may have had to block IO ports one more time, but I don't remember for sure), the battery is working normally ever since.
---------- Post added at 09:08 AM ---------- Previous post was at 09:00 AM ----------
Correction: It was Endless CM7.2. Can not edit post, since the edit form won't load for me. Well, I guess one post closer to commenting in the ROM release thread
Wow, interesting approach :cyclops: I also did some searching about this issue, but unfortunaely I haven't found your thread.
Before I coincidentally found "BetterBatteryStats" I was so cheesed of this problem so I completely disabled the display of the battery charge level as well as battery LED
Great, one more possibility to solve this problem if it will occur again.
Oh, same problem as me: not enough posts to post in the ROM release thread
Do you also use czechops CM11?
Regarding to the latest version "24.02.2014":
Bluetooth headset/handsfree connection is working now, many thanks for this! I also noticed the very low volume, I had to increase the volume of my car's handsfree nearly to the max. Also my counterpart told me, he was hearing his own voice while speaking.
I also noticed some sproadic reboots the last few days. But never reproducable, each one after totally different action (using camera, after app installation, during standby...).
http://forum.xda-developers.com/showpost.php?p=50628909&postcount=370
Also had the locking sound a couple of times like patrol-cz. Last time half an-hour ago: send device to standby, after ca. 10 minutes the locking sound appears.
Did it support the chinese version of milestone 2 (me722) ?
Is its bug importent ?
Can I use art mode ?
telephony problem
anybody have telephony problem on the lastest CM11 by czechop
What exactly do you mean with "Telephony problem"?
I have some random reboots from time to time. Sometimes I've got the message in the attached screenshot after reboot (in German; sloppy translated: "The device was restarted due to a problem with the telephone modem."). Don't know the reason for this. I hope czechop recognized this thread and have an idea
Last week I've had a lot of random reboots. This week it's okay so far :good:
@violente: sorry, I don't know...
Unfortunately I have a lot of reboots with the current version "12.03.2014". Sometimes with the telephony layer message, sometimes not.
Is there any way to find out the reason for that? Maybe an error log or something?
Does it depend on the baseband like patrol-cz in the ROM thread mentioned?
Since I switched the baseband to "2.5.1" (Europe > Central Europe) two weeks ago the telephony layer error seems to be solved for me :good:
(my location is south-west Germany)
Nevertheless I still have sporadic reboots
Is there any error log or something to find out the reason?
Yesterday I've tried to stream music via Bluetooth A2DP to my Beewi BBR100. The playback was extremely stuttering/impossible to use. Anyone experience the same problem?
LYAJUN said:
anybody have telephony problem on the lastest CM11 by czechop
Click to expand...
Click to collapse
Hi! I too have telophony problems. I have no phone or packet data reception. Does anyone run without gapps? I started without, then minimal, then browser sync, then calendar sync. But still, can't make or recieve calls or packet data. My service provider can't find any problems at there end either
Laggy video playback
Hi All,
I've installed the latest ROM two days ago and it seems to be fine except the video playback. It's very laggy while I was trying to play back 720p videos (recorded with stock or current ROM). I've installed MX Player and if I enable software decoding the video playback not lagging anymore (hardware decoding not working for me), but in this case I have sound delaying problem.
It seems to me that hardware acceleration (GPU) is not enabled for video playback.
Anyone else experienced the same problem?
Camera focus problem
I've found another problem but I don't know if it's related to the rom or not.
The camera auto focus is not working for me, I cannot take sharp pictures. It tries to focus but it can't.
Anyone else experienced the same problem?
CM11 on Milestone 2 (a953)
Hi,
I installed CM11 as Czechop descirbed.
First CM10 (was fine), then CM10.2 (keyboard errors, but done)
Right now Milestone is booting: blue CM log and and an arrow is circle around, but nothing happens.
Unfortunately i can not enter into the recovery menu. I tried Power and Vol down, Power and X buttons also, no luck.
Any idea?
Bocskay said:
Hi,
I installed CM11 as Czechop descirbed.
First CM10 (was fine), then CM10.2 (keyboard errors, but done)
Right now Milestone is booting: blue CM log and and an arrow is circle around, but nothing happens.
Unfortunately i can not enter into the recovery menu. I tried Power and Vol down, Power and X buttons also, no luck.
Any idea?
Click to expand...
Click to collapse
To access recovery, you need to press VolumeDown when you see blue led after turning on the phone.
Also, have you formatted data as ext4?
A953
Hi,
So now i can go into the bootrecovery menu (Android system recovery<3e>), but everytime when i select a packaeg to install, during verification it fails:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Is there any tip or trick?
Very strange the phone boots up only when usb cable is connected to a PC (MotDevManager installed). All i can do is torn on/off USMB Mass storage. No home screen , only task bar. I can not run any app.
Pease help!
:crying:
Thx
---UFO--- said:
To access recovery, you need to press VolumeDown when you see blue led after turning on the phone.
Also, have you formatted data as ext4?
Click to expand...
Click to collapse
Thx for the help, vol down on blue led was working, But still not booting up without pc cable connected.
So, formatted as ext4, but still not booting uo , only CM logo and arrow cricle.
When connceting PC, boots up, but no apps, no icons, no home screen, just black, empty screen, only taskbar.
Tried to rcover, then install new package with TWRP, but no luck.
Finally i a had red Motorola logo and nothing else (no leds, no waves)
Vol Up+Down and power at the same time bring black screen with Ready to program Connction as USB.
With RSDlite 6.1.6 i was able to upload stock fw.
Viola!
Boots up with stock fw (Android 2.3.4), and everything looks fine.
Now roll again CM10, CM10.2 then CM11
I don't know in what point exactly this started to happen, but when the screen shown when charging the phone while turned off is not working. Pressing the power button just gives me a screen that says:
Charging!
??/100​
I already tried several roms, including the stock and non rooted ones, and the only rom that shows me the battery percentage is MIUI. Maybe it has something to do with the Android version (6.0).
Anyone who has got the same problem? Any fix for this?
Thanks in advance,
macrolex said:
I don't know in what point exactly this started to happen, but when the screen shown when charging the phone while turned off is not working. Pressing the power button just gives me a screen that says:
Charging!
??/100
I already tried several roms, including the stock and non rooted ones, and the only rom that shows me the battery percentage is MIUI. Maybe it has something to do with the Android version (6.0).
Anyone who has got the same problem? Any fix for this?
Thanks in advance,
Click to expand...
Click to collapse
Did you try it on OOS 3.5.8?