[Q] Stockrom series v7.1 questions - Galaxy Tab 3 Q&A, Help & Troubleshooting

Hii there y'all! I've been lurking here for quite a while now and suddenly decided to become an active member of the community.
Partially because i've always been able to find what i'm looking for and to solve any issues i had with the info on xda here.
(awesome site btw)
Now though i've got myself a Galaxy tab 3 7.0 and was shocked to see it came with 4.1 so i rushed to xda thinking "Yeah right, 4.1.... I gots to get me some kitkat!" and.....
Well, lets just say i was less than overwhelmed.
Appearantly 4.4 is "coming soon" or something and 4.3 is conspicuously not spoken of. Sooo..... i Started looking for a rom that would at least allow me to do app2sd and did some flashes. Crashrom was aptly named i found and the LT02wifi rom scared the heebeegeebees out of me (turned out nothing more than a no boot animation bug).
Basically i came to find there is NO 4.2.2 ROM for this tab that doesn't have issues. I decided to choose the one with the least remaining issues and slapped Stockrom series v7.1 on there last night. Must say it went like a dream and the tab is noticably quicker. I've not yet installed any apps i want to app2sd so i haven't tested the purpose for which i started this endevour but i do have some oddities which i want to ask about.
One is that i get SM-T210R model number in device info. Second is that the status in device info states the batterystatus "not charging" while i do have it on the USB cable. I can confirm it charges as it went from 42 to 43% just now.
I have the much discussed bluetooth keyboard problem, in a sense. When i freshly coupled the device to the tab i could use it fine. Once that idle timer put the keyboard "to sleep" however it doesn't come back. It says it is connected but it isn't.
The last oddity is that the android version states 4.2.2 while the release notes state they went back to the 4.1.2 version.
Is there anything i can do to help solving that keyboard issue or is there already a fix?
Why is my SM-T210 suddenly thinking it has infrared (or did your h4xx0rc0d3z actually generate ir hardware somehow? ) and saying its an SM-210R?
Why is my battery "not charging" while it in fact is?
and who's wrong, my tab or the release notes, about 4.2.2?
If there is any way i can be of use, ask me, worst thing that can happen is i KILL EVERYONE ON THE PLANET!! HAR HAR har ha.....
(eeermm... ignore that last bit.. )

deuZige said:
Hii there y'all! I've been lurking here for quite a while now and suddenly decided to become an active member of the community.
Partially because i've always been able to find what i'm looking for and to solve any issues i had with the info on xda here.
(awesome site btw)
Now though i've got myself a Galaxy tab 3 7.0 and was shocked to see it came with 4.1 so i rushed to xda thinking "Yeah right, 4.1.... I gots to get me some kitkat!" and.....
Well, lets just say i was less than overwhelmed.
Appearantly 4.4 is "coming soon" or something and 4.3 is conspicuously not spoken of. Sooo..... i Started looking for a rom that would at least allow me to do app2sd and did some flashes. Crashrom was aptly named i found and the LT02wifi rom scared the heebeegeebees out of me (turned out nothing more than a no boot animation bug).
Basically i came to find there is NO 4.2.2 ROM for this tab that doesn't have issues. I decided to choose the one with the least remaining issues and slapped Stockrom series v7.1 on there last night. Must say it went like a dream and the tab is noticably quicker. I've not yet installed any apps i want to app2sd so i haven't tested the purpose for which i started this endevour but i do have some oddities which i want to ask about.
One is that i get SM-T210R model number in device info. Second is that the status in device info states the batterystatus "not charging" while i do have it on the USB cable. I can confirm it charges as it went from 42 to 43% just now.
I have the much discussed bluetooth keyboard problem, in a sense. When i freshly coupled the device to the tab i could use it fine. Once that idle timer put the keyboard "to sleep" however it doesn't come back. It says it is connected but it isn't.
The last oddity is that the android version states 4.2.2 while the release notes state they went back to the 4.1.2 version.
Is there anything i can do to help solving that keyboard issue or is there already a fix?
Why is my SM-T210 suddenly thinking it has infrared (or did your h4xx0rc0d3z actually generate ir hardware somehow? ) and saying its an SM-210R?
Why is my battery "not charging" while it in fact is?
and who's wrong, my tab or the release notes, about 4.2.2?
If there is any way i can be of use, ask me, worst thing that can happen is i KILL EVERYONE ON THE PLANET!! HAR HAR har ha.....
(eeermm... ignore that last bit.. )
Click to expand...
Click to collapse
U had problem with my LT02wifi rom? What was the issue?
Sent from my Galaxy Nexus using Tapatalk

Related

TP2 Android biggest disapointments... ---> BATTERY METER

