[Q] stock everything - screen freeze issue - Galaxy Note II Q&A, Help & Troubleshooting

Hello,
I'm running into a very strange issue. I've had Note 2 for a while now (since Nov 2012 -ish) and up until a few days ago it's performed magnificently. I have not load any custom ROM/mod or anything like that - simply because I use Note for work and Good For Enterprise freak whenever there's a custom ROM mod (I didn't even attempt it with Note 2, due to my experience with GFE crapping out on my Galaxy Nexus every time I try to load a custom ROM). But, no complaints so far.
A few days ago (Mar 1st? give or take a day), I got a prompt for a system software update. Ever since then, I have had nothing but trouble with my Note 2. It would boot up fine, but in a few minutes, whether I'm in email, or browsing the net, or running WeChat, or Viber, Pulse, or any of the other apps that I normally use, the screen would freeze up. Power button would turn the screen off, but then once you turn on the screen again, you can't swipe to unlock the screen. Home button doesn't work. The only thing that I could do "to reset the phone" is hold down power and home button and force it to reboot.
Edit: I forgot to mention something, I remember many of the times when I am experiencing the freeze issue, I can still drag down the notification settings, but can't click on anything though. If this helps any one to help me troubleshoot my issue.
Now, I've tried to reload 4.1.1 stock kernel (there are a couple of them), 4.1.2 stock kernel via Odin (I downloaded them from http://samsung-updates.com/). with 4.1.1, the device would be stuck in a bootloop, 4.1.2 works, but after a while, screen freeze problem comes back. I've tried a bunch of things, such as:
1) Just flashing the kernel
2) factory reset via the VolUp+Power+Home, then flash kernel
3) removed my MicroSD, repeat 1 or 2.
I'm totally out of ideas.. can someone help?? Please! I'm stuck with my old iPhone 4s and let me tell ya.. Once you get used to Note 2, iPhone 4s seems positively TINY!!!
any help is appreciated.. but can someone please enlighten me??
PS. Adding insult to injury, my SO who is a hardcore apple fan, now chants "see how stable Apple is?" every time I'm *****ing about this damn Note 2.. heh..

mobilebuddha said:
Hello,
I'm running into a very strange issue. I've had Note 2 for a while now (since Nov 2012 -ish) and up until a few days ago it's performed magnificently. I have not load any custom ROM/mod or anything like that - simply because I use Note for work and Good For Enterprise freak whenever there's a custom ROM mod (I didn't even attempt it with Note 2, due to my experience with GFE crapping out on my Galaxy Nexus every time I try to load a custom ROM). But, no complaints so far.
A few days ago (Mar 1st? give or take a day), I got a prompt for a system software update. Ever since then, I have had nothing but trouble with my Note 2. It would boot up fine, but in a few minutes, whether I'm in email, or browsing the net, or running WeChat, or Viber, Pulse, or any of the other apps that I normally use, the screen would freeze up. Power button would turn the screen off, but then once you turn on the screen again, you can't swipe to unlock the screen. Home button doesn't work. The only thing that I could do "to reset the phone" is hold down power and home button and force it to reboot.
Edit: I forgot to mention something, I remember many of the times when I am experiencing the freeze issue, I can still drag down the notification settings, but can't click on anything though. If this helps any one to help me troubleshoot my issue.
Now, I've tried to reload 4.1.1 stock kernel (there are a couple of them), 4.1.2 stock kernel via Odin (I downloaded them from http://samsung-updates.com/). with 4.1.1, the device would be stuck in a bootloop, 4.1.2 works, but after a while, screen freeze problem comes back. I've tried a bunch of things, such as:
1) Just flashing the kernel
2) factory reset via the VolUp+Power+Home, then flash kernel
3) removed my MicroSD, repeat 1 or 2.
I'm totally out of ideas.. can someone help?? Please! I'm stuck with my old iPhone 4s and let me tell ya.. Once you get used to Note 2, iPhone 4s seems positively TINY!!!
any help is appreciated.. but can someone please enlighten me??
PS. Adding insult to injury, my SO who is a hardcore apple fan, now chants "see how stable Apple is?" every time I'm *****ing about this damn Note 2.. heh..
Click to expand...
Click to collapse
Um, you mentioned Odin. I say go back to the site you got the "kernel" from and download a full stock firmware. Try to find the original one that came with your phone model. Flash via odin. Should fix if a software issue. If after wipe and stock reinstall issue still occurs you may want to consult whom you purchased it from. Could be a hardware failure.

