[Q] Help with my GT N5110? - Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti

Hello! It's my first post so I'm a little bit nervous.
Okay so a couple weeks ago I got myself a Galaxy Note 8.0 (finally). It's all shiny and fantastic and great. Yeah. But I noticed that if I clicked in a text field (be it a word processor, Google Docs, or a URL bar) it would take a lot of time to open the keyboard. Like a whole lot. Like I'd wait a good 30 seconds sometimes before it opened. And sometimes it would just not register keystrokes or lag a lot. Now I've had an S3, a Galaxy Tab 2 7.0, and a Galaxy Note N7000. None of them had this problem ever and they went through some serious wear and tear. This one out of the box was lagging. This is Problem 1.
I read online (didn't search too extensively) that this was a "ROM Issue" and loading a different ROM would fix the issue. My cousin also recently got a Note 2014 Edition (I don't know the model or anything), and said she'd read that simply updating the Android version would fix this lag. So I decided, hey, why not. I didn't know what it was updating to, but I hoped it wasn't 4.3 (which I updated to on my cellphone and did not like).So it updates all fine, but then I saw what I'd been dreading. My Google Talk had updated to Hangouts. I cannot stand Hangouts. Honestly if they changed one or two things about it, it wouldn't be bad. But Talk is a program I use frequently and I hate Hangouts. So here is Problem 2.
So since I gave myself a crash course on flashing due to having to get my N7000 unlocked and updated to ICS, I figured that I could do this easy before I go to bed at around midnight of February 10. It is now past midnight of February 10, and I haven't even flashed CWM on it yet (because I've read that rebooting it without directly installing a new ROM gets rid of CWM).
Problem 3? I'm unable to find a stock ROM of GTN5110. A "deodexed" (new term to me) version of one. I won't really use the root for anything on this, I think.
I know my limitaions at finding a ROM are due to the fact that I want a STOCK one and not a custom one. I'm biased. I think the stock is really pretty already and don't want to go changing it. Maybe one day I'll change my mind, but for now I just want stock. I'm kind of wishing on a whim that these stock ROMs will have Google Talk (Problem 2) and not Hangouts, and also that that lag issue is not present. I'm also not biased against going completely stock and flashing back to 4.1.2 which DID have Google Talk, except that I haven't been able to find any ROMs of THIS, either.
TL;DR
1. My tablet was laggy so I updated it
2. The update gave me Hangouts instead of Talk
3. I decided I'd flash CWM and install a stock deodexed ROM (or just a plain old stock ROM) with it but can find no such ROMs
So, community, I present you with two questions.
1. Is there anyone who can point me to a COMPLETE stock ROM for my N5110 (and as there are usually specific Firmwares and stuff, tell me how to find exactly the one I need by finding my PDA and stuff)
OR
2. Is there anyone who can point me to a DEODEXED stock ROM for my N5110 (firmware yadayadayada)
a. WITH Google Talk
b. WITHOUT Hangouts (And maybe if you're feeling generous, explain how to install a Stock APP so that I can HAVE Talk?)
Thank you!

Related

[Q] stock everything - screen freeze issue

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.

[Q] A Few Questions About New Nexus 7

Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.
happy4ya said:
Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.
Click to expand...
Click to collapse
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.
Aerowinder said:
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.
Click to expand...
Click to collapse
Thanks for all the info. So I definitely have the FLO model.
I would like to use Titanium Backup for Root and a few other things that need root access so I definitely want to do this.
Also, being that this tablet has no micro SD, I definitely want to have read-write access with a USB drive. I've had this for almost a week already and I haven't loaded anything into it yet because I figured I'd be wiping it. I really don't want to mess with stock because of the lack of a few things. I really just can't stand having devices with restricted use. That's not what I paid for.
I never used Kit Kat before and not sure if I'll like it. Do you know if you can go back to 4.3? I know with some of the other devices (like my Galaxy S3 phone), once you update it OTA, they lock stuff up and you cannot roll back.
Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.
happy4ya said:
Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.
Click to expand...
Click to collapse
You can roll back to 4.3. Google hasn't gone full Apple yet. But I strongly advise against doing so, as it's a large step backwards.
Understood on stock OS, agree no options anywhere. Slimkat+franco.kernel+banks gapps. You won't look back. Also in developer options, switch to ART. Dalvik sucks. If you're using Banks' minimal gapps, the lack of some syncing libs (for the AOSP calendar nobody uses) will cause random FCs until you reboot a second time. Nothing to worry about. Just grab the Google Calendar, or whatever calendar you use, from the play store and freeze the AOSP one with TiBu. Another FC you might see is gms.location. It should only happen once. Something with play services.
Once you are rooted, you can grab BetterBatteryStats to see what's killing your battery. On stock installs, it's mostly going to be location-based stuff keeping it awake. You already turned off reporting, but you also need to switch location mode to Device only.

[Q] Game refuses to run?

So I'm running into a wall on this.
https://play.google.com/store/apps/details?id=com.square_enix.ff7g_bike Updated a week ago to 1.2.0, and prior to that it would run fine (if a bit laggy at times). But since installing the update (required to play) it won't run. I'll tap on the icon, it'll load and show in the background with other running apps, but just won't run proper? I even updated to Android 4.4.4 cm-11-20141112-SNAPSHOT-M12-d2lte, from 4.4.2), used the Triangle Away app to reset things so the phone wouldn't appear to be custom/flashed, and still doesn't work.
I tested the update on a friend's S4 (un-rooted) and haven't had the same issue.
Is my phone (SGH-T999) just too old/no longer supported? The S3 is still on the device list: http://help.finalfantasy7-gbike.com/model but perhaps it wasn't updated.
So the last update to 1.4.0 at the end of April took care of the problem, which was great.
However..... they've updated to 1.5.0 today, and I'm experiencing the same exact problem I had prior to that update.
I don't know what to do, if there's anything that CAN be done.
Help, please.
Probably because you are using an aftermarket rom. Only thing I can suggest is to use a TouchWiz rom, or update cm. That zip is extremely old. Try the latest nightly. In case you didn't know, cm12 is available for the s3 under d2tmo in case you want to try it
It's possible.... so far unrooted/stock-rom devices are fine. However my friend let me root their S4 and that didn't cause an issue.
As for updating CM, I'll give that a try. I hadn't checked since March (and CM updater didn't give me any indications of a newer version oddly).
*edit* Ok I used TWRP 2.8.6.0 and updated to cm-12.1-20150614-NIGHTLY-d2tmo (along with gapps-5.1-2015-04-20-15-56-24), during the "Android is upgrading" screen (after a very long time on the CM splash) the phone rebooted.... currently back on CM splash screen... will edit in more details once beyond that screen.
*edit2* Past the CM splash, on "Android is starting".... optimizing apps 3 of 108.... and again with reboot.
*edit3* Again at "Android is starting" now optimizing app 198 of 199.... *fingers crossed*
*edit4* Finishing boot.... ok looks like I need to use a newer gapps... ok, updated to gapps-5.1-2015-06-02-15-19...
*edit5* Well everything appears to be working.... though the G-Bike game still won't load once updated to 1.5.0... it does at least switch to the horizontal position and the screen goes dark longer before returning to the homescreen... but that's about it. :crying::crying: Switching to TouchWiz may have no change either, correct?
*edit6* I've always used the default messaging app, but when I opened it it's seemingly stuck on "loading conversations", I read elsewhere that it may take a very long time to load if you have a lot of texts... which I guess given that one contact has 4,000+ texts saved in that thread, perhaps it's just a matter of time before all previous texts load?
A rooted rom shouldn't affect it. I mean aftermarket like cm or aosp. It could work fine on TouchWiz, especially since it's listed as a supported device. Yes, texts may take long time to load if you have many
Texts finally did load. I'm about to install CM on the S4, to see if the game no longer loads then. If that's the case, then I'll switch to TW on my S3 and hope that the game works afterwards.
Unfortunately I'm under a bit of some time constraint, the 1.5.0 update was for an event to gain a new support character, and that ends in exactly 1hr....
Given the time-frame, is there a "quick & easy" method to flash a TW rom without having to do various app data backups/nandroid backup (I will have to factory wipe, yes?), and not lose much/any data? I unfortunately don't have a high capacity SD Card (4GB, my 64GB one in the S3 stopped allowing write access a few days ago, seems to be an issue with that particular card), and 4GB isn't nearly enough to backup everything from the S3 to SD.
*edit* Well well..... 1.5.0 will not run on the CM rom on the S4!
You can back up to your internal memory. As long as you factory reset with custom recovery, you won't lose anything stored on it, except apps and settings
Great! One further question, is there any possibility that by switching ROMs, the game might think I'm on a different phone/new user (and if so, is there a way to fix this?)? Despite all the un/re-installs, I've never lost my progress most likely due to it being saved on their servers... but I'd hate to appear as a new user and lose month's worth of progress.
Yeah there's always that possibility. That's why you should always back up your apps with data so you can restore it in case
Thanks again. I wish I knew exactly what was being changed from version to version, that makes the game not work on an aftermarket rom. If it never worked from the beginning, that'd be one thing... but it's a yes/no/no/yes/no type of deal here. Shame I can't just take what works in the 1.4.0 version and compile it into the 1.5.0 ver... Or figure out what it's checking, and make it think it's a stock rom instead.

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.

[Q] Which CryanogenMod version should I use?

Hi all,
i need to reinstall my android phone (Galaxy W I8150) due to an error with google play. I'm currently running android 2.3.6 I8150XXLMI. While researching how to reset my phone i found CryanogenMod and this forum. Despite some basic knowledge on windows OS and how to reset them even after 4h of research im quite lost with the different possibilitys and methodes.
1) If i want to install CM which version should i use? (10, 11, 12.1?) Are there any advantages/disadvantages to the versions.
2) Is there a tutorial video you can recomend? I found several but as a complete newb in android moding, i can't judge how trustworthy they are.
Thanks in advance
Chris
I think that no one will answer you, so as fellow beginner user I'll write you a few suggestions.
There is an overview of i8150 ROMs which could be useful for you choosing one: http://forum.xda-developers.com/galaxy-w/development#romList
A few months ago I also decided to switch from factory installed to custom ROM, and very easily I got into troubles (soft bricked phone, here is my current situation: http://forum.xda-developers.com/galaxy-w/help/bricked-dead-upload-stock-rom-odin-t3294141). There are several MUST DO points in that process, so be very careful not to miss one, and be very cautious. Some ROMs are not compatible with some recoveries. There are several guides here which should be red first, so take your time, be patient. One of starting guides is: http://forum.xda-developers.com/showthread.php?t=1941028
And, stick to the i8150 guides/Q&A, you can learn there a lot about device specific issues.
Good luck!
The most confusing part about all of these is when you google. Why? Because you get all sorts of correct, wrong, out-of-date and downright useless, etc answers.
4h of research? I probably spent a lot more than 4 days. (so Ok, I'm slow ...).
With the latest apps, 2.3.6 is no longer usable. I jumped to 4.4.4 Kitkat, CM 11. There's some improvement in CM11, but it's also laggy as heck in other areas. An stability is also a question. YMMV. I installed an app to schedule reboot daily, and that helped noticeably. That kept going for a while, but the lagging problem became worse as I installed, and uninstalled, more apps.
Then I tried CM12. Guess what, gapps doesn't work. I don't care about all the other Gapps, but without Google Play, the smart-phone is useless.
And I went back to CM11. I suspect if you use only the basic apps and features, and make/receive phone calls/emails/whatsapp, it should work fine. So should CM10 and CM12. (without Google apps)
But I've also decided, I'm going to get a new phone.
Thanks, that helped a lot
anyone tried CM10?

Categories

Resources