Very very thankyou ppls for your hard work... i really appreciate the hard work of the devs.. but can some1 tell me that when the battery metter is fixing.....i only bought this to use android on it but due to unstable battery indcator i m not able to properly get the fun of android on this device.....seriously i have no intrest to use winmo..i liked the keyboard and read that its android compatiable so i bought it .... i know some ppls will say that go buy something else ..... all i need is battery fix and i think many of the ppls here will agree with me....well i for me i m w8ing more 15 days to see if the proper battery fix appears then i will continue it else i will go for Motorola Milestone...i m not saying that these ppls are not working .. all i m saying that all we need is a battery fix with Wifi
w8ing for the ppls opinions
Thanks
honestly man, whats the point of this post? The devs know whats working and what isn't and I'm sure they're working on fixing and improving things. The fact that you can even boot up and run Android on a Windows Mobile phone shows the dedication and work they've put into this so far, its just a matter of work and time until everything is working, have faith and wait it out
dont be surprised if u start gettin some negative responses.
first off, the battery fix wrks great and is very accurate. there must b something u not doing right. i even posted my initial battery readings in the thread with this new build. actually the battery fix is almost dead accurate. i got 8+ hrs. outta of it yesterday. with overclock, with constant use. so nonoverclocked build will probaly bring even longer use.
second, wifi wrks perfectly.
third, why would u buy a device just to run a project build then if u wanted everything wrking? i understand the keyboard thing but unless u got ur device on a good ass deal, kind of silly to buy it just to run something not even fully completed yet. come on now.
Fourth, b4 u bought ur device, did u thoroughly read everything going on with this build or u just jumped in head first?
this is why so many people getting flamed cuz they dont do the research or homework. then come on here posting about why this or that isnt wrking. or what ASSUMPTIONS they have.
dont take this post the wrong way cuz this will probaly be one of the nicer posts towards u. lmfao juss way too many people jumping in and complaining when they wouldve already known the known issues with the build. which in ur case is incorrect. there has to be something u did wrong.
these are questions to ask self why batter fix and wifi not wrking for u.
Am i using the latest builds? Did i thoroughly follow instructions on installing it? Did i install the build with the battery fix in it? Did I break my battery fix by updating the zImage and modules?(which will break the battery fix). if thats not the case, then, Did i update the latest roofts and inirtd files? Did i even troubleshoot the problems b4 posting saying they dont wrk? lol
im not trying to sound like a dckhead..lmfao but im sure the developers would say the same thing basically.
they might have to implement what they doing on the other threads now. if u dont have a certain number of posts, then dont download and try out builds with doing the research first. a moderator stepped in and said that. cuz way too many people complaining about stuff thats already known or complaining about stuff that wrks but they didnt do it correctly.
food for thought, try the latest build. then DO NOT UPDATE THE ZIMAGE AND MODULES AFTERWARDS. only update the roofts and inirtd files.
if u need help getting it running right, let me know. ill be more thn happy to help or assist u, seriously. srry to sound cranky, just woke up n stressed about other things in life..lol
good luck
jamb said:
... all i need is battery fix and i think many of the ppls here will agree with me....well i for me i m w8ing more 15 days to see if the proper battery fix appears then i will continue it else i will go for Motorola Milestone...i m not saying that these ppls are not working .. all i m saying that all we need is a battery fix with Wifi
w8ing for the ppls opinions
Thanks
Click to expand...
Click to collapse
What the hell is the point of this post? Can we lock this thread, please?
@demandarin
1st i was prepaired for the negative response..
2nd... right now i m testing the new 2.2 froyo beta build as stock no overclocked no thing just extract to mc... and testing while calling / messing with it...very much stable rather then old builds :d.....very much stable /nice reponse / no battery warming(which i was worried of) / no force close atleast now.. / played assassin creed and many thing works preety nice.. wel right now i have'nt use wifi or data roaming /
3rd..well i got 2 options 1 was TP2 and 2nd was Motorola milestone ... well i dont like to milestone keyboard but i forgot that it was way slimmer then tp2 / also compatiable with new builds by defualt...well i was tp2 in local market then came to xda and saw the thread about android and just go for it.. as seeing the progress i thought that it will be fixed soon...now i cant tolarate windows-mo anymore just want to go to the android again asap...so i started this thread...
4th well i readed all the faqs / tips everything before buying tp2...like 50%
well its cool , its nice to get a proper postive feedback from a geek :d wel i will defenately ask for help from u if i came across with anything which i will not able to understand..
Thankyou
jsmith8858 said:
What the hell is the point of this post? Can we lock this thread, please?
Click to expand...
Click to collapse
the point of this post is to know about battery fix.. because i think its damaging the battery...because while turing on the android the led indicator turns on and battery start heating-up sorry dont sound to be rude but please if u cant help dont bother to post you will waste your time...
Would you all kindly stop being illiterate? English words are made of letters not numbers.
On topic, jamb, you could have dropped the silly threats (Imma buy another phone) and just asked the question.
Considering this phone wasn't intended to even run android..... and you bought it without clearly reading through and seeing what was working and what wasn't... yeah I can see peoples frustrations with your question.
Your best bet, as I'm sure you know, if you wanted a perfectly working andoid phone was to buy one that was designed for it OR at least play with someones touch pro 2 who has android running on it so you would know what to expect.
It's called development for a reason, its still on going and there is still a LOT of work to be done and no one knows time frames on this. It's like asking when we're going to mars (all be it that might be a very dramatic example)
Regarding the battery. As was discussed... there is a fix and if it isn't working for you then you aren't doing something right. It's accurate and thats all anyone can hope for. As far as becoming warm. Well it probably has something to do with what you are using on your phone. Internet, GPS, etc etc... all at once. overclocking it is a big culprit for the warmness of phones. The more you tax the phone the more it will become warm.
It wont 'ruin' your batter by using the phone... Just be patient and understand that these fixes could come out tomorrow or could never come! Just what it is.
Considering this phone wasn't intended to even run android..... and you bought it without clearly reading through and seeing what was working and what wasn't... yeah I can see peoples frustrations with your question.
Your title isn't so much directed at andoid as it is the people who spend hours and hours and hours developing a working version for our phone. So, yes it can be taken as being insulting, with that people are going to see this post and think "who is this guy?"
Your best bet, as I'm sure you know, if you wanted a perfectly working andoid phone was to buy one that was designed for it OR at least play with someones touch pro 2 who has android running on it so you would know what to expect.
It's called development for a reason, its still on going and there is still a LOT of work to be done and no one knows time frames on this. It's like asking when we're going to mars (all be it that might be a very dramatic example)
Regarding the battery. As was discussed... there is a fix and if it isn't working for you then you aren't doing something right. It's accurate and thats all anyone can hope for. As far as becoming warm. Well it probably has something to do with what you are using on your phone. Internet, GPS, etc etc... all at once. overclocking it is a big culprit for the warmness of phones. The more you tax the phone the more it will become warm.
It wont 'ruin' your batter by using the phone... Just be patient and understand that these fixes could come out tomorrow or could never come! Just what it is.
My battery meter seems to be working just dandy. I did a test yesterday and it was dead on. When in Android I looked at the battery meter and it was about 3/4 full. I opened spare parts and it was at 64%. I then rebooted the phone into WM (6.5, energy ROM) and opened tbattery and it was at 64%
I chared my phone to 100% yester afternoon around 5pm and after heavy use; 5 minutes twitter updates, constant facebook, automaticl gmail check, and non-stop text, I'm still sitting around 50%.
The work they are doing is awesome.
Sent from my MSM using XDA App
Any battery meter needs to have several complete charge/recharge cycles to be completely accurate (charge phone to 100%, drain until it powers off by itself, repeat at least 3 times). So I would think Android on the TP2 is no different.
Anyway, if the OP got the message that the TP2 is "Andriod compatible", that that was the wrong impression, or at least an overstatement. This is an ongoing project. Given, one where some great folks are putting in tons of work and doing a wonderful job (and much appreciated). But its not perfect, and not the same as a phone which natively runs Android. If that was the OPs intent, then big mistake and he should have done more research before buying.
And its always been posted that the battery meter has issues. I don't know how he could puurchase a TP2 for android and didn't even read the 1st post of the thread.
Sent from my MSM using XDA App
Anyone tried buying those larger batteries off ebay? I saw one that's lager but isn't larger in size where you'd need a new back case.
How much difference is 1800mAh compared to 1500mAh anyway? Another hour of life?
Aaron McCarthy said:
Considering this phone wasn't intended to even run android..... and you bought it without clearly reading through and seeing what was working and what wasn't... yeah I can see peoples frustrations with your question.
Your best bet, as I'm sure you know, if you wanted a perfectly working andoid phone was to buy one that was designed for it OR at least play with someones touch pro 2 who has android running on it so you would know what to expect.
It's called development for a reason, its still on going and there is still a LOT of work to be done and no one knows time frames on this. It's like asking when we're going to mars (all be it that might be a very dramatic example)
Regarding the battery. As was discussed... there is a fix and if it isn't working for you then you aren't doing something right. It's accurate and thats all anyone can hope for. As far as becoming warm. Well it probably has something to do with what you are using on your phone. Internet, GPS, etc etc... all at once. overclocking it is a big culprit for the warmness of phones. The more you tax the phone the more it will become warm.
It wont 'ruin' your batter by using the phone... Just be patient and understand that these fixes could come out tomorrow or could never come! Just what it is.
Click to expand...
Click to collapse
1st well i completely readed the faqs that which things was working and which r not ..when i was going to buy new fone i was damn excited that the great devs make it happen to run android on TP2 and because i liked the keyboard and android compatible i thought that battery fix will come soon ... i got no interest to use winmo ..now i m fedup with winmo and just want to switch to android completely thats y i just asked for the battery fix.i m not forcing them to make it for me..just asking
2nd well i got 2 options motorola milestone(totally android ) or htc tp2 .. i was not into motorola devices so readed about tp2 is compatible ..well in my country only 5 or 6% ppls use other brand otherwise the remaining ppls use nokia or samsung so i wasnt able to use tp2 before the only option i got was to use it personally .....
i know that many many works need to be done...
well i readed about the fix but it is working without wifi and as i said earlier , i know its sound mean but all i need is battery fix with wifi...well as for battery warming without internet , no gps , no overclocking , no nothing just used with its original files it was just lying on my table and when i put it into my pocket i can feel that the battery is warming up so i have to restart the fone to switch back to winmo...
Your best bet, as I'm sure you know, if you wanted a perfectly working andoid phone was to buy one that was designed for it OR at least play with someones touch pro 2 who has android running on it so you would know what to expect.
Click to expand...
Click to collapse
well thankyou for ur help ... i really liked your suggestion so within 2 or 3 days i will switch to motorola asap....
Thankyou
1jaxstate1 said:
My battery meter seems to be working just dandy. I did a test yesterday and it was dead on. When in Android I looked at the battery meter and it was about 3/4 full. I opened spare parts and it was at 64%. I then rebooted the phone into WM (6.5, energy ROM) and opened tbattery and it was at 64%
I chared my phone to 100% yester afternoon around 5pm and after heavy use; 5 minutes twitter updates, constant facebook, automaticl gmail check, and non-stop text, I'm still sitting around 50%.
The work they are doing is awesome.
Sent from my MSM using XDA App
Click to expand...
Click to collapse
i know they done an awesome job ... i simply love this forum...
redpoint73 said:
Any battery meter needs to have several complete charge/recharge cycles to be completely accurate (charge phone to 100%, drain until it powers off by itself, repeat at least 3 times). So I would think Android on the TP2 is no different.
Anyway, if the OP got the message that the TP2 is "Andriod compatible", that that was the wrong impression, or at least an overstatement. This is an ongoing project. Given, one where some great folks are putting in tons of work and doing a wonderful job (and much appreciated). But its not perfect, and not the same as a phone which natively runs Android. If that was the OPs intent, then big mistake and he should have done more research before buying.
Click to expand...
Click to collapse
mate i already did these things like i charged the fone 100% in winmo then switched the android after using for a while like calling for 2 or 3 minutes and some txt msgs and fone pop-up opens of charging the device.. i know its not perfect .. i didnt asked for every fix and i do alot research before buying the device. i spend 2weeks searching about tp2 and android.... and for now all i can say is
I LOVE THIS FORUM AND THEIR HELPING PPLS
I LOVE THE DEVS HERE FOR THEIR AWESOME WORK
AND I M SWITCHING TO MOTOROLA MILESTONE(COMPLETELY ANDROID )because i was tired to use winmo...
1jaxstate1 said:
And its always been posted that the battery meter has issues. I don't know how he could puurchase a TP2 for android and didn't even read the 1st post of the thread.
Sent from my MSM using XDA App
Click to expand...
Click to collapse
i know i know i know ...... i readed the faqs / complete post about .... i purchased the device just for its keyboard after blackberry 9700 i liked this device keyboard and android compatible i thought i going to be fun to use this device...Happy now???
Mods i got my answers and want to close this Thread
Thankyou
Might want to give this a read:
HTC Vision with Android, full QWERTY in the wild
Aaron McCarthy said:
Might want to give this a read:
HTC Vision with Android, full QWERTY in the wild
Click to expand...
Click to collapse
thanks mate but its in rumors i think it will release Q4 2010 or Q2 2011... and i dont have that much time ... just fedup with this winmo....android is far far better then winmo