You are right, I actually meant to say full firmware images (they are about 1.5GB uncompressed "md5" files).
aswethinkweiz said:
Um, you mentioned Odin. I say go back to the site you got the "kernel" from and download a full stock firmware. Try to find the original one that came with your phone model. Flash via odin. Should fix if a software issue. If after wipe and stock reinstall issue still occurs you may want to consult whom you purchased it from. Could be a hardware failure.
Click to expand...
Click to collapse

Do a mega wipe via zoot's script. Then from recovery reboot into download mode. Then flash the latest stock rom for your country. (If latest is 4.1.1 then flash latest france rom)
After this procedure every bit of information would be deleted from your phone. So backup accordingly.
Sent from my GT-N7100

I have the same problem. Wiping and resetting didn't help. I sent mine for repair but Samsung is ignoring the issue and they sent it back to me unrepaired. I'll probably have to send it in again or try to get a replacement.
Many people here in the forum seem to think these are symptoms of imminent sudden death syndrome so no fu Good luck and let us know how it goes for you.

install "eMMC Check" from google play and run it.
If your eMMC chip is;
Type: VTU00M
FwRev: 0xf1
read this thread, Note 2 SDS (sudden death syndrome) and worry!!
I have 0xf1 insane chip and am experiencing your exact same symptoms.

Hey Honestly ,
I am not a big Fan of APPLE but i should say that the Apple Os is Very stable , Now the reason of it being stable is because the Apple is not an Open Source Os , Where in Android is an Open Source so there are huge number of Developers who are giving you so many apps for free,u've got lot of Mods and tweaks that can be done on Android where as not on Apple , So Please stop comparing that Apple is stable , not Android , Where there is always a fix for all the problems , I would suggest you to try a Clean install of Stock Firmware by Formatting your Sd and Resetting your Phone and Flash the Stock with Odin.

It is not a sign of sds. It is like fever.
When you have a disease you get fever.
Fever means that your body is fighting against the disease.
Freezing is the fever here. To prevent sds the phone freezes. There is no correct explanation but it seems it only happens after upgrading to sds fixed roms.
this is XXXDDDAAA

Had 5 freezes and/or resets between 07:00 and 08:00, same story for the past few weeks since firmware upgrade XXDMB2.
Now with latest XXDMB6 firmware downloaded this morning its been to rock steady for the last 6 hours
I am 0xf1.

Related

[Q] Buggy screen on any DK28 rom

