hi guys, as title says, will any custom roms allow bell mobility TV to work? im just curious, on my older phone that i put CM9 onto i could not get bell mobility tv to work, it would say it stopped working, even after 30 different builds,
is this the same case here? or does it work? Thanks!
I just tried mine running task650 aokp and after the app opens it tells me that my device is not supported. But, maybe I'll try changing my build.prop so that it reflects a Bell Canada phone and not an American AT&T phone.....might work....I'll have to get back to you.
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
patthe said:
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
That is also possible....may not work until we get the holy Jellybean update. Going to be tomorrow night before I get back to my computer to get at my backed up original build.prop to compare device ids and stuff.
jethro650 said:
That is also possible....may not work until we get the holy Jellybean update. Going to be tomorrow night before I get back to my computer to get at my backed up original build.prop to compare device ids and stuff.
Click to expand...
Click to collapse
ok good to know, and rom wise what is a good rom to run right now? i notice there is jellybean roms and cm10 rom, well cm10 is jelly bean i know that but whats the differences? i know my old phone, all roms where gingerbread and cm9 was ics, so of course you'd go cm9 if you wanted ics because its your only choice
and not sure device id wise, but i got this for you if it might help, kernel version 3.0.8-20120814.100513-user and build number of imm76d.i747mvlalh1
patthe said:
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
The App is Jelly Bean compatible, as I am using it on the latest leak. I have tried to flash Bell's csc on top of other ROMs in the past and have had no luck getting Mobile Tv to work. This includes AOKP CM10 and stock ROMs from other countries. On my S2 as well. Maybe there is something in Build.prop, but I haven't been able to figure anything out.
BCSC said:
The App is Jelly Bean compatible, as I am using it on the latest leak. I have tried to flash Bell's csc on top of other ROMs in the past and have had no luck getting Mobile Tv to work. This includes AOKP CM10 and stock ROMs from other countries. On my S2 as well. Maybe there is something in Build.prop, but I haven't been able to figure anything out.
Click to expand...
Click to collapse
where do i find this leak? , i kinda want for some reason to keep being able to use mobile tv, i gave it up before but now with this phone being faster and just better than my old, i wouldnt mind to have the ability to watch some tv when i bored lol
update: i found the leak, put er on my phone too, yay jelly bean, so what is the difference or advantages of running say CM10 vs this jellybean update from bell? thanks
Octanee said:
where do i find this leak? , i kinda want for some reason to keep being able to use mobile tv, i gave it up before but now with this phone being faster and just better than my old, i wouldnt mind to have the ability to watch some tv when i bored lol
update: i found the leak, put er on my phone too, yay jelly bean, so what is the difference or advantages of running say CM10 vs this jellybean update from bell? thanks
Click to expand...
Click to collapse
The Bell leak is somewhat buggy, but not enough to keep me from using it as a daily. The reason I use it over CM10 is simply because I love Touchwiz. CM10 seems way faster and loads of other benefit, but I think that Samsung has done really well with this as stock. If you don't stay stock, the Bell TV app will not work (to the best of my experience). It all comes down to what you like and what you want to work.
Octanee said:
hi guys, as title says, will any custom roms allow bell mobility TV to work? im just curious, on my older phone that i put CM9 onto i could not get bell mobility tv to work, it would say it stopped working, even after 30 different builds,
is this the same case here? or does it work? Thanks!
Click to expand...
Click to collapse
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
kvpxray said:
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
Click to expand...
Click to collapse
interesting, i have not personally used or edited roms or files as such, how would i go about that more specifically? decompile a rom and put that into the .prop or open .prop in notepad or what lol
i am a technical computer guy but when it comes to androids and such and their builds, i know how to root, and flash and all that dealio just not about their filesystem structure, etc,
Octanee said:
interesting, i have not personally used or edited roms or files as such, how would i go about that more specifically? decompile a rom and put that into the .prop or open .prop in notepad or what lol
i am a technical computer guy but when it comes to androids and such and their builds, i know how to root, and flash and all that dealio just not about their filesystem structure, etc,
Click to expand...
Click to collapse
Download ES File Explorer, and under settings make sure: Root explorer, up to root and mount file system are checked.
Go into the /System/ Directory and you'll see the build.prop file in there, press and hold to bring up the menu and open as a text file, and you should see the settings in there that you can change
kvpxray said:
Download ES File Explorer, and under settings make sure: Root explorer, up to root and mount file system are checked.
Go into the /System/ Directory and you'll see the build.prop file in there, press and hold to bring up the menu and open as a text file, and you should see the settings in there that you can change
Click to expand...
Click to collapse
so this is a sure fire way to get mobile tv to work?, if so then i'd go to CM10 or something if its worth it vs bells jellybean,
also if i root and put cm10 on, can i undo it all and unroot, etc so that if i had to get the phone fixed they would never know it happened? or is there some special internal sucker that knows that youve went custom and doesnt revert back that the factory checks?
sorry i suck at explaining some times but i hope that worked LOL
Octanee said:
so this is a sure fire way to get mobile tv to work?, if so then i'd go to CM10 or something if its worth it vs bells jellybean,
also if i root and put cm10 on, can i undo it all and unroot, etc so that if i had to get the phone fixed they would never know it happened? or is there some special internal sucker that knows that youve went custom and doesnt revert back that the factory checks?
sorry i suck at explaining some times but i hope that worked LOL
Click to expand...
Click to collapse
Haha, I think i got it. Yup, so far so good on my phone running CM10, in fact I'm using it right now! hahah.
There's a thread under the development section that tells you how to root without tripping the counter so that no one will know that you've rooted. And I believe that all you have to do to unroot is to flash an original stock rom
Please read forum rules before posting
Questions go in Q&A
Thread moved
FNM
kvpxray said:
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
Click to expand...
Click to collapse
This works for me also running task650's jellybean aokp.
I just edited this file, but I am still greeted with, "Coming to your device soon!"
Wiped app data with Titanium; rebooted as well.
I see this issue is current.
Any suggestions?
Edit: I am on 10/04 nightly
Sent from my SGH-I747 using xda app-developers app
otoolerc said:
I just edited this file, but I am still greeted with, "Coming to your device soon!"
Wiped app data with Titanium; rebooted as well.
I see this issue is current.
Any suggestions?
Edit: I am on 10/04 nightly
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Did you reboot after making the changes? I got the exact same message when opening the app. Made the changes and rebooted and started watching TV.
Beautiful, sir.
For the record: I had restarted, initially, but when it didn't work and I went back to the file to review the text once again, I realised I forgot to stick that capital M in there. I changed it, saved it, but still no tv - simply because, I didn't restart again.
Cheers bud.
Sent from my SGH-I747M using xda app-developers app
I'm curious if anyone has got this working with Rogers Live TV. I have edited my build.prop to reflect what has been posted in this thread to no avail. I am running the latest AOKP. I have even taken editing the build.prop as far as modifying the description and fingerprint.
The ro. product.name may be different for Rogers. The rest should be the same. After editing make sure you save the edited file. Hopefully you have a nandroid in case changing something here makes your phone non-booting. After saving the edited file reboot, if that doesn't work reboot recovery wipe cache/dalvic/fix permissions and try that. If none of that works you may have to get a Rogers stock ROM and see what those four lines are on stock and change them to reflect that.
BTW- which app are you using to edit the build.prop?
Related
Hello all,
I was looking through, the development section when I realized there was no thread about how to edit the build.prop file.
The build.prop file helps Google Play and other apps identify what device you have.
This guide will show how to edit the file to get maximum app availability. You can also edit the file in order to change the pixel density and there are quite a few other changes as well.
(Note: This does not work on the stock kindle fire rom)
The first thing you should do is backup the build.prop file to your enternal storage.
(The build.prop file is located in the folder)
Once you have made a backup, you are free to edit it.
Change the following lines to:
ro.product.model=GT-I9100
ro.product.brand=samsung
ro.product.name=GT-I9100
ro.product.device=GT-I9100
ro.product.board=GT-I9100
(a few more rows down)
ro.product.manufacturer:samsung
Save your changes, reboot your device and you will have access to the complete android market. Gameloft games that say, "Your device is not compatible with this, game please request a refund" will work. Please note that it could take up to an hour before Google starts to think that you have a GT-I9100.
Enjoy the full market experience right from Cm7-9,
Greg
Thanks. This is a great guide!
Just a warning though: Some games/apps really are incompatible even though they may show up.
veeman said:
Just a warning though: Some games/apps really are incompatible even though they may show up.
Click to expand...
Click to collapse
This is true, but a majority of the games at least will work. It is more the Gameloft games that can start having problems.
Lemme throw this out there...
Many ROMs already have a device ID set. Currently on my gedeROM, I'm listed as a Galaxy Tab. Is the build.prop easy enough to change to any device? And could we take time to post in this thread, settings for other compatible devices? I do like my KF to be registered as a Kindle. And I would guess some device IDs offer benefits over others?
TinkerToyTommy said:
Lemme throw this out there...
Many ROMs already have a device ID set. Currently on my gedeROM, I'm listed as a Galaxy Tab. Is the build.prop easy enough to change to any device? And could we take time to post in this thread, settings for other compatible devices? I do like my KF to be registered as a Kindle. And I would guess some device IDs offer benefits over others?
Click to expand...
Click to collapse
The steps that I just posted above will work on almost any device running a stock rom or a custom rom. For some reason, it just does not work on Kindle Fire stock rom. There are benefits to each device, some device's have similar hardware as others. But if you are looking for more apps, the Nexus devices have the best app availability. just as a random example, the GT-I9100 might have a more similar processor to the Kindle then a Galaxy Nexus.
Sent from my Galaxy Nexus.
Could someone please post the original build.prop settings before making these changes.I didn't save a copy of it before I changed them and my KF has been stuck in portrait mode for some reason ever since I did this several days ago. Unfourtunately it didn't yield any better results for me in the Google Play store anyway even though my KF is rooted with KFU and I use GoLauncher.Thanks guys :laugh:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
technut said:
Could someone please post the original build.prop settings before making these changes.I didn't save a copy of it before I changed them and my KF has been stuck in portrait mode for some reason ever since I did this several days ago. Unfourtunately it didn't yield any better results for me in the Google Play store anyway even though my KF is rooted with KFU and I use GoLauncher.Thanks guys :laugh:
Click to expand...
Click to collapse
If you use root explorer it will save a backup for you
Sent from my LG-P999 using xda premium
eoy4 said:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
Click to expand...
Click to collapse
I am using the same ROM and am wondering the same thing. I will try it to see if the same thing happens to me.
Sent from my Kingle Fire running CM10 Jellybean
eoy4 said:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
Click to expand...
Click to collapse
It should be fine as long as you don't change anything important.
veeman said:
It should be fine as long as you don't change anything important.
Click to expand...
Click to collapse
What's an example of an app that doesn't show up using the default build.prop on my ROM?
I did this and after reboot everything seems fine except my brightness is stuck on high and nothing I've found will adjust it.
Any ideas?
Sent from Epic Touch ICS
eoy4 said:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
Click to expand...
Click to collapse
Had the same problem, so i booted in to recovery and wiped dalvik and cache then rebooted system.
I follow all the steps and the result is that phone is booting but the screen is tatally in black. Already did Dalvik and chache wiping proces with no lucky results...
Any idea what else I could do...
I did it on a LG Hub...
Regards
Thank you for this.........thank you very much
Wouldnt it be better if the build.prop was of a Nexus 7
All u really need to change in the build.prop is two lines
ro.product.model=Kindle Fire(or whatever it is)
ro.product.brand=Amazon(whatever it may be)
To
ro.product.model=Nexus 7
ro.product.brand=google
BTW this will work on any ROM
Sent from my Nexus 7 using XDA Premium HD app
This'll work right now on Euroskank(CM10) as that's what I'm on. Want to try on something else, try it should work I wont test.
YOU SCREW UP GOOGLE WALLET IT'S ALL ON YOU
What to do...
Move app to system>app
edit build.prop
Code:
ro.product.device=maguro
ro.product.name=yakju
ro.product.model=Galaxy Nexus
reboot
enter Google Wallet
edit build.prop
Code:
ro.product.device=d2tmo
ro.product.name=d2tmo
ro.product.model=SGH-T999
reboot
Give Thanks
got it working
This originally worked for me on stock, but didn't seem to stick for some reason. When I tried to use it a few days later, Wallet just told me that my phone wasn't authorized. I had to go back in and change my build.prop back to the maguro settings. Then it worked just fine.
it opens and I can log in, but I get unsupported device in the upper left corner of app. Does that mean it no work? (sorry, I am noob).
Thanks
i get insecure element
Sent from my maguro using xda app-developers app
qben88 said:
worked on caspers AOKP nightly build 3. should add that after you edit the build prob, go into play store and download wallet. then push the modded wallet from here to system and open up wallet.
Click to expand...
Click to collapse
Why the hell would I add that if 1. I didn't do that. 2. that makes no sense. Just follow the directions and it'll work.
mikew29 said:
it opens and I can log in, but I get unsupported device in the upper left corner of app. Does that mean it no work? (sorry, I am noob).
Thanks
Click to expand...
Click to collapse
It means you are rooted. That's all.
this has an updated wallet that removes the unsupported device message. i followed this for a more permanent solution, not to say this method doesnt work but this is a more widespread method. http://forum.xda-developers.com/showthread.php?t=1794733
qben88 said:
this has an updated wallet that removes the unsupported device message. i followed this for a more permanent solution, not to say this method doesnt work but this is a more widespread method.
I did this and nfc service kept crashing..
Click to expand...
Click to collapse
You guys need this one. I have used this on stock and cm10. On stock u have to flash the NFC tw fix first then this. On cm u just flash this. I used the htc_jewel build.prop. anyways I get no unsupported device bull sit and everything works awesome.
http://forum.xda-developers.com/attachment.php?attachmentid=1236702&d=1343889041
which one did you flash. theres a way to do it with TW and one for all others. read a little bit more and try again. i had to read it a couple times and even went to the original modaco post before i flashed.
Any one else have a crash issue? Mine will vibrate and say Nfc services crashed
omega46 said:
Any one else have a crash issue? Mine will vibrate and say Nfc services crashed
Click to expand...
Click to collapse
Do u guys read? U had to flash the wrong one. Same thing happened to me a long time ago then I tryed the version I posted on page 1 and have been good since
Did as instructed, doesn't say "unsupported device" so that's good. Now I need to test to confirm.
Sent from my S3
Has anyone been able to get this to work on a, LH2 base rom
Sent from my SGH-T999 using Tapatalk 2
sarni84 said:
Do u guys read? U had to flash the wrong one. Same thing happened to me a long time ago then I tryed the version I posted on page 1 and have been good since
Click to expand...
Click to collapse
um yes I read, and followed the basic instructions. Thank you for your witty sarcasm, +1 for you buddy.
Anyway, I followed orig post and got the insecure error. Then went over to the thread with the lib fix and all works well with the exception of the nfc services error. Wondering if anyone on a tw rom is having the same issue or suggestion. Thank you in advance
Ronsha95 said:
Has anyone been able to get this to work on a, LH2 base rom
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
um yes I read, and followed the basic instructions. Thank you for your witty sarcasm, +1 for you buddy.
Anyway, I followed orig post and got the insecure error. Then went over to the thread with the lib fix and all works well with the exception of the nfc services error. Wondering if anyone on a tw rom is having the same issue or suggestion. Thank you in advance
Click to expand...
Click to collapse
Nothing will work on an LH2 base until Sprint gets an update that lib files can be pulled from. For this reason I flashed Wicked ROM and had to temporarily mod the build.prop and flash the latest update.fix file. Haven't tested it yet but I feel confident it will work as setup went smooth once I took those steps. If you are willing to use a ROM version prior to LH2 it will work.
Thanks for this. I installed wallet a week ago, but couldn't add any cards, saying that it has failed. I just did this on my phone and I could finally add my card. THANKS! Going to go test it out tomorrow. I am on Wicked v5.
s0nniez said:
Thanks for this. I installed wallet a week ago, but couldn't add any cards, saying that it has failed. I just did this on my phone and I could finally add my card. THANKS! Going to go test it out tomorrow. I am on Wicked v5.
Click to expand...
Click to collapse
Great! I've got my fingers crossed. If for any reason it should fail this time when I test tomorrow, I'll just wait for Jelly Bean, lol.
s0nniez said:
Thanks for this. I installed wallet a week ago, but couldn't add any cards, saying that it has failed. I just did this on my phone and I could finally add my card. THANKS! Going to go test it out tomorrow. I am on Wicked v5.
Click to expand...
Click to collapse
Tested today and it's working fine! I'm on Wicked V5 too.
This is my first post, so it would not let me reply to the thread here
http://forum.xda-developers.com/showthread.php?t=1739426
i wanted to give thanks as i really appreciate the rooted stock ATT 4.1.1 ...... your super quick! I am up and running jelly bean now, and i still have my root... i had a minor issue of odin saying "pass" after flashing but my phone was stuck in boot loop untill i went into recovery mode and did a factory reset. Im not sure if that is normal or not but whatev it works great now
doing the same thing right now. i'm in germany so i'm not sure if that's what's causing the slow download speed 500Mbps link @ a convention center, but i'm at 416MB out of 617MB and very very very patiently waiting.
it's good to hear that you only ran into that small issue. i'll keep an eye out for it. Thanks!
ak907 said:
This is my first post, so it would not let me reply to the thread here
http://forum.xda-developers.com/showthread.php?t=1739426
i wanted to give thanks as i really appreciate the rooted stock ATT 4.1.1 ...... your super quick! I am up and running jelly bean now, and i still have my root... i had a minor issue of odin saying "pass" after flashing but my phone was stuck in boot loop untill i went into recovery mode and did a factory reset. Im not sure if that is normal or not but whatev it works great now
Click to expand...
Click to collapse
Welcome to XDA!
I'm downloading it on my computer at home right now but I was in a rush to get to work. Looks like I'll have to wait until my lunch break to flash this, haha.
Also I see you're from Wasilla! Enjoying the weather? (I'm originally from Fairbanks)
Maroon Mushroom said:
Welcome to XDA!
I'm downloading it on my computer at home right now but I was in a rush to get to work. Looks like I'll have to wait until my lunch break to flash this, haha.
Also I see you're from Wasilla! Enjoying the weather? (I'm originally from Fairbanks)
Click to expand...
Click to collapse
First post here as well. I was rooted on stock, and this flashed flawlessly. Not 1 problem. Thanks!
ran the update, installed cwm and the phone works flawlessly minus one issue. gaming has become laggy. anyone else with studder or lag issues?
Aww man. It figures, I just finished flashing another rom like, about 18 hours ago. Now with finals coming up, I don't have time to do this one! Oh well, I guess I have something to do AFTER finals then, hahaha.
bluemax189 said:
ran the update, installed cwm and the phone works flawlessly minus one issue. gaming has become laggy. anyone else with studder or lag issues?
Click to expand...
Click to collapse
Is your power saving mode on? I've always found it makes so many things laggy, unfortunately. Might be enabled by default on the rom. Worth a look.
Great community here. Yesterday I was non-rooted ICS. Today I'm rooted JB with Wallet.
My phone just got 1000% better.
First of all, I appreciate all the Devs hard work bringing these Roms to us! :good:
I was running rooted UCALH9. Updated to this JB via Odin and all SEEMED good. Problems I had:
1) Play Store FC's - FIX - I went into Application Manager and removed updates for the Play Store app, which reverted it back to the default Play Store app. This fixed my problem. MAKE SURE YOU DO NOT UNINSTALL!
2) Rom Manager - I would get root user authentication error when trying to Fix Permissions. Everything else in Rom Manager worked. No fix at this time.
3) Gallery - None of my pictures were showing up. This is even after clearing caches. I am convinced it's because I can't Fix Permissions, but what do I know... No fix at this time.
Any help would be appreciated!
Damn I had that same Play Store FC problem yesterday -- I wish I'd have figured that out. I ended up doing factory reset lol.
I receive same fix permission error as you, but I rebooted into recovery to do it.
egyan said:
Damn I had that same Play Store FC problem yesterday -- I wish I'd have figured that out. I ended up doing factory reset lol.
I receive same fix permission error as you, but I rebooted into recovery to do it.
Click to expand...
Click to collapse
You didn't happen to play with the camera at all, did you?
I can live with the Fix Permissions via CMW, so that would clear up 2 out of 3 of my problems. All I need is a fix for the Gallery problem, and I can go back to Official JB.
Thanks!
Howl long was the flash?
I'm inside Odin on flashing system.img.ext4 right now and it stays there which looks like about 20% for last 10 minutes with no forward movement.
How long do I need to wait before I consider something is wrong with flash process?
Changing cable to Samsung one did the trick if you are in the same situation.
Can you do this AFTER upgrading to Jellybean?
questionmillennium said:
Can you do this AFTER upgrading to Jellybean?
Click to expand...
Click to collapse
Wondering the same thing. I already installed the official JB and set all my stuff up. Will this wipe all of those settings or just simply inject the root files?
questionmillennium said:
Can you do this AFTER upgrading to Jellybean?
Click to expand...
Click to collapse
greystealth said:
Wondering the same thing. I already installed the official JB and set all my stuff up. Will this wipe all of those settings or just simply inject the root files?
Click to expand...
Click to collapse
If you are talking about flashing the root injected JB i post, yes you can flash it after upgrading and no it won't wipe anything in data, everything should be preserved for you.
Weather here sux.... Hovering slightly above 0 degrees with 80 mph winds for the last week so add on the wind chill factor and u can only imagine... And no snow yet.
So far no other issues with this rom. Seems to run perfectly. Now just waiting for someone to write a power menu options and enable stock tethering script =P
Sent from my SAMSUNG-SGH-I747 using xda premium
You might try wiping data for gallery app and I think it's media storage app...see if that helps with gallery.
Toested said:
You didn't happen to play with the camera at all, did you?
I can live with the Fix Permissions via CMW, so that would clear up 2 out of 3 of my problems. All I need is a fix for the Gallery problem, and I can go back to Official JB.
Thanks!
Click to expand...
Click to collapse
Flashed this over stock and works flawless no lag no stutter. Thx
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ak907 said:
This is my first post, so it would not let me reply to the thread here
http://forum.xda-developers.com/showthread.php?t=1739426
i wanted to give thanks as i really appreciate the rooted stock ATT 4.1.1 ...... your super quick! I am up and running jelly bean now, and i still have my root... i had a minor issue of odin saying "pass" after flashing but my phone was stuck in boot loop untill i went into recovery mode and did a factory reset. Im not sure if that is normal or not but whatev it works great now
Click to expand...
Click to collapse
Wanted to say the same thing. ..thanks all came from black jelly to rooted jb with mobile Odin with no problems !
Sent from my SAMSUNG-SGH-I747 using xda premium
Anyone figure out how to enable stock jellybean lock screen?
Sent from my SAMSUNG-SGH-I747 using xda premium
Neflhiem said:
Wanted to say the same thing. ..thanks all came from black jelly to rooted jb with mobile Odin with no problems !
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I kinda miss the added features from the rom I was on frosty jb but I'm adding things here and there, wish we had multiview seems cool but I'm just waiting for the 4.2 roms to start coming out but so far not too bad, except the flash counter thing, but I'm happy with it so far just need someone to put out a hd theme like the one I had on my phone before but that to will come, also glad that the 4.2 camera with photosphere still works that feature is cool
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok. I am really upset with Tmo for blocking Wallet. I used it ALL THE TIME on my Nexus S on AT&T and I LOVED it. I've been trying to get it installed since October when I bought the phone and I cannot for the life of me get it to work. Everything I try fails or screws up the phone and I have to re-flash, so I eventually just said screw it and went to AOKP because I felt like trying something new. My friend said that I would be able to just install wallet once I did, but that is not the case. the install fails when using an apk, wallet is hidden in the market, and once when I got it installed it says "not available on your device/carrier blah blah blah" and quits. So, what I want is a solution. I need to know how to make this work because I am starting to get really upset. No solutions I can find work, nothing I've tried is successful... I might just be doing it wrong or missing something but I am determined to get it to work. NFC is working fine, I used it several times already.
Phone info:
Model: SGH-T999
Android Version: 4.1.2
Baseband: T999UVDLJA
Kernel: 3.0.48-cyanogenmod-faux123-att-tmo-00041-ga2c7267
AOKP Version: aokp_d2tmo_jb_milestone1
Build: aokp_d2tmo_userdebug 4.1.2 JZ054K eng.sethyx.20121029.025840 test-keys
I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.
Pennycake said:
I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.
Click to expand...
Click to collapse
I tried that the first time and it caused a failure to boot. second time, it was a program that was supposed to do it for me - same result.
If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app
Pennycake said:
If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
up until now I was using touchwiz. I screwed up the phone both times while using touchwiz. Now, I'm on AOKP and cannot find anything that works for that - everything seems like it's for touchwiz. What I tried was flashing wallet now on aokp, and it didn't harm the phone but the program will not work. If I load it, it just says "Unfortunately, Google Wallet is not yet available for your device or mobile network." and I want to know how to get around that on aokp, ignore touchwiz, I was just mentioning that because I ditched it in part due to the problems it had with wallet.
Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app
There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy
Pennycake said:
Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok ok, I think I understand you now. You still have to mod build.prop even on aokp? just don't have to do all that other stuff that you do have to do for touchwiz?
osmosizzz said:
There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2044362&highlight=wallet This thread?
I was using this exact app that it screwed up my touchwiz last time, and now it does not show an option for AOKP, just AOSP. Will the AOSP work?
Ok seriously. I didn't even run the app this time I just opened it and it screwed up my rom! God, why is this so infuriating! If someone had told me I would have to go through all this bull**** to get my stupid phone to work as well as my old, slow nexus s I would never have upgraded! BRB, time to reflash aokp.
*seeths with rage*
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
IF I'm not mistaken aokp is rooted by default. Anyways, I'm in the process of reinstalling it... again.
Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
used an app from the market to edit my build.prop and it works perfectly now. Thanks!
Q&A for [ROM][SPH-D710][KK][4.4.4] CyanogenMod 11 Official Nightly Builds
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
torch2424 said:
Yo! by the way, I don't know if it's my device or kit kat, but I've tried liquid smooth and this rom, and for some reason everything displays kinda blurry, or like low res on the screen. Is it because my dpi is too high or low? or is it a setting I gotta switch. Hopefully someone can help me out here, thanks!
Click to expand...
Click to collapse
Yeah, this is a problem with CyanogenMod 11. It was not a problem with VILLUMINATI. Maybe Dastin can help fix the issue in the main CyanogenMod build?
Here essentially is the problem and what I've found to be the solution - the LCD density settings are incorrect. It is set by default to 220, but that density doesn't seem to match the screen's native resolution. I read online somewhere that for the S2 the setting should be 240. It's not intuitive, but lower numbers actually result in higher resolutions. Because this phone's screen isn't as sharp/has a lower Pixel Per Inch (ppi) count than some of the later model phones, it needs the high 240 number to get the lower resolution to match what the screen natively displays (hopefully I just said that correctly). Anyway, when you get the correct resolution settings, even if they aren't as "high" things become less blurry and look sharper, since the native resolution is correct.
So, how to change this? Here goes:
Download the "File Explorerer ES" app (it's free) from the app store.
Open the app
Click the menu icon in the top left.
Expand "Tools"
Turn on "Root Explorer" (and give the app root access whenever you get prompted... you'll need root to edit the system file).
At the top of the screen, click on "Storage".
At the top of the screen, click on "/". The goal here is to get to the root (aka /) of your filesystem, where the file we want is.
The top of the screen should now say "Device". If so, scroll down the list until you find the file called "system", and then open it.
Scroll down again and select the "build.prop" file.
It will probably ask what program you want to use to open it with. Pick "ES Note Editor".
In the top right of the editor, click the settings icon, then pick the "edit" option.
Scroll down the file until you find the line that says "ro.sf.lcd_density=220". Change that so that the number is 240.
Click the back arrow at the top left of the editor. You should be prompted on whether you want to save. Click yes.
Reboot your phone. When you log back into it again, you should see clearer icons.
thanx
thanxxxxxxxxxxx
Blank APN list
My SPH-D710 on Ting isn't getting 3g or LTE since flashing to CM 11. I've tried a number of different radios including ICS, GB, and JB with no luck. If I look in the APN list under Mobile Networks the list is completely blank and if I try resetting the list to defaults nothing is restored. I've tried factory resetting the phone several times and each time I clear all the caches, etc. Does anyone have a trick I can try?
Yes. First flash a stock ROM. Update prl profiles and whatever until ting works. You'll hopefully have 3g and lte doesn't matter because it won't work on this phone after jelly bean. Then flash whatever you like.
thegoatmilkguy said:
My SPH-D710 on Ting isn't getting 3g or LTE since flashing to CM 11. I've tried a number of different radios including ICS, GB, and JB with no luck. If I look in the APN list under Mobile Networks the list is completely blank and if I try resetting the list to defaults nothing is restored. I've tried factory resetting the phone several times and each time I clear all the caches, etc. Does anyone have a trick I can try?
Click to expand...
Click to collapse
haci30 said:
The day I have been waiting for, CM11 and WiMax 4G working great so far.
Click to expand...
Click to collapse
What carrier do you use? I can't get boost to connect to 4g...
Sent from my SPH-D710 using Tapatalk
Huh... I just was in Jacksonville and couldn't pick up anything driving all over the city lol
Sent from my SPH-D710 using Tapatalk
hello
QA Bot said:
Q&A for [ROM][SPH-D710][KK][4.4.4] CyanogenMod 11 Official Nightly Builds
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Click to expand...
Click to collapse
thank you for the cm11 ,i will keep using this rom till it came to L
anyone know why my battery become fast drain after flash this rom,i'm been 3 days using it.
haci30 said:
I have 4g at home and work now when I stream music so works great for me.
Click to expand...
Click to collapse
I also have 4g -- I live in Hendersonville, TN, just outside of Nashville. On Sprint.
SMS Issues
Hi:
FWIW, I have been suffering these same text-messaging issues since going to CyanogenMod 11 on my SPH-D710 a few months back. I also recall seeing at least 1 or 2 other users on the older 'Villumiati' thread with similar issues, never resolved to my knowledge. I'm also on the FL24 modem, and re-flashed that as well a month or so ago to no avail. I have found that I can 'refresh' my text messages by going into "airplane mode" and then turning the radio back on, but this is not a very practical solution. Also, in case it might be a factor, I should include that my Sprint account is configured to use Google voice so that I can see/reply to SMS messages online. I'd appreciate any/all ideas as to how to 'fix' this issue, as it has caused all sort of social 'problems' related to not getting messages. (Also, I cannot send messages when this problem occurs, resulting in more time going in-and-out of airplane mode just to send a simple message).
(edit: this posted to a different forum - the above was in reference to posts #205-207 here: http://forum.xda-developers.com/epi...anogenmod-11-official-nightly-t2852074/page21)
Dastin, thanks again for everything that you do!
Installing CM 11
I apologize if this sounds like a very newb question, but I want to install CM 11 on my Epic 4g Touch. I simply haven't used it in a long time, and I won't even be using it as a phone. I am rooted on a stock 4.3 with AGAT recovery. Do I just need to load an AOSP kernel and then flash CM 11? Is it that simple, or do I need to load a different modem as well?
Thanks!
i have lg optimus gk f220k.
can any one help me pleas. i purchased many new memory card, bud when i insert it into my phone it only shows cd card inserted, but not shows drive in file manager or in storage.
what can i do??
Sent from my LG-F220K using XDA Free mobile app
Sent from my LG-F220K using XDA Free mobile app
eclorian said:
I apologize if this sounds like a very newb question, but I want to install CM 11 on my Epic 4g Touch. I simply haven't used it in a long time, and I won't even be using it as a phone. I am rooted on a stock 4.3 with AGAT recovery. Do I just need to load an AOSP kernel and then flash CM 11? Is it that simple, or do I need to load a different modem as well?
Thanks!
Click to expand...
Click to collapse
Try here Sir http://forum.xda-developers.com/showthread.php?t=2637510
[GUIDE][HOW-TO]Go from stock unrooted to 4.4.2 in 10 minutes or less! No PC needed!
SuperSU crashing
It appears that after flashing the latest nightly of CM11, my phone has lost root. SuperSU is installed, but no apps can are using it. I can't modify the /etc/hosts file on my phone. Is there something that I need to do other than flashing superSU from the recovery menu to get root working? I also checked one of the free root checkers from the play store and it also said that my phone wasn't rooted.
I came from Touched by S4 ROM, made sure to default and wipe everything before moving to CM11. While on touched by S4, I had root.
TIA for any assistance.
harrijs said:
It appears that after flashing the latest nightly of CM11, my phone has lost root. SuperSU is installed, but no apps can are using it. I can't modify the /etc/hosts file on my phone. Is there something that I need to do other than flashing superSU from the recovery menu to get root working? I also checked one of the free root checkers from the play store and it also said that my phone wasn't rooted.
I came from Touched by S4 ROM, made sure to default and wipe everything before moving to CM11. While on touched by S4, I had root.
TIA for any assistance.
Click to expand...
Click to collapse
Try to flash super Su again. Or just reflash cm.
3g
Linux guy said:
Yes. First flash a stock ROM. Update prl profiles and whatever until ting works. You'll hopefully have 3g and lte doesn't matter because it won't work on this phone after jelly bean. Then flash whatever you like.
Click to expand...
Click to collapse
Hi linux guy,
Thanks for your note up, but unfortunately I followed your steps reverted back to stock GB28 where everything including 3g was working perfectly and then flashed CM11 with ICS modem but all I get is a 3g icon on the signal bar but there is no actual internet?!!, is shows connected but no net!
My camera will not take video! Anyone have the solution to this problem?
Did you try using a different resolution? I know mine would only take 480, until i flashed this new kernel...
http://forum.xda-developers.com/showthread.php?t=2978105
Sent from my SPH-D710 using XDA Free mobile app
APNs in Dec. nightlies
Latest nightlies (12/20, 12/23, 12/24) lost ability to send text completely. Send button is grayed out and does nothing. Thought it might be due to the change in APN settings. Going to settings - mobile networks - apns does nothing. Read back through the thread several times and resetting apns back to default does nothing, the choices to choose sprint, boost, VM, or ting never appears. Tried wiping /system, /data, and /cache and installing fresh. Still same results. Restoring back to my last known working nightly (11/23) texting works fine again without ever going to APN settings.
Am I missing something?
4G WiMax?
Please tell! Do you mean you actually have 4G WiMax working on CM 11 with this kernel???
@dirtyhewr
I sent some screens of the difference between before and after on the kernel's thread...
http://forum.xda-developers.com/show...php?p=57664744
... This phone now runs better than it ever has... No lags at all anymore! I am running cm nightly with the trim+FPbug kernel... AND 4g still works... Anytime i have flashed another kernel on this ROM, 4g stops working...
... Also, and i don't know if it has anything to do with kernel, it must, but i can now record 1080hd with the camcorder... I have never been able to do that before!
Make sure you thank @Lanchon for his work here... This is huge for this device!
Sent from my SPH-D710 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 09:36 PM ---------- Previous post was at 08:52 PM ----------
Does 4G work on the 11-12-14 SNAPSHOT build? Which nightly do I need to use to get 4G WiMax up and running again? When I first updated to 4.4.4 a long time ago, WiMax was killed by upgrading beyond 4.2.2 forever.
RedRover88 said:
Please tell! Do you mean you actually have 4G WiMax working on CM 11 with this kernel???
@dirtyhewr
Click to expand...
Click to collapse