Related
Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.
Unrelashade said:
Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.
Click to expand...
Click to collapse
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2
mattlowry said:
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own
demkantor said:
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own
Click to expand...
Click to collapse
Thanks guys! Fastboot says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
Click to expand...
Click to collapse
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha
Unrelashade said:
Thanks guys! Fastboot says:
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha
Click to expand...
Click to collapse
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2
Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium
You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?
mattlowry said:
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
demkantor said:
Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
WeekendsR2Short said:
You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?
Click to expand...
Click to collapse
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.44.1107
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
Jun 27 2011, 14:08:29
Click to expand...
Click to collapse
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha
If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Sent from my HTC MyTouch 4G Slide using xda premium
Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2
A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Sent from my myTouch_4G_Slide using xda app-developers app
Unrelashade said:
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha
Click to expand...
Click to collapse
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.
WeekendsR2Short said:
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.
Click to expand...
Click to collapse
Thanks for the info.
demkantor said:
If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Click to expand...
Click to collapse
Ok, right now I'll not try flashing bootloader since everything seems to be normal.
What I did to get last_kmsg:
Code:
Open terminal app
Enter "su" to get root privileges
Enter "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" to save current log.
Close terminal app.
I attached the last_kmsg.txt. What do I do with it now? I don't have knowledge to understand it.
mattlowry said:
Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
I can't remember using a ROM that never crashed, but I'll try a stock ROM if nothing else works. However an old kernel of scverhagens CM 9.1 seems to work flawlessly if battery is not about < 15%. The newest r10 kernel on the other hand always immediately crashes when the phone is not charging. When charging I haven't experienced a crash yet. That's strange and makes me suspect my battery is the problem.
mojoffdawal said:
A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Click to expand...
Click to collapse
Thanks! I guess I'll try an Anker since I have seen so much users here using it.
virtuous rom works great! when i had mine, i was running 4.0.3 overclocked to 1.5ghz. super stable too! daily driver for sure.
Sent from my SGH-T999 using xda app-developers app
Thanks, but the problem is I'm pretty sure that something's wrong with my phone...
I'll try virtuous ROM and a new battery though.
hope it works
Sent from my SGH-T999 using Tapatalk 2
So, I'm reviving this thread, because I stopped writing only because my phone was broken. Now it's back and I'm facing this problem again.
I've tried a lot of the 4.x ROMs here from the forums, but all of them rebooted or shut down after 5 - 10 minutes after flashing. I also tried some without flashing gapps even, but still the same symptoms. Also tested it with my new battery, nothing changed. Even the scverhagen CM 9.1 ROM rebootet shortly after flashing that worked longer previously (guess that was just by chance)
Now I've tried the original image and it works! Ugh. So what can be wrong, any ideas?
I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app
bit1 said:
I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
It happened with both stock and new battery (Anker).
Thanks, update to latest TWRP had been my next try, if it didn't work now. But it does! Yeaaah so happy Thanks to everyone again. Almost three hours uptime and not a single issue so far!
To conclude: What I did:
Revert completely back to stock with BlueIX6's stock image (except that phone was still s-off and sdcard not wiped).
Then followed instructions to unlock bootloader, flash CWM recovery and finally flashed ROM (see sticky thread). Works like a charm!
In hindsight maybe radio made my phone unstable... I think it's the only thing that's different from now.
A humble request let the development thread be for just development.Just try to keep that one clean and post anything however random(about CM10.1 ofcourse) here.Don't flood the dev thread with about 70 posts regarding black screen problem.
Let this thread be for general questions, comments, discussion, complaints concerning CM10.1 for the Atrix 2.
CM10.1 development thread .
PS: Help the devs in understanding the reason for black screen problem, participate in the poll.
Thanks...
Sent from my MB865 using xda premium
Thanks for creating this thread to keep the dev thread clean.
I got the black screen after I flashed the ROM and the boot logo. How to get past tge black screen? I had to FXZ back to ICS for now. I did a couple of battery pulls but it did not help.
~
Sayantan
Unlock blaxk screen
i cannot unlock after lock using on off button. how to unlock if still black screen? any solution? after i flash gapps camera and gallery fc. it happen when i open camera.
buglist 28/03/13
cLock can't find any location for weather
forfarded call message not work like on scrren from this http://forum.xda-developers.com/showpost.php?p=37850271&postcount=68
and also unavailable change shutter sound and camera save destination.
qwerfv said:
cLock can't find any location for weather
forfarded call message not work like on scrren from this http://forum.xda-developers.com/showpost.php?p=37850271&postcount=68
and also unavailable change shutter sound and camera save destination.
Click to expand...
Click to collapse
+1 for cLock weather issue but honestly I'm so thoroughly impressed with this ROM that I only see that as a minor hitch. I really never thought a fully functional JB would make it to the Atrix! Thank you Devs! :thumbup:
Sent from my SGH-I997 using xda app-developers app
SMONDAL84 said:
Thanks for creating this thread to keep the dev thread clean.
I got the black screen after I flashed the ROM and the boot logo. How to get past tge black screen? I had to FXZ back to ICS for now. I did a couple of battery pulls but it did not help.
~
Sayantan
Click to expand...
Click to collapse
Actually there's no specific reason(at least till now) and hence solution for this black screen bug.Some of the guys who have it have reported to come around it by taking out the battery and rebooting until they get rid of it.But again the number of battery pulls varies from just one time for some to about 40 minutes of battery pull for some others.So can't really say if you tried enough or what else might be the solution.This is the situation as is.
Keep trying or wait till it gets fixed there is really nothing else that you can do at the moment.
Sent from my MB865 using xda premium
Is there a way to keep the capacitive key backlight always on? Didn't spot anything in the main thread about this.
What is with this "♫" symbol?? It's very annoying, ugly, and it's everywhere on this ROM. in instagram, when entering passwords, in descriptions of apps in the playstore.
Loving this so far, but I do have a few concerns. I did make sure to install correctly (CM recovery -> wipe data, flash, reboot, flash gapps), but I'm running into some minor issues.
- My phone seems to be sluggish at times, especially noticeable when turning the screen off and when it vibrates (anything that vibrates twice in a short amount of time). There's a good half-second delay with each of these, much slower than on CM10. Is this normal? Other than that it runs pretty quickly.
- This is the more major issue, the alarm. Everything else in the gapps package works properly except for the alarm function of the clock. When an alarm goes off, there's no popup or anything, and pressing power stops the vibration from the alarm, but it doesn't actually turn the sound off. I have to kill the Alarm Klaxon service to shut it off. Any idea what could be causing this? I haven't heard of anyone else with this bug yet.
Will try flashing once again with BMM this time..
deveshmanish said:
Actually there's no specific reason(at least till now) and hence solution for this black screen bug.Some of the guys who have it have reported to come around it by taking out the battery and rebooting until they get rid of it.But again the number of battery pulls varies from just one time for some to about 40 minutes of battery pull for some others.So can't really say if you tried enough or what else might be the solution.This is the situation as is.
Keep trying or wait till it gets fixed there is really nothing else that you can do at the moment.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Will try with BMM this time along with the patch. Fingers crossed! (I went through the threads and it appeared that people with BMM probably had a greater success rate with installing in the 3rd system - getting superstitious now! )
Will update the results.
~
Any one found a way to OC the phone on this ROM ?
After flashing this ROM it is not booting. It is stopped at boot logo and showing black screen. Could any one help in this
Regarding , I am on pa ver2.99
Kernel 3.0.0.8
And please tell me which is the best radio apk for PA2.99
Thanks in advance.
Sent from my MB865 using xda app-developers app
android.reddy143 said:
After flashing this ROM it is not booting. It is stopped at boot logo and showing black screen. Could any one help in this
Regarding , I am on pa ver2.99
Kernel 3.0.0.8
And please tell me which is the best radio apk for PA2.99
Thanks in advance.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Enter cm recovery select custom recovery and again flash the rom
Sent from my MB865 using xda premium
any of you guys have problem cannot transfer files through usb? mine, when i connect click turn on USB storage, it just loading and loading and just loading.:crying:
Need help flashing the 4.2.2 ROM
My Atrix 2 is on the JB 4.1.2 leak. Model No. ME865. I have ROM Manager installed. I have copied the zipped ROM and GAPPS files to the external memory card. When I boot into Recovery mode, I cannot see any option to Wipe Data / Factory Reset. I am pretty new at this and so if anyone outlines the steps in detail or posts any link to point in me in the right direction, it would help me much. Thanks in advance.
ozzman77 said:
My Atrix 2 is on the JB 4.1.2 leak. Model No. ME865. I have ROM Manager installed. I have copied the zipped ROM and GAPPS files to the external memory card. When I boot into Recovery mode, I cannot see any option to Wipe Data / Factory Reset. I am pretty new at this and so if anyone outlines the steps in detail or posts any link to point in me in the right direction, it would help me much. Thanks in advance.
Click to expand...
Click to collapse
If you are new to flashing ROM's stay away from this because currently a lot of users face black screen issues etc. Also it should not be installed over JB base as well. Read the entire thread from post one till current and you will see for yourself as it will enlighten you on a lot of aspects what people have already tried & which may save you from heartburn. JB gives a great user experience, enjoy it for a while & then get on the bandwagon when you are more of a informed user.
ozzman77 said:
My Atrix 2 is on the JB 4.1.2 leak. Model No. ME865. I have ROM Manager installed. I have copied the zipped ROM and GAPPS files to the external memory card. When I boot into Recovery mode, I cannot see any option to Wipe Data / Factory Reset. I am pretty new at this and so if anyone outlines the steps in detail or posts any link to point in me in the right direction, it would help me much. Thanks in advance.
Click to expand...
Click to collapse
I agree go for CM10 instead it's been pretty stable.
Sent from my MB865 using xda premium
It's in vain, he already flashed CM 10.1 & now he posted in the black screen thread.
Did get hit by the Black Screen Bug
RAD7 said:
If you are new to flashing ROM's stay away from this because currently a lot of users face black screen issues etc. Also it should not be installed over JB base as well. Read the entire thread from post one till current and you will see for yourself as it will enlighten you on a lot of aspects what people have already tried & which may save you from heartburn. JB gives a great user experience, enjoy it for a while & then get on the bandwagon when you are more of a informed user.
Click to expand...
Click to collapse
You were right. I watched the video on flashing ROMS from here https://www.youtube.com/watch?v=kumkZiGbTFI and tried it out. Got the black screen issue when flashing over JB. Then FXZd back to stock ICS and reflashed, but got the same thing again. So i'm back on ICS now. I suppose i'll upgrade to JB later and stay there for a while till this thing is sorted out.
Anyone getting YouTube problems.... Freezing... Could not stream at all with March build.
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui
3. Kexec 4.2.2
6. ASOPA 4.2.2
Ok so it is like this:
I bought my galaxy r here in sweden 1 year and 3 months ago, it was working perfectly for around 1 year.
At the one year mark i started to have some problems with the touchscreen where the phone would feel a pressure in the middle of the screen, to get rid of this i simply locked and unlocked the phone or rubbed a bit with a cloth on the screen.
Recently when I saw there was a cm10.1 rom with nightlies I rooted my phone and later installed the cm10.1 rom. Now the most anoying thing. I have a problem with my battery where the phone just shuts down randomly (mostly when playing games) even though it sometimes have up too 80% battery remaining. Then when I restart the phone it usually have 0% battery left and therefore shuts itself down again, sometimes it restarts with just a 20-30% batteryloss. This have occured more often recently and it shuts itself of 3-4 times a day. I can't remember if it was like this when i was on stock, before I started to flash and root, but i think it was.
A few days ago i flashed stock ics from odin and I confirmed that both of these problems still were there, so i have hard to belive that it is the modding of the software that have caused this.
Do you guys have any suggestions to how i can be able to use my phone normally again?
Im just a poor student so i don't want to waste money on a new phone after just 1 year :/
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Will this help with the battery?
kataria.vikesh said:
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Will this help the crashing/battery?
DippN said:
Will this help the crashing/battery?
Click to expand...
Click to collapse
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
kataria.vikesh said:
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
Click to expand...
Click to collapse
Nope, im not takeing backup of anything.
And one other thing i forgot to mention earlier, the phone now also thinks it is charging itself evrn when it is not. It think the usb cable is still connected.
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
DippN said:
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
Click to expand...
Click to collapse
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Both of you install CM10.1 using Procedure no 2 from OP.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Will try that when i get home, thx.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
paKS7 said:
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
Click to expand...
Click to collapse
Sadly, I can confirm that this did not change anything.
The problems are still there :/
DippN said:
Sadly, I can confirm that this did not change anything.
The problems are still there :/
Click to expand...
Click to collapse
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
DippN said:
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
Click to expand...
Click to collapse
May be hardware or software too..when you will vanish all data & cache then Software issue may be gone but if problem still persist, means you have hardware problem.
Also, root will be lost after flashing Stock ROM from ODIN.
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
paKS7 said:
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
Click to expand...
Click to collapse
Well, we are not on the same baseband. I'm on I9103XXLQ3.
About the cm verison im not quiet sure, the latest i flashed was "20130406" but since the problem were there the time before that when i flashed cm I cant answer exacly but i have a cm version "20130305" on my desktop and it could be that one that I used.
I never used cm before it was on nightlies so the modem file flashing i dont know anything about.
The thing you mention about that it shuts of when the phone gets busy and touchscreen gets unresponsive I can kind of confirm too.
I will flash GB now, will report back in an hour how it went.
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
DippN said:
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
Click to expand...
Click to collapse
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
DippN said:
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
Click to expand...
Click to collapse
Wipe data again.. If possible after wiping data Just reflash the GB.
G'day people I've run into something pretty weird with my OnePlus One. I installed the CM12 nightly and booted it up, ran it for a few hours then got ghost touches and the screen became unresponsive at times.
So, having my usual backup of CM11S, I wiped and restored to the latest backup I had and everything was weird. I kept getting ghost touches and reduced responsiveness, and sometimes it would just randomly malfunction and not unlock and just keep the screen off.
Rebooting clears up the problem for about 5 minutes and then it comes back at full blast.
I tried installing the last CM11S update via flashing Calkunins stock XNPH44S zip and still I have all these weird issues that wasn't there before I flashed the CM12 nightly.
Has anyone come across this problem or is it just me and my device? It's seriously a cause for concern, and I'm posting this to both XDA and the OnePlus forums in hopes of getting some sort of help and relief in this situation.
Any assistance is appreciated and I thank you in advance for taking the time to read this.
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
kthejoker20 said:
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
Click to expand...
Click to collapse
not entirely true, there are different screens, that could be the issue. It was reported in boeffla kernel thread. sesrch throught it and it might contain something useful to try.
also open a support question, Oneplus needs to know how annoying their poor choice of different lcds are
Sent from my A0001 using XDA Free mobile app
bachera said:
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try to flash CM11S via fastboot to see if it clears up the issue. For now, the date I got mine is 2014-07-16. Shipped to me after 12 days (International shipment via courier)
UPDATE
Flashing CM11S via fastboot resolved all issues as far as I can tell.
Will remain on the lookout for the bugs in the future but for now I'm happy to say it worked for me.
Thank you all again for the advice and guidance, it was appreciated.
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
kthejoker20 said:
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
Click to expand...
Click to collapse
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
timmaaa said:
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought it was the partition thing too because I had almost the same problem on my HTC Amaze back in 2014, and flashing the OEM RUU helped with sorting things out.
But as for the random screen touches, flashing everything from fastboot helped for only a few hours. The symptoms came back after a while, specifically when I replaced my music and pictures. I'm thinking that I may have a corrupted file on it somewhere but I doubt it'll cause a malfunction like that.
So I tried flashing Franco Kernel, and it seems to have cleared it up..... for now.
It's so frustrating thinking that my device may be defective
UPDATE #2
Flashing Franco Kernel didn't help. Symptoms came back within a couple hours. Will try a custom ROM, specifically AOPK (because I want to )
If that doesn't fix the issue then I've just got to face the fact that I have a defective device (somehow)
Bump
Nothing worked. I contacted the manufacturer but they seem to think doing a factory reset will help. It didn't.
Flashing CM11S via fastboot doesn't help
I really think this is a hardware issue that just emerged from nowhere, probably due to lack of premium or standardized quality adhesive.
There's a really long thread over at the OnePlus forums about a guy who found it was a grounding issue and took some adhesive tape to insulate the area near the proximity sensor (I think? I'll include the link in here somewhere)
Honestly, OnePlus impressed me....at first. But I cannot use a phone that's not working properly.
https://forums.oneplus.net/threads/...-hint-it-was-never-a-software-problem.186235/
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
sylvain15250 said:
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
Click to expand...
Click to collapse
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
rdar_93 said:
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
Click to expand...
Click to collapse
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
bachera said:
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I actually did unlock my bootloader.
PS I also got tired of seeing CM11S try to boot up so I flashed ColorOS (because it's the only rom I had on my laptop. Why not download another 4.4.x AOSP rom? Unstable wifi at school)
So yeah, wifi is not turning on. Gonna try the program again. I wonder if it would work this time?
The conditions aren't as different as before, could work, right?
Honestly I want to wait but they take so long to reply.
UPDATE
After flashing ColorOS I decided to go back and try doing the CM11S via fastboot commands. Still got a bootloop but hey I got the correct fastboot logo now in case if it made a difference.
So I did the compulsory flashing commands when I went from Color to CM11S and still bootlooped.
So I booted into fastboot again
fastboot oem unlock (supposed to unlock bootloader and reboot if it's locked, no reboot if unlocked [assumption])
then rebooted into fastboot again, ran the batch files OnePlus sent to me which essentially flashed CM11S just like you would over fastboot, but with added modems etc.
Successfully booted into CM11S without issues, WiFi works again and so far no symptoms as yet.
Will keep this post updated if anything happens.
My screenshots of the batch file commands OnePlus sent would be found in the attachments.
UPDATE 2
So I think it's fixed permanently this time.
I'm not sure though. It hasn't done anything weird. I will copy my music and photos to see if that would cause anything to happen
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
FYI, when you flash CM12 the radio is overwritten with an alpha/beta radio which causes (well, caused for me) THE EXACT issues OP was having in CM11/S. The CM12 radio (as far as I can tell) ONLY works with CM12 - making going back a PITA.
If you have the baseband in this thread (see screenshot in first post) then that means you are on the experimental radio and are going to have a bad time if you aren't on CM12.
I flashed the latest OTA radio found here and all was right with the world (at least where my OPO was concerned ).
hp13 said:
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
Click to expand...
Click to collapse
I would like to go back to CM11s to check if the situation is better. I tried to flash the lastest CM12 build and it seems to be better but still not as good as before
When I do a wipe and then flash the ROM in TWRP, there are some "folder already up to date", which I would like to avoid. What I would like to do is doing a complete clean install of either CM12 or CM11s plus rewriting the partitions,... So that I'm sure if the problem is still here it is due to an hardware issue.
Is there any chance someone can help me with this? Even with a link... I searched for "write partition" without any luck :-/
Thanks !
EDIT: Do you think the OnePlusRecovery Tool can help me with this?
Hi, I've done some research through xda and other outside sources and haven't been able to find a solution or explanation for my issue. The problem that I am having is my phone is randomly shutting down and I have to pull the battery before it allows me to turn it back on. I'm not sure if this is a software, hardware, or battery issue.
I'm running an LG G3 D850, rooted and running flexos 5.1.1, and the 777 kernel. Everything has been fine until about a week ago when I noticed the first shutdown. As of the past two days it has become more frequent. I think the issue may have been with the settings I had set for the app I was using to manage my kernel settings. So I've uninstalled it and will report back. I have a logcat and a screenshot of my about phone, i just dont know how to post it. Any and all help is appreciated, really not wanting to flash another ROM if it can be avoided. Thanks.
definx said:
Hi, I've done some research through xda and other outside sources and haven't been able to find a solution or explanation for my issue. The problem that I am having is my phone is randomly shutting down and I have to pull the battery before it allows me to turn it back on. I'm not sure if this is a software, hardware, or battery issue.
I'm running an LG G3 D850, rooted and running flexos 5.1.1, and the 777 kernel. Everything has been fine until about a week ago when I noticed the first shutdown. As of the past two days it has become more frequent. I think the issue may have been with the settings I had set for the app I was using to manage my kernel settings. So I've uninstalled it and will report back. I have a logcat and a screenshot of my about phone, i just dont know how to post it. Any and all help is appreciated, really not wanting to flash another ROM if it can be avoided. Thanks.
Click to expand...
Click to collapse
First thing to try is a factory reset or flash stock rom.
Sent from my iPhone using Tapatalk
hyelton said:
First thing to try is a factory reset or flash stock rom.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thank you for your quick response. Im trying to avoid that as long as possible, but will turn to it as a last resort. Would you maybe have any other suggestions? I would like to post this logcat as I'm hoping it may shed some light on the shut downs. How might I do that?
definx said:
Hi, I've done some research through xda and other outside sources and haven't been able to find a solution or explanation for my issue. The problem that I am having is my phone is randomly shutting down and I have to pull the battery before it allows me to turn it back on. I'm not sure if this is a software, hardware, or battery issue.
I'm running an LG G3 D850, rooted and running flexos 5.1.1, and the 777 kernel. Everything has been fine until about a week ago when I noticed the first shutdown. As of the past two days it has become more frequent. I think the issue may have been with the settings I had set for the app I was using to manage my kernel settings. So I've uninstalled it and will report back. I have a logcat and a screenshot of my about phone, i just dont know how to post it. Any and all help is appreciated, really not wanting to flash another ROM if it can be avoided. Thanks.
Click to expand...
Click to collapse
First thing to try is a factory reset or flash stock rom.
Sent from my iPhone using Tapatalk
Try safe mode diable all apps then u know if in system or apps