Is there any major milestone that must be overcome in order for the cyanogenmod team to officially support the HOXL? Are we just waiting for ROM cooks to take initiative? I know S-off is nice to have, but I don't believe it's a requirement.
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
jordanetodd said:
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Seems like ther'es been a fair amount of work as far as ROMS and mods and things go, but the Kernel source is the reason that there are working JB roms for the GS3 and we don't even have CM9 fully working yet....
I believe the developer interest come from a few factors.
1) There are few developers that get paid nothing and porting CM9/10 is a lot of work.
2) There are hundreds of devices how do you pick which one gets the CM9/10 .... sales.
The HTC One XL is a nice device but as a LTE device and from HTC it is likely not the strongest selling phone in North America
shorty6049 said:
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Click to expand...
Click to collapse
There's definitely more people on the One X international version. People will find that most phones with kernel source available and unlocked bootloader will draw more developers... But in this case quantity =/= quality. I've had several android phones over the years and yes, while it's nice to have a giant land of developers with pages and pages of roms to look through, they lose their luster to mediocrity. You'll find some of the best devs who weren't discouraged by the locked down devices such as this one, and as a result, the product (ROM, kernel, etc) will always be top-notch. And a smaller, more intimate dev community encourages more interaction and community support, making the overall experience that much better.
I think we already have pretty solid support, given that there's still no kernel source available.
We have great Sense-based ROMs (the CleanROM family, amongst others) as well as pretty-solid alphas of CM9 and AOKP. Personally I've been very tempted to try either CM9 or AOKP, but I haven't made the plunge yet. A friend of mine is using CM9 has his daily driver without issue.
I believe the team working on CM9 has plans to incorporate their currently-unofficial branch into being officially a part of CM9 (or CM10) once kernel source is released and the remaining issues are resolved.
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
pearlbrian said:
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
Click to expand...
Click to collapse
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
stnguyen09 said:
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
Click to expand...
Click to collapse
Sorry, i didn't mean functional. I meant, like you said, 100%.
pearlbrian said:
Sorry, i didn't mean functional. I meant, like you said, 100%.
Click to expand...
Click to collapse
yeah, my issue is that the few things that ARENT working are the things I want the most. Frustrating that this is as good as it can get unless HTC releases that source (which it's sort of staring to look like they may get away with not doing at all)
I think source will come. It's just sad that i have JB running on my old as bones Captivate while my shiny new one x is stuck with Sense :crying:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
kleeman7 said:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
SkizzMcNizz said:
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
Click to expand...
Click to collapse
Not quite sure what you mean,
The tablet would get Internet from my phone, then I'd use the tablet to stream music to my stereo via bluetooth
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
stnguyen09 said:
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
Click to expand...
Click to collapse
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
shorty6049 said:
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
Click to expand...
Click to collapse
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
I got it to work using CleanRom (not a photo, it told me it didn't support receiving large files) . I might flash something new tonight... I really just want something that does wifi tether (which I'll have to read into more... I feel like it's tougher to get that feature working on this phone than it was on my Evo) and NFC (so I can automatically turn on tethering when I get in the car) . I'm alright using a sense-based ROM if I have to since anything is pretty fast on this phone and cleanrom is relatively AOSPish
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
Sending Photos only works on JB. With ICS you can you can send contact info and Youtube links. Works between CM9 on One X and my N7 running JB.
Related
So, this thread is not about when the Thunderbolt will get Cyanogenmod support, because I can search and find that.
This thread is about how "official" CM support works. When I go to the Cyanogenmod site, I see a list of officially supported devices, which if I guess, are made, maintained and released by their team? I've been following along Android forums for almost a year now and see a lot of phone users trying to give their respective phones a CM port or CM rom to use. I presume these are "unofficial" and are being put together "aftermarket" by outside developers.
How and will the Thunderbolt get adopted by the Cyanogemod team and be one of those official phones listed on their site?
I'd take the root plunge for a rom like CM, which seems to be heavily updated and maintened and has the updater which would make updates for me very easy.
The thunderbolt will eventually.. I believe the reason it's not "supported' right now is because it's still in alpha. They don't state official support until they have a solid build.
My location is in montevideo urugauy according to CM7 lol.. On the map it shows me my location but somehow it thinks im in uruguay.. Any fix for this?
marc314 said:
My location is in montevideo urugauy according to CM7 lol.. On the map it shows me my location but somehow it thinks im in uruguay.. Any fix for this?
Click to expand...
Click to collapse
Clearly you must move to Uruguay.
Sent from my ThunderBolt using Tapatalk
At this point CM7 support is mostly anecdotal experiences by users to assist other users.
necosino said:
Clearly you must move to Uruguay.
Sent from my ThunderBolt using Tapatalk
Click to expand...
Click to collapse
Mine had me in Paris somewhere. Get GPS Status from the market. From the app hit menu, tools, manage a-gps state. Hit reset. Then go through those again but hit download data this time. After that and a refresh, it should all be well.
Sent from my ADR6400L using XDA Premium App
obeygiant said:
Mine had me in Paris somewhere. Get GPS Status from the market. From the app hit menu, tools, manage a-gps state. Hit reset. Then go through those again but hit download data this time. After that and a refresh, it should all be well.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thanks man.. Let me try this out..
macewank said:
The thunderbolt will eventually.. I believe the reason it's not "supported' right now is because it's still in alpha. They don't state official support until they have a solid build.
Click to expand...
Click to collapse
Where is it even listed in alpha?
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#HTC_Thunderbolt
All I see are messages in the Wiki that the Thunderbolt is not yet supported. I am not talking about the port(s) that are here in XDA... I'm referring to a release by the CM team.
I am not rooted, and haven't played around with Rom Manager, but is an alpha "official" version of CM listed in there for the Thunderbolt?
Bwangster12 said:
Where is it even listed in alpha?
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#HTC_Thunderbolt
All I see are messages in the Wiki that the Thunderbolt is not yet supported. I am not talking about the port(s) that are here in XDA... I'm referring to a release by the CM team.
I am not rooted, and haven't played around with Rom Manager, but is an alpha "official" version of CM listed in there for the Thunderbolt?
Click to expand...
Click to collapse
slayher is part of the CM team and the thunderbolt CM7 he's building is the "official" version. it's not listed under the officially supported devices because the code isn't anywhere near stable enough to be considered a daily driver. it's buggy, things don't work like they should. it's not release quality software yet.
all CM builds are technically ports. the base CM code doesn't just magically work on all phones by itself. there are specific people assigned as vendor maintainers that are generally responsible for making sure that CM works on their individually assigned device. see http://wiki.cyanogenmod.com/index.php?title=Community_Members for a list.
edit: i'm sure I did a poor job of explaining it and there's way more to it than what I described, but that's the gist. hope it makes sense
The CM7 alpha for the Thunderbolt is awesome. I have yet to find anything that it does not do well... except wireless tether..
4g, wifi for some people, battery life, soft buttons lighting up, call volume, getting settings to stick.
Just some of the bugs still plagueing CM7 for the thunderbolt.
Sent from my ThunderBolt using XDA App
It seems to be coming along nicely from my end user perspective. I'm running the pre-alpha pre-release on my TB from http://forum.xda-developers.com/showthread.php?t=1049542
I've been using it as a daily driver because of its Netflix support. One of the users in that thread posted a kernel and wifi fix which seem to greatly improve wifi and data connectivity, at least for me. I can deal with some minor bugs and annoyances. I'm just happy to have Netflix.
So once it becomes more stable, is considered a daily driver and presumably added to their support page....it will show up in rim manager and have the cyanogenmod updater support?
Right now for updates, you havta just keeping flashing the time from ur flash card right?
Bwangster12 said:
So once it becomes more stable, is considered a daily driver and presumably added to their support page....it will show up in rim manager and have the cyanogenmod updater support?
Right now for updates, you havta just keeping flashing the time from ur flash card right?
Click to expand...
Click to collapse
yep! i don't suspect it will be too much longer before we've got official support. exciting times
It's the only LTE phone. That's why it will take a while to get all bugs cleaned to be in the supported list.
Sent from my thunderbolt
Thats fine... didn't mean this to sound like a pushy thread. I thought the description given in this thread was fantastic, thanks. I was unclear as to what exactly happens when CM releases a rom.
I haven't rooted yet, but am sort of waiting for CM. From what I've read, it seems to be one of the most stable and maintained roms available and one of my main concerns is "quality" and maintaince/updates. Some of the roms available now sound good, but I don't wanna deal with having to be flashing left and right when new updates get released by Verizon.
My assumption with CM is that I can put install it with Rom manager and worry about updates using their Updater, right? Any GPS issues, battery concerns, whatever would be dealt with by CM?
If anyone has questions or concerns regarding the CyanogenMod 10 please ask here and stay away from the development section for these posts, as it has over 3000 posts.
To start off please read the CM10 faq on the first Page of the CM10 thread before asking any questions here or in the official thread. Thanks
Sent from my HTC One X(L/AT&T)
So, does (or will) the camera app in CM10 have the same burst mode that the Sense camera has? Can you take AS MANY photos AS QUICKLY? Will those photos be similar quality? Will we be able to pull stills from previously recorded video? Or take Hi Res stills while shooting HD video?
I read the last 15 pages of the development thread and didn't see any of this being discussed.
Thanks a bunch!
Billy
Sent from my Nexus 7 using Tapatalk 2
Burst mode is a sense cam feature only, because there is no sense in cm those features will not be there. Your best bet is if you want sense cam but asop feel go with clean rom or tn rom, they can desense the launcher but keep the apps but you will be on ics. But i will say the cm cam is alot faster then it used to be and is still a good camera.
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
PaKMaN787 said:
To start off if you want the video camera and/or audio fixes, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
yungskeeme said:
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Click to expand...
Click to collapse
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
PaKMaN787 said:
To start off if you want the video camera and/or. music workarounds, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
PaKMaN787 said:
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
Definetly hit or miss. Heard it was fixed in the 8/28 but no music so I guess I'll stay on 8/22 and deal with it. Heard someone say they flashed AOKP ICS rom and reflashed CM10 and it was fixed.
bstephens2u said:
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I'll do a little poking around and see if I can get this working (I probably won't) and I'll let you know if I do!
tropazr said:
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
Click to expand...
Click to collapse
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Is wake locks an issue with cm10 so far or just a few users isolated type instance? I was getting massive wake lock for alarmmanager that I do not get on CleanRom.
anyone else getting bad battery life with this ROM? currently running the 8/29 nightly.
Right now im at 33% battery with 11h on the battery but only 1h45min screen time. I also have GPS on and brightness around 1/2..which could possibly be the problem.
JeepFreak said:
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
toptalent said:
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Click to expand...
Click to collapse
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
h8rift said:
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
Click to expand...
Click to collapse
Wooooooooooot!! And would it just be TeamDouche in general that deserves the donation? Or was somebody specific working on this?
Thanks H8!
Billy
Sent from my Nexus 7 using Tapatalk 2
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
Click to expand...
Click to collapse
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
toptalent said:
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
Click to expand...
Click to collapse
I'm not entirely sure if something is being worked on but I think you should flash CR4.0 as it is definitely working and is 4.0.3 base which is what h8rift said to flash.
Sent from my HTC One X(L/AT&T)
May I ask what is the right procedure to flash CM10? In the zip there is a boot.img. Do we need to manually extract and flash it with fastboot?
I ask this because some people (including me) can't make LTE to work in CM9/10. Some say by flashing CleanROM 4.0, full reset then flash CM10, LTE will be the default. This trick does not work for me. What is the mechanism of this trick? What stays after full reset? All I can think is the boot image. But even manually flashing CleanROM's boot.img then flash CM10 does not work for me. Changing build.prop (ro.ril.def.preferred.network and ro.telephony.default_network as suggested at code.google.com/p/cyanogenmod/issues/detail?id=1623 , sorry can't link external) of course does not work either.
I know #*#*info*#*# can change the preferred network type, but it does not stick after reboot, which renders this approach useless.
Thanks.
When should we expect the release of KitKat for the Relay?
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Nardholio said:
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Click to expand...
Click to collapse
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Guiyoforward said:
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Click to expand...
Click to collapse
That's a question we won't really be able to answer until there is more solid information on KitKat generally available.
Looks like CM is setting up the KitKat AOSP code for there builds Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/396000889011326976
Sent from my SGH-T699 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
Cyanogenmod Google+ post " Android 4.4 Source
Source is now being pushed to the AOSP trees. Of course, when it is all there we will begin the process of figuring out what changed, needs work, and/or is no longer feasible or needed.*
We are not in a rush to get 4.4 builds out. We are going to continue the process of working on CM 10.2 M1 - getting that out the door and onto your devices. Further, we will 'finish' the 10.2 code base, similar to what we did with 10.1.*
As a friendly reminder, please don't flood us with requests for 4.4 - we all want new and shiny things, but we will not do so at the expense of abandoning the hard work our contributors have put into 10.2.*
Final note, a lot of folks are reading into the "512mb" item on the release notes. No, this does not mean a sudden resurrection of older hardware, there are dependencies beyond the RAM (and CM has enforced that minimum since ICS)."
Sent from my SGH-T699 using Tapatalk
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Nardholio said:
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
andrewsfm said:
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
Click to expand...
Click to collapse
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Jax184 said:
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Click to expand...
Click to collapse
4.2 and 4.3 were minor updates with no name change. JB was a major update and they did update to it.
4.4 KitKat being a major update, I've got my fingers crossed considering the wide range of devices that it's being planned for.
Was just hoping to see if there was any news on a KK update for this model.
CM is fun to play with and all, but it's not something I would trust on an everyday phone.
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
onebornoflight said:
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
Click to expand...
Click to collapse
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
andrewsfm said:
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
Click to expand...
Click to collapse
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Jax184 said:
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Click to expand...
Click to collapse
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
Guiyoforward said:
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
Click to expand...
Click to collapse
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
andrewsfm said:
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
Click to expand...
Click to collapse
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
chris122380 said:
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
andrewsfm said:
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
Click to expand...
Click to collapse
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Looks like coding for CM 11 has started. Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/397817644650205185
Sent from my SGH-T699 using Tapatalk
Magamo said:
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Click to expand...
Click to collapse
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
andrewsfm said:
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
Click to expand...
Click to collapse
True, there have been some bugs. However, I use the official nightly of cm10.2 as a daily driver. I'd rather put up with the MINOR issues that are left (hardware is stable for the most part) than have a manufacturer ROM. IMHO, the stock ROM that comes with the phone is usually full of crap bloat ware that I don't use and takes up space, and a UI that is SEVERELY limited in customization.
Also, the more people participate and report problems, the faster it takes TeamApex to fix and push out. At least team apex RESPONDS to their users. As mentioned before, it can take as long as 6-8 months after an android release for the manufacturer to roll out an update...still full of crap ware that's NOT used and cannot be uninstalled without root privileges or botching up the UI further.
These people who work tirelessly to provide to us, the end user, an updated version of Android, do so out of their own free will, and don't get a penny. These devs are here to proudly share what they have created, and I applaud and give my utmost respect to them.
You don't wanna install aftermarket firmware? Don't want to aid in bug reporting? Fine, put up with the crap that the manufacturer pushes onto you. Plus, Samsung & T-Mobile don't get any more of your hard earn dollars rolling out an Android update for our year-old device. They'd rather you dump it and buy the latest phone. THAT'S THEIR BUSINESS MODEL! So they have no interest in rushing an update to something as "old" as the Relay.
If you want JB or KK and are unwilling to wait for & install after-market firmware, I suggest you pony up the dough and buy a nexus 5. Better still, learn how to dev and make your own version of JB or KK for the Relay. That's the beauty of open source.
Your rant and *****ing about when "they are going to develop Kit Kat" makes you come across as arrogant, snobbish, and child-like.
Sorry for MY ranting, but it's unappreciative asshats like andre that just piss me off.
Sent from my SGH-T699 using XDA Premium 4 mobile app
Sounds like they did a good job with optimizing broadcast batches so as to cut down on battery life and also cut down on memory requirements for the system and phones like ours with low RAM.
It sounds like a great fit for this phone. Does anyone know if CM or other solo developers plan to bring KitKat to the MPQ?
Thanks
Yes, in due time.
Patience. Don't ask for ETA's.
Looks like Motorola has updated their software upgrade page for the Moto X to say that it is receiving Kit-Kat, but Photon Q's page has an ambiguous "Future plan coming soon". I doubt we'll get an official update, but personally I care more about the Play Services updates. Most of the Kit-Kat features (besides some IR stuff) seem like they are already in CM.
Solust said:
Looks like Motorola has updated their software upgrade page for the Moto X to say that it is receiving Kit-Kat, but Photon Q's page has an ambiguous "Future plan coming soon". I doubt we'll get an official update, but personally I care more about the Play Services updates. Most of the Kit-Kat features (besides some IR stuff) seem like they are already in CM.
Click to expand...
Click to collapse
i dont think that Motorola will make another update for our photon q and even if so, why should they update it to android 4.4 instead of 4.2 or 4.3 ?
pujdo1 said:
i dont think that Motorola will make another update for our photon q and even if so, why should they update it to android 4.4 instead of 4.2 or 4.3 ?
Click to expand...
Click to collapse
Google has been releasing updates fairly fast, so some device manufactureres deciced to skip some of them and move to the latest version available to keep up with development.
Though I am not avare of any Motorola produced device that was receveing long term updates, they abandon it soon (more-less) after release.
Even nexus devices fall under 18-month update policy: http://www.phonearena.com/news/Goog...Galaxy-Nexus-will-not-get-Android-4.4_id48950
However, there are other factors regarding samsung galaxy nexus: "While Google clearly states the 18-month rule for dropping Galaxy Nexus support, it is also likely that the company was forced to take this step because Texas Instrument, which manufactured the processor for the device, has shut down its mobile phone business."
Agreed. Better battery life and less RAM usage on 4.4 would make it a welcome improvement for the Photon Q LTE. I would also like to see Miracast (Widi) working properly. At 1.9 Ghz on the Wheatley gov with it's dual Core, thanks to Dev's like Argggh, if we had 4.4....it would be another year before I even thought about getting a new phone. May be an GS5 by that time, or the Nexus 6.
If not by moto is it possible to compile it from source? Like cm, or would it be dependent on moto proprietary 4.3 stuff?
Sent from my XT897 using XDA Premium 4 mobile app
T-Mobile Moto X has got KitKat leaked update yesterday. It's too fast and will be the first non nexus to receive KitKat.
Sent from my XT897 using XDA Premium 4 mobile app
CM-11.0 is in development, but I'd not expect that to be stably useable in a month.
It can boot and the graphics seems to be fine, but no audio, camera and wifi yet, at this moment...
kabaldan said:
It can boot and the graphics seems to be fine, but no audio, camera and wifi yet, at this moment...
Click to expand...
Click to collapse
Hah, I saw the branches... good work!
I was going to try compiling it but ran into build errors, haven't put much effort into it lately. Good to know it can be built and boots! :good:
pujdo1 said:
i dont think that Motorola will make another update for our photon q and even if so, why should they update it to android 4.4 instead of 4.2 or 4.3 ?
Click to expand...
Click to collapse
Because there is probably no upgrade path in the coming year for the Photon Q. Slates don't count. So it should get the latest and greatest until a successor is planned.
Do somebody hear something about CM11 on our phone ? recently do a terrible silence in this matter
niko99 said:
Do somebody hear something about CM11 on our phone ? recently do a terrible silence in this matter
Click to expand...
Click to collapse
...you must be patient
aosp from arrrghhh works good...but without sd card and keyboard backlight
CornholioGSM said:
...you must be patient
aosp from arrrghhh works good...but without sd card and keyboard backlight
Click to expand...
Click to collapse
The SD card is kind of a critical one... And I'm not sure what is missing :/
As for keyboard backlight, I've ported this to other ROM's like AOKP - and it is NOT going to be a straightforward task on AOSP - probably not worth the effort.
Hoping to get the SD card fixed, that is annoying!!
arrrghhh said:
The SD card is kind of a critical one... And I'm not sure what is missing :/
As for keyboard backlight, I've ported this to other ROM's like AOKP - and it is NOT going to be a straightforward task on AOSP - probably not worth the effort.
Hoping to get the SD card fixed, that is annoying!!
Click to expand...
Click to collapse
Yeah, it was fun booting your build up just to see^^
Only problem I had was finding a working GApps....could load your build fine but if i tried to load any of PA's GApps or some others(like the one you have listed in your thread) I would just get constant bootloop. Anyway, looking forward to CM 11! Thanks for the update Skrillax :good:
slimbrady said:
Yeah, it was fun booting your build up just to see^^
Only problem I had was finding a working GApps....could load your build fine but if i tried to load any of PA's GApps or some others(like the one you have listed in your thread) I would just get constant bootloop. Anyway, looking forward to CM 11! Thanks for the update Skrillax :good:
Click to expand...
Click to collapse
there is already working CM11
http://forum.xda-developers.com/showpost.php?p=47954424&postcount=348
- GSM SIGNAL / CALLS / CALL BACK working
- KEYBOARD BACK LIGHT working
- SD CARD Working
- CAMERA with recording wideo working
- GSM DATA working
- GAAPS / STORE etc working
- WIFI working
- SMS / MMS ( for GSM users look bottom)
- ROOT etc working
- HDMI out working
- MEDIA DOCK working
What dont work
- camera button (but work if you start manual camera apk )
For GSM user there is needed to change in bulid.prop like below
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
telephony.rilV7NeedCDMALTEPhone=false
regards
niko99 said:
there is already working CM11
http://forum.xda-developers.com/showpost.php?p=47954424&postcount=348
- GSM SIGNAL / CALLS / CALL BACK working
- KEYBOARD BACK LIGHT working
- SD CARD Working
- CAMERA with recording wideo working
- GSM DATA working
- GAAPS / STORE etc working
- WIFI working
- SMS / MMS ( for GSM users look bottom)
- ROOT etc working
- HDMI out working
- MEDIA DOCK working
What dont work
- camera button (but work if you start manual camera apk )
For GSM user there is needed to change in bulid.prop like below
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
telephony.rilV7NeedCDMALTEPhone=false
regards
Click to expand...
Click to collapse
Hrmm nice, i'll give it a whirl. This site turned me into a real rom junkie lol
Is SMS working now?
ZenInsight said:
Is SMS working now?
Click to expand...
Click to collapse
Yes, but if you are gsm user you need to edit build.prop like i wroted
This is a thread where you can post your thunderbolt problems
.android_secure
OK, I've got one that's been bugging me. I have a LOT of apps installed and if I have moved a number of the larger ones to the SD Card (to free up /data), once I get to greater than 1GB in android_secure, my phone fails to boot completely and just locks up. It's not the SD Card (32GB Class 10) that has errors (scanned with both Windows and 4Ext), just seems to be too much for the OS to handle.
I'm still running ShiftHackedA05P 2.8 (CM 2.7.3) from days gone by. Suggestions welcome. Thanks.
Edit: And I use Autostarts (Advanced mode) to turn off receivers for apps that I don't want to load, and LBE to disable permissions.
You might try using a Rom that has ext4 support since it supports larger file sizes.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
You might try using a Rom that has ext4 support since it supports larger file sizes.
Click to expand...
Click to collapse
Thank you for the reply, expert one
The folder has ~87 files of sizes 3MB to 40MB, which causes the lockup after booting at random times (sometimes it makes it further and ultimately boots, after MANY battery pulls). Once the folder is pared down to a lesser total size, the phone boots more rapidly and doesn't lock up; seems to be a linear relationship between how many files and the total time to boot until the CPU usage drops.
It might also be that most apps are moving away from app to sd since it isn't used as much anymore.
Sent from my HTC6500LVW using Tapatalk
I rule
Æaa\../
New issue, perhaps?, I am noticing that when LTE/CDMA mode my connection is showing as LTE only where it used to use ehrpd for transport and thereby still keeping 3g radio enabled. Normally no big deal but at times I am unable to send/receive texts or make/receive phone calls. Has Verizon stopped using this middle transport for LTE? I am unsure why I am always showing LTE only and if this is causing a problem. Switching to CDMA (auto prl) is the only remedy that I have found. Any thoughts?
Sent from my ADR6400L using xda app-developers app
Not really a problem but I noticed a thread that mentioned A LOT of older devices getting a port of KitKat...any chance that could happen with this old relic? Other HTC phone with some sort of working KitKat are: Sensation, Desire HD, Vivid, Raider, Evo, Amaze and Incredible S...or at least that is what this site claims.
Oh, sorry, I'm new here so I can't post the link.
Santod was working on a KK ROM but since he has newer devices as many of us old bolt users do he puts it on the back burner because the demand for it just isn't there anymore. Be patient and maybe eventually you will see one. Or you won't....
Sent from my One using Tapatalk
I appreciate the feedback. Fingers crossed.
Sent from my Galaxy Nexus using xda app-developers app
heeey whats going on??
why this new rom thread closed???
[ROM][Aosp][2.3.7]Smasher X [5.3][Multiview][Pie][02/15/2014]
http://forum.xda-developers.com/showthread.php?p=50387543
the rom working, only home n searach button not responding.
but overall rom ran normally n smooth
plz someone help me!
I'm stuck now after unconsciously deleted system apps from my newly rooted HP slate plus! The screen turned black and it become dark! When I turned the tablet on it didn't start working and the screen remained black! I'm sure I ruined the stock rom' HP support is bad, I went to their website but didn't find the stock ROM to download... I'm really don't know what to do ,, plz help ,, and sorry for bad English , its a third language in my country
ellmou said:
I'm stuck now after unconsciously deleted system apps from my newly rooted HP slate plus! The screen turned black and it become dark! When I turned the tablet on it didn't start working and the screen remained black! I'm sure I ruined the stock rom' HP support is bad, I went to their website but didn't find the stock ROM to download... I'm really don't know what to do ,, plz help ,, and sorry for bad English , its a third language in my country
Click to expand...
Click to collapse
You should probably find an HP slate forum to post that issue in.
Sent from my One using Tapatalk
disconnecktie.
I just saw where Droid Incredible 2 has a fully functioning CM 10.1 rom. Just wondering if that could be possible for us since DINC 2 has same processor, same resolution, same manufacturer, same everything except 4G. I'd love to have CM10.1 if it meant sacrificing 4G (or even all data).
I'm new to all this, but if you think a port is possible or maybe some other way to get this on our device I will give it 100% effort.
If it can't be done then crush my dreams now and I will somehow learn to live without my TB.
Thanks.
Porting the dinc2 ROM breaks data for the bolt since the bolt has an svdo radio setup. I have ported from it before and I either had calling with no data or just data. I'm not saying it couldn't be done but it is out of my area of expertise. Go to infectedrom. com and there is a cm10.2 build made by Santod that has working WiFi. Since data doesn't seem to be an issue for you.
Sent from my One using Tapatalk
Thanks.
I'm awefully attached to my TB and I still think it is a great device.
I really enjoy all of santod's roms, but the PacMan one just doesn't perform well on my phone.
Thank again.
jwillmeng said:
Thanks.
I'm awefully attached to my TB and I still think it is a great device.
I really enjoy all of santod's roms, but the PacMan one just doesn't perform well on my phone.
Thank again.
Click to expand...
Click to collapse
Yeah none of the newer stuff will perform well honestly. It is just to much for the old bolt to handle.
Sent from my One using Tapatalk
[all in one] thunderbolt tool
New to xda so can't post in the original thread, but I need info on the thunderbolt tool. I have used it before with great results, now trying to root my other TB and old vesion won't update and new download won't unzip (reads no files when extracting).
if anyone has any ideas i could use the help. I want to upgrade my other TB to the ICS rom that santod posted but i am dependent on its wifi tether and want to have a backup device if any problems a cure (doubtful, as the instructions seem strait forward).
Thanks
E.R.Rider .
guinzo said:
heeey whats going on??
why this new rom thread closed???
[ROM][Aosp][2.3.7]Smasher X [5.3][Multiview][Pie][02/15/2014]
http://forum.xda-developers.com/showthread.php?p=50387543
the rom working, only home n searach button not responding.
but overall rom ran normally n smooth
Click to expand...
Click to collapse
It could be closed for any number of reasons. Cjen isn't a developer by any stretch of imagination. He's the same guy that kanged CM, and liquidsmooth code in the past in roms he called "liquidsmooth remastered", etc. He basically kangs roms, adds and removes apps, then rereleases them himself as though he built them, all without providing the source that would show no commits made by him. The irony is, liquidsmooth 3.2, CM7.2, And thundershed actually worked perfectly for the most part, his so called rom doesn't... If you're interested in gingerbread AOSP roms for the bolt, i'd stick with thundershed and liquidsmooth. At least workshed's and team liquid are real developers and their roms worked...
quickdraw86 said:
It could be closed for any number of reasons. Cjen isn't a developer by any stretch of imagination. He's the same guy that kanged CM, and liquidsmooth code in the past in roms he called "liquidsmooth remastered", etc. He basically kangs roms, adds and removes apps, then rereleases them himself as though he built them, all without providing the source that would show no commits made by him. The irony is, liquidsmooth 3.2, CM7.2, And thundershed actually worked perfectly for the most part, his so called rom doesn't... If you're interested in gingerbread AOSP roms for the bolt, i'd stick with thundershed and liquidsmooth. At least workshed's and team liquid are real developers and their roms worked...
Click to expand...
Click to collapse
Looks like he was either banned or quit trying to kang everyone under the sun. Every thread he opened is locked now and his account is currently disabled.
Sent from my HTC6500LVW using Tapatalk