[Q] Boot loop problem

Hi, I have a few questions I hope you can help me with?
My wife has a galaxy nexus, stock and unrooted. It is only around 6 weeks old and last week it started crashing, turning off then getting stuck in a boot loop just displaying the starting colours. I understand this is a known problem, she has software version 4.0.2 and it says her phone is up to date.
I "fixed" her phone once with a factory reset however this time she is away with work till Friday and now has no use of her phone or contractual minuets or data ect.
To make things worst she was planning on using the sat nav and wireless tethering to her laptop. It is the second time this has happened and she has lost all faith in her phone. She can maybe upgrade the software by downloading the 4.0.4 software but she/I don't see why she should have too. She just wants a phones that does what it says on the tin without needing to mod or mess around with it.
My questions are...
Is this problem enough for her to exchange the phone for another phone all together, she fancies a One X. Has anyone here managed to exchange the phone for this reason?
If not will updating the software to 4.0.4 fix the issue for sure? She really needs a reliable phone. Maybe it will be best to send it back under the warranty but we are afraid she will get another GNex with the same issue.
Any advice will be much appreciated
Sorry for the long post and thanks for reading,
Oliver
I would just try updating it and then wipe it. If that doesn't fix the issue it's most likely a hardware issue and I would warranty the phone.
Sent from my Galaxy Nexus using xda premium
Hey there,
Well first I would suggest calming down and not reverting to hardware issues just yet, Bootloops are pretty common, especially when using phones which were meant for the (a bit) more advanced user, it's advantage is also it's flaw, being a modding monster that it is..
And this is by no means a flame - but I wouldn't want my wife to have a GN for that exact same reason, yes - she knows about flashing roms and stuff, but she needs a reliable phone, that will work and do what she needs it to do and nothing more, as opposed to me, I like to mess around a bit with my phones (also not that much, I plan to stay stock with my GN).
To your question, I don't have any experience with RMA's but it maybe worth a try.
You also mentioned she fancies the one-x.. that means she wasn't really keen on buying the GN in the first place (I believe).. and also - and don't take this the wrong way - I think she\you don't really know what the GN is all about, this isn't a phone for everybody, I mean - it is, but it's a shame to see it fall into hands that do not appreciate it for what it is, think of it as a nice new Ferrari, sure - it'll get your wife to work But she is not going to the Nurborgring to time her laps with it.. she'll complain that once in a while the clutch is too sensitive and that she cannot count on the car to take her to work every day, and that she really fancies the new Volkswagen beetle... you get my drift
Also - I believe that flashing to the 4.0.4 will sort the bootloops, which usually has everything to do with the kenrel.
Best of luck!
p.s. All of the above is said in a humoristic way!
omricn said:
Hey there,
Well first I would suggest calming down and not reverting to hardware issues just yet, Bootloops are pretty common, especially when using phones which were meant for the (a bit) more advanced user, it's advantage is also it's flaw, being a modding monster that it is..
And this is by no means a flame - but I wouldn't want my wife to have a GN for that exact same reason, yes - she knows about flashing roms and stuff, but she needs a reliable phone, that will work and do what she needs it to do and nothing more, as opposed to me, I like to mess around a bit with my phones (also not that much, I plan to stay stock with my GN).
To your question, I don't have any experience with RMA's but it maybe worth a try.
You also mentioned she fancies the one-x.. that means she wasn't really keen on buying the GN in the first place (I believe).. and also - and don't take this the wrong way - I think she\you don't really know what the GN is all about, this isn't a phone for everybody, I mean - it is, but it's a shame to see it fall into hands that do not appreciate it for what it is, think of it as a nice new Ferrari, sure - it'll get your wife to work But she is not going to the Nurborgring to time her laps with it.. she'll complain that once in a while the clutch is too sensitive and that she cannot count on the car to take her to work every day, and that she really fancies the new Volkswagen beetle... you get my drift
Also - I believe that flashing to the 4.0.4 will sort the bootloops, which usually has everything to do with the kenrel.
Best of luck!
p.s. All of the above is said in a humoristic way!
Click to expand...
Click to collapse
Thanks for your post.
My wife wanted to upgrade her htc desire to a faster phone with bigger screen, she loves android and Google products and the Google nexus seemed like the best choice at the time (b4 the one X was released) she loved the phone till now.
The phone has twice randomly gone into a boot loop and twice we managed to get it working again both times within the week. This has caused her to lose faith in the phone. I guess the update should fix the issue but it doesn't seem to be available on her phone just yet.
A basic phone would not be enough 4 my wife, as I said in my first post she uses it to connect her laptop to the Internet and as a satnav. Also she watches youtube videos (720p screen is handy here) and for facebook.
We never had any such issues with our desires. When my wife returns home we will update her phone via pc if it doesn't void warranty (I'm sure it won't ) and hopefully the issue will be fixed for good.
Sent from my HTC One X using xda premium
Sounds like our wives can get along my wify loves her htc desire hd! and to be honest, in my opinion in many ways it's much better than the sensation I had (stock).
And by what you described, if I was your wife (lol ) I'd also go for the GN.. I trust you know how to upgrade to 4.0.4, if you need any help just say so and I'll be more than happy to help
Also - from what I know upgrading will not void you warranty, you can simply lock the bootloader once you're done upgrading if you wish.
I really wish the bootloops will stop and that you wife will continue to enjoy her GN!
Hi again
I unlocked, rooted and installed Android Revelution HD 3.0.0 (based on 4.0.4) by mike1986 on her phone.
She is happy with her phone again.
Now it's rooted she likes the extra apps she can now install like AdFree.
I have a quick noob question though..
After installing the new rom her phone it said their is an update available. I understand that she should NOT accept over the air updates now she has a custom rom, and is that right?
Cheers, Oliver
Sent from my HTC One X using xda premium
Hey Oliver, sorry.. seems I didn't get subscription notifications on your reply...
anyway, she "can" download the update, but it will not install, it will simply give an error upon installation, the reason is the original files that the update needs to update are not there anymore, or they are but have changed, so it will just give an installation error.. that's the only downside to having a custom rom. me personally - I like mine stock at the moment
Just a quick update, I rooted, s- offed and install Arhd rom on my wife's gnex.
She says her phone is running faster/smoother than ever and has not restarted since. It's running great and she is happy again
Sent from my HTC One X using xda premium

