Related
Hi guys, just this week I got a new Galaxy Tab from T-Mobile, so far so good, but I have a few questions about it.
1-) This is my first time using Android, is there a better version or ROM for this particular tab (or another that is fully compatible) which I should flash into it which is better or gives me more functionality than the default Android installation that T-Mobile puts on it?
2-) How are upgrades of Android OS obtained? I heard 3.0 is out, any ideas if Samsung or T-Mobile will make it available on these devices?
3-) Can "Line2" be used with it? I noticed when I'm connected to Wi-Fi at home Line2 works, but when I'm connected to 3G it wont work.
4-) Is it easy to install Themes on the Galaxy Tab, any tutorials?
5-) Any specific tricks/tweaks or apps, that are a must have for Galaxy Tab owners?
Thanks in advance!
-Eli
I also just got my SGT T-mobile. What is the model number of your tablet? What is the Baseband version of your tablet? Have you rooted yours?
Mine's model is SGH-T849, Baseband T849UVJJB, and yes, I downloaded a program from this board which supposedly roots it, after installing and running the commands it said it had successfully rooted my device, now how do I know if it is really rooted?
Also what's the Baseband? lol sorry but I'm lost, this is my first ever tablet and also first ever Android OS device.
RealAct said:
Mine's model is SGH-T849, Baseband T849UVJJB, and yes, I downloaded a program from this board which supposedly roots it, after installing and running the commands it said it had successfully rooted my device, now how do I know if it is really rooted?
Also what's the Baseband? lol sorry but I'm lost, this is my first ever tablet and also first ever Android OS device.
Click to expand...
Click to collapse
We both have the same model and baseband. I'm not sure what baseband is. You can check to see if your tablet is rooted by going to Applications and look around to see if you can find a Superuser icon.
If it's rooted, I guess your next step is to find a custom ROM and flash it.
Do you remember what you used to root your tablet? Was it SuperOneClick?
Yes, it was the SuperOneClick one from http://forum.xda-developers.com/showthread.php?t=812367
Baseband is the modem you have. The modem controls the phone, wirelass data, wifi, and bluetooth. Yours is JJB.
RealAct said:
Hi guys, just this week I got a new Galaxy Tab from T-Mobile, so far so good, but I have a few questions about it.
1-) This is my first time using Android, is there a better version or ROM for this particular tab (or another that is fully compatible) which I should flash into it which is better or gives me more functionality than the default Android installation that T-Mobile puts on it?
2-) How are upgrades of Android OS obtained? I heard 3.0 is out, any ideas if Samsung or T-Mobile will make it available on these devices?
3-) Can "Line2" be used with it? I noticed when I'm connected to Wi-Fi at home Line2 works, but when I'm connected to 3G it wont work.
4-) Is it easy to install Themes on the Galaxy Tab, any tutorials?
5-) Any specific tricks/tweaks or apps, that are a must have for Galaxy Tab owners?
Thanks in advance!
-Eli
Click to expand...
Click to collapse
Well, I'm not an expert but here is my experience:
1. You should flash the new Overcome experience Hermes:
http://overcome.mimzo.com/
There is also the unofficial cyanogenmod beta, but as you said the overcome is fully compatible and it will not change the feel of the Tab, just adds to the functionality.
2. The updates are two types:
# Official, these are over the air and you will find notifications in the notification area to tell you that there is a new update, or may be through kies for Samsung.
# Unofficial, which is basically flashing other ROMs whether official or custom.
# As for Android 3.0 (which is called honeycomb), it is not officially coming to the Tab. May be after the 3.2 announced a couple of days ago, but I still don't think so. Still, you might want to follow this thread as there are trials to get it fully working on the Tab:
http://forum.xda-developers.com/showthread.php?t=1122959
3. I don't have any idea about this, as I got mine used and then I rooted and flashed it the day I got it.
4. Of course there are themes for the Android. This Overcome I was telling you about has a Gold theme. There are a lot of ways to get themes on the Tab. I myself use different home launchers with different themes. You don't need to flash anything if you are just looking to change the looks of your device. Check this out and let me know if you like it:
Go Launcher EX https://market.android.com/details?id=com.gau.go.launcherex&feature=search_result
There are a lot other but this is my favorite. You can even change the fonts of the display.
5. The most common used tips and tweaks that you should use is over-clocking/ under-volting which gives you more speed and less battery drainage.
As for the apps, these are my favorites:
Tango, Photfunia, ezPDF reader, Movies (or IMDB), Springpad (or Catch), File Expert, Go Launcher, Go weather, Google Goggles, Google Shopper, Just reader, Splashtop, Plex, GrooveIP. I guess there are more on my device but these are the ones that I found more functional and fun to use.
Hope this helps...
Thanks rangercaptain,
Hey ahmadshawki, thanks so much, I will check out all of your suggestions, does overcome comes with Gingerbread?
Yes it does.
RealAct said:
does overcome comes with Gingerbread?
Click to expand...
Click to collapse
Any 2.2 rom is froyo (frozen yogurt).
Any 2.3 rom is gingerbread.
You can have either "flavor". They are both in the development section. Both are highly recommended.
Hi guys,
I've been visiting this forum for more than 6 months now, but I think this is my first post. I have a T-Mobile SGH-T849 GT-P1000.
Last year I unlocked it and changed it to a Gingerbread Euro. Below is the current setup:
Firmware version 2.3.3
Baseband version P1000XXJPZ
Kernel version 2.6.35.7 [email protected] #2
Build number GINGERBREAD.XXJQ1
Tab has been working fine, with the exception of:
- often does not remember wi-fi hotspots automatically, need to switch off/on wi-fi to do this
- 3G & phone works erratically. I don't use it as a phone, but those times that I tried I noticed the phone would loose connectivity to the mobile network and needed a reboot in order to fix it.
I'd like to upgrade it to Ginger 2.3.6, but which rom should I use? I checked on the forum, but I'm not sure if I should use this:
http://forum.xda-developers.com/showthread.php?t=1380595&page=3
or any other.
Is my modem correct or should I use this guide:
http://forum.xda-developers.com/showthread.php?t=902323&page=4
to install JL5 modem?
Sorry for the noob questions.
I have a galaxy tab 7+ sgh-t869 I need to chance my build prop in order to play order and chaos online it doesn't support operating system I have no idea how to chance it or what to change it to please help thanks
I would post this in the developer forum, but I'm new and don't have privileges yet. I just did a clean install of the Cyanogen 10.2 Mod of Android 4.3.1 on the Wifi model 8.9. Since then, I am unable to use Google Voice Search. Any ideas? It worked with my previous ROM without issues, but if I can't get it working here I might just reinstall that one.
In fact, it appears the mic in general isn't working and it was on the last ROM. Darn.
i_am_scifi said:
I would post this in the developer forum, but I'm new and don't have privileges yet. I just did a clean install of the Cyanogen 10.2 Mod of Android 4.3.1 on the Wifi model 8.9. Since then, I am unable to use Google Voice Search. Any ideas? It worked with my previous ROM without issues, but if I can't get it working here I might just reinstall that one.
Click to expand...
Click to collapse
Had this issue on my 8.9 3g model. I used Odin to revert to stock rom then reinstalled 4.3.1 after and the mic worked. Tab lagged a bit agfter though. Cyanogenmod 11 works better in my opinion. Give it a try.
So I just got a Nexus One and I was hoping to download a stock ROM for each Android version it went through. So I went to http://shipped-roms.com/index.php?category=android&model=Passion%20(Nexus%20One) but I cant figure out what the names mean. Can anyone help out with this?
I what I need is pretty much which is the ROM (most updated version) with Android 2.1, 2.2 etc.
try here
http://forum.xda-developers.com/nexus-one/general/n1-factory-image-t2915375
most of the PASSIMG would work..
Does anyone know how to fix the Ok Google voice function in android 7? It only works in the Google app and not everywhere.
tApPeD fROM mY nExUs 6
This works, if not try to do it with an older version of google app, and then update to latest beta
http://forum.xda-developers.com/showpost.php?p=69190540&postcount=82
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Strephon Alkhalikoi said:
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Click to expand...
Click to collapse
Just installed cyanide and it works very well
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Strephon Alkhalikoi said:
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Click to expand...
Click to collapse
No, i don't think so, it runs on aosp too, nitrogen
for example
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Strephon Alkhalikoi said:
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Click to expand...
Click to collapse
i actually think its a google now issue. both my lg k7 and lg blahblahblah both had it working on any screen, then it stopped working, and options disappeared. a few days later, the options reappeared, i enabled them, and now works again on any screen.
I guess I didn't word things quite right, as I meant to say the interaction between the Google app and ROM was causing the issue. Hopefully you're right about it being app related so I can move back to Pure Nexus.
I'll give it a shot... I'm running Chroma MM and it works but not in Nitrogen OS. I think it was working on the sky dragon ROM but I was having corruption issues on boot with it while using multirom.
tApPeD fROM mY nExUs 6
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Strephon Alkhalikoi said:
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Click to expand...
Click to collapse
Sorry to rehash this but it's a bit of a bump. It's actually not Google's fault. OoenGapps made a change back in September, changing HotwordEnrollment.apk. okGoogle anywhere has been broken ever since. It's only happening to AOSP Roms like the person above stated. The maintainers of CM for the 6P are trying to get to the bottom of it to see if they can do anything to fix the issue.
MrBrady said:
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Click to expand...
Click to collapse
Try to freeze the hotword enrollment apk.....I use ROM Toolbox Pro for this. It is a system app.....froze it and then followed the directions around the forums and google assistant worked for me on nitrogen on screen off, it seemed to me to be a little more "finicky" at starting from screen off then on stock, but that could just be me and how my voice training was saved or whatever....good luck
Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,
You can't use an M kernel on N or vice versa. Won't work.
joseph230 said:
Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,
Click to expand...
Click to collapse
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).
zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
I flashed radio of 7.1.1 over 6.0.1 and it did not cause any issues. This is a proof to what you just said. Kernel is full of bugs and that is hard to fix
Sticking with 6.0.1 for now! Maybe I should get back into using custom roms again!
Thanks.
joseph230 said:
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).
Click to expand...
Click to collapse
Heck 98, XP and 7 were the only good ones. Dont even get me started on 10. I had to go back and revert over 300 PC to windows 7 when the 10 upgrade happed. That was just a nightmare.
What sort of issues are you talking about? Besides the speakerphone echo.
zelendel said:
Your issue is 7.1.1. Android N is full of issues...
Click to expand...
Click to collapse
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.
Lawstorant said:
What sort of issues are you talking about? Besides the speakerphone echo.
Click to expand...
Click to collapse
Wifi and Radio connection drops all the time. Many people seem to experience it!
NLBeev said:
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.
Click to expand...
Click to collapse
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!
joseph230 said:
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!
Click to expand...
Click to collapse
It seems to me that Google changed policy.
Till now the changes made the N6 great again.
No encryption, dark interface when possible.
Aquamail is better than Gmail, Signal is better than G-messenger. Nova launcher is better than G-now launcher.
I replace/disable G-apps and G-services when possible.
No Google Assistant, no Fit, no Pay, no Game, no Hangouts, no Wearable, no G-drive, no G-now.
Runs smoothly, no issues. Excellent battery life. Good to have XDA.