Related
I've been working with a great group of developers over at PPC-geeks.com on the Titan bluetooth problems, and I'm proud to say that our efforts have been fruitful!
The History:
In case you didn't know, the Titan has had horrible official Bluetooth support, and even the custom roms only get it "partway" there.
HTC's latest CDMA device, the Touch, uses roughly the same hardware under the hood as the Titan, however their bluetooth worked flawlessly. So, clearly the hardware is capable, its a matter of running the proper software!
After many attempts at porting the Vogue (htc touch) Bluetooth drivers into any number and combination of titan roms, it was concluded that it is NOT the answer (sorry custel).
This was the first obvious approach, however every attempt had some problem or bug, or sometimes wouldn't even boot up!
So we took another approach...
The Solution:
Update the OS, but keep the drivers from an earlier build that had less new "issues" with BT. The 2.09 rom from sprint had stable bluetooth, however it had poor quality over the headset/handsfree profile. This was apparently NOT an issue with the drivers as much as it was an issue with how the OS handles them!
Replacing the OS with a ported AKU .7 from a Universal, and basing the rest of the rom on 2.09, we have what appears to be a release with stable, decent quality bluetooth that works as it should have out of the box!
More testing is needed, but it seems like the best build so far, and should be a strong candidate as a base rom for future customs.
What this fixes:
-No more poor BT quality
-No more random BT shutoffs
-No more system freezes when coming out of standby due to BT stack left on and disconnected
-No more D-pad lock issues
-Generally stable Bluetooth performance that works AS EXPECTED.
Known issues:
-Alarm Bug, which was and still is a part of 2.09
However, we're working on a fix for this.
Find it here:
ftp://ppcgeeks:[email protected]/Titan/Users/sfaure03/ithinkwegotsit.rar
(as of this writing, the ppcgeeks ftp and webserver have been hit pretty hard, and are timing out an awful lot, so if it doesn't work, try again later. Perhaps someone would like to mirror it somewhere?)
Special thanks to all who contributed to this effort, particularly PPC-geeks users Sfaure03, DogGuy, no2chem, jtrag, and all the others who tested, theorized, and gave sage advice.
Personal thanks to ImCoKeMaN, for explaining how things work and having the patience to answer bizzare questions from the rest of the group.
edit: whoops nevermind
I'm not expereinced enough in using this type of file - can you please tell me what is the procedure to install a .rar file into the phone.
its an .nbh file, rar is the compression method. Its like .zip, only you need winrar (or something compatible) to uncompress it.
there's a tutorial on ppc-geeks (which I should really post here as well) about how to unlock and flash custom firmwares on the titan.
you guys rock!
So installed this ROM a couple hours ago. So far the phone's working fine. Tested BT in my RAV4. Wife says it's much improved -- previously if I called from the carphone she'd known instantly and ask me to switch it off. Now she's says it's fine. (High praise indeed. )
So bottom line: quality issues appear much improved. Major kudos!
Update: maybe I was slightly hasty. So the phone sits in my pocket for a few hours. I press the power button to bring it out of sleep. Password screen takes 15 seconds to come up. Enter the password, Today screen takes 30 seconds. Click on the Voicemail link, get a message that the phone cannot make the call. (low RAM?) Nothing else (afaik) except SPB Mobile Shell running at the time.
Boom, soft reset. Is it the phone? Is it the ROM? Is it me?
Mirror at: http://rapidshare.com/files/71094429/ithinkwegotsit.rar.html
The ROM finally makes my BT usable, but is still quite choppy and compressed. Unfortunately not a true fix for my device.
But, kudos to the developers for getting it to be usable! Thanks!!! You clearly beat Sprint/HTC!
However, my RAZR2 and Touch still have much better BT, so will keep using them at least for awhile.
Will see if the 'official' Sprint ROM (1) actually happens, (2) truly fixes the problem. If not, then I'll use my Touch until the Treo 800w or Titan 2.0 come out and likely swap my Titan at that point.
Unfortunately, even if Sprint fixes BT, Titan 1.0 will never have adequate memory for WM6. Sadly, the lack of memory is an unfixable product design deficiency.
wsparvis said:
Unfortunately, even if Sprint fixes BT, Titan 1.0 will never have adequate memory for WM6. Sadly, the lack of memory is an unfixable product design deficiency.
Click to expand...
Click to collapse
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Dishe said:
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Click to expand...
Click to collapse
I have to agree here - the Cingular 8525 runs quite well with only 64MB of RAM (Other at work run it). My Titan runs quite well with only 64MB of RAM - HTC Home from the touch on the other hand makes it run like a three legged dog. Without the 3rd party plugins it zooms along quite well even with several apps running.
Dishe said:
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Click to expand...
Click to collapse
OK - fair enough, my memory comment WAS off topic! BTW you introduced the word "major"; I never said it was major - just unfixable. And, yes, you're right - if you want to manually do the OS's job for it, there is an acceptable workaround.
Interesting, though, that you responded only to that one sentence out of five in my post, not the other four which stated that BT quality is poor/mediocre on my device (which is an improvement from the prior unlistenable state).
Anyway - what kind of success rate are you seeing from various forums with this ROM? I still suspect the problem is partially HW, and that BT on some devices (mine probably one of them) may be unfixable.
Dishe said:
After many attempts at porting the Vogue (htc touch) Bluetooth drivers into any number and combination of titan roms, it was concluded that it is NOT the answer (sorry custel).
This was the first obvious approach, however every attempt had some problem or bug, or sometimes wouldn't even boot up!
So we took another approach...
Click to expand...
Click to collapse
Why call out another developer? I fail to see how it was necessary. I'm assuming you have no life, and make roms for a living? I'll download whatever works; but because of your approach to criticize other people who try (which is EXACTLY what you do) to make something work, makes me not want to download your rom.
dishe is an such arrogant SOB, who think he's all that because he's creating ROM...well props to you that you do create rom...but its just people opinion/wish about having more ram (which is UNFIXABLE! on mogul)...you don't have to bash them for it...would u preferred an old style laptop/computer from the 2000's or newer/faster in 07's. However, you might be able to upgrade their RAM through hardware...but does HTC have such RAM upgrade for mogul!? anyways...i'm not hating on your work at all...but i just get disgusted when you go and ranted on someone post (n it was a valid post.)
ps. If you want to brag, make something that's useful w/o any glitches. Success at that then brag all you want, but at this moment you still using the public to test whatever ya doing. So stop tripping home boy.
Wow, I've heard of people venting on forums, but this is rediculous. Did you all have really bad days or something?
Look, there's a lot going on that doesn't take place on this forum. I used to be a big XDA-dev's fan, but unfortunatley I've found that there just isn't enough research and development for our particular device going on here, so I started broadening my horizons.
Maybe I didn't make it clear in the first post, but I didn't make this rom.
At least, not by myself. I worked with a team of people from other boards and we formed a group that has been testing theories and building different rom combinations to try and come up with the best solution possible currently. We've made some amazing progress, and the nostalgic part of me wanted to come back to XDA and not leave you guys in the dark.
We've noticed Custel doing similar things on XDA, and we had already tried a lot of what he was doing. We found that the vogue BT didn't play nice with the rest of the Titan rom components in many situations, yet Custel kept trying. I beleive that some of the devs in our group tried to contact him, possibly even get him involved, share what we've learned so far (collaborative efforts are the best way to go). I don't know exactly what happened after that, and I didn't ask because its not my business. I mentioned him because he's still trying something, where we've had a bit of success. Not that its a race, but it would appear that we got there first using another method. I'm sorry that you read that as a "flame" on his part, I didn't mean to disrespect. Just that we we're doing is not what he's doing, and we've tried that route already.
Some of the others in the group of devs warned me not to go posting here. Thought maybe there would be too much animosity. I decided on my own to bring the information here because XDA was always a great source of info in the past, and there's no reason you guys should be left out. Are you trying to make me regret it, as if I'm wasting my time here?
Lazy and cool6324, I'm not forcing you to try this rom. I'm also not "bragging" about what was created. I'm filling you guys in. If you don't want it, that's fine. I won't bother updating.
hey DISHE
bro u dont even owe these guys an explanation, they contribute nothing and take everything. they dont understand whats involved and quick to criticize anything they dont agree with.
it appears to me that they think they are all that and a bag of chips/ but if the DEVs of these fixes decided not to share, i bet they would keep there mouth shut real quick/
bottom line bro, dont bother posting any more responses to these idiots / look at the end of the "
Hard-SPL - or how to not brick your PDA ever again" post and u will see what these guys are like on this forum, calling each other names and etc just like they r doing now.
i c u at ppcgeeks
Dishe said:
Wow, I've heard of people venting on forums, but this is rediculous. Did you all have really bad days or something?
Look, there's a lot going on that doesn't take place on this forum. I used to be a big XDA-dev's fan, but unfortunatley I've found that there just isn't enough research and development for our particular device going on here, so I started broadening my horizons.
Maybe I didn't make it clear in the first post, but I didn't make this rom.
At least, not by myself. I worked with a team of people from other boards and we formed a group that has been testing theories and building different rom combinations to try and come up with the best solution possible currently. We've made some amazing progress, and the nostalgic part of me wanted to come back to XDA and not leave you guys in the dark.
We've noticed Custel doing similar things on XDA, and we had already tried a lot of what he was doing. We found that the vogue BT didn't play nice with the rest of the Titan rom components in many situations, yet Custel kept trying. I beleive that some of the devs in our group tried to contact him, possibly even get him involved, share what we've learned so far (collaborative efforts are the best way to go). I don't know exactly what happened after that, and I didn't ask because its not my business. I mentioned him because he's still trying something, where we've had a bit of success. Not that its a race, but it would appear that we got there first using another method. I'm sorry that you read that as a "flame" on his part, I didn't mean to disrespect. Just that we we're doing is not what he's doing, and we've tried that route already.
Some of the others in the group of devs warned me not to go posting here. Thought maybe there would be too much animosity. I decided on my own to bring the information here because XDA was always a great source of info in the past, and there's no reason you guys should be left out. Are you trying to make me regret it, as if I'm wasting my time here?
Lazy and cool6324, I'm not forcing you to try this rom. I'm also not "bragging" about what was created. I'm filling you guys in. If you don't want it, that's fine. I won't bother updating.
Click to expand...
Click to collapse
Where was I supposedly contacted?
dishe don't even trip! The folks *****ing are the ones using the Roms also. Take their comments with a grain of salt....F**K EM!!!! Don't waste your time on these idiots. Others apperciate the work you do to make our Moguls useful.
to step: shut ur ass kissing d!ck sucking ***** depriving n a **** hole that you called a mouth! I dont even use BT, yeah its nice to have clean/custom rom to rig my phone. But a stock is fine with me. Just tired of people kissing dev's asses geeze....get them stick out of ur ass....
ps. i never did dish at dishe's rom nor either ***** at it....it was his tactics of bashing on people posts...so get it right...
lazee said:
to step: shut ur ass kissing d!ck sucking ***** depriving n a **** hole that you called a mouth! I dont even use BT, yeah its nice to have clean/custom rom to rig my phone. But a stock is fine with me. Just tired of people kissing dev's asses geeze....get them stick out of ur ass....
ps. i never did dish at dishe's rom nor either ***** at it....it was his tactics of bashing on people posts...so get it right...
Click to expand...
Click to collapse
LMAO...such childish folks here....I'm gonna just LMAO!! at u...so sad
Lazee,
its not about kissing ass. Its about appreciation for what these guys do (AND FOR FREE they do it!!!!) they rarely ask anything of the rest of us, if anything at all. Because of the fact that they do give up alot of free time, which they could be doing something else, to help out alot people they dont even know, i have a certain amount of respect for that alone, regardless if they might seem arrogant. the truth is that they really do care about people or they wouldnt even share what they do! theres no law that says that they have to share anything with us/ sometimes its easy for us to forget this and take it all for granit/ lets just call a truce and stop with the name callin and etc and try to maintain a respectible forum ok.
PEACE!!! come on guys we are all in this together
Oh and by the way Custel, u rock bro, do what it is u do and dont stop!! dishe luvs ya nothing personal, i dont want to speak for him but i get the feeling that things might have came out wrong when he was responding to the "lazee's post and was just a lil fluddered.
Why was I getting that error? It's gone now I just want to make sure it's answered for everyone else. I was flashing a rom and it was doing that. Do a reboot. Your system wont be there so reboot into botoloader and go back into recovery.
I'm getting the same error when trying to flash and when I reboot I can't get past the htc screen. I'm using the twrp recovery and I have tried resetting a few times.
EDIT**
I tried resetting my phone a couple more times and it finally just worked. I have no clue what causes this.
Original poster is correct, this method works for whatever reason. I tried it twice now.........
Same thing
Trying to flash a kernal. I tried several reboots of bootloader and recovery and no luck. I am going to flash clockwork since I am using team wins recovery and see if that works.
Same exact thing......OP's solution worked......Thank you
Yeah had this error too. I think it happens when you try to flash a different kernel on the stock ROM. After I switched to a different ROM the error went away.
Sent from my PG86100 using Tapatalk
I'm having the same issues, but rebooting isn't helping. TWRP needs to be updated to address this issue. Until then, no ROMs for me.
That error will usually occur with signature verification failures, you need to make sure that signature verification isn't turned on when installing an unsigned rom.
It would make sense if this has to do with permissions, but I have signature verification turned off in the bootloader. Is there somewhere else that signature verification needs to be turned off?
I'm getting this error trying to root the phone using the sticky guide. It happens when I try to flash the superuser file.
what the op said worked for me as well...restarted and everything worked fine
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
myn said:
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
Click to expand...
Click to collapse
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
I was receiving this error for two days after s-off and updated recovery. I was breaking my head trying to figure out a solution. I tried everything from switching recoveries to even pushing SU again. I also downloaded ROMe using my pc and my phone bc many ppl were calling the ROMs "corrupted." Nothing worked. I even received hate mail from multiple XDA members bc I was posting "too" many questions "without" searching the forum.
Solution, changing out my SDcard. LMAO, yes I know, wanted to run through a wall bc i had thought of it right off the back but did not want to believe my 32 gig card was causing the problem. I replaced with the card that came with the phone and BAM have been switching ROMs ever since.
Food for thought.
AssassinsLament said:
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
Click to expand...
Click to collapse
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
First off, who really cares about "Backup Naowz!" being an issue but you? I mean seriously, you're just trolling. So do you go tell people they can't speak improper english because you don't like it? Come on. We do this for free, for fun. If you paid us to make this recovery for you, then sure, if what you want is Backup Now!, we can do that for you. But you are using it for free. At least feel grateful of what we've done as a hobby for everyone instead of nitpicking 10+ issues on the smallest inaccuracies that go against your perfect world. Seriously, I'm sure others might like the "Backup Naowz!". Anyways, if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Here's the zip that was giving me the sideload errors.
I don't see any issues with the updater-script and the updater-binary is ver 3.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
i completely agree with polish and consistency portraying professionalism, and we're glad for and always open to suggestions. however, in this case, we purposely used that terminology. we, as teamwin, like to have fun with our projects. some of them are very serious (wimax, hdmwin, kernel manager). others are a bit more on the entertaining side (theninjatweeter, twinpic 3d). with the recovery, we wanted to do something that stood apart from the rest. we do things that reflect our personality as a team.
as for the sideload issues that many are experiencing, we've discussed many times in our threads as well as on twitter and even google+; it is an issue with an outdated updater-binary script. update the scripts, no more sideload errors.
to come out and say we're not willing to listen to suggestions seems a bit presumptuous, even dangerous, when the issues you put on our github were more along the lines of requests.
AssassinsLament said:
...
if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Click to expand...
Click to collapse
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
myn said:
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
Click to expand...
Click to collapse
Again, I don't mind real issues... That's not my point. My point is a lot of your so called bugs or issues are the way we cosmetically chose to do it. Your issues are more so opinions, and wish lists. There is a place for opinions, and a place for real bugs. That's all I am saying.
It would be on the same level as me using your bug/issue space to say "hey i don't like that color.", "hey, can you take off myn from everywhere in your rom, I like it without?" <--- these are NOT issues. These are just what I would like/want. Do you understand?
Anyhow, I am looking into your script. Sadly we do not have any documentation of the differences between api's but, I will try to figure it out. It looks simple enough, so it should work. I'll let you know.
I know I will almost indefinitely be flamed for asking this, but oh well here goes.
When I first got my AT&T SGS2, I installed an international rom (villain) It ran perfectly fine other than the fact calls were not operating properly. I immediately jumped ship though scared for my phone's life. I reflashed stock and AT&T modem, but now that I think back on it- wouldn't having flashed the at&t modem remedied that problem? and if truly need be couldn't an at&t version kernel be flashed( i.e. Entropy's DD) Everything seemed to operate perfectly fine (install went well, booted properly, smooth homescreen, apps running great)
In theory, replacing kernel/modem (and making sure the ROM doesn't include a bootloader) should work - however this is untested.
I'm going to be trying it tonight with SensatioN, as I did like that ROM when "hellraised" on Infuse and someone requested it, and it's about time someone tries to do a "hellraise" on an I9100 ROM.
Entropy512 said:
In theory, replacing kernel/modem (and making sure the ROM doesn't include a bootloader) should work - however this is untested.
I'm going to be trying it tonight with SensatioN, as I did like that ROM when "hellraised" on Infuse and someone requested it, and it's about time someone tries to do a "hellraise" on an I9100 ROM.
Click to expand...
Click to collapse
You go entropy. Awesome. I will be glad to test it for you if needed.
Sent from my SAMSUNG-SGH-I777 using XDA App
Very cool! I more or less figured as much but i'm not quite that daring. I would be willing to do testing as well ( Oh and Entropy, Sensation was the rom I was looking at ) I too came over from the Infuse.(Thanks for all the kernel love!)
Hammersuit said:
Very cool! I more or less figured as much but i'm not quite that daring. I would be willing to do testing as well ( Oh and Entropy, Sensation was the rom I was looking at ) I too came over from the Infuse.(Thanks for all the kernel love!)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1328110 - Once I get permission to do so from the SensatioN ROM dev, I'll post it in dev as a proof-of-concept with details of what I did to port it.
Note that I don't have too much time to continue maintenance of a ROM - it's not where my skillset lies and between Real Life and kernel work, I'm pretty busy as is! But at least this will provide a starting point for those that want to go further.
Entropy512 said:
http://forum.xda-developers.com/showthread.php?t=1328110 - Once I get permission to do so from the SensatioN ROM dev, I'll post it in dev as a proof-of-concept with details of what I did to port it.
Note that I don't have too much time to continue maintenance of a ROM - it's not where my skillset lies and between Real Life and kernel work, I'm pretty busy as is! But at least this will provide a starting point for those that want to go further.
Click to expand...
Click to collapse
you're correct bro. ports from i9100 roms are very possible. the one thing you will need to do is change some of the lib and bin files to rid the issues with the mic on in calls. i think ive successfully ported just about most of the i9100 dev section so far. lol. for personal use only. if you need some help just let me know.
Entropy512 said:
http://forum.xda-developers.com/showthread.php?t=1328110 - Once I get permission to do so from the SensatioN ROM dev, I'll post it in dev as a proof-of-concept with details of what I did to port it.
Note that I don't have too much time to continue maintenance of a ROM - it's not where my skillset lies and between Real Life and kernel work, I'm pretty busy as is! But at least this will provide a starting point for those that want to go further.
Click to expand...
Click to collapse
Ha! Completely understandable. Thank you so much though, this proof-of-concept is wonderful news. It would be most beneficial to see some ports of well-supported GT-I9100 roms such as villain and DLEV rom etc.
Looks like there might be some known issues with my PoC port then... as I said, I haven't tested outgoing audio much (this is much harder for me to test than dialing voicemail...)
task650 said:
you're correct bro. ports from i9100 roms are very possible. the one thing you will need to do is change some of the lib and bin files to rid the issues with the mic on in calls. i think ive successfully ported just about most of the i9100 dev section so far. lol. for personal use only. if you need some help just let me know.
Click to expand...
Click to collapse
Which files are those? I tried to find the relevant CM7 commit (since they had mic issues in calls) but couldn't find it.
I know that turning Samsung Noise Reduction off (or on? It's freaking unclear whether "on" is the current state or destination state in the menus) seems to work around the problem on a per-call basis.
Entropy512 said:
Which files are those? I tried to find the relevant CM7 commit (since they had mic issues in calls) but couldn't find it.
I know that turning Samsung Noise Reduction off (or on? It's freaking unclear whether "on" is the current state or destination state in the menus) seems to work around the problem on a per-call basis.
Click to expand...
Click to collapse
When I get home tonight ill look at which files I had to replace for dlev rom and shoot them over to you. Might be tomorrow depending on how late though bro.
Hi,
I'm currently S-ON rooted running a Senseless ROM. I've been tempted to go full AOSP/AOKP/CM9, but I keep seeing a caveat for the ROMs that there are issues with Bluetooth Calls. Before I plunge down that path could someone please elaborate on what the specific issue is? What should I expect? Are there workarounds?
I use bluetooth frequently in the car, so it has the potential to be quite important to me.
My understanding is that it is related to the kernel source being used and that is why it plagues all the versions, is this something that can be expected to be fixed, or will it always be an issue?
Thanks!
Bluetooth media will work fine. The issue with the calling is u only hear static. There's no fix or work around at this time.
Its being worked on at the moment. Could be tomorrow or next year. You never really know with these things.
Nobody is working on it right now. Chad wants to get to it, but he is really busy. (Devs have lives outside of XDA)
Wow your nitpicking? Hell must be freezing over right now! OK its not being worked on right this second but when Chad gets more time he will continue to work on it. Btw who said devs don't have lives and that we think they have to do whatever we want when we want?
GrayTheWolf said:
Nobody is working on it right now. Chad wants to get to it, but he is really busy. (Devs have lives outside of XDA)
Click to expand...
Click to collapse
Sent from my Rezound using xda app-developers app
Thanks for the clarification guys, these were just questions and clarifications, not a commentary on the fantastic devs we have [/no snark] I do predominately make calls in the car via bluetooth so I'll probably be holding off until there is a fix/workaround.
I did see it mentioned directly related to CM9 for other devices, not sure if it's related... http://code.google.com/p/cyanogenmod/issues/detail?id=5349
All checks and analysis were done to fresh installs only. No additional apps were installed except for those required for the security checks. The analysis is of currently active projects ONLY.
[ROM] Stock official firmware 20140513
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
CVE-2014-1600
Masterkey 9950697
Masterkey 10148049
USSD
Optimizations;
CPU Governor- Stock
SDCard Cache- Stock
OOM- Stock
SYSCTL- Stock
Network- Stock
Build.prop- Stock
BT Tether (watch>phone>internet);
Not working
BT Companion;
Not working
Kernel
Whatever kernel is provided.
[ROM] monxDIFIED™ SMART ROM ? SECURE + BT TETHERING v01-04
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
CVE-2014-1600
Masterkey 9950697
Masterkey 10148049
USSD
Optimizations;
CPU Governor- Stock
SDCard Cache- Stock
OOM- Stock
SYSCTL- Stock
Network- Stock
Build.prop- Minimal edits (Density config, Enable USB debugging, Disable debugging notify, Disable Bytecode, Disable sending data and logging)
BT Tether (watch>phone>internet);
Not properly working. Blue icon, no connection. Browser, Play Store, Voice Search, Google Now, Maps, etc., all fail to find a connection.
BT Companion;
Not properly working
Kernel
Whatever kernel you have prior to flashing is what you get.
[ROM] 07.06 EnSec STOCK Secure
(Continuation of the, Omate officially supported and approved, EnSec Project by Adam Outler, ClearD , Dees Troy, kuronosan and others.)
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
Masterkey 9950697
Masterkey 10148049
USSD
Optimizations;
CPU Governor- Tuned for lower CPU clocks under load to save battery
SDCard Cache- Tuned for optimal R/W speeds
OOM- Stock
SYSCTL- Tuned
Network- Tuned
Build.prop- Multiple edits (Density config, Network, playback, etc....)
BT Tether (watch>phone>internet);
Not working
BT Companion;
Not working
Kernel
Device specific matched kernel.
[ROM] mystery companion ROM
(if you don't know, don't ask. If you do know, don't tell)
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
Optimizations;
CPU Governor- Tuned for lower CPU clocks under load to save battery
SDCard Cache- Tuned for optimal R/W speeds
OOM- Tuned
SYSCTL- Tuned
Network- Tuned
Build.prop- Multiple edits (Density config, Network, playback, etc....)
BT Tether (watch>phone>internet);
Not properly working
BT Companion;
Mostly functional. Working notifications, working contacts sync, working remote app management, working speaker phone. Remote camera control not working,
Kernel
Whatever kernel you have prior to flashing is what you get.
How did you perform these security checks? I would like to check my own device.
Belarc
Bluebox
Dou Security XRay
Eeye
Secunia
SRT App Integrity
(all in attached zip)
USSD can be checked by going to ESET. You can also create your own page to check USSD and have it issue more aggressive codes, that what I've done. CVE-2014-1600 has to be checked by hand.
I'm still running EnSec + Operative Casual Edition 20140318 20140120 firmware ONLY!
It suits my purposes. The watch does what it's supposed to do. Tethering would do me no good unless I could tether to Maemo 5 or Meego Harmattan, which seems singularly unlikely.
Should I be worried and reflashing to something else, or is there no real point in a change from what I'm running right now?
EnSec STOCK Secure is a continuation and is based on newer firmware. There may be some sensor fixes and a couple of other things but other than that is very close to the original EnSec. Even though neither are perfect, both are still the best choice for security at this time. I personally would suggest flashing kuronosan's EnSec simply because it is a current and active release.
I have not tested the current version of monx ROM as every dev that was here prior to monx has quit releasing on xda for this device. I have quit dev support for the device on xda as well. You can pretty much thank monx for that.
So ClearD is gone, kuronosan is only providing support, and Dees wasn't surprised at what happened. Adam Outler is off on other projects. Any other dev I've talked to also found monx's kanging, games and insults a bit offensive. Enjoy your monx flavored icing as, from what we can tell, there is almost no real ROM work and mostly themeing. But what do we know, we are nothing but wannabe devs according to monx anyway.
You guys are so pathetic, NO ONE CARES ABOUT YOUR ISSUES
Focus on your own roms and ignore the rhetoric, because no one actually cares.
xcooling said:
You guys are so pathetic, NO ONE CARES ABOUT YOUR ISSUES
Focus on your own roms and ignore the rhetoric, because no one actually cares.
Click to expand...
Click to collapse
If you want to support somebody that stole Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and my work then calls the very same people whose work he stole fakes and wannabe's go ahead. Enjoy your easily hacked, unoptimized theme being passed off as a ROM.
And it wouldn't have been a problem if he had simply done the proper thing and asked and credited and not called everybody else a fake and wannabe. Not a problem though as of 8/7/2014 I have rescinded any and all permissions for xda and it's members to use my works, reference my works and mirror my works.
awesome, what a helpful person.
Thanks for standing by the community.
xcooling said:
awesome, what a helpful person.
Thanks for standing by the community.
Click to expand...
Click to collapse
Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and myself all work(ed) together on the TrueSmart/x201. Almost all work released on xda and any other forums, English or otherwise, is either based on our work, or authorized mirrors of our work. Some of our work is even in official firmware as we have worked with Omate since October of last year on issues.
I maintained an updated archive of almost every firmware and ROM released for not only the TrueSmart but the entire x201 platform and did security checks on all of it as well as look for any changes that may benefit all x201 users. I was also responsible for the core ROM work as well as being part of the early TWRP development and assisting the other devs with their work. Adam Outler, Dees Troy and kuronosan have all referenced my work at one point or another for their own works. In fact my work was called "amazing" by Adam Outer and "required" buy multiple other devs.
monx STOLE the work of at least five other devs and never even so much as apologized, then have repeated called other devs wannabe's.
And as far as the security and optimizations analysis, those results are after a peer review in which all the results matched. monx has called it b$ and and yet again called multiple devs wannabes.
I have better things to do than be part of a community that allows an ass like monx to kang, distribute an admitted trojan infected ROM and call multiple devs that came before him wannabe's and be a general ass with little repercussions.
In short. This section would not even be here if it was not for myself and a couple others. Also, the vast majority of the work, support and info would not even exist. This is not the first device I've done this for either. I did my part, and more.
xcooling said:
awesome, what a helpful person.
Thanks for standing by the community.
Click to expand...
Click to collapse
When several MTK developers (who have coded custom ROMs, kernels, and firmwares for MTK devices) tell you that your ROM has issues and you call them wannabes or haters, you really don't deserve any sort of adulation.
Besides, I'm still here providing support. Much of what I've discovered while working with other developers has become commonplace on future firmwares. I don't appreciate being called a "wannabe" or "hater" when calling people out on stupid mistakes.
XDA is not a place for Solid Snakes. It's a place for developers to work together. Not helping others is the peak of asshole-i-tude and accepting contributions to your work while not contributing to that of others is the antithesis of XDA.
Loosers attitude: give up and run away, complain because you were not given enough credit or fame
Winners attitude: would be to make your rom better, keep helping the community as you have done.
xcooling said:
Loosers attitude: give up and run away, complain because you were not given enough credit or fame
Winners attitude: would be to make your rom better, keep helping the community as you have done.
Click to expand...
Click to collapse
Cool story bro
So you support lying, theft of intellectual property and copyrights and acting like an 3 year old by calling people names? If that's the case then let me steal his work, improve it and call it my own vs trying fixing real problems like the ability to erase the IMEI with nothing more than a webpage or destroy the partition map with an email. Themes are the least of this devices problems.
Awesome. This device already had a bad rep with the devs for various reasons, then this monx guy swoops in to crush any remaining hope we had. Oh well, I'm thankful for what you guys have done, I actually enjoy my TS because of you guys, and that's all I could have asked for.
speedyink said:
Awesome. This device already had a bad rep with the devs for various reasons, then this monx guy swoops in to crush any remaining hope we had. Oh well, I'm thankful for what you guys have done, I actually enjoy my TS because of you guys, and that's all I could have asked for.
Click to expand...
Click to collapse
I'm still working on quite a few projects. Stay tuned. They likely won't end up here, but you never know.
Glad to hear kuronosan! I understand if you don't want to release it here, maybe you could PM me where you plan to release it or something? I've been interested in what you've been doing, and you have said some things in the past that sound promising (like news of KK and the like).
Thanks for sticking with it, and again to all the devs for all the previous work that helped us get as far as we are.
Lokifish Marz said:
Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and myself all work(ed) together on the TrueSmart/x201. Almost all work released on xda and any other forums, English or otherwise, is either based on our work, or authorized mirrors of our work. Some of our work is even in official firmware as we have worked with Omate since October of last year on issues.
I maintained an updated archive of almost every firmware and ROM released for not only the TrueSmart but the entire x201 platform and did security checks on all of it as well as look for any changes that may benefit all x201 users. I was also responsible for the core ROM work as well as being part of the early TWRP development and assisting the other devs with their work. Adam Outler, Dees Troy and kuronosan have all referenced my work at one point or another for their own works. In fact my work was called "amazing" by Adam Outer and "required" buy multiple other devs.
monx STOLE the work of at least five other devs and never even so much as apologized, then have repeated called other devs wannabe's.
And as far as the security and optimizations analysis, those results are after a peer review in which all the results matched. monx has called it b$ and and yet again called multiple devs wannabes.
I have better things to do than be part of a community that allows an ass like monx to kang, distribute an admitted trojan infected ROM and call multiple devs that came before him wannabe's and be a general ass with little repercussions.
In short. This section would not even be here if it was not for myself and a couple others. Also, the vast majority of the work, support and info would not even exist. This is not the first device I've done this for either. I did my part, and more.
Click to expand...
Click to collapse
Could just not ignore him,,, I only flashed the rom to see what the BT tethering was like out of curiosity (its very slow and useable)... will be ditching the ROM when I can get round to it... been annoying me all week I can't wear my watch has it just drains flat with this ROM....
speedyink said:
Glad to hear kuronosan! I understand if you don't want to release it here, maybe you could PM me where you plan to release it or something? I've been interested in what you've been doing, and you have said some things in the past that sound promising (like news of KK and the like).
Thanks for sticking with it, and again to all the devs for all the previous work that helped us get as far as we are.
Click to expand...
Click to collapse
I've personally approached monx about sharing work and ideas but he clearly has no intention of doing so; he has not responded but he continues to post in his topics.
That's fine. I'm only interested in continuing to better this watch and I have my own things to work on. As far as battery tweaks, I've managed to stabilize that (one of my users mentioned battery life 4-5 days with regular use) and I've managed to make quite a few gains.
Some of the things I would like to share involve making BT more stable and accessible across all ROMs, but again... he has no interest in sharing.
So while some of you hang from his beard as though Loki is the bad guy here, remember the ROM you love so much came from Loki's work and from the relationship I continue to foster with the CEO of this company.
But hey, no worries. Keep on praising a glorified themer who won't share his work with anyone else.
I'll be back here when I get my hands on the KK build.
Well, I'm gonna stick to my MotoACTV for a little longer. Planned on buying a TS secondhand, but hardware issues, software issues, and the current bout of drama, are very well keeping me from upgrading.
I understand your (TS devs) positions and motives. I know that there's a reason why you left the development on this device, and I'm glad you've simply quit development, rather than fighting and starting a riot.
However, with nearly all of the developers having abandoned the device, I don't see a good future coming from this.
I was hopeful through the kickstarter phase, and it's a pretty cool piece of tech, but, chances are, Omate will support it better than the community, until someone stands up, starts their own thing, and isn't afraid of getting their work ripped off.
Anyway, thanks for the development it did get, and all the cool things you guys do. If it weren't for you, this device would probably be dead in the water unless the OEM goes above and beyond to support it for a while.