any time i try to flash to anything dk28 based, i get the same result. the touch screen (almost) randomly stops responding to input. seems to be related to keyboard opening, but not always. example: from sleep, wake > slide unlock > slide notification bar > tap... "damn it..." can't open the notification unless i sleep it and start over. this is not a hardware problem so far as i can tell as it works fine when flashed to stock. it's less than 2 weeks old and no, i did not spill anything on it. am i alone here?
not new to android, nor am i new to flashing roms, hacking portable devices / electronics in general or using forums. i did search and nothing matched my issue. please don't treat me like a noob just bc my account is new.
As of this morning my phone seems to have developed this kind of behavior, out of the blue. I have no idea what caused it, just that it is exceptionally frustrating.
further info:
...this was all using cwm3 one click with conversion to ext4. just installed cwm 2.5 and flashed the zip version of dk28 (from here) and got the same result again... damn it... back to the beginning again...
Flashed Nebula (seven sisters) and got the same... I mean, if it did this on stock fw I would obviously exchange it... but its only when I flash. So either I'm doing something wrong, there is something wrong with my handset or there's something with cwm or dk28 causing this. Not outside the thought of me doing something wrong, but I've tried so many different things at this point... the only thing I have left I think is flashing dk28 as an update. Is there one around?
Sent from my SPH-D700 using XDA App
my epic was doing the same thing after i flashed midnight but then just a soon as it started it stopped and hasnt happened since. ive tried to recreate to solve it but to no avail if you figure anything out please let me know
Odin back to stock = fine.
flash update.zip for here = intermittently unresponsive again.
seriously... no one else is getting this continuously? i mean it's pretty unusable...
I'm still getting it pretty consistently, I haven't flashed back to DI18 to see if that fixes it. (Odin and I have a bitter history) I suppose if I'm going to take it back I need to flash it back though.
yeah, i did something wrong the first time with Odin but i'm pretty comfortable now. don't know what i did before, but it failed and nearly bricked. as i understand it now:
1. remove sd card (i just go ahead and pop out the battery while i'm at it)
2. boot into download mode (boot while holding "1")
3. select victory PIT and DI18 in PDA
4. uncheck everything but restart
5. connect handset and verify that it is seen
6. go.
have done this about 10 times now and haven't had a problem... until i try to do go to DK28...
I think i'm going to have to wait for official FROYO... it's killing me but i don't want to try to walk into sprint like "hey, my rooted phone doesn't work right...". if it still happens on official 2.2, i will swap.
Mine does the exact same thing. I asked about it yesterday because I couldn't find anyone with a similar issue but the only answer I received was to go back to stock and try it again. I did that and I got the same result.
I ended up just taking the phone into a Sprint repair center, they replaced the screen and didn't even mention the DK28 Bonsai 2.0.1. For free, in less than three hours.
I'm a little confused, are u flashing DK28 with Odin?
It doesn't seem to matter how I flash:
tried flashing just DK28 in Odin
tried flashing modem/pit in Odin and ROM in CWM3
tried the same with CWM2.?
tried update.zip from stock recovery
all get the same result. Behavior seems to actually be time based - like when wake from sleep, it responds for a few seconds and then stops. it doesn't come back until i sleep/wake again, then it's fine.
UPDATE
EB13 is out, installed and still causing an issue. I will be going to the Sprint store later. Still don't know why this didn't happen on DI18, but whatever - happens on official release now so a replacement is justified.

[Q] Note II dying, Please help!

Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*
mrkupochan said:
Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*
Click to expand...
Click to collapse
Could you please specify what Rom and version that you flashed?
Sent from the rabbit hole.
Did you install one of the other custom recoveries manually yet? Btw. IMHO TWRP is the best anyways. Did you do a full wipe before installing new ROM? what kernel/version are you on?
I went from using the Android revolution HD 10.0 version with stock kernel, I changed to AllianceROM N7100 XXDMA6 JB V1.0 but didn't find it smooth enough so I swapped back to Revolution, thats when I found twrp had installed.
I've tried flashing the stock recovery and i'm still getting the same issue.
I've since reflashed cwm but this hasn't solved the problem unfortunatley.....No idea what to do
You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.
Martux76 said:
You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.
Click to expand...
Click to collapse
All done, several times, no difference
Have you considered it could be sudden death syndrome?
You should have nothing to worry about in terms of it dying, since you have a very recent base rom (dma6), which include safeguards against it.
When it freezes, have you tried waiting to see if the phone responds after you press the Home Button?
I ask this because I've read reports of people waiting for over 20 minutes for the phone to become responsive again after pressing the home button when in standby.
Another thing: have you ever flashed a full stock rom after DLL7 (including DMA6)? I ask this because DLL7 and later include a new bootloader that *supposedly* helps address the sudden death issue. It doesn't hurt to try anyway.
Sent from my GT-N7100
If ur pc recognises ur phone in download mode seaech the forum for rescue firmware (it comes with pit file) and flash it with odin..u should be sorted then.
Sent from my GT-N7100 using Tapatalk 2

[Q] SDS- EMMC DATA Corrupt, ROM RE-FLASH OR SEND BACK TO SAMSUNG FOR MB-REPLACING?

I've posted earlier in one of the SDS/Freeze topics the exact story what did happen with my (roughly 7-month old phone).
A short summary:
I was running a 4.1.2 DLK7 -ROM together with the Perseus 36.3 kernel. I've changed kernel since I knew that I was vulnerable for the SDS. I got a INSANE Fx01 chip.
I've did ran eMMc many times to check if any memory was corrupted, it did pass the tests fine. About 4 weeks ago I had my first phone crash (reboot) while updating a Google Play Store application. Afterwards the phone was alright for roughly two weeks. Then suddenly another crash (reboot). Not even a day later I had a phone-freeze. Only option was pressing Power-button. Then the phone-freezes started to increase, the times became shorter and shorter. A new eMMC test caused a error this time and made my phone do a re-boot. Last time the phone did freeze before even seeing the log-in screen. The next day I tried to power it on, it did not respond! I removed the battery and put it back in. Then it started, but it would not go past the Samsung LOGO Screen. I could still enter the download-mode but it also says : binary counter 1 that means that the OS- is now really broken. I could also still access the recovery TWRP-modus.
I could give it a shot the flash the latest 4.1.2 ROM with Odin (if it doesn't give a nan-d error). But do you guys think it is worth it?
Is it not better to visit a repair-center and let the motherboard replaced?
My concern:
There are also many topics to find here that even with the soft-rom/kernel fix the phones start to act like this : freezes / reboots. It is the SDS-fix kicking in, that saves it from dying but the data-memory-corruption cannot be repaired. So sooner or later even with the latest rom and this chip you will have this problem, lose your data?
Thanks for the advice in advance.
Iriseyoufall said:
I've posted earlier in one of the SDS/Freeze topics the exact story what did happen with my (roughly 7-month old phone).
A short summary:
I was running a 4.1.2 DLK7 -ROM together with the Perseus 36.3 kernel. I've changed kernel since I knew that I was vulnerable for the SDS. I got a INSANE Fx01 chip.
I've did ran eMMc many times to check if any memory was corrupted, it did pass the tests fine. About 4 weeks ago I had my first phone crash (reboot) while updating a Google Play Store application. Afterwards the phone was alright for roughly two weeks. Then suddenly another crash (reboot). Not even a day later I had a phone-freeze. Only option was pressing Power-button. Then the phone-freezes started to increase, the times became shorter and shorter. A new eMMC test caused a error this time and made my phone do a re-boot. Last time the phone did freeze before even seeing the log-in screen. The next day I tried to power it on, it did not respond! I removed the battery and put it back in. Then it started, but it would not go past the Samsung LOGO Screen. I could still enter the download-mode but it also says : binary counter 1 that means that the OS- is now really broken. I could also still access the recovery TWRP-modus.
I could give it a shot the flash the latest 4.1.2 ROM with Odin (if it doesn't give a nan-d error). But do you guys think it is worth it?
Is it not better to visit a repair-center and let the motherboard replaced?
My concern:
There are also many topics to find here that even with the soft-rom/kernel fix the phones start to act like this : freezes / reboots. It is the SDS-fix kicking in, that saves it from dying but the data-memory-corruption cannot be repaired. So sooner or later even with the latest rom and this chip you will have this problem, lose your data?
Thanks for the advice in advance.
Click to expand...
Click to collapse
would suggest to take to Samsung Service rather you giving a try coz this seems to be a Hardware problem .
aukhan said:
would suggest to take to Samsung Service rather you giving a try coz this seems to be a Hardware problem .
Click to expand...
Click to collapse
Yes, I know it is a hardware problem and I do not really trust those Soft-SDS fixes. Many report that even with the latest Rom and a kernel with the fix, eventually the same happens. Data just becomes corrupt. Freezes and Reboots occur. Also the loss of data-settings did happen to me. On a re-boot I suddenly had to re-config Swiftkey , Whatsapp + etc :S.
Guess I will visit the repair-center then and ask them to replace the motherboard and flash the latest rom. Only **** part is that I have to root it again and install my 190+ apps, flash perseus or redpill and do a couple of hundred settings. I got a titanium back-up of my apps but I do not trust the back-up anymore. Maybe some data of the apps became corrupt or something.
Btw perseus or redpill with the original stockrom? what do you advice atm? both support the 64gb-micro sd cards right?
Iriseyoufall said:
Yes, I know it is a hardware problem and I do not really trust those Soft-SDS fixes. Many report that even with the latest Rom and a kernel with the fix, eventually the same happens. Data just becomes corrupt. Freezes and Reboots occur. Also the loss of data-settings did happen to me. On a re-boot I suddenly had to re-config Swiftkey , Whatsapp + etc :S.
Guess I will visit the repair-center then and ask them to replace the motherboard and flash the latest rom. Only **** part is that I have to root it again and install my 190+ apps, flash perseus or redpill and do a couple of hundred settings. I got a titanium back-up of my apps but I do not trust the back-up anymore. Maybe some data of the apps became corrupt or something.
Btw perseus or redpill? what do you advice atm? both support the 64gb-micro sd cards right?
Click to expand...
Click to collapse
Yea its Painful to re do the entire process again , and also nice thought dont restore backup do a fresh install rather restore.

Trouble when attempting to flash back to stock

Hello everyone, long time lurker here.
I feel embarrassed even posting this thread in the first place but I'm currently flat out stumped. Over a year ago I flashed CM10 to my SGH-I747 using CWM (the whole process was done in a pretty outdated way, everything was basically manual) and a few months ago when I discovered cwm rom manager I installed cm11. I only ever used stable releases, never even thought about using a nightly.
Long story short after encountering the no service error I decided to try a nightly build for the first time ever. I had no problems after I installed it, functionality was just fine, but still the fact that my phone wouldn't save an APN was unresolved.
Today I decided that flashing back to stock and then reinstall CM using the app in the play store. After browsing this forum and youtube I foolishly used odin mobile to flash what I beleive is a stock version of android for my device. I got a normal starting animation (that annoying AT&T tun-tun-tun-tun with the words re-think possible show up like before) but it gets to this point where all I see is the word SAMSUNG in all white on my screen (it kinda has this glowing effect).
That's it.
First time I waited 30 mins and then pulled the battery. Restarted it twice more after waiting for the same amount of time.
The MD5 file I used came from file dropper. The URL after the dot com is /i747ucalemi747attalematt (sorry for posting this in a confusing way, I can't post links yet because I'm a noob).
Now when I boot my phone into recovery mode It says -
Android system recovery <3e>
Volume up/down to move highlight;
power button to select.
etc... the rest of the reboot/apply/wipe options
So... now what? Sorry for the giant explanation I just don't know what next step I should take. I wanna go back to stock, restore my data functionality, and properly set up CM using a rom manager. Thanks for taking the time to read this, I really appreciate any help you guys can offer.
P.S. I have the modem .zip for my carrier and I'm fine with using mobile Odin to install if I can just get normal functionality in my phone back.
What bootloader is on your phone? Did you try doing a factory reset from recovery mode?
Squerlli said:
Hello everyone, long time lurker here.
I feel embarrassed even posting this thread in the first place but I'm currently flat out stumped. Over a year ago I flashed CM10 to my SGH-I747 using CWM (the whole process was done in a pretty outdated way, everything was basically manual) and a few months ago when I discovered cwm rom manager I installed cm11. I only ever used stable releases, never even thought about using a nightly.
Long story short after encountering the no service error I decided to try a nightly build for the first time ever. I had no problems after I installed it, functionality was just fine, but still the fact that my phone wouldn't save an APN was unresolved.
Today I decided that flashing back to stock and then reinstall CM using the app in the play store. After browsing this forum and youtube I foolishly used odin mobile to flash what I beleive is a stock version of android for my device. I got a normal starting animation (that annoying AT&T tun-tun-tun-tun with the words re-think possible show up like before) but it gets to this point where all I see is the word SAMSUNG in all white on my screen (it kinda has this glowing effect).
That's it.
First time I waited 30 mins and then pulled the battery. Restarted it twice more after waiting for the same amount of time.
The MD5 file I used came from file dropper. The URL after the dot com is /i747ucalemi747attalematt (sorry for posting this in a confusing way, I can't post links yet because I'm a noob).
Now when I boot my phone into recovery mode It says -
Android system recovery <3e>
Volume up/down to move highlight;
power button to select.
etc... the rest of the reboot/apply/wipe options
So... now what? Sorry for the giant explanation I just don't know what next step I should take. I wanna go back to stock, restore my data functionality, and properly set up CM using a rom manager. Thanks for taking the time to read this, I really appreciate any help you guys can offer.
P.S. I have the modem .zip for my carrier and I'm fine with using mobile Odin to install if I can just get normal functionality in my phone back.
Click to expand...
Click to collapse
that's the stock recovery. try to wipe data/factory reset.

Need S4 Rom advice!

Hello! Pretty new in XDA forum and I have a couple of questions and concerns. I was browsing through some threads and I was wondering if I could get some opinion/help from other members.
I have a second phone that I want to mod and I need some help.
Device: Samsung Galaxy S4 (ROOTED)
Model#: SGH-M919
Android Version: 4.4.4
Baseband: M919UVUFNK2
It's an old phone and lately, it's been running really slow and if possible, I'd like to make it run as if it was brand new or at least somewhat close. So the question is, are there any recommended stable roms/mods I could use and if there are/is, will I be able to use it with my rooted phone or do I have to completely factory reset it before I apply the mods/roms?
Thank you!
Hi @Mr.LinK,
Just yesterday I finally got sick of my M919 slow/battery drain/old stuff and decided it was time for a reset. I was running SlimKat from over a year ago and while it was a great ROM, I had accumulated so much crap that it was getting really bogged down. This just happens over time no matter what OS, no fault to Slim. But I was also looking to move to Lollipop. Here's what I did:
1. Backed up using several methodologies (full backup with TWRP just in case, then from Android I backed stuff up with Helium, and used Backup My Mobile for SMS/MMS etc., an EFS backup just in case, etc..)
2. From within Android, did a factory reset. This sent the phone into recovery, and it formatted the data partition.
3. Rebooted to recovery again, and used TWRP to manually format the media section, just in case something was left there. Then wiped everything except the external SD.
4. Used ODIN to flash the OH3 firmware onto my MDL M919, without letting reboot after (unchecked the reboot checkbox). Pulled battery, rebooted back into download mode again, and flashed OH3 a second time... this gets around some instance people have reported about incomplete upgrades of firmware and all sorts of issues... better safe than sorry.
5. Let phone boot into now 100 % stock OH3 Android 4.4.4. YEEEUKKK. Some part of me thought I would just root the thing and get rid of Samsung crapware, but just the sheer annoyance of the T-Mobile boot animation was enough to remind me why I left stock long ago. Anyway, I let it boot, and set it up minimally with just 1 Google account, not restoring from backup. To my surprise it found the ATT network (I'm an ATT user, not T-Mobile... I just prefer T-Mo phones because they have unlocked bootloaders) and APN no problem no effort from me. Usually I have to enter an APN.
6. I tested the phone out to make sure all systems were working. GPS, WIFI, Bluetooth, etc.. To my surprise, first time I ran the camera app, it applied a firmware patch. Sweet. I'm glad I went through this step. Coming from ancient MDL, I figured there might be some kinks like this. I let it sit on stock for a few hours while I did stuff with my kids.
7. Back home, I did a factory reset from within Android. Then I flashed the latest TWRP tar file (2.8.7.0) using ODIN, and in TWRP did a full wipe of everything again.
8. At this point I flashed Danvdh's GPE edition of Lollipop from here.
http://forum.xda-developers.com/showthread.php?t=2539361
Installation went smoothly. It's a very basic set of apps that it comes with (Google play is there, but you have to download email/messaging apps from the store such as Gmail and Messaging, Maps, etc). I like this approach!
I've been gradually setting things back up, and am very happy with things so far. Haven't run into any problems yet. The nice pure GPE android experience is refreshing.
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Mr.LinK said:
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Click to expand...
Click to collapse
Good luck and let us know how it goes!
Frankenscript said:
Good luck and let us know how it goes!
Click to expand...
Click to collapse
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Mr.LinK said:
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Click to expand...
Click to collapse
I'm pretty sure we can change the reported model number by modifying the build.prop file. I just haven't poked around with it yet... I did ask the question in the thread and am waiting for a reply. I haven't had to do this kind of thing for over a year, and I forget the build.prop key that does it. But I had some concern that it might bork something else down the road so I decided to wait a bit. IT's just a cosmetic thing and I'm SOOO enjoying the experience right now.
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Still, these are all minor things to sort out. Really, I think I'm very sold on GPE editions now thanks to Danvdh's work.
Marc
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Mr.LinK said:
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Click to expand...
Click to collapse
Haven't seen random reboots. I think I got maybe one reboot since installing the ROM. Then again, I haven't put NF on the phone. I do know that Netflix app had some issues on my Shield tablet, and the manufacturer (Nvidia) came out with a patch... maybe it's something general in Lollipop?
Frankenscript said:
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Click to expand...
Click to collapse
Both if those can be fixed with Xposed modules.
Sent from my SGH-M919 using XDA Free mobile app
Will look into doing this in a week or so. Thanks
Sent back in time via Android 9.0 TimeText feature.

Categories

Resources