[Q] Nexus 7 owners...... problems, fixed or not?

Guys, I was all set to get a new 32gb Nexus 7....the reviews are great, and then I start reading about the issues.
After a bit more reading, I'm left wondering if its such a good idea? I read that Google released an update, then I also read that it didn't always fix things for people?
So the questions I guess are, Do you own one? Have you had a problem? Is it now fixed by the update? Maybe you've never had any problems?
Would you recommend getting one? I don't wanna spend out on something that I'll regret.
Thanks guys.
I've had mine since the first weekend of availability and it's lived up to all my expectations and then some, you're just buying the usual support vocal minority, sume have legit issue, noisy are just being nitpicky
Sent from my HTC One using Tapatalk 4
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Thanks for your reply.
Mine worked 100% out of the box, no light bleed, no multi-touch issues, no GPS issues. Updates have installed perfectly. I am running stock deodexed + root + TWRP + Elemental X 1.1 Kernel. Couldn't be happier with my purchase. :good:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
madpete said:
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Click to expand...
Click to collapse
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
I bought the 32gb. Works flawlessly, I got it a week and half ago.
Sent from my Nexus 7 using xda app-developers app
GET ONE
I would say go for it, you are always going to have issues with most anything. Just buy from a retailer with a good return policy, I own the nexus 7 2012 and the nexus 7 2013 , no issues here, awesome devices.
Thanks guys. Sfhub, you make some good points....think I will buy from a large high street store, rather than online.
Sent from my GT-N7100 using XDA Premium 4 mobile app
sfhub said:
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
Click to expand...
Click to collapse
i think mine is definitely, hardware, maybe , cuz of user error, ie, bad dirty flashing of zips, i dont' want to start all over fresh again, too many apps/settings to revert back (yes call me lazy sob)
most of the reboots happen when im clicking on an app with wifi on , but one of my last reboots, it just just rebooted out of the blue, i didn't even touch the tablet, but i seen it reboot!
Not sure, really, whether I have/had problems or not. Got mine over the weekend. During my initial playing, I did not notice any touch issues. The GPS would lock, but I didn't have time to take it anywhere for long enough to be sure if it would stay locked for a long period of time. Almost immediately (1 day) I got the JSS15Q OTA update. The GPS DOES seem to lock a bit faster, and I seem to be seeing more satellites than before -- it could be my imagination, though. Still no touch issues that I can see.
New Nexus 7 (then) past issues, (now), Cool TAB!
phab3k said:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
Click to expand...
Click to collapse
I HAD issues out of the box. Waited for the first update from Google, rebooted once after. Took forever to get the screen to respond to any kind of tap. Rebooted a couple of times and was able to get somewhat R E A S O N A B L E response out of the screen. GPS would work for all of 2 minutes and then shut down. No problems with Wi-Fi.
That was then, along came update: JSS15Q! All is happy in Nexus land. GPS is strong and works flawlessly even in the darkest center of my house! Screen is responsive my fingers are happy.
APPS? That is another matter, remember, even with a stock Nexus 7 fhd you are on the bleeding edge meaning that many apps found on Google Play may fail. Live with it until either the app is updated, ***** at the (no don't *****, contact the developer and kindly tell him/her your problem; or find another app that works for now.
Games? Heh, that is a real crapshoot. If it won't function, move on.
This is one hell of a tablet with excellent video, good sound, fast processing. Short of it not being the size of my 60" monitor (TV) I can read everything with these 78 year old eyes!
[email protected]@dog!
Google Nexus 7FHD
Kindle Fire Rooted Android 4.3
Kindle Fire HD 8.9 Rooted 2nd boot loader Android 4.2.2
Droid Bionic stock Android 4.1.2
Guys, just wanted to say thanks for all the posts. You help me make up my mind, and gave some sound advice.
I've took the plunge and brought the 32gb model (from a big high street retailer), and I have to say....what a cracking little tablet this thing is, I am really impressed with it. I have not had any issues with it, so I seem to be one of the lucky ones....either that or they have fixed the issues by the time we got them in the UK.
I do feel for all the people who had problems though, its a nightmare when these thing happen. Theres no doubt there has been or are some issues out there, one thing with a Nexus device I guess is it is patched fast if its sw...obviously hw is a different issue.
Looking forward to enjoying this device now, if I can get on it....have to wrestle it off the wife and kids first!
......thanks again guys.
Pete.
Just got my 32gb Nexus today in the UK. Only thing I have noticed is that tap and hold on screen is slow to react. Can take a couple of trys before it works. Sometimes taping an app is slow to open. Running stock and latest update. Only change made is to use Nova as the launcher.
Sent from my HTC One S using Tapatalk 4
To Wugfresh Re: Toolkit
This is a followup to my 2 confusing Twitter's I made it worse by referencing Nexus 4 and 7 so I will stick to 7 (mostly). I now realize that lurking has its penalties since I need 9 posts after this before I can post this in the relevant thread (with a nostalgic tear for the days we welcomed all comers and left our doors unlocked).
I bought an N7 FHD (2nd gen) and rooted it after the 4.3 auto update soft bricked (right term of art?) it. I used the other toolkit to restore it to JDQ39 factory unrooted. Then it installed JSS15J. Today it tried to do an update and (presumably) it failed because of rooting. That build is no longer on the developer's website and has been replaced by JSS15Q. I would never presume to call myself a developer but my first modem was a 300 baud acoustic coupler and I have a 5 1/2" floppy disks older then most of you and it's actually floppy. ROFL.
Back to reality, on the Nexus 4, I could not discern how to upgrade to the latest Y build but I did manage to restore it to factory settings and Google handled the rest, You were kind enough to add JSS15J to your toolkit for the Nexus 4 but it is not available (in your drop-down) for the Nexus 7. I figured that if you made JSS15J available for the N7 I could restore the N7 to a factory fresh un-rooted one and Google could update it to JSS15Q. In the alternative you might guide me to how I could go from JSS15J to JSS15Q. I am certainly not in your league but this is not my first rodeo and I cannot tell you how grateful I am for your efforts. Your toolkit saved my Nexus 4 from the 2 week wait during which Google might have told me rooting voids the warranty or just have left me phone-less till they returned it.
Again thank you especially, and to all the others here who light candles in the darkness for each other and the rest of us pilgrims. A tip of my fedora to ya. Never forget one definition of a pioneer is someone with an arrow in their back.
Much of the time I am as confused as a baby in a topless bar who said, "What do you mean this is not a lunchroom, what else could it be?"
My suggestion is to keep root, grab the latest carbon ROM, the elemental 1.1 kernel and you should be all set. They already have the updates From G in them and they work superb.
Sent from my Nexus 7 using Tapatalk 4
Do you own one?
Yes, from day one.
Have you had a problem?
Yes, GPS and the touchscreen grounding issue.
Is it now fixed by the update?
Yes, GPS seems fixed.
No, grounding issue may be worse. Works fins as long as I'm holding it. Placing it causes touches to become sporadic.
Maybe you've never had any problems?
I wish...
Would you recommend getting one?
Yes, it still a FANTASTIC device and many have no issues. If you do return it right away until you get one without issues.
I spoke too soon....at first I thought everything was ok....then I began to notice when I was typing that sometimes it would come out as gibberish. I thought nothing of it as we all make typos now and then, then I noticed that press and hold didn't always register (sometimes takes a few goes). I downloaded the multi-touch test from play and to my horror it's all over the place (compared it against my note 2), this is with the latest update. After reading around a bit more, I'm beginning to think these touch screen issues are hardware....and that it's more widespread than people think. Will be exchanging it for another one, hopefully fair better second time.
Sent from my GT-N7100 using XDA Premium 4 mobile app
madpete said:
Will be exchanging it for another one, hopefully fair better second time.
Click to expand...
Click to collapse
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
sfhub said:
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Hey man, thanks for the reply.
I opted for the swap out because I don't want to loose the warranty, which I believe you would if you unlocked it?
I bought from PC World / Currys so the swap was no hassle.
Using the new one now, its testing better and typing and "hold and drag" is working much better (although hold and drag still isn't 100%, it's now acceptable to me).
I tested before and after the update, the observation I made is that the update seems to dull down the touch screen a little. It became slightly less responsive after the update than before, but hasn't really affected the usability on this one....although I think I prefered it pre update.

Help needed to upgrade a Note 2 that was lost for 2 years.

I bought an unlocked Note 2 in the summer of 2013.
I happily used it until Christmas when it 'disappeared' in our house. My toddler daughter had hidden it somewhere.
Despite turning the house upside down it was never found and I reluctantly moved backwards to older phones I already had.
Nearly 2 years later and a builder found it hidden away in our spare room.
I know have my phone back which has been in hibernation for 18 months. It is running 4.4.1 and my question is this.
Despite it now being old I would like to upgrade the firmware to the best I can for the device without it slowing down. Please can someone recommend an upgrade and where I can find it. Phone is not rooted so will I have to do this?
Thanks in advance for your time.
There is no 4.4.1 for the note?
Sent from my SM-N910C using XDA Free mobile app
tomhirvin said:
I bought an unlocked Note 2 in the summer of 2013.
I happily used it until Christmas when it 'disappeared' in our house. My toddler daughter had hidden it somewhere.
Despite turning the house upside down it was never found and I reluctantly moved backwards to older phones I already had.
Nearly 2 years later and a builder found it hidden away in our spare room.
I know have my phone back which has been in hibernation for 18 months. It is running 4.4.1 and my question is this.
Despite it now being old I would like to upgrade the firmware to the best I can for the device without it slowing down. Please can someone recommend an upgrade and where I can find it. Phone is not rooted so will I have to do this?
Thanks in advance for your time.
Click to expand...
Click to collapse
Good news that you found your phone. Probably your firmware is 4.1.1 and not 4.4.1 because 4.4.1 not exist and also you have to update this firmware immediately because of sds bug. If you don't know about it Google it. There are plenty of roms at forum and also plenty of instructions how to flash a custom rom and also how to update at latest official if you don't prefer custom.
Sent from my GT-N7100 using Tapatalk
Thanks for your reply Vagsvag. Just checked and it's running 4.4.2. I think it automatically upgraded something when I turned it on and logged in for the first time (sorry I'm not very savvy). In your opinion will this suffice or is there a newer platform I can safely download. I did a cursory bit of research on Google and it looks like 'Android L' is the last one offered for the Note 2, but I couldn't see if it was ever confirmed. I'll do some more research on here. I'd rather not load up a custom rom as when I did that to my last phone (S2 and the Lite'ning Rom) the phone became very glitchy. Perhaps things have improved in the last 5 years.
tomhirvin said:
Thanks for your reply Vagsvag. Just checked and it's running 4.4.2. I think it automatically upgraded something when I turned it on and logged in for the first time (sorry I'm not very savvy). In your opinion will this suffice or is there a newer platform I can safely download. I did a cursory bit of research on Google and it looks like 'Android L' is the last one offered for the Note 2, but I couldn't see if it was ever confirmed. I'll do some more research on here. I'd rather not load up a custom rom as when I did that to my last phone (S2 and the Lite'ning Rom) the phone became very glitchy. Perhaps things have improved in the last 5 years.
Click to expand...
Click to collapse
4.4.2 is the latest official, for newer version of Android you must go to custom rom, cm or aosp, there are also some roms transfered from official s3 firmware android version 4.4.4. My opinion is if you are ok with speed, response etc stay with this only root it to remove junk apps and block the ads. Now if you want something little bit more fresh you can try cm base, one of the more stable is Ivan_Meler's cm 12.1 at original android forum.
Sent from my GT-N7100 using Tapatalk
Thank you for all your help. I've rooted the phone which seems to make everything quicker. I'll stick with 4.4.2 for now but will have a look at CM12.1 at some point.
Ivan Meler CM 12.1, Best ROM so far. Whenever you plan to get in the CUSTOM ROM Zone !!!

