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.
Over the past ~2 weeks, many people have been seeing this bug. We often write it off as being the bug that requires you to flash a Sense ROM, get a lock, then flash back to AOSP, but this is something different. Rather than discussing this separated in half a dozen different threads, I'd like for us to tackle this bug here in a thread focused to it.
I've seen what I believe to be this bug manifest with two different symptoms:
Full GPS works fine while network location works in some apps but gives you an obviously bogus location in other apps.
Full GPS works fine while network location works in some apps and simply fails in other apps.
NOTE: If Full GPS fails for you (such as in Google Maps), then go tackle that problem first before discussing here. If full GPS fails, then you probably have the bug that requires you to flash a Sense ROM. Please do NOT confuse that bug with this one!
I have seen this bug reported for all functional AOSP-based ROMs that I've followed, specifically CM7, OMFGB, OMGB, and Liquid Thunderbread. The funny thing is that some people get this bug while others do not, and there is not a clear pattern.
As I said before, this is clearly happening on pretty much every AOSP-based ROM. What is not clear, however, are what causes this. So it sure would be nice to figure this out. I'm not sure exactly what we need to do to find this but since you all are smart cookies, we'll still figure this out...
Click to expand...
Click to collapse
We aosp users have been plagued with the location bug for a VERY long time when it comes to rom dev time. Has anyone even bothered to look into it, or has everyone just excepted that it dosent work?
every thread or mention ive seen on multiple forums all ended in DEAD TOPICS.
rootz wiki has a DEAD 9 page thread on the matter, not one further post.
XDA has... 0 threads?( correct me if im wrong) on this, but ALOT of mentions
can I ask a dev to look into this? Excuse me for making broad assumptions, but it appears to me that all devs are doing right now is working on the bells and whistles for their roms and modding kernels and such while this bug got swept under the rug. I can understand that devs are BUSY and I thank them for that, I just request that we iron out this little bug, so that these AOSP gems are FLAWLESS.
After following the various video/text guides to install cm7 alpha 2.1 on the TouchPad, I am getting a weird error and non-responsive device.
I have installed cm7 on other TouchPads and had no problem. On this one it re-boots to a screen which says, "Please release keys...". There is no combination of keys which fixes this. Only thing which has worked is to Doctor it.
The only thing different on this TP is that it is the ATT 4G version, which uses a different ROM/Doctor.
I've been searching various forums for 3 days and haven't seen anyone else with this problem.
amenditman said:
...The only thing different on this TP is that it is the ATT 4G version, which uses a different ROM/Doctor.
I've been searching various forums for 3 days and haven't seen anyone else with this problem.
Click to expand...
Click to collapse
Really?? I'm shocked! The search function must be broken, I've read at least 20 or 30 threads on this problem...
Considering they're as common as dirt, the Cyanogen touchpad team certainly must had access to that particular model and I have no doubt ensuring the compatibility & functionality of the alpha on that particular model of hardware was their absolute top priority!
I honestly can't imagine what must have precipitated this unforeseen calamity! Fear not! I'm sure the greatest minds on this forum are feverishly working, day & night, without food or bathroom breaks, to determine the root of this dysfunction using the spare ATT 4G Touchpads they had sitting around, relegated to propping doors open, leveling wobbly tables, etc...
over in the rootz forum for CM, apparently, this is a known issue for the 4G models, copmatibility is not yet available, but it is reported on the bug list so im sure it will be fixed, but as usual, no eta's!
Solidus_n313 said:
over in the rootz forum for CM, apparently, this is a known issue for the 4G models, copmatibility is not yet available, but it is reported on the bug list so im sure it will be fixed, but as usual, no eta's!
Click to expand...
Click to collapse
Thanks, I didn't see that in my internet searches.
Could you point me to the bug in the list? I can't seem to find it or at least I don't want to open a duplicate one.
its issue #398
http://code.google.com/p/cmtouchpad/issues/list?num=100&start=100
link might get removed, but its the open issues list, 2nd page (was apparently reported today, was it you? ;P)
also, i know dalingrin adresses the issue in the thread, but may be something on the back burner for future release and not requested on bug list per se
This thread is here to warn others of the broken rom Copperhead OS. I have flashed roms on plenty of other devices since android first came out. I would consider myself a moderately experienced user. I currently work in the cyber security community so naturally when I heard about Copperhead OS I thought finally a security focused OS for people like myself. Sadly that is not the case. This rom does without a doubt offer many improved security features. What the developer fails to mention in the mountain of documentation is that his rom offers NO MOBILE DATA SUPPORT. NONE it does offer great wifi security including mac randomization and a firewall. What the documentation doesn't tell you is that the main source of its security is its lack of DATA support. I have spent days trying to fix my mobile data on this rom. I have flashed all the needed apn zips for T-mobile, at&t, Verizon, and Sprint. Ejected my sim, rooted the rom (which kills the security) and tried to edit apn files. I can assure you there is no fix for this. The developer seems keen on only getting the name of their cyber security firm out there rather than actually making any meaningful strides in securing android in a meaningful way. If your reading this post and thinking of flashing it YOU HAVE BEEN WARNED. If you dont believe me try it for yourself I will personally send .01 BTC to the first person who can post a working fix for this. Word to the wise though be ready to surf from wifi hotspot to wifi hotspot if you flash this broken software. If you know of a fix for this then prove me wrong.
Working just fine on T-Mobile.
This is a user error not the ROM error.
Sent from my Huawei Google Nexus 6P
Do you have another active SIM that is causing this one to have ID but no action?
If not, wipe data. I feel like there is a configuration that got changed that isn't agreeing with data.
Make sure you are on the proper radio, and vendor image for what they recommend. NOT what is the latest. They provide all of what you need.
https://copperhead.co/android/docs/install follow those instructions to perfection.
The Flashall will do a majority of the work for you.
Keep in mind Copperhead is developed in Canada, so, any radio settings outside that country are yours to resolve. That being said, data wouldn't work with my default t-mobile settings, but this was resolved by changing my APN info from fast.t-mobile.com to epc.t-mobile.com and setting all protocols to IPv4. All MMSC and MCC settings remained the same. Not sure who your carrier is, but the issue is not with the operating system.
Love me some copperhead, always worked flawlessly.