Related
Hello everybody,
I purchased my galaxy note 2 in late December, I kept the stock samsung ROM (android 4.1.1)and almost rooted it immediately after I had opened its box. Rapidly, I noticed it rebooted from time to time, it seems it happened randomly, i.e. not whilst performing a specific task on my phone. For instance, sometimes when I wanted to check my emails or texts, I picked it up from my pocket, and android was asking me to enter my SIM PIN. So basically my phone rebooted while sitting in my pocket. More rarely, it also suddenly rebooted while I was using it. (but to be honest, it spends more time in my pocket than it does in my hands, that's definitely why it did the latter far less frequently).
I saw that there was an update available, so I flashed the 4.1.2 stock ROM using kies, and rooted it again shortly after. But the reboots issue was still there, so in February I decided to give a try to a cyanogen mod 10.1 nightly build. For like a week or 10 days, it appeared to work properly, no more random reboots. However, after that delay, unfortunately it started to randomly reboot again.
I don't think that rooting the phone can cause such an abnormal behaviour, can it? I use several apps that require root privileges, that's why I did root it every time I flashed a new ROM.
Well the bottom line is that it's really pissing me off, so I'm considering to return it to samsung using a RMA procedure. But anyway, if you have any idea that could help me solve this problem, please feel to let me know, I'll gladly appreciate it. Also I'm wondering if anyone has an alike problem?
If need be, I'll return it for a repair or an exchange, if so, what do I need to do to reset it to factory defaults? I can re-flash the stock ROM, that should unroot it, but resetting the flash counter is also required, for that purpose I'll probably try the 'Triangle Away' app, hopefully it's gonna work. But AFAIK, when doing so on my former phone - a samsung galaxy S 2 - there was another counter, that counted how many times the first counter has been resetted, so one has to actually reset both of them in order for the mobile not to look having been tinkered with. Is anyone aware of a similar second counter on the galaxy note II? If you think of anything else I forgot to mention, please give me a shout.
Thanks for reading my post and helping me out.
Sadly it sounds like you might have a defective Note II. I have a stock (not rooted) Note II and, while I've only owned it for a month, it hasn't exhibited any problems with rebooting. Nor did I have anything like that with my S3 previously.
Probably not what you were hoping to read, sorry.
Thanks for your input muppetmania, well fortunately all galaxy note II don't have this problem
I just hope that if I return it, they'll be able to reproduce the annoying issue as they probably won't install as many apps as I did, or use it the same way, etc ...
My note 2 is the first android phone I've had that I have not rooted (yet). I've had it about a month now and it has randomly rebooted 3 times so far.
Every time it has happened it's been while I had 10+ tabs open in Chrome and was reloading several at once while also using other apps. For example one time I was composing an email and pulling excerpts from several sources on different web pages.. midway through composition and BAM, random reboot
In my opinion you did not cause this by rooting the phone
nebenezer said:
My note 2 is the first android phone I've had that I have not rooted (yet). I've had it about a month now and it has randomly rebooted 3 times so far.
Every time it has happened it's been while I had 10+ tabs open in Chrome and was reloading several at once while also using other apps. For example one time I was composing an email and pulling excerpts from several sources on different web pages.. midway through composition and BAM, random reboot
In my opinion you did not cause this by rooting the phone
Click to expand...
Click to collapse
If mine had only rebooted 3 times in a month then I'd be "happy" But for me it's more like 3 times a day. Well any random reboot is never a good thing, especially if you're are typing a text or writing an email. I'm scared it happens when I'm using my phone as a GPS on my motorbike, could be really pesky if I have to stop, wait for the mobile to reboot, get another GPS fix, and set my destination again ...
Just out of curiosity, you're also running the stock samsung ROM? Switching from it to cyanogen made virtually not difference for that matter.
I still have not rooted this device so yes... I'm running the stock Samsung rom
In case it may be relevant though, I do also use nova launcher and LOVE it. This new generation of TouchWiz is not bad at all not Nova is better, imo
I use the default launcher, both for the stock ROM and cyanogen Mod. I did not really like touchwizz, but I think the dual screen function and the stylus management were quite good though.
I gave a call to the after sales service, and they advised me to go to a Samsung store in order to get my phone repaired. Just to make sure it's going to be be alright (I mean that I don't want them to find out that I have rooted / installed a custom ROM on the mobile and use that as a pretext for refusing to fix it), can someone tell me exactly what do I need to do in order to revert the phone back precisely to its factory configuration?
So far, here is what I plan on doing:
- install the last official samsung ROM (which is currently the 4.1.2 version of android if i'm not wrong), that should unroot the phone altogether
- Use an app called "triangle away" to reset the flash counter
But I still wonder is there is anything else that would allow them to know that I flashed / rooted the phone. Is there anything like a second counter, that counts how many time the counter mentioned above has been resetted itself? Also I do remember that when I flashed my galaxy S II with an insecure kernel, a yellow triangle with an exclamation mark appeared during boot up (I know that "Triangle Away" should remove it), I don't currently have that on my GN 2, but I don't know whether Samsung still uses this method or if they have implemented something else?
Thank you.
Ok, so here's one particular issue that I just haven't been able to solve. I have the Samsung Galaxy S3 (for Sprint) and I hate S-Voice. I want to be able to use Google Now, and with the Home2 app I can do so with the double-tap on the home button. However, I also keep my phone PIN locked (this way if someone steals it, they can't get to my data and I have time to remotely wipe the phone or locate it), and apparently while S-Voice can work whent the phone is PIN locked, I'm not sure if there is any way to get Google Now to work while it's PIN locked by double-tapping the home button.
Basically, the reason I want this is that I just got a Honda CR-V and the bluetooth implementation in the car is absolutely awful. The only way to make calls while driving is 20 pre-programmed speed dials, or else I have to fumble with my phone which is completely unsafe. Shame on Honda for such an absurdly limiting Bluetooth system that basically makes it much more likely one will fumble with their phone while driving. Anyway, I'd love to be able to just double tap the home button on my phone and get Google Now going (while PIN locked) and then just tell it to call someone or do something else.
Anyone know how I can accomplish this?? By the way, my Galaxy S3 isn't rooted, and I'd prefer not to root it since that would mean I'd have to reinstall everything and re-configure everything.
Thanks!!
Rooting your phone doesn't wipe your data or cause you to have to re-install apps or reconfigure. Have you taken the 4.3 OTA?
jhill110 said:
Rooting your phone doesn't wipe your data or cause you to have to re-install apps or reconfigure. Have you taken the 4.3 OTA?
Click to expand...
Click to collapse
My mistake - I think I must have been thinking about custom ROMs. And my phone hasn't been offered the 4.3 OTA yet - I keep reading that there were roll-out issues with it so the timeframe was pushed back, although the last thing I heard was that they started rolling it out again. Will the 4.3 OTA help me with this issue at all?
So I updated to 4.3 via Kies - haven't had a chance to see if I can "fix" my issue in 4.3 yet, but will hopefully get a chance to today or tomorrow and will post back here. Also, someone mentioned trying an app called widgetlocker to control the lock screen, and I'm wondering if I can use this to help get what I want accomplished...we shall see!
hi, every one !! i need your help guys !! i do have a samsung galaxy tab s sm-t 705 i need to pair up with my samsung gear s watch !! i do try pair it up with samsung gear manager but it dos not pair up not seeing the watch !! it was working before i did get received phone calls , sms, and all the allerts came to my watch !! I could not download new programs to my watch gear manager not aloud it !! so please help me with this !!! thanks so much !! zoltán from hungary
Hi im having several issues i am hoping someone would help me fix it.
1. Upon choosing an app from the app selection menu the ROM crashes and reboots it gets really annoying
2. Word prediction on the Samsung keyboard isn't working
3. Autobrightness is somewhat functioning the screen will brighten up but not dim back down automatically.
I love this Rom I hope I get help with this
I went from a Galaxy S2 to a new Galaxy Watch a month or so ago. One of the features that was most important to me was SOS. I use it to discreetly request a phone call to get away from a long conversation. I double press the button and a couple of minutes later I get a call to get me away and back to work.
With the new GW, the call goes directly to my watch and auto answers - so my phone never rings thereby defeating the purpose that I use it for.
Is this still possible or do I need to go back to my S2?
Thanks!
Anyone know the answer to this?
I am considering Putting Lineage OS on my S9+ but am unsure of a few things.
I have read many threads on the subject and see that there are a number of things that can go wrong. Unfortunately, the answers use many abbreviations which means I have no idea what they are talking about. Also they talk about flashing the stock firmware to get the camera working. This seems to be different to the OS.
I did successfully install CyanogenMod on my Galaxy S2 and was very happy with it. I'm particularly unhappy with the direction of Samsung's updates. Every new update seems to break something else I use regularly.
My alternative to installing Lineage OS is to downgrade to Android 9, but remembering how snappy and clean CyanogenMod was on my S2 I'd certainly prefer Lineage as long as key functions work.
With that in mind, here are my questions:
1/ Can the Bixby button be configured to operate the flashlight without unlocking the phone? I currently have an app that does that, although it's a little unreliable and sometimes takes 3 presses.
2/ If for some reason I don't like Lineage, is it reasonably easy to go back to a stock OS? (My phone is no longer under warranty.)
3/ I understand the camera does not work as well. Is this a problem with basic picture quality or is it just some of the more advance features that are missing?
4/ Is Lineage OS compatible with Google Daydream? Samsung removed Daydream support with the Android 10 update and this is the main reason I want to go to the effort of changing the OS on my phone.
5/ Is star2lite the correct version of Lineage for my phone, SM-G965F?
5 yes. See supported model
https://wiki.lineageos.org/devices/star2lte/
2 should be fine with odin. But knox keeps triggered
All other questions
https://forum.xda-developers.com/ga...evice-development/rom-lineageos-17-1-t4083325
kurtn said:
5 yes. See supported model
https://wiki.lineageos.org/devices/star2lte/
2 should be fine with odin. But knox keeps triggered
All other questions
https://forum.xda-developers.com/ga...evice-development/rom-lineageos-17-1-t4083325
Click to expand...
Click to collapse
Thanks for your reply.
I couldn't find any mention of the Bixby button in that thread, but installed Lineage anyway. So far I have not had any luck getting access to the Bixby button. I've tried Bxactions and Button Remapper. BxActions requires Bixby on the device and seems to work by detecting Bixby starting, so that's not a solution. Button remapper looks promising, but refuses to activate. I just get in a loop of being told to run the PC software. Everything looks OK, but when I come out of the setting it's still switched off.
As for Daydream, it runs but looks like at a very low frame rate. I tried both reduce blur and reduce flicker, but both are not pleasant to use. Also, Skybox video player doesn't work at all. It starts and connects, but just presents a blank display.
As an experiment I tried to use Odin go back to a stock Samsung Android 9, but the boot loader is locked at 10 so I guess I can't do that either.
Looks like a phone I originally chose because of its good VR support is just going to be a basic device. Not having the torch on the Bixby button is something i'm going to sorely miss. I use the torch many times a day for work and not having to unlock the phone was great.
Mike Warren said:
Thanks for your reply.
I couldn't find any mention of the Bixby button in that thread, but installed Lineage anyway. So far I have not had any luck getting access to the Bixby button. I've tried Bxactions and Button Remapper. BxActions requires Bixby on the device and seems to work by detecting Bixby starting, so that's not a solution. Button remapper looks promising, but refuses to activate. I just get in a loop of being told to run the PC software. Everything looks OK, but when I come out of the setting it's still switched off.
As for Daydream, it runs but looks like at a very low frame rate. I tried both reduce blur and reduce flicker, but both are not pleasant to use. Also, Skybox video player doesn't work at all. It starts and connects, but just presents a blank display.
As an experiment I tried to use Odin go back to a stock Samsung Android 9, but the boot loader is locked at 10 so I guess I can't do that either.
Looks like a phone I originally chose because of its good VR support is just going to be a basic device. Not having the torch on the Bixby button is something i'm going to sorely miss. I use the torch many times a day for work and not having to unlock the phone was great.
Click to expand...
Click to collapse
I'm sure the bootloader is mot locked in lineageOS 17.1
kurtn said:
I'm sure the bootloader is mot locked in lineageOS 17.1
Click to expand...
Click to collapse
I'm not having any luck with loading either a 9 image or a 10 image using Odin. Is there another way?
Every time I try the phone displays: SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 9. BINARY: 7