Weird freezes, not sure how to troubleshoot

I'm not sure if it's a software problem or a hardware problem that's not the motherboard.
This is my phone's original stats, as I have written down.
N7105
ROM: DN3 v3.2
kernal: AGNi v3.9
bootloader: 4.1.2
Recovery: Philz 6.07.9
The problem is that the phone just randomly stopped waking from sleep. Not all the time, but it just started one day and slowly increased in frequency. I eventually figured out that the phone was simply not waking up, causing the phone to (presumably) freak out, because if the freeze happened hours ago, then the phone would be very warm when I picked it up and, after forcibly rebooting via the power button, the battery would be way down.
I noticed IndexServices was using a lot of battery power, and google tells me that it freaks out at files over 200mb in size, but best I can tell, I have no such files. I can't recall anything that would change this when the freezes started happening. It may not be relevant at all.
I could live with the forced reboot for a while, but having my battery capacity killed for no reason sucked.
Screw this, I thought, I have a spare motherboard, I'll figure out the problem later or never.
Nope.
My phone's current stats.
SGH-t889
ROM: DN3 5v2 final slim
kernal: default
bootloader: 4.1.2
Recovery: TWRP 2.8.0.0
I swapped the motherboard in and used Titanium to restore my most-used apps and their data. Unfortunately, the problem seemed to have followed the change, although in a different way. The phone just freezes and doesn't accept any kind of input- no touch, no buttons, nothing. I have to pull the battery to reboot. It doesn't just happen when asleep. I've had the phone literally just stop responding as I was scrolling through a webpage. It seems to happen mostly at night and early morning, which is no bueno. I can't use it as an alarm anymore. But it's still better than leaving it alone only to find the battery down 40%.
It also occasionally reboots on its own. I haven't found a pattern to any of these problems.
I played with this motherboard when installing the ROM and such and never had the above problems, so it may or may not be related to the problem I had with the other motherboard.
It's not my SD card. I pulled it when I still had the N7105 motherboard in. It didn't make much of a difference.
I installed SysLog and got a bunch of logs from the N7105 motherboard right after one freeze/reboot. But I'm not entirely sure what I'm looking at nor what to look for. It's been a while since I've fiddled with my phones, so I'm not very enthused at the idea of reflashing my phone.
What can I do to better pin down the root of the problem, short of reflashing everything and hoping the problem goes away?
I would flash stock rom and kernel without apps restoring just to see if it's hardware or software issue.
there is service menu where you can test sensors *#0*#
you can try to overclock cpu, I remember that some time ago it helped to similiar problems with waking up
Yeah, I think I'll probably have to reflash at some point, just to make sure. But I'm going to avoid it for now, since I have other concerns.
I forgot about the service menu! That's a good idea, thanks!
I've never overclocked a CPU, computer or phone, so I'll read up on that. Not sure it'll help with the t889 motherboard, but it might work for the N7105 motherboard.
Thanks again for the suggestions!
For what it's worth, I have the same problem. It started a few weeks ago. I was using Dr. Ketan's rom and thinking that it might be a rom problem, flashed Resurrection Remix 5.1.1. CM 12.1. For a week there was no problem, but now it's back again.
If the phone is left untouched for a while, it won't wake up and is warm to the touch. And yes, the battery is greatly reduced...
I'll be interested in anything that is discovered....
Thanks.
Well, this is mildly frustrating and not at all helpful, but the weird freezes on the t889 motherboard seem to have stopped by themselves. I didn't do anything beyond poking around the service menu. Everything looked ok there. The freezes continued a while longer, and yesterday I noticed that it had been over a day since I had to pull the battery to force a reboot.
My best guess is that an app update caused a minor hardware incompatibility, and some update this past weekend resolved that incompatibility. I'm going to give it another couple of days before swapping the N7105 motherboard back in and seeing if some app update fixes that problem.
Update: I swapped the N7105 motherboard back in and ran all my app updates. No go; the problem showed up again while I was charging the phone. On the other hand, I was able to confirm without a doubt that it's a problem with this motherboard and not the headphone port that causing the lack of sound output with headphones in. The phone acknowledges the headphones when I plug them in. It just doesn't play anything through it.
Indexservice is still using up far more battery than it should. It might be higher than normal due to all the app updates, but it really shouldn't be as high as it is, so I'm tentatively declaring it related or the cause. Since it's not a file size problem, it may be a corrupted file, which means a reflash in my future, if I want to keep using the N7105 motherboard.
It's possible that all these problems mean that the motherboard is failing. It's two years old. It might just be its time.
Hopefully, reflashing everything will fix the problems. If not, at least I had another motherboard to fall back on.
I'm still having the same problem and haven't found a solution. It often won't awaken and needs a long push on the power button to boot. After booting, if we use it a lot it seems to be fine, but if we leave it alone for a while, it won't wake up.
Is that what you are getting? My wife wants another phone!
We always leave in on the charger all night long (as I have done with all my phones). Can that have damaged something?
I could try flashing a stock rom, but fear this may be a hardware problem. I don't see many participants in this thread...
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
---------- Post added at 06:45 PM ---------- Previous post was at 06:22 PM ----------
That service menu that you quoted above doesn't work on my phone. Could it be misspelled?
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Yes, that is exactly it. As long as I'm actively using the phone, it's fine. It's only when I leave it for a while that it won't wake and I have to press the power button to force reboot.
I also leave my phone on a charger all night, but I hardly think we're the only ones to do this. It might be related, but I kind of think it's not.
You could swap out the motherboard like I did. I imagine they're much cheaper now then they were when I bought mine ages ago. The Note 2 is very easy to take apart.
The service menu as written above works for me. Not sure why it won't work for you.
Did the new motherboard solve the problem completely? I see replacement motherboards for $45 online. They offer both 7100 and 7105. What is the 7105? I now have a 7100 European model.
I downloaded the EMMC check program. My phone does not have the "Insane Chip" that causes the Sudden Death Syndrome, but it has eMMC chip VTU00M -for what that's worth.
Samsung Galaxy S5
Exodus CM12 5.1.1
Boeffla kernel
Apex Launcher
Yes, the problem is completely gone with a new motherboard. Any problems I had with the new motherboard seems to have worked itself out, which is why I concluded that the problem lay with the N7105 motherboard.
I think the difference between the 7100 and 7105 is that the 7105 is the LTE model. There's no harm in buying the motherboard of another model number- I did- you just have to make sure to install the appropriate modems/ROMs for that particular model. (And hey, if you get the 7105- you just upgraded to LTE! Yay!)
Phenomenal. I'm going to order a 7105 motherboard. It will take a while to arrive and my wife will grumpy until it is installed.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Selofain said:
Yes, the problem is completely gone with a new motherboard. Any problems I had with the new motherboard seems to have worked itself out, which is why I concluded that the problem lay with the N7105 motherboard.
I think the difference between the 7100 and 7105 is that the 7105 is the LTE model. There's no harm in buying the motherboard of another model number- I did- you just have to make sure to install the appropriate modems/ROMs for that particular model. (And hey, if you get the 7105- you just upgraded to LTE! Yay!)
Click to expand...
Click to collapse
When you installed the new motherboard, did you have to do anything with your imei number?
In reading above it sounds like you changed motherboards several times and during that time the problem went away, but was it really the different motherboard? There are motherboards for sale in China, but I don't see any indication that they are Samsung manufacture. They are compatible, may be used actually, and although they cost 45€, shipping will be 38€ more unless I want to wait 2 months for the free shipping by mail.
Did you try reflashing a stock rom? I am tempted to try that first.....
Regards
I only have two motherboards, and I only swapped them out a couple of times. I had minor problems with the t889 motherboard at first, but the problem went away on its own after a week or so. It had actually been nearly three weeks before I swapped the N7105 motherboard back in, and I didn't leave it in for long, just long enough to determine that the problem was still there. I'm back to using the t889 motherboard now, and haven't had any problems with refusing to wake from sleep.
I haven't flashed a stock rom yet. I found that I couldn't restore the data of one of my apps to the new motherboard, and the data was something I spent hours inputting, so until I find a way to save that data, I won't be reflashing.
I didn't do anything with the imei when I installed the new motherboard, but I was prepared to transfer the imei if necessary. I backed up my old one and would have restored it to the new motherboard if necessary, but it wasn't necessary, so I didn't do anything. I bought my motherboard on ebay, which has both advantages and pitfalls. I'd say definitely try reflashing first, since that won't cost you anything but time.
My girlfriend has had the same issues for around one week (exactly the same symptoms_freezes when left untouched, especially at night, and she has to reboot). She has been on revolution HD 31 rom for months without problem ; she hasn't installed anything lately either... an update is probably the cause. I flashed ditto N4 (after factory reset) but the issue has shown up again... It's a european n7100.
We have a solution (I think). I did a factory reset and then used Odin to install the most recent 4.4.2 stock rom for Spain (where we live) . I didn't let Google update my applications and installed just the basics that my wife uses. So far so good (12 hours).
Little by little, I will add applications.
This started when we were using Dr. Ketan's excellent modified TouchWiz rom. Apparently some app upgraded itself causing this problem. When I flashed Resurrection Remix, the apps came along with us and so the problem persisted. Wish us luck.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Weird thing, I got that insane chip but my note doesn't seem to randomly reboots overtime.. I experienced some reboots using some rooms, though, mainly with 5.1.1 releases. Is there any trusty app that really informs me the right chip? Thanks.
Enviado do banheiro
Oh, great! It's good to know that it was a software error rather than a hardware error. Let us know if you figure out which app is causing it. It can't be too common an app, or we'd see more people here in this thread.
So far, the phone is behaving perfectly. My wife is thrilled because she is used to the look and feel of Samsung roms. She didn't like AOSP which is considerably more buggy. Yes, with CM12 roms, random reboots are common. Little by little, we are adding essential apps. We don't even have the phone rooted and may not ever do that since my wife likes to keep it simple.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
quijote1 said:
We have a solution (I think). I did a factory reset and then used Odin to install the most recent 4.4.2 stock rom for Spain (where we live) . I didn't let Google update my applications and installed just the basics that my wife uses. So far so good (12 hours).
Little by little, I will add applications.
This started when we were using Dr. Ketan's excellent modified TouchWiz rom. Apparently some app upgraded itself causing this problem. When I flashed Resurrection Remix, the apps came along with us and so the problem persisted. Wish us luck.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Click to expand...
Click to collapse
I also suspected a touchwiz app update, and maybe a conflict with google play services or a google play services update conflicting now with a touchwiz app (maybe not updated). By the way, did you use hangouts or whatsapp ? and what recovery do you use ?
I have just flashed 'rubbaband_note4_lp_4-4-4_gt-n7100_v1-2.zip' late in the evening, had not enough time to set the phone up as previously, and for the first time it didn't freeze at night...
oliwek said:
I also suspected a touchwiz app update, and maybe a conflict with google play services or a google play services update conflicting now with a touchwiz app (maybe not updated). By the way, did you use hangouts or whatsapp ? and what recovery do you use ?
I have just flashed 'rubbaband_note4_lp_4-4-4_gt-n7100_v1-2.zip' late in the evening, had not enough time to set the phone up as previously, and for the first time it didn't freeze at night...
Click to expand...
Click to collapse
I used the latest TWRP recovery because the AOSP roms seem to like that better. Otherwise I have always preferred Philz. I always froze hangouts but our whole family are heavy WhatsApp users. I have now frozen most of the Samsung and Google bloatware and the phone is very happy. Today root and more apps. Oh, I also use Greenify and it's working fine.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher

Categories

Resources