Related
I tried searching for this but haven't found anything on it, so I decided to post this.
There is a lot of skepticism on this.
Now I have heard it doesn't come preloaded but that UMA hooks (UMA is what Wi-fi Calling uses) are on the development piece.
Which makes sense since they will need to have it there for Skype.(Microsoft owns Skype)
This is the info I know, but I just wanted insight from more experienced developers.
Is it possible to use T-mobile Wi-fi Calling on Windows 8x?
Wifi Calling! Maybe
To follow up on the question I posted earlier:
Benjam'in said:
I tried searching for this but haven't found anything on it, so I decided to post this.
There is a lot of skepticism on this.
Now I have heard it doesn't come preloaded but that UMA hooks (UMA is what Wi-fi Calling uses) are on the development piece.
Which makes sense since they will need to have it there for Skype.(Microsoft owns Skype)
This is the info I know, but I just wanted insight from more experienced developers.
Is it possible to use T-mobile Wi-fi Calling on Windows 8x?
Click to expand...
Click to collapse
I have found some proof on the Internet here:
HTML:
https://skydrive.live.com/?cid=7ac840829c778f5e&id=7AC840829C778F5E%212924&sff=1&authkey=!ANhBCDuIfFrB2P0
And it seems as though an OTA update has been hitting some phones here are the specs:
OS version: 8.0.102211.204
Firmware revision: 1532.20.20010.531
Hardware revision: 0003
Radio software: 1.11b.32.19.23_2_15.42.32.19
Just wanted to pass this information on for others.
-Benjam'in
To follow up on my earlier post:
Benjam'in said:
I have found some proof on the Internet here:
HTML:
https://skydrive.live.com/?cid=7ac840829c778f5e&id=7AC840829C778F5E%212924&sff=1&authkey=!ANhBCDuIfFrB2P0
And it seems as though an OTA update has been hitting some phones here are the specs:
OS version: 8.0.102211.204
Firmware revision: 1532.20.20010.531
Hardware revision: 0003
Radio software: 1.11b.32.19.23_2_15.42.32.19
Just wanted to pass this information on for others.
-Benjam'in
Click to expand...
Click to collapse
I was on the phone with three different techs giving me the run around like phone techs love to do.
But, I eventually got to the bottom of what is going on. The above firmware release was accidentally released on March 20th it hit 1000 or so phones causing more problems then good and also containing wifi calling. This firmware was then pulled back and has yet to resurface. (If it even will resurface again) This is also disappointing do to the fact that now the HTC 8x has been labeled EOL.
Just thought I would inform everyone who is interested.
In a lighter note, some windows phones coming out soon will have wifi calling.
-Benjam'in
Benjam'in said:
To follow up on my earlier post:
I was on the phone with three different techs giving me the run around like phone techs love to do.
But, I eventually got to the bottom of what is going on. The above firmware release was accidentally released on March 20th it hit 1000 or so phones causing more problems then good and also containing wifi calling. This firmware was then pulled back and has yet to resurface. (If it even will resurface again) This is also disappointing do to the fact that now the HTC 8x has been labeled EOL.
Just thought I would inform everyone who is interested.
In a lighter note, some windows phones coming out soon will have wifi calling.
-Benjam'in
Click to expand...
Click to collapse
Thanks sssooooo much for this info! I have an HTC 8x with the 20008 firmware that I bought a couple of weeks ago. I was wondering what happened to this update! That was the whole reason I pulled the trigger on it...the promise of WiFi calling...the Nokia's that TMO had were all crap. Maybe we can get someone with the 200010 firmware to dump it off their phone?
compu829 said:
Thanks sssooooo much for this info! I have an HTC 8x with the 20008 firmware that I bought a couple of weeks ago. I was wondering what happened to this update! That was the whole reason I pulled the trigger on it...the promise of WiFi calling...the Nokia's that TMO had were all crap. Maybe we can get someone with the 200010 firmware to dump it off their phone?
Click to expand...
Click to collapse
Yes I wanted to make sure it had wifi calling before I bought it. (Thank God I know a Tmobile Reseller) - he let me play with the phone till I found out what was going on, also let me talk to someone knowledgeable (Dealer Line).
TMO did happen to land the Lumia 925 (Release in July sometime, Nokia's current flagship phone) which is what I will probably go with, although they haven't mention whether it will have the wifi calling or not, but the Lumia 521 (or something close to that, crappier version of current lumia's) will be released with wifi calling.
Which makes me hope/assume they would put it on the Lumia 925.
Good Luck to you though.
-Benjam'in
Thanks. I actually got a good deal on a sealed, NIB 8x on eBay. I desperately needed to replace my iPhone 3GS and I didn't want to go with the iPhone 5. I am guessing when the next update comes, it will have Wi-Fi calling. I heard it was in beta, and still has a major bug with "Wi-Fi only" mode (I'm guessing that's why they pulled it).
The 925 looks pretty damn sexy, though!
---------- Post added at 07:33 PM ---------- Previous post was at 06:55 PM ----------
I was actually just reading the Windows blog about the Lumia 521, and it says that WiFi calling will be delivered to those devices OTA starting on 5/20. Maybe it will get delivered to other devices as well? *crosses fingers*
Source:
http://blogs.windows.com/windows_ph...an-you-buy-for-under-150-answer-not-much.aspx
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
McDastardly said:
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
Click to expand...
Click to collapse
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
What features were taken out? Anything that can be replaced with better apps on the market shouldnt count. In my opinion the new stock task manager makes it worth it.
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
Well if I could go back in time I would have just waited for a custom 4.3 tw rom. But at least I don't feel the need to flash a new rom every day now.
ThePagel said:
What features were taken out?
Click to expand...
Click to collapse
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
galets said:
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
Click to expand...
Click to collapse
I can understand your annoyance with the hidden menu being gone. But that wasn't a "feature" it was a "hidden menu" after all and with root there are ways to get rid of the volume warning. That bugs the crap out of me as well but not to the point to change it yet.... YET!
galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
Click to expand...
Click to collapse
Nah, Samsung hasn't been overwhelmingly developer friendly for awhile. There's a bit of dislike for them due to Exynos processors.
Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step. That's why it was mentioned multiple times to not accept the 4.3 update in case it locked the bootloader.
Samsung hasn't been developer friendly for a long time. Anytime you take an OTA update you can expect it to prevent the use of custom firmware unless a trusted source says it doesn't.
Sent from my SCH-I535 using Tapatalk 2
Hey everyone, just looking for advice mainly.
I just recently bought my M8 as I retired my DNA which I ran ViperDNA for the past couple of years. I am still on a grandfathered unlimited plan, thus the reason for creating a thread. I haven't been in depth with androids in quite a while. I simply rooted and rom'd my DNA, and left things.
A little background - obviously I have the M8 and unlimited data. I also have a macbook pro, and my old windows 7 laptop died out on me. And finally, I am not the most code savvy anymore and wish to keep things simple.
What I am looking for from my new phone is pretty simple. I am perfectly fine with most things stock on it. All I would really like to do is remove the tethering block, and possibly delete a bit of the bloatware that came with it.
From my reading, it looks like I need to root to be able to tether. If I root without flashing a custom rom, am I still able to update when they hit verizon? Will simply rooting my phone give me the options to remove bloatware?
If not, what other options do I have? I am passed the point of wanting to wipe my phone from time to time to update and such. I tend to keep everything on it, and it gets old having to re-personalize it to my liking.
Thanks in advance for any help.
I would say a good choice is root/unlock and install the Viper ROM for the verizon M8. This ROM will do OTA updates as they come out and does not require you to re-personalize. I have been running this ROM for several months now and have had no issues. Great solid ROM.
HollywoodTate said:
Hey everyone, just looking for advice mainly.
I just recently bought my M8 as I retired my DNA which I ran ViperDNA for the past couple of years. I am still on a grandfathered unlimited plan, thus the reason for creating a thread. I haven't been in depth with androids in quite a while. I simply rooted and rom'd my DNA, and left things.
A little background - obviously I have the M8 and unlimited data. I also have a macbook pro, and my old windows 7 laptop died out on me. And finally, I am not the most code savvy anymore and wish to keep things simple.
What I am looking for from my new phone is pretty simple. I am perfectly fine with most things stock on it. All I would really like to do is remove the tethering block, and possibly delete a bit of the bloatware that came with it.
From my reading, it looks like I need to root to be able to tether. If I root without flashing a custom rom, am I still able to update when they hit verizon? Will simply rooting my phone give me the options to remove bloatware?
If not, what other options do I have? I am passed the point of wanting to wipe my phone from time to time to update and such. I tend to keep everything on it, and it gets old having to re-personalize it to my liking.
Thanks in advance for any help.
Click to expand...
Click to collapse
Just root won't stop ota's but do you want to keep root? There are certain apps that you can use from the play store for tethering that say they get around needing the paid service for tethering. I have used them in the past but i like the native tether app my phone didnt seem to get as hot. Honestly never tried any on my m8 rooted and soff since aquirering the phone. If your not interested in flashing want ota and root.. Might want to root and soff.
See that the last post offered viper ROM good ROM allows what you want.
From having had Viper previously, I will say I loved it. But at the same time, there was still a bit of flashing to do and that is not what I am looking for at the moment. As for the apps to use to get my tether working, nothing that I know of will allow wifi tethering without root.
So I guess my question at this time is am I able to just simply root my phone to do all that I have mentioned above without flashing a rom? Are there other steps I need to take to reach my goals? I am fine with the stock rom. I just dislike bloatware, need the wifi tethering, and would also not mind to have the battery saver app that comes stock but is hidden.
Thanks for the suggestions so far.
Well, you can use Weaksauce to root only, the question is if you will keep root through the next OTA update. Nobody will know until you try it....
Just rooting will not allow you uninstall apps on the /system partition. You need to be S-off for that. Somebody correct me if I'm wrong, but that is my current understanding of S-on on this device......
There is a way to tether without root: it's the paid version of FoxFi. Not the most elegant solution from what I'm reading, but it works.
But you know, I think you would get everything you desire by getting S-off, flashing a custom recovery and then CleanROM. It's strictly debloated, perm-rooted stock. Clean, simple and stable.
And when the next OTA comes out, you can bet that Scott will put out a CleanROM version of it in no time. Why is that harder than taking an OTA?
It just involves downloading a file and flashing it in recovery..
I'm curious to see the outcome of the OP. I recently came back to Android from using an iPhone for over a year. I went to the iPhone because I was tired of roming and never being content with the device performance. There was always bugs, updates or new kernel. Now that I'm back I'm getting the root itch again but really want to refrain of tinking with it and going through that downward spiral again. I love the stock look and would like to deploy maybe try a asop rom or two.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I like clean ROM also.... It is kept up-to-date very well... The good stuff worth having in an ota is usually offered by most devs very quickly. I don't know what was needed on your DNA to root and unlock for custom recovery but the m8 process is really quite easy (if you have a PC) lol.
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
ddgarcia05 said:
I'm curious to see the outcome of the OP. I recently came back to Android from using an iPhone for over a year. I went to the iPhone because I was tired of roming and never being content with the device performance. There was always bugs, updates or new kernel. Now that I'm back I'm getting the root itch again but really want to refrain of tinking with it and going through that downward spiral again. I love the stock look and would like to deploy maybe try a asop rom or two.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe a gpe ROM? Lol so may choices. The problem with to root or not to root is that its an option now but what if an ota patches the exploit allowing the root? Then you don't have an option except to wait for another exploit if you didn't root and soff your device. If you ask me I would rather have the control to make that decision and not be forced into one. You never know when an update includes a patch for known exploit(s). Just my opinion.
ddgarcia05 said:
I'm curious to see the outcome of the OP. I recently came back to Android from using an iPhone for over a year. I went to the iPhone because I was tired of roming and never being content with the device performance. There was always bugs, updates or new kernel. Now that I'm back I'm getting the root itch again but really want to refrain of tinking with it and going through that downward spiral again. I love the stock look and would like to deploy maybe try a asop rom or two.
Click to expand...
Click to collapse
No spiral with CleanROM. Check out the thread. It's pretty boring - which is good! Because there are no bugs (unless introduced by users flashing something on top of the rom), it works just as good as stock, battery is great.... Flash and forget....
thunderbls said:
I like clean ROM also.... It is kept up-to-date very well... The good stuff worth having in an ota is usually offered by most devs very quickly. I don't know what was needed on your DNA to root and unlock for custom recovery but the m8 process is really quite easy (if you have a PC) lol.
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
Maybe a gpe ROM? Lol so may choices. The problem with to root or not to root is that its an option now but what if an ota patches the exploit allowing the root? Then you don't have an option except to wait for another exploit if you didn't root and soff your device. If you ask me I would rather have the control to make that decision and not be forced into one. You never know when an update includes a patch for known exploit(s). Just my opinion.
Click to expand...
Click to collapse
Exactly right! It seems to be getting harder and harder to find exploits for root, S-off etc. Anybody think it'll get easier with Android L??? I don't.
You can always flash back to stock, but you never know if the next update won't lock it down for months - or longer....
Rather than removing the bloat, I'd use something like Titanium Backup to just freeze it. I can't say for sure about this phone but my last phone was a Razr Maxx. With that phone, if any of the bloat was removed, the update would fail. If you just froze the apps, you could always unfreeze them, then run the update.
I am basing this thread on "[Q] How To Root the Straight Talk SCH-S968C Samsung Galaxy S III" (the latter portion of it)
Hey all, creating a new thread on this as it has blew up in the past couple of days and got the original thread all sorts of off topic. I am sharing my findings here in hopes that it will help others get Lollipop running on their StraightTalk S3 (or KK roms based off of CM after the 9/7 updates).
First a little history. Before the unified roms I was running d2vzw LiquidSmooth without any issue, then in late Feburary (2/26) the S3Unified rom was built, putting the correct rilblobs in /system/lib upon boot (if I am reading the code right that is). This was when I noticed that the Unified rom broke the S3 ST phone (no data), so I spent a couple of days researching and learning how to build roms and came up with this commit to LiquidSmooth, I noticed a few days later that it was pulled into the CM source, so all roms were back to working with our phone. I also vaguely remember something with rilblobs needing reverted around this time. So at this time, everything was working, up until the 9/7 CM updates where the rilblobs were once again changed. I worked with one of the CM devs (invisablek) on this issue and we were never really able to figure out what the issue was, the radio was throwing all sorts of odd error messages and would never connect. During that time there was enough of a change that even the old rilblobs wouldn't work (spent about a week worth of evenings trying to no avail). So I ended up giving up until 5.0 hit.
Yesterday I came across a d2lte CM12 build! Flashed it and was quite impressed to see everything working except mobile (both calling and data). In that thread I ran across the first linked thread here and seen that inserting a sim card seemed to work, so I hit up a coworker (on AT&T) and asked him if I could borrow his sim. He agreed, so I pulled the battery, popped in the sim and was AMAZED to see mobile working again, did a test call, browsed on 3g, and everything was working quite well. Got home last night and found an old (deactivated) sim card in my basement, popped it and have ran CM12 all day. Hooked it up to the bluetooth head unit in the car, setup a second account for my son, taken a few pictures, everything seems to be working fine.
One thing that has bugged me for a while (which I rarely use) was that MMS stopped working (not sure exactly when, but I'd guess back on 2/26), so I spent some time today pulling apart files, modifying things, and really haven't gained much (at least for the stock MMS). I did get hangouts working as MMS by adding an apn (Hangouts -> Settings -> SMS -> SMS Enabled, then scroll to the bottom and click on Access Point Names, Add one with the following settings Name Verizon Internet, MMSC http://mms.vtext.com/servlets/mms MMS proxy and port are blank, MCC 311 and MNC 480 ). I haven't completely given up on the stock messenger app, but I am done with it tonight.
Here are the things I have done so far:
Modified build prop to include TracFone Settings
added apns-conf.xml to /system/etc (and modified it a few times)
a few different apps to change APN settings (seems like all of them fail)
If anyone wants, my wifes S3 hasn't been touched, so I can get any of the 4.1.2 rom files from it if its helpful to anyone. I did run across this but I haven't had time to try it yet, and I ran across another page where they modified the messenger.apk and changed some of the apn settings in there (definitely interested in looking into this).
Also to clarify, what I believe is happening here with the sim card is this, Verizon updated their RIL's to require a SIM (make sense since they use 4G), and if it doesn't find one it shuts down the radio in the phone, so until ST updates their RIL's, we will probably be stuck. It might be interesting to see if some could 'emulate' having a sim card in using a 3rd party app (its well beyond my programming capabilities I am afraid).
Sorry for my rambling, but I hope this has been helpful to someone, and I am hopeful that this will take off and let the ROOTING thread go back to helping people root . Please post any other SCH-968C findings you have here, maybe we can get a good collection of information in one place.
RiXtEr
@rixter13 so you're telling us that what we already suspected was true, we have figured out that the verizon device the roms are for requires a SIM so that's why we needed it also, we have suspected that the rom is trying to drive our device the same way it does the verizon, now, how do we remove the 4g function from the ROM so it bypasses needing the SIM or 4g function and just go straight for 3g as our phones normally would? or how do we mod the stock MMS apk so it plays nice with our 3g
also I consulted with motorhead at AA51 and explained what was happening with the roms on our device and he mentioned that the rils were gonna be a b****h, we've all been digging at this trying to get it surrounded, we've approached from every angle we can think of, its to the point that its gonna take some dev to fix
or call straight talk and get them to enter the APNs because they can't be entered manually on straight talk so we need a volunteer to call them and see if them doing the APNs will fix our issue, I have a feeling it won't because if the sim is required for the rom to work then even if the APNs are done by straight talk the SIM might mess that up because with the SIM in the system pulls the APNs from the SIM, so what is on the SIM might wipe out the APNs that straight talk enters from their end. I've stopped trying to think like the phone and started trying to think like the ROM, its gonna follow its programming unless we change the ROM, I no longer think the data tricks and edits are gonna work unless the ROM is cracked open and things for our phone spliced in and the verizon stuff taken out. Can this be done?
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
@rixter13 so you're telling us that what we already suspected was true, we have figured out that the verizon device the roms are for requires a SIM so that's why we needed it also, we have suspected that the rom is trying to drive our device the same way it does the verizon, now, how do we remove the 4g function from the ROM so it bypasses needing the SIM or 4g function and just go straight for 3g as our phones nornally would? or how do we mod the stock MMS apk so it plays nice with our 3g
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Well, unless StraightTalk (or someone else) comes out with android 4.4.4 rilblobs that don't force a SIM check we are stuck with the SIM card hack. The cm patches from 9/3/14 on are what caused our phones radio's to stop working properly.
As for the MMS issues, I haven't yet had the time to dig through the code to see what changed where (I am assuming I would be looking for a pre Unified commit 2/26 or around that time). I will try to tear apart that apk and look around in there for a smoking gun, but currently my PC is dead (lightening wiped out my motherboard) and I don't have any android tools on my wifes machine. So it may be a few days before I can get that done.
I will keep you posted on any progress (or lack thereof) on this, if anyone tries anything in this area (even if it doesn't work) I'd like to know about it so we don't waste more time running down the wrong path.
how about we have everybody pull logs, would that help?
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
how about we have everybody pull logs, would that help?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
So the radio logs often have the IMEI number in them, so we need to be careful there posting them, I can pull logs from a VM I have on my work computer and compare them to my wifes 'virgin' ST S3.
rixter13 said:
Well, unless StraightTalk (or someone else) comes out with android 4.4.4 rilblobs that don't force a SIM check we are stuck with the SIM card hack. The cm patches from 9/3/14 on are what caused our phones radio's to stop working properly.
As for the MMS issues, I haven't yet had the time to dig through the code to see what changed where (I am assuming I would be looking for a pre Unified commit 2/26 or around that time). I will try to tear apart that apk and look around in there for a smoking gun, but currently my PC is dead (lightening wiped out my motherboard) and I don't have any android tools on my wifes machine. So it may be a few days before I can get that done.
I will keep you posted on any progress (or lack thereof) on this, if anyone tries anything in this area (even if it doesn't work) I'd like to know about it so we don't waste more time running down the wrong path.
Click to expand...
Click to collapse
so users with non SIM compatable devices are screwed, I've got 4.4.4 on my KFHD7 and my S2E4GT and neither one of them are SIM compatable so how do they run 4.4.4 without one?
wait! let me guess, those devices have an internal SIM?
so you're saying that even if we strip all the verizon stuff we'll still need the SIM for anything 4.4.4 and up?
there's even a 5.0 for the S2E4GT
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
so users with non SIM compatable devices are screwed, I've got 4.4.4 on my KFHD7 and my S2E4GT and neither one of them are SIM compatable so how do they run 4.4.4 without one?
wait! let me guess, those devices have an internal SIM?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
rixter13 said:
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
Click to expand...
Click to collapse
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha
Sent from my SCH-S968C using Tapatalk
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
rixter13 said:
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
Click to expand...
Click to collapse
has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha
Sent from my SCH-S968C using Tapatalk
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
The good news (if there is such a thing) is we get a fresh start with Lollipop. It looks like the first efforts for the SIII was to DE-Unify the rom . The flipside of this coin is that the Lollipop builds are still buggy. Once I get my main machine back up and running, I may try to roll my own rom for the SCH968. I have compiled CM and Liquid roms, but never ventured out on my own yet.
N_psycho_PD_uh? said:
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha
Sent from my SCH-S968C using Tapatalk
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
So RIL stands for Radio Interface Layer (essentially the radio drivers), so even if you could get them for the AT&T, they don't help us since our phone uses Verizon towers. And as far as I know, they are closed source and carrier specific, which is what makes this an almost impossible feat.
rixter13 said:
So RIL stands for Radio Interface Layer (essentially the radio drivers), so even if you could get them for the AT&T, they don't help us since our phone uses Verizon towers. And as far as I know, they are closed source and carrier specific, which is what makes this an almost impossible feat.
Click to expand...
Click to collapse
its a good thing that anything is possible, the trick is HOW? I'm actually kind of enjoying the challenge with this phone, my other devices have been easy compared to this one, this things like a finicky @$$ cat that got rubbed the wrong way! I'm actually learning something from you guys on this one, I might just go get another pain in the @$$ device when we get this one beat, I know everyone has tried with the H2 device but I'd like to find an exploit to root it so we can get what is in the H2 because its not available, I thought about just pulling what I can from it before I downgrade to root, kinda why I've waited to root it, gotta be a way to root this one
Question, does anyone know what part of the H1 had the vulnerabilities and is there a way to take these parts out of H1 while leaving everything else and apply those parts to the H2 to give it the same vulnerabilities so that stock H2 can be rooted, I've been trying to track down every root method I can find, I've read about rooting devices with another rooted device but they both have to be OTG capable, I've also wondered if there's a way to use the s-beam feature on this device to root it since it is another way to push or pull data to and from it, I know nothing of these things though, I'm just a thinker, but I do wonder about that and if anyone has tried even if its only remotely possible its worth a shot but it would take someone that knows way more than I, I learn fast but I wouldn't know where to start with that.
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
its a good thing that anything is possible, the trick is HOW? I'm actually kind of enjoying the challenge with this phone, my other devices have been easy compared to this one, this things like a finicky @$$ cat that got rubbed the wrong way! I'm actually learning something from you guts on this one, I might just go get another pain in the @$$ device when we get this one beat, I know everyone has tried with the H2 device but I'd like to find an exploit to root it so we can get what is in the H2 because its not available, I thought about just pulling what I can from it before I downgrade to root, kinda why I've waited to root it, gotta be a way to root this one
Question, does anyone know what part of the H1 had the vulnerabilities and is there a way to take these parts out of H1 while leaving everything else and apply those parts to the H2 to give it the same vulnerabilities so that stock H2 can be rooted, I've been trying to track down every root method I can find, I've read about rooting devices with another rooted device but they both have to be OTG capable, I've also wondered if there's a way to use the s-beam feature on this device to root it since it is another way to push or pull data to and from it, I know nothing of these things though, I'm just a thinker, but I do wonder about that and if anyone has tried even if its only remotely possible its worth a shot but it would take someone that knows way more than I, I learn fast but I wouldn't know where to start with that.
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Chainfire could root the H2's. It'd be best to ask him.
heXacode said:
Chainfire could root the H2's. It'd be best to ask him.
Click to expand...
Click to collapse
how do I go about doing that? He's a complete stranger to me, I've used plenty of things that are his though
Sent from my SCH-S968C using Tapatalk
Speaking of the H2, what android version is on it?
N_psycho_PD_uh? said:
how do I go about doing that? He's a complete stranger to me, I've used plenty of things that are his though
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.
rixter13 said:
Speaking of the H2, what android version is on it?
Click to expand...
Click to collapse
4.1.2.
As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
heXacode said:
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.
4.1.2.
As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
Click to expand...
Click to collapse
yeah its 4.1.2 why?
the H1 and H2 are identical except for the patched kernel and the fact that H2 has two different versions itself, a qcom and a exynos
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
yeah its 4.1.2 why?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
No explanation as to why. They just don't handle that kind of thing which sucks.
heXacode said:
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.
4.1.2.
As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
Click to expand...
Click to collapse
yeah I know, I'd rather try myself than bother him, he has bigger fish to fry than a prepaid ST, even if it is one of the better S3's (H2/qcom anyways)
Sent from my SCH-S968C using Tapatalk
---------- Post added at 10:37 PM ---------- Previous post was at 10:33 PM ----------
Im gonna like seeing what I can do with CM on 2Gb RAM with no bloat!
Sent from my SCH-S968C using Tapatalk
So to give an idea of what we need, here are the ST (older) rilblob files (ignore the dates listed below):
-rw-r--r-- 1 root root 3.7M Dec 3 19:46 libril-qc-qmi-1.so
-rw-r--r-- 1 root root 49K Dec 3 19:45 libril.so
and here are the new ones (VZW):
-rw-r--r-- 1 root root 2.5M Feb 28 2008 libsec-ril.so
-rw-r--r-- 1 root root 53K Feb 28 2008 libril.so
(the same files as the later ones are found on Lollipop as well)
I am looking into how to decompile a .so file at the moment.
rixter13 said:
So to give an idea of what we need, here are the ST (older) rilblob files (ignore the dates listed below):
-rw-r--r-- 1 root root 3.7M Dec 3 19:46 libril-qc-qmi-1.so
-rw-r--r-- 1 root root 49K Dec 3 19:45 libril.so
and here are the new ones (VZW):
-rw-r--r-- 1 root root 2.5M Feb 28 2008 libsec-ril.so
-rw-r--r-- 1 root root 53K Feb 28 2008 libril.so
(the same files as the later ones are found on Lollipop as well)
I am looking into how to decompile a .so file at the moment.
Click to expand...
Click to collapse
so do you intend to swap or decompile both and paste parts of the ST into the other? Just trying to reason out what you are doing for myself so I understand it better, I am pretty new at this depth, been rooting and romming a short time but only been into modding system for about two months or so so don't get too far over my head, I can follow you but don't take it for granted that I understand what you are saying, I'm learning, you won't have to wait on me ill catch up quick just give ne the time and resources.
Sent from my SCH-S968C using Tapatalk
---------- Post added at 11:18 PM ---------- Previous post was at 11:05 PM ----------
to give you an idea when, CM11 4.4 was the first ROM I ever flashed lol
Sent from my SCH-S968C using Tapatalk
Don't hold back the details. I "need" (not want)... "need" to know if I put Nougat on the Galaxy S6 if it will just make it ridiculously slow and unusable or could it actually improve it?
I do not believe in putting new software on old hardware, for all devices, but I would really not like to hear "guesses" - but people who know from others who have done it or who have done it themselves.
I want to put the Samsung factory unlocked Nougat on the S6. I'm not asking for instructions on how. I just want to know if its worth it.
Thanks!!!!!
---------- Post added at 08:08 AM ---------- Previous post was at 08:08 AM ----------
[/COLOR]
searcherrr said:
Don't hold back the details. I "need" (not want)... "need" to know if I put Nougat on the Galaxy S6 if it will just make it ridiculously slow and unusable or could it actually improve it?
I do not believe in putting new software on old hardware, for all devices, but I would really not like to hear "guesses" - but people who know from others who have done it or who have done it themselves.
I want to put the Samsung factory unlocked Nougat on the S6. I'm not asking for instructions on how. I just want to know if its worth it.
Thanks!!!!!
Click to expand...
Click to collapse
Ok I don’t use my s6 full time. In fact it’s become my backup. I did use my s6 on android N prior to upgrading and had no issues with it running it at all.
In fact I still power it up and play with it now as I will no doubt use it again and I believe it performs very well to this day. I’m sure battery life is an issue regardless of what os is running as the battery in the device itself isn’t big! But I’d have no doubt about putting android N on it again given the choice.
Sent from my iPhone using Tapatalk Pro
Sent from my iPhone using Tapatalk Pro
I'll say it in few words: the best version you'll ever use in your s6
Wow, even though just 2 replies, that makes me feel better. Thanks! I'll try to remember to post back here what happens after I do it. I will be needing to rebuild the phone too: New Battery, LCD and Camera... lol - I'm bothering because... well the phone has always done great. It "was" the best phone I've ever had, but now network updates are forcing me to move it into "current times" .