Related
Hello,
Currently, I have two GS2 (i9100 and T989) and a GS3. The problem is that only the T989 works on my data plan (T-Mobile USA 1700/2100MHz HSPA+)
So, now, I'm looking for a phone that combines the speed of the i9100 and GS3 with the AWS frequency support of the T989. The T-Mobile branded GS2 is rather laggy during important tasks (mainly SMS). If I want to send a text in a thread with a long history, the phone lags very badly. Even opening up the SMS app lags that phone. I don't have these problems with the two Exynos based phones. Archiving SMS messages is very important to me, so I can't delete them and need a phone that can handle long threads without massive lag.
How is the Galaxy Nexus at handling lag? I don't really play any intense games (and I'd have the GS3 for that if needed) so really I'm mainly looking to avoid SMS/browser/Gmail/UI lagging.
Additionally, I take pictures a lot. I know the camera on the Nexus is lower, but I've heard that it's about the same quality as the GS2. If that's true, I would be fine with 5MP.
Also, I see a lot of people complaining about factory defects in their phones in this forum.. How bad is the screen burn in issue?
If anyone has used a T989 in the past, how does the GNexus battery life compare?
tl;dr version:
* I need a phone that doesn't lag
* I have really, really long SMS threads
* I like taking pictures. Will I be okay with the Nexus camera? (coming from GS2)
* Should I get the Galaxy Nexus?
Thanks to anyone who can help!
Well, if the GS 2 is laggy (Which it really is, I had it myself), then flash SensatioNROM, that's the best ROM you'll find for the GS 2 and install Siyah, or Darknight kernel...
So much for the GS 2, to the Nexus, only buy this, if you don't mind having no buttons (I'm regretting it) and buy it, if you want to be the first of your friends, to have Android "Jelly Bean", which will be Android 4.1, coming out in the autumn months (For americans, the "fall"), and generally, only get the GNex, if you want PURE Googleness, which I'm also starting to regret, that's why I'm porting TWiz 5.0 to the GNex... But anyways... I'll give you a quote, from a film, 80% (at least) of this forum know:
I can only show you the door. You must go through it.
Click to expand...
Click to collapse
This is a quote, that I have been using for quite some time, now.
familyguy59 said:
Well, if the GS 2 is laggy (Which it really is, I had it myself), then flash SensatioNROM, that's the best ROM you'll find for the GS 2 and install Siyah, or Darknight kernel...
So much for the GS 2, to the Nexus, only buy this, if you don't mind having no buttons (I'm regretting it) and buy it, if you want to be the first of your friends, to have Android "Jelly Bean", which will be Android 4.1, coming out in the autumn months (For americans, the "fall"), and generally, only get the GNex, if you want PURE Googleness, which I'm also starting to regret, that's why I'm porting TWiz 5.0 to the GNex... But anyways... I'll give you a quote, from a film, 80% (at least) of this forum know: This is a quote, that I have been using for quite some time, now.
Click to expand...
Click to collapse
Well, I can only use a phone with AWS (1700MHz) as my main phone. The i9100 doesn't lag for me.. but the T989 does.
And I'm fine with software buttons. In fact, I think it's better..
Mainly, I'd like to know how the Nexus performs in terms of lagginess compared to i9100 and T989.
I really can't comment compared to the other phones, but the Nexus is perfect for tasks like what you mentioned, I prefer to use ChompSMS for all my texting needs, but I did use the stock Messages app and it handles just fine (even with 400 texts per convo), Gmail runs fine, and is really smooth, browsing is probably the best you can get at the moment (Try Chrome), and overall the UI doesn't lag at all for me. Even when it's 100% stock, it is still really smooth.
I highly recommend this phone, and I think you will be very happy with it
Any phone will get laggy with long sms threads. it uses a database, which get exponentially more taxing to open /w more data.
get sms backup (wise shark software), set it to sd-card only (gmail feature is kinda unreliable) ...it automatically adds sms messages to text files on your sd card, each phone number has its own text file and messages get added to the end of a file with a timestamp and arrow indicating whether they were incoming or outgoing. It should be noted that restoring /w this is worthless too, the restore feature does not work like you would expect and there is no real reason to restore anyway as you allready have all of them searchable and archived. make sure you check "auto-backup", it has allways worked perfectly for me. Also, dont delete the database (.db) file in the smsbackup folder, this is how the app keeps track of what sms have been backed up and which havent.
Next get agrep from the play store and pick the smsBackup directory as a search directory.
to view the text files (as they can get quite large), get jota which can open very very large text files.
Finally, i personally move all the text files out into a different directory on the first of every year into another directory called SmsArchive /w the folder structure (add this folder to agrep's search folders)
SmsArchive>Year>text files
Now you can backup every single sms you ever get while being able to search through them without bogging down the internal sms database.
again, the SMS backup app is kinda weird but I have searched to the ends of the earth, and as far as I know this is the only app for any platform that does this, let alone does this reliably.
Well the only laggy thing I have seen is the lwp. Most lag really bad.
Sent from my Galaxy Nexus
For taking quick pictures I love the instant responsiveness of the Nexus out of the box.
Its so fast I often take dozens of photos and just delete the ones that aren't 'perfect' (like any photographer does).
Liskrig said:
I really can't comment compared to the other phones, but the Nexus is perfect for tasks like what you mentioned, I prefer to use ChompSMS for all my texting needs, but I did use the stock Messages app and it handles just fine (even with 400 texts per convo), Gmail runs fine, and is really smooth, browsing is probably the best you can get at the moment (Try Chrome), and overall the UI doesn't lag at all for me. Even when it's 100% stock, it is still really smooth.
I highly recommend this phone, and I think you will be very happy with it
Click to expand...
Click to collapse
I'm glad to hear that! However.. I'm looking at more like ~3000 messages per thread than 400. Hopefully it will be okay.
starnostar said:
get sms backup (wise shark software), set it to sd-card only (gmail feature is kinda unreliable) ...it automatically adds sms messages to text files on your sd card, each phone number has its own text file and messages get added to the end of a file with a timestamp and arrow indicating whether they were incoming or outgoing. It should be noted that restoring /w this is worthless too, the restore feature does not work like you would expect and there is no real reason to restore anyway as you allready have all of them searchable and archived. make sure you check "auto-backup", it has allways worked perfectly for me. Also, dont delete the database (.db) file in the smsbackup folder, this is how the app keeps track of what sms have been backed up and which havent.
again, the SMS backup app is kinda weird but I have searched to the ends of the earth, and as far as I know this is the only app for any platform that does this, let alone does this reliably.
Click to expand...
Click to collapse
Hmm.. I've used two SMS backup apps in the past: SMSBackup+(Jan Berkel) and SMSBackup/Restore(Ritesh Sahu). Have you tried these two apps? If so, why did you like Wise Shark's app more? I'd like to know a little more about it if you have time, cause it is $5. Thank you
I like it more because it automatically pushes any new sms messages to the end of an existing text file on the internal storage, /w a text file for each number.
It seems to be the only good solution for a "long-term archive" of text messages, I don't like it when the backup apps tie a name to the number, numbers are static and never change but what if you misspelled a persons name and correct it?...after years of that kind of stuff it turns into a disaster.
I also chose it because I'm a linux nut...text files are the most simplistic type of file this can be put into (next to csv, but csv loses "human readability" in exchange for limited import/export ability), you DON'T want a database for years of sms messages, a database like that will give your computer a run for its money depending on the database structure. Take the simplicity of a text file and add it to the enormous power of grep (and if you wanna get really nerdy, regex) and you can search literally decades of sms messages with very little cpu power/memory in seconds.
It should be dualy noted that I also use rsync to sync my sms-archive (via mobile network) every day to my home-server, at which point a cron-job encrypts it, renames it to the current date/time-stamp and sends this file to dropbox. I backup many other files on my phone and other computers with this method too.....go ahead and make fun if you like
I also try to keep my own data...if you trust gmail for your sms backup, what would you do if something happened to gmail? I like to have my data in a tangible form that I can backup/edit/use without crossing my fingers and relying on the competence of another party.
tl;dr version - simple and portable files that can be read on anything and searched with open source tools, no messy database, its the most simple type of file data like this can be stored in. its also the only app for any phone/platform that I have ever found capable of this, at least without saying "F*^$ it" and making my own app.
So, I decided to buy it!
Thanks to everyone who answered my questions
Some first impressions:
* amazing feeling in hand.. this phone feels great to hold without a case
* updated itself to 4.0.4 automatically..? Saved time; but a warning would have been nice before using up like 60MB data.
* that really nice button glow effect disappeared after 4.0.4 update
* so far, browser performance is amazing, definitely better than the T989
* the LED hardware acts a little weird.. only activates sometimes
* black blobs under the screen.. but I hear that 90% of these phones have this issue
* keeps switching between "3G" and "H." These are the same thing, no?
I'm getting worried hearing about so many people having problems with their phones in this forum...
But so far, asides from some minor problems, the Galaxy Nexus seems like the right choice for me
3g and h (hspa) are indeed the same thing, can't say why they switch randomly though.
As far as all the people with problems with their phones it may be worthwhile to bear in mind that people are much more likely to post if they have problems than if they have none. I personally have no complaints about the phone, in fact I love it, and won't be starting a thread called "omg I love my gnex, it's perfect"
Sent from my Cyanogenmodded GNex
I too have had no problems with gnex. I'm on 4.0.4 stock and its smooth, fast and reliable.
Sent from my Galaxy Nexus using XDA
It's good to know many people have no issues! I hope I won't have any major problems.. :x
Anyone know what's going on with the notification LED though? Is it normal for it to only activate like 50% of the time?
And is it worth asking for a replacement if you have the black blobs under the screen?
3g and h (hspa) are indeed the same thing, can't say why they switch randomly though.
I believe that h shows with an active data connection. When it shows 3g, should be an idle connection.. Dont quote me on that lol but remember reading something bout it..
****WARNING, THIS BREAKS MARKET FOR SOME APPS AND CAUSES YOU NOT TO BE ABLE TO DOWNLOAD SOME APPS**** see bottom of this post for the fix.
Example on my phone running in Tablet UI.
http://www.youtube.com/watch?v=Im9WV9GmQFc
Required:
ROOT
A file manager that supports root (Like ES File Explorer)
Wouldn't try this on stock software/launcher, but let me know how it goes.
Note: It makes things a bit hard to read, even if you make the font "Huge" in the settings.
1. Create a backup of your phone.
2. In ES File Explorer, go to the SYSTEM folder.
3. Open build.prop with the ES Note Editor.
4. Change the line ro.sf....LCD Density to =160.
5. Save. Reboot phone.
Ta da, tablet mode. This may work on other phones too, but as tested it requires a lower number for lower resolution phones which may make it impossible to read/use.
If you have a Nexus 7 Tablet, use =170.
To fix the Play Store if its an issue for you: http://forum.xda-developers.com/showthread.php?t=1839871
ka24e said:
Example on my phone running in Tablet UI.
http://www.youtube.com/watch?v=Im9WV9GmQFc
Required:
ROOT
A file manager that supports root (Like ES File Explorer)
Wouldn't try this on stock software/launcher, but let me know how it goes.
Note: It makes things a bit hard to read, even if you make the font "Huge" in the settings.
1. Create a backup of your phone.
2. In ES File Explorer, go to the SYSTEM folder.
3. Open build.prop with the ES Note Editor.
4. Change the line ro.sf....LCD Density to =160.
5. Save. Reboot phone.
Ta da, tablet mode. This may work on other phones too, but as tested it requires a lower number for lower resolution phones which may make it impossible to read/use.
If you have a Nexus 7 Tablet, use =170.
Click to expand...
Click to collapse
Wont a resolution other then 160-240-320 break the market? Some apps will not show up for non standard DPI I think. Not sure.
Also I used this yesterday, as I tried to download Cut the Rope HD, even if that didn't work. I was surprised what 160DPI did to my phone. One X international.
Anyway confirming this works on the One X for me with CM10.
But if you find a way how to switch it without the use of DPI change let me know . Something like the paranoidandroid project.
I found few guides, but they do not apply to my phone. Or I do not know where those files are to decompile them.
PAGOT said:
Wont a resolution other then 160-240-320 break the market? Some apps will not show up for non standard DPI I think. Not sure.
Also I used this yesterday, as I tried to download Cut the Rope HD, even if that didn't work. I was surprised what 160DPI did to my phone. One X international.
Anyway confirming this works on the One X for me with CM10.
But if you find a way how to switch it without the use of DPI change let me know . Something like the paranoidandroid project.
I found few guides, but they do not apply to my phone. Or I do not know where those files are to decompile them.
Click to expand...
Click to collapse
Use your regular DPI, download your apps, then switch the DPI. #winning.
Cut the Rope HD (Lite) shows up in the market for my Nexus 7 Tablet (DPI set to 170, stock is 270.. i think). Going to test with S3, i'll update in a few with my findings.
Changed DPI to 160 on the S3 and went to the Market, Cut The Rope HD lite is listed, installed fine and runs perfectly fine.
So i have a DPI of 170 and a dpi of 160, market working on both devices, unless you have a full list of apps I can test, doesn't seem to affect anything. If so, just do what I said above. Should get around the issue.
ka24e said:
Use your regular DPI, download your apps, then switch the DPI. #winning.
Cut the Rope HD (Lite) shows up in the market for my Nexus 7 Tablet (DPI set to 170, stock is 320). Going to test with S3, i'll update in a few with my findings.
Click to expand...
Click to collapse
That did not work for me. Once market gets the wrong DPI, some apps wont show up. Last time I tried I ended up with Nandroiding back. Even clear Data and Cache didn't work.
The lite shows up everywhere ... Thats not the issue The one on sale HD doesnt and it says I have no compatible phone with that.
PAGOT said:
That did not work for me. Once market gets the wrong DPI, some apps wont show up. Last time I tried I ended up with Nandroiding back. Even clear Data and Cache didn't work.
The lite shows up everywhere ... Thats not the issue The one on sale HD doesnt and it says I have no compatible phone with that.
Click to expand...
Click to collapse
Oohh gotcha... I'll have to do some more testing then I guess. I usually only use the Google apps and that's it. Maybe Facebook twitter and such. Personally haven't noticed anything else missing. Ah well lol
Yeah you're right. Even on play.Google.com it says incompatible. Argh. When you nandroided back did it fix it? Or is this still broken for you?
ka24e said:
Oohh gotcha... I'll have to do some more testing then I guess. I usually only use the Google apps and that's it. Maybe Facebook twitter and such. Personally haven't noticed anything else missing. Ah well lol
Yeah you're right. Even on play.Google.com it says incompatible. Argh. When you nandroided back did it fix it? Or is this still broken for you?
Click to expand...
Click to collapse
Nevermind, still broken here....
I tried this: http://forum.xda-developers.com/showthread.php?t=1839871
But no luck, anyone want to try it and report back?
I could be doing something wrong haha
Also could we put a list of apps together that are incompatible... everything else I look for seems to work fine... hrmm..
Comments on Cut The Rope HD:
Ahzi - September 16, 2012 - Version 1.4
No Nexus 7 Support
I love this game and it worked great on my old tablet but for some reason this version has cannot be installed on my Google Nexus 7. I tried the HD lite version and it says it's compatible but not the one I've already paid for.
That gets me wondering, because it says ALL my devices are incompatible (S3, Nexus 7, Nexus S and Nexus One). The Nexus S and One are unmodified. I'm wondering if this is one of a select few apps that are affected? I can download Asphalt 7 no problem at all on both devices (Nexus 7 and GS3)
ka24e said:
Nevermind, still broken here....
I tried this: http://forum.xda-developers.com/showthread.php?t=1839871
But no luck, anyone want to try it and report back?
I could be doing something wrong haha
Also could we put a list of apps together that are incompatible... everything else I look for seems to work fine... hrmm..
Comments on Cut The Rope HD:
Ahzi - September 16, 2012 - Version 1.4
No Nexus 7 Support
I love this game and it worked great on my old tablet but for some reason this version has cannot be installed on my Google Nexus 7. I tried the HD lite version and it says it's compatible but not the one I've already paid for.
That gets me wondering, because it says ALL my devices are incompatible (S3, Nexus 7, Nexus S and Nexus One). The Nexus S and One are unmodified. I'm wondering if this is one of a select few apps that are affected? I can download Asphalt 7 no problem at all on both devices (Nexus 7 and GS3)
Click to expand...
Click to collapse
I think you misunderstood me there completely or I confused you there a bit.
1. Forget the Cut the rope HD. It has nothing to do with the problem is anything of the problem. I just mentioned it because it was the reason for which I changed my DPI to test if can download it.
They have trouble with it on Nexuses etc. As said, I wanted to test it only with it, I couldn't download it before as well. (was for it also changing device name etc, making myself to Xoom, Eeepad etc)
2. Using not standard DPI indeed breaks market , but for example apps like Beautiful Widgets, HD Widgets that I remember.
3. I would rather go another approach, if not using paranoidandroid. And the tweaks to the java files. Maybe we could use bigger fonts. Not sure how that would look like though
PAGOT said:
I think you misunderstood me there completely or I confused you there a bit.
1. Forget the Cut the rope HD. It has nothing to do with the problem is anything of the problem. I just mentioned it because it was the reason for which I changed my DPI to test if can download it.
They have trouble with it on Nexuses etc. As said, I wanted to test it only with it, I couldn't download it before as well. (was for it also changing device name etc, making myself to Xoom, Eeepad etc)
2. Using not standard DPI indeed breaks market , but for example apps like Beautiful Widgets, HD Widgets that I remember.
3. I would rather go another approach, if not using paranoidandroid. And the tweaks to the java files. Maybe we could use bigger fonts. Not sure how that would look like though
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1839871 does work. Just needed to reboot again.
I try not to ask for help, but unfortunately this one has me a bit stumped..
I started this journey a couple weeks ago by picking up a T-Mobile Galaxy Note 2. Needless to say I <3 it.. Shortly thereafter I received an AT&T upgrade and figured my T-Mobile days were becoming limited (REALLY poor service where I live), So I got an AT&T version.
Although I've rooted both and such within hours of them being charged - I've found one (what I want to call BIG) difference, and I hate it.
It's the keyboard when I'm texting. On the Tmobile version the space button is a little smaller, has a comma on the left side, period on the right side and the 'mode' button (handwriting/speech/keyboard/settings) ..
On the AT&T version the space is a little wider, to the right is the . to the left is a single button that expands out to have ,?!' talk, handwriting, settings.. All of these are into this one little button.
With Tmobile the 'magic button' (since I dont know what it's called) - it defaults to the speech/speak now prompt. AT&T's button defaults to handwriting..
I ACTUALLY use the voice version, however I can count the number of times I've used handwriting / spent on 1 hand. Therefore the only thing I really would pray for is to be able to get the Tmobile note 2 Keyboard layout on the ATT note 2
Background: Both phones are setup exactly the same, with the exact same settings etc.. Just stock roms etc, rooted w/ CWM..
See Screenshots
Wow that is strange. Do you use the number keys at the top? If not you could try out the 4.2 stock keyboard. You could also try copying the "SamsungIME.apk" from "system/apps" from the T-Mobile N2 and onto the AT&T N2.
ainen said:
Wow that is strange. Do you use the number keys at the top? If not you could try out the 4.2 stock keyboard. You could also try copying the "SamsungIME.apk" from "system/apps" from the T-Mobile N2 and onto the AT&T N2.
Click to expand...
Click to collapse
Well I went ahead and copied both the apk and the opek?
Anywho what that did was it made the 'smart' button turn into the comma.. Better than before (since I dont use the handwriting in texts etc).
The space button is still large as in the difference between the ATT/TM versions.
Also - yes I do use the numbers, since i have many alpha-num passwords it's quite handy not having top flipflop between the regular keyboard and 'sym' to be able to get to the numbers.
Hrmm any other magic files to copy? =)
I'd really just love to have the keyboard from the TM version instead of the ATT version.. Sounds easy but I have no clue where it would be hiding..
I'm going to try it without the odex this go around, will post the results.. Im thinking that may have something to do with it still being different..
I dont know a whole lot about the guts of android programming so I'm going to wing it till I get it where I like it..
If I didn't have to worry about the bloat and other stuff from TM, i'd almost flash the TM version onto it, then flash the ATT modem? /shrug,, however I do really did the I7105 international firmware,, it's fairly nice but i've had a few bugs with it.
pirgulation said:
I'm going to try it without the odex this go around, will post the results.. Im thinking that may have something to do with it still being different..
I dont know a whole lot about the guts of android programming so I'm going to wing it till I get it where I like it..
If I didn't have to worry about the bloat and other stuff from TM, i'd almost flash the TM version onto it, then flash the ATT modem? /shrug,, however I do really did the I7105 international firmware,, it's fairly nice but i've had a few bugs with it.
Click to expand...
Click to collapse
Welp - just odex free didnt help at all..
I did however install the TM image which isn't too bad, put the ATT rom on it, and i'm ALMOST where I want it to be..
Somehow the samsungIME.apk/odex isn't all I'm looking for..
Does anyone know what other files control the keyboard layout / keys etc on these?
(Would love to run international 7105 w/ Tmobile key layout =)
Seeing as you have both phones, you're in an ideal position to compare the config files and see what parameters are different.
The general concept:
http://forum.xda-developers.com/showthread.php?t=1988202
I am guessing - GUESSING - that the solution lies in what is different between the two phones in here:
/system/usr/keylayout
(The layout files are all text files.)
Good luck!
normaaaan said:
Seeing as you have both phones, you're in an ideal position to compare the config files and see what parameters are different.
The general concept:
http://forum.xda-developers.com/showthread.php?t=1988202
I am guessing - GUESSING - that the solution lies in what is different between the two phones in here:
/system/usr/keylayout
(The layout files are all text files.)
Good luck!
Click to expand...
Click to collapse
I finally got the chance to disect the directory you mention.. Unfortunately the files are exactly the same from what I can tell by looking at each file side by side.
Also copying the whole directory over changed nothing - which further supports said theory in case I overlooked something.
GOT it!
Root Instructions:
http://forum.xda-developers.com/showthread.php?t=2143479
Once rooted, use ES with Root Explorer - change the / and /system to r/w first
Copy /system/crc/feature.xml to your computer, edit with notepad.
copy the feature.xml to /system/crc (rename the old one)
Changes to feature.xml:
<CscFeature_Email_UseFixedBgColorAsWhite>false</CscFeature_Email_UseFixedBgColorAsWhite> (Changed to false)
<CscFeature_Sip_DefaultMultiModalKeyAs>VOICE</CscFeature_Sip_DefaultMultiModalKeyAs> (Changed to VOICE)
The second change was what set the button to go to voice instead of HANDWRITTING. That's what I was looking for!
rayb2001 said:
Root Instructions:
http://forum.xda-developers.com/showthread.php?t=2143479
Once rooted, use ES with Root Explorer - change the / and /system to r/w first
Copy /system/crc/feature.xml to your computer, edit with notepad.
copy the feature.xml to /system/crc (rename the old one)
Changes to feature.xml:
<CscFeature_Email_UseFixedBgColorAsWhite>false</CscFeature_Email_UseFixedBgColorAsWhite> (Changed to false)
<CscFeature_Sip_DefaultMultiModalKeyAs>VOICE</CscFeature_Sip_DefaultMultiModalKeyAs> (Changed to VOICE)
The second change was what set the button to go to voice instead of HANDWRITTING. That's what I was looking for!
Click to expand...
Click to collapse
I chose to go with a custom ROM for my N2 (AT&T) and I grieved the loss of my Sammy Keyboard. Once you move to custom, the keyboard is standard or aosp android. i never liked the Android keyboard layout, even though it;s functionality ran circles around Sammy.
To cut to the chase, their are some reasonably priced key boards in the Play Store that run circles around both Sammy and Android. I use Swift, which seems to be the current leader in sales and ratings. Swipe is another one that I hear a lot of people like and it is a third of the price of Swift. I think Swift is worth what you pay for it, even though I still like the layout of the Sammy better.
Hey, so I just got a GS3 after coming from an Evo 4G LTE, and so far I'm loving it. Plus, this is my first Samsung phone, my previous 3 have all been HTC. (The many versions of the EVO) Anyway I do have a few questions that maybe someone can help me with.
1. I noticed that there are different settings for the vibration. Now, when I receive a txt it seems to do the basic ring vibration. I saw that there's an option to create your own vibration, which is pretty cool, but it didn't set for my txt messaging, perhaps I'm doing it wrong?
2. This might be just me or perhaps I'm just used to the keyboard on sense, but I'm noticing I'm making a lot of mistakes while typing. Lol, it's probably just me.
3. I love how samsungs threw in a lot of neat (or gimmicky) features. However, if I'm concerned about battery are there any I should turn off (I know motion is one, but I kinda like it)
4. Out of curiosity, what rom is everyone using? I'm debating whether to stay stock rooted, although I might switch to AOKP. Lol unlike sense, touchwiz really doesn't have a lot of issue with it.
5. Now if I do switch to AOKP or AOSP how is the camera quality?
Thanks in advanced!
filmaker said:
Hey, so I just got a GS3 after coming from an Evo 4G LTE, and so far I'm loving it. Plus, this is my first Samsung phone, my previous 3 have all been HTC. (The many versions of the EVO) Anyway I do have a few questions that maybe someone can help me with.
1. I noticed that there are different settings for the vibration. Now, when I receive a txt it seems to do the basic ring vibration. I saw that there's an option to create your own vibration, which is pretty cool, but it didn't set for my txt messaging, perhaps I'm doing it wrong?
2. This might be just me or perhaps I'm just used to the keyboard on sense, but I'm noticing I'm making a lot of mistakes while typing. Lol, it's probably just me.
3. I love how samsungs threw in a lot of neat (or gimmicky) features. However, if I'm concerned about battery are there any I should turn off (I know motion is one, but I kinda like it)
4. Out of curiosity, what rom is everyone using? I'm debating whether to stay stock rooted, although I might switch to AOKP. Lol unlike sense, touchwiz really doesn't have a lot of issue with it.
5. Now if I do switch to AOKP or AOSP how is the camera quality?
Thanks in advanced!
Click to expand...
Click to collapse
1. No idea I haven't been on touchwiz since i got my phone
2. I hate the Samsung keyboard I switch to a ICS keyboard that's available in the market
3. Not sure. The only motion I ever left on was the swipe your palm to screen shot and I didn't noticed a decrease in battery. As long as you clear stuff in the task manager you should be fine
4. I've been on Paranoid Android for awhile. Touchwiz isn't as bad as people make it seem just not my style. A lot of cool looking touchwiz roms
5. Camera quality should be exactly the same except you lose certain features that are only available on the touchwiz
Sent from my SPH-L710 using xda app-developers app
filmaker said:
Hey, so I just got a GS3 after coming from an Evo 4G LTE, and so far I'm loving it. Plus, this is my first Samsung phone, my previous 3 have all been HTC. (The many versions of the EVO) Anyway I do have a few questions that maybe someone can help me with.
1. I noticed that there are different settings for the vibration. Now, when I receive a txt it seems to do the basic ring vibration. I saw that there's an option to create your own vibration, which is pretty cool, but it didn't set for my txt messaging, perhaps I'm doing it wrong?
2. This might be just me or perhaps I'm just used to the keyboard on sense, but I'm noticing I'm making a lot of mistakes while typing. Lol, it's probably just me.
3. I love how samsungs threw in a lot of neat (or gimmicky) features. However, if I'm concerned about battery are there any I should turn off (I know motion is one, but I kinda like it)
4. Out of curiosity, what rom is everyone using? I'm debating whether to stay stock rooted, although I might switch to AOKP. Lol unlike sense, touchwiz really doesn't have a lot of issue with it.
5. Now if I do switch to AOKP or AOSP how is the camera quality?
Thanks in advanced!
Click to expand...
Click to collapse
1. I am pretty sure the vibrate pattern is just for incoming calls not notifications even if you create a custom.
2. Yea lots of different keyboards mess around with a few find the one that fits you. I am using the new swiftkey flow and will not be looking back.
3. When on a TW rom I only use the swipe screenshots and hold phone to ear to call no battery issues for me. I delete S voice completely and disable other motion controls I dont need.
4. Currently running FreeGS3 3.0 really enjoying it. I spend most of my time on CM or other AOSP roms but if you are happy with TW for my phone anyways FreeGS3 has been very solid with the right amount of features and completely stable. The Aroma installer is easy and feature filled almost idiot proofs ROM installation.
5. As he said above the image quality will be fine just loose a few shiny du hickys in the camera ui
Thanks for both of your replies. I'm going to try CM and some other touchwiz roms.
Okay I have another question to. What is the purpose of the 0 folder inside of Scdard0. I noticed that some app data like Titanium Backup is defaulting there.
yeah im new to this phone as well and was wondering the same. The storage, extsd, and 0 thing throws me off sometimes. I'll get used to it though.
filmaker said:
Okay I have another question to. What is the purpose of the 0 folder inside of Scdard0. I noticed that some app data like Titanium Backup is defaulting there.
Click to expand...
Click to collapse
From JB and up all app data is stored in that folder (if you wanna know why they did that, ask google lol)
CNexus said:
From JB and up all app data is stored in that folder (if you wanna know why they did that, ask google lol)
Click to expand...
Click to collapse
True! Actually I just found out some interesting information. Apparently the "0" folder holds all the information that was in the /sdcard folder before the jellybean update. Another user found it on their galaxy nexus. Oddly enough, most of the folders in mine were empty. Titanium Backup was the only one taking up space because for some reason it backed up there, I also had around 200mb in the android data folder, but I really had a hard time finding out where, so anyway I just ended up deleting it. So far no ill effects.
filmaker said:
True! Actually I just found out some interesting information. Apparently the "0" folder holds all the information that was in the /sdcard folder before the jellybean update. Another user found it on their galaxy nexus. Oddly enough, most of the folders in mine were empty. Titanium Backup was the only one taking up space because for some reason it backed up there, I also had around 200mb in the android data folder, but I really had a hard time finding out where, so anyway I just ended up deleting it. So far no ill effects.
Click to expand...
Click to collapse
Yeah, I read this in another thread when a user couldn't find anything on their sdcard
Its weird why they would do that though, maybe to separate phone stuff from things that the user puts on their sdcard? Idk
By the way, just had to say this but I love your sig, the "life would be so much easier....." part
I love to code myself and I just found that really awesome lol
Haha thanks, it made me chuckle too when I first read it.
Sent from my SPH-L710 using xda app-developers app
To bad cm doesn't read external sd :/
Sent from my SCH-I800 using Tapatalk 2
Hi, rather new here so I can't post in the thread on the developers board. Thought I'd try here. I recently flashed Tiny's latest CM 10.1 nightly rom and I really like it so far. There are a couple of issues but after messing with it for a while, it's mostly smooth and works well. My biggest beef, aside from those couple issues is Netflix. The app loads and I can select a show, but when I try to load a video, I just get the red loading screen that goes on forever until I hit the back button. I tried an older apk, and it wouldn't load, period (1.5.2), which I guess is to be expected when running Android 4.2. I tried 2.1 and I got the same issue with the red loading screen. Tried loading it in the browser and I got the usual page that tells me I need a certain browser for it to work. The app worked just fine in the official CM 7.2. Is there an option in settings I'm missing or something or does it not work on this rom (which I don't see why it wouldn't)?
Other naggy issue is epsxe. It works alright but if I press a volume button, it either increases or decreases all the way and all buttons freeze. Nothing works. Home, menu, power button, touch, etc (yet the emu keeps going and the music keeps playing). Sometimes when I press an on-screen button to move, it's like the button gets stuck and the character keeps moving in that direction. I have to remove the battery to reboot. Did not have this issue in cm 7.2.
Other than that, awesome rom and thanks, Tiny, for working on it.
EDIT: Well, I just tried using epsxe again and it even worked when using the volume button. Not sure why it worked except that I let the game load for a bit before pressing anything. After that, it worked just fine. So, I guess it may be even an app issue on 4.2, rather than the rom. Hope Netflix is as easy to get working.
Netflix hasn't worked on JB or ICS. Known issue since day one. Probably won't be fixed as it's not a high priority in the overall picture.
...sorry...I was on the phone...
omniatic said:
Netflix hasn't worked on JB or ICS. Known issue since day one. Probably won't be fixed as it's not a high priority in the overall picture.
...sorry...I was on the phone...
Click to expand...
Click to collapse
Well, that's disappointing. I really like this this rom but Netflix was one of the biggest reasons to keep using this device. It's mainly used as a tablet now and I don't want to buy anything else right now. Funny thing, Netflix was the only reason I didn't switch from Windows 7 to Linux. I figure, if I'm paying them every month, I should be able to play their vids on any device I please and it irks me that I can't even get it working in the android browser. Oh well. Thanks for the quick response.
EDIT: Well, I did some research and found that Netflix 1.81 seems to work to an extent. I get sound and subtitles but no video. Going to look into it some more.
Kaepernick said:
Well, that's disappointing. I really like this this rom but Netflix was one of the biggest reasons to keep using this device. It's mainly used as a tablet now and I don't want to buy anything else right now. Funny thing, Netflix was the only reason I didn't switch from Windows 7 to Linux. I figure, if I'm paying them every month, I should be able to play their vids on any device I please and it irks me that I can't even get it working in the android browser. Oh well. Thanks for the quick response.
EDIT: Well, I did some research and found that Netflix 1.81 seems to work to an extent. I get sound and subtitles but no video. Going to look into it some more.
Click to expand...
Click to collapse
It works on better supported devices on ICS and JB. The issue here is the codecs and hardware support / drivers which will not be fixed for now. Just confirming its not androids fault or Netflix's.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
It works on better supported devices on ICS and JB. The issue here is the codecs and hardware support / drivers which will not be fixed for now. Just confirming its not androids fault or Netflix's.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So no amount of tinkering with older apks and workarounds (to make it so the app uses older netflix video players) will work because the rom/hardware simply doesn't support playback? I was looking at some other threads and google and a lot of people seem to be having trouble getting Netflix to work on 10.1 and Android 4.2 in general. Seems when the app detects Jelly Bean, it uses its newest video player, which has some problems on some devices. Forcing it to use an older player seems to work for some people. Adding a line to the code to make it use player "6" instead of "10" or something. Haven't actually applied anything to the app to try it because I'm a complete novice at this.
You're the expert and I assume if there was an easy method that wouldn't screw anything up in the CM 10.1 build, you'd apply it. I do appreciate the work you and others are putting into these roms and other than this Netflix issue, it rocks. I may go back to CM 7.2 after a bit but I'll definitely keep an eye on your updates and try them out.
Kaepernick said:
So no amount of tinkering with older apks and workarounds (to make it so the app uses older netflix video players) will work because the rom/hardware simply doesn't support playback? I was looking at some other threads and google and a lot of people seem to be having trouble getting Netflix to work on 10.1 and Android 4.2 in general. Seems when the app detects Jelly Bean, it uses its newest video player, which has some problems on some devices. Forcing it to use an older player seems to work for some people. Adding a line to the code to make it use player "6" instead of "10" or something. Haven't actually applied anything to the app to try it because I'm a complete novice at this.
You're the expert and I assume if there was an easy method that wouldn't screw anything up in the CM 10.1 build, you'd apply it. I do appreciate the work you and others are putting into these roms and other than this Netflix issue, it rocks. I may go back to CM 7.2 after a bit but I'll definitely keep an eye on your updates and try them out.
Click to expand...
Click to collapse
That may just work. I'm kind of a newb at smali but it may be worth a shot. I haven't heard of this workaround before. In theory it should work under software.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
That may just work. I'm kind of a newb at smali but it may be worth a shot. I haven't heard of this workaround before. In theory it should work under software.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, that gives me some hope, at least. Here's one of the threads I was looking at.
http://forum.xda-developers.com/showthread.php?t=2101525
On the last page, someone posted the code that enabled it to work on theirs.
EDIT: I tried the Xposed app workaround, by the way, which did not work for me, using 1.8.0 (thought it was 1.8.1 but wasn't. Plan on trying that next) or the newest version. I realize that these are different devices, but I'm hoping there's a way to get it to work on ours. I wonder if there's a way to trick it into thinking it's Gingerbread instead of ICS (in the thread) and using the player that works on CM 7, if it would work?
Kaepernick said:
Well, that gives me some hope, at least. Here's one of the threads I was looking at.
http://forum.xda-developers.com/showthread.php?t=2101525
On the last page, someone posted the code that enabled it to work on theirs.
EDIT: I tried the Xposed app workaround, by the way, which did not work for me, using 1.8.0 (thought it was 1.8.1 but wasn't. Plan on trying that next) or the newest version. I realize that these are different devices, but I'm hoping there's a way to get it to work on ours. I wonder if there's a way to trick it into thinking it's Gingerbread instead of ICS (in the thread) and using the player that works on CM 7, if it would work?
Click to expand...
Click to collapse
I don't have a netflix account currently (had it and didn't use it), so I can't do much testing but based on the link you showed me, the app should work fine. Try the init.d script linked in the github in the thread you posted. Are you familiar with pushing files to your device? You just need to copy it to /system/etc/init.d and add execute permissions. Usuaully I use read-write-execute for user and read-execute for group and other.
tiny4579 said:
I don't have a netflix account currently (had it and didn't use it), so I can't do much testing but based on the link you showed me, the app should work fine. Try the init.d script linked in the github in the thread you posted. Are you familiar with pushing files to your device? You just need to copy it to /system/etc/init.d and add execute permissions. Usuaully I use read-write-execute for user and read-execute for group and other.
Click to expand...
Click to collapse
The xposed_init file under assets? Can't say I've ever tried this before. I know how to add files to that folder, but no idea how to copy it to a file or whatever that would work. Don't know how to execute permissions either.
Looking things up, I can't just add a file to my sdcard and use ES File explorer to add it to the init.d folder? I copied one of the files on my desktop and opened it up with notepad. It sadly didn't help me. Like I said, total novice with android here or this stuff in general. Would like to give this a shot though. Do I add the text to notepad and then delete the .txt or do I need to make a .js file? As for permissions, do I just add r rw and x to the file?
Kaepernick said:
The xposed_init file under assets? Can't say I've ever tried this before. I know how to add files to that folder, but no idea how to copy it to a file or whatever that would work. Don't know how to execute permissions either.
Looking things up, I can't just add a file to my sdcard and use ES File explorer to add it to the init.d folder? I copied one of the files on my desktop and opened it up with notepad. It sadly didn't help me. Like I said, total novice with android here or this stuff in general. Would like to give this a shot though. Do I add the text to notepad and then delete the .txt or do I need to make a .js file? As for permissions, do I just add r rw and x to the file?
Click to expand...
Click to collapse
Yeah, you can add it to notepad and remove the .txt at the end but it uses different line breaks in Windows than what Linux uses so the script may not work right. I'm not sure though. The worse thing that can happen is nothing. Android doesn't use .js which is Javascript. For permissions, yes that will work.
ealassi content
tiny4579 said:
Yeah, you can add it to notepad and remove the .txt at the end but it uses different line breaks in Windows than what Linux uses so the script may not work right. I'm not sure though. The worse thing that can happen is nothing. Android doesn't use .js which is Javascript. For permissions, yes that will work.
Click to expand...
Click to collapse
Tried it. Not sure if I did it right. Most likely not. lol But in any case, it doesn't work. Getting a bit tired, so I may just relent. I'm sure many who are more experienced have tried already.
Just curious: If your primary use for your old Dinc is as a portable Netflix viewer, then why not just flash back to a stable GB-based ROM and enjoy?
Seems that would be a lot simpler than trying to get Netflix to work on JB, especially if you're not doing anything with the phone that requires JB.
MysticCobra said:
Just curious: If your primary use for your old Dinc is as a portable Netflix viewer, then why not just flash back to a stable GB-based ROM and enjoy?
Seems that would be a lot simpler than trying to get Netflix to work on JB, especially if you're not doing anything with the phone that requires JB.
Click to expand...
Click to collapse
I like Jelly Bean. I like how it looks and feels. It's a more mature Android. Plus, I like keeping up to date with software. It's kind of nice to have 4.2 running on the aging, yet good o'l Dinc, when some newer devices don't even have 4.1 yet officially.
Also, I got it working, by the way! Before, when I downloaded the newest one onto 10.1, it would just continuously load when picking a video and not work. After tinkering, I got it to play sound but no video. I could tell that the video player was different than the one I used on 7.2 (also, the newest app). I switched back to 7.2 for a bit and downloaded my apps. I backed everything up using Clockwork mod so I could go back to it whenever. Then I backed up all the Apps with Titanium Backup. I switched back to Tiny's 10.1 and restored the apps. I tried out Netflix and it worked. It was using the same player it used on 7.2. I don't know if it detects Jelly Bean when you download it from Google Play or if it does it when you sign in to your account. When I restored it, I was already signed in, so maybe that's it. At any rate, it works.
Well, I spoke too soon. It did work for the first few videos but then stopped. I tried uninstalling and reinstalling with the Titanium Backup, but when I try to choose a video, it says I've been signed out. I sign back in and I'm back to the forever loading red screen. So yeah, I think it detects which OS I'm on as I sign in. Just a guess though. Just shows that it has nothing to do with your ROM aside from their newest player not working properly on it. It can indeed be fixed via the software with some tinkering.
Can you check the value for int name="nflx_player_type" in /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml from a working Netflix in Gingerbread? Easier yet, pull that file from your Netflix backup from Gingerbread for me. Check for passwords in the file and clear them out before giving it to me for security.
tiny4579 said:
Can you check the value for int name="nflx_player_type" in /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml from a working Netflix in Gingerbread? Easier yet, pull that file from your Netflix backup from Gingerbread for me. Check for passwords in the file and clear them out before giving it to me for security.
Click to expand...
Click to collapse
Here you go. Says It's using Player 9. I have read that 10 is the newest player. At least I believe so.
Edit: just checked that file on 10.1. It says player 10. That means it switched when I signed back in.
Kaepernick said:
Here you go. Says It's using Player 9. I have read that 10 is the newest player. At least I believe so.
Edit: just checked that file on 10.1. It says player 10. That means it switched when I signed back in.
Click to expand...
Click to collapse
Hmm, if you edit that file back to 9 and open Netflix does it work?
tiny4579 said:
Hmm, if you edit that file back to 9 and open Netflix does it work?
Click to expand...
Click to collapse
Yes and it didn't work. Then I tried "6". Didn't load. I tried 9 again and for whatever reason, it loaded. It works just fine now, using the same player it did in 7.2. The kicker is that I check the XML file again and it changed somewhat. It now says "6" and it looks different. I believe the Player line used to be before the Logged in line. Now the logged in line is last. If there was some way to force it to use 6 every time, even when logging in, we'd have a working netflix app on your rom.
Maybe "old app version=17" is the key, I don't know.
EDIT: Exited the app. Still works. Rebooted the phone. Still works. There's no log out button, so I assume to log out, I need to clear data, which I assume would just put me back at square one. Seems to be working fine now, as long as I stay signed in. If I somehow have to sign in again, I'll check the xml file.
Attached the file. Just edited the user id part.
Well, it was working. Then it quit. I checked the xml file and it had switched to 10. Didn't sign in or out or anything. Tried the 6 file and it immediately switched back to 10. So, I uninstalled and then installed 1.8.1. Replaced the nfxpref file with the one I backed up and it worked. Funny thing, it's actually using an older version of the player. I believe that may actually be "6". In cm7.2, it said "9" and was using a newer version of the player (newer than the one I'm using now). It seems to work well so far. Haven't tried updating from this yet, to see if the newest one works by updating, but I doubt it would work anyway. I did notice that in the shared prefs folder, there's only one other file with the nfxpref file. In the newest version, there looked to be about six or seven other files.
Watching this with interest, if you guys figure it out please post a guide and link to it because you're not alone. My Netflix stopped working when I upgraded to 10.1 as well (interestingly it worked fine on my ICS One-Click ODIN Rom that I got last June, not CM) and this was the first thread to pop on my google search as I've started looking for answers.
*UPDATE* Got mine working using the directions in this thread: http://forum.xda-developers.com/showthread.php?t=2101525
Hope this helps!
Kaepernick said:
Well, it was working. Then it quit. I checked the xml file and it had switched to 10. Didn't sign in or out or anything. Tried the 6 file and it immediately switched back to 10. So, I uninstalled and then installed 1.8.1. Replaced the nfxpref file with the one I backed up and it worked. Funny thing, it's actually using an older version of the player. I believe that may actually be "6". In cm7.2, it said "9" and was using a newer version of the player (newer than the one I'm using now). It seems to work well so far. Haven't tried updating from this yet, to see if the newest one works by updating, but I doubt it would work anyway. I did notice that in the shared prefs folder, there's only one other file with the nfxpref file. In the newest version, there looked to be about six or seven other files.
Click to expand...
Click to collapse