Question about Cyanogenmod - Sprint Galaxy S 5 Q&A, Help & Troubleshooting

Hi, I am just asking a question, not trying to start anything at all. I just want to know why Cyanogenmod isn't officially supporting the S5? It's just weird, I have never had a phone that Cyanogenmod didn't officially support. Is there something wrong with it? Thanks

The our camera doesn't like to connect to the stock android. They are working hard to fix this.

Shad Stang said:
The our camera doesn't like to connect to the stock android. They are working hard to fix this.
Click to expand...
Click to collapse
Alright, thank you. So Cyanogenmod is just holding off releasing it till they figure out a fix for it?

Looks like there are still GPS, camera and microphone issues for klte. Since hlte took almost 6 months for a device tree I'd expect at least that long for S5. Samsung doesn't like power users or devs.

Related

Touch screen issues on GB roms

Hello!
So I've been flashing various ROMs on my Inspire for a few months, however I always have to revert to a Sense ROM to get correct touch screen input on my phone.
What will happen is, when I use CM7 or any other CM7 based rom, my touch screen will act very odd.
For example, when I go to use the keyboard, and I try to touch and hold on the period to get to another punctuation mark, when I drag my finger to the mark, I have to go a good half an inch above the actual button for it to register that I am over that specific button. Regular button presses work relatively fine, however I don't have this issue at all when I use Sense ROMs.
It happens in any game or app that requires me to do anything regarding dragging my finger on the screen.
I have no idea why this is happening, most recently on Gingerbeast 2.1.2, with the newest ATT aosp radio.
Any tips or help?
bump 10char
kingmike26 said:
Hello!
So I've been flashing various ROMs on my Inspire for a few months, however I always have to revert to a Sense ROM to get correct touch screen input on my phone.
What will happen is, when I use CM7 or any other CM7 based rom, my touch screen will act very odd.
For example, when I go to use the keyboard, and I try to touch and hold on the period to get to another punctuation mark, when I drag my finger to the mark, I have to go a good half an inch above the actual button for it to register that I am over that specific button. Regular button presses work relatively fine, however I don't have this issue at all when I use Sense ROMs.
It happens in any game or app that requires me to do anything regarding dragging my finger on the screen.
I have no idea why this is happening, most recently on Gingerbeast 2.1.2, with the newest ATT aosp radio.
Any tips or help?
Click to expand...
Click to collapse
Sounds like an issues with the open source drivers that cm based roms use. If this happens on all cm based roms. There is nothing you can really do about it till the CM team fixes the drivers. Same thing with WIFI and BT
This happens to me as well!
I can confirm this happens on Sense ROMs too. I thought initially it was a keyboard issue, but it happens whether I'm in SwiftKey or HTC's stock keyboard. It's sometimes so bad I can't type a specific letter at all and have to wait a minute for whatever is wrong to go away.
Does anyone think this could be a hardware issue?
lufis said:
I can confirm this happens on Sense ROMs too. I thought initially it was a keyboard issue, but it happens whether I'm in SwiftKey or HTC's stock keyboard. It's sometimes so bad I can't type a specific letter at all and have to wait a minute for whatever is wrong to go away.
Does anyone think this could be a hardware issue?
Click to expand...
Click to collapse
Its not a hardware issue, its a known issue with HTC touchscreen driver
Ah ok. Has there been any effort by HTC to fix it?
lufis said:
Ah ok. Has there been any effort by HTC to fix it?
Click to expand...
Click to collapse
epic quote! haha, sorry couldnt resist. Likely we are on our own with these phones, they are about to come up on being a year old so not so much development is gonna be done on the corporate side of things.
Darunion said:
epic quote! haha, sorry couldnt resist. Likely we are on our own with these phones, they are about to come up on being a year old so not so much development is gonna be done on the corporate side of things.
Click to expand...
Click to collapse
frustrating but true
MMM-BACONSTRIPS said:
frustrating but true
Click to expand...
Click to collapse
would be nice if manufacturers would at least support a phone for 2yrs from launch, to accommodate standard contract. I know its not their problem, and even when they dont support their phones, we still buy them :/
Darunion said:
would be nice if manufacturers would at least support a phone for 2yrs from launch, to accommodate standard contract. I know its not their problem, and even when they dont support their phones, we still buy them :/
Click to expand...
Click to collapse
I was just about to edit my post saying the same thing..how dare the consumer expect a phone manufacturer to continue support for a standard contract length..but then again, the contract is up to AT&T and not so much the manufacturer...hhaha but then again neither AT%T is really doing much for the Inspire as well..we're all sheep though, thank God for XDA and the devs!
Can anyone verify this is happening on stock ROMs?
MMM-BACONSTRIPS said:
I was just about to edit my post saying the same thing..how dare the consumer expect a phone manufacturer to continue support for a standard contract length..but then again, the contract is up to AT&T and not so much the manufacturer...hhaha but then again neither AT%T is really doing much for the Inspire as well..we're all sheep though, thank God for XDA and the devs!
Click to expand...
Click to collapse
Yeah, I too have been *****ing about this for a while. Manufacturer roughly follows warranty period for support, and AT&T follows... oh wait, AT&T doesn't really give a crap about phone support!
The Desire HD will most likely be supported for 2 years. October will be 2 years matter of fact. It came to ATT late in the game. That is not HTC's fault. Also HTC has released a 2.3.5 Sense 3.0 ROM for the Desire HD. And even the Telus Desire HD (exactly like the inspire) just received the update. So the ROM is available. Again it is ATT holding it back and not HTC.
I've been having the same issue on my ICS rom. Happens just randomly and I haven't been able to figure out what it is that's causing it. Fresh load, no other apps aside from barcode scanner, facebook and twitter.
bbypat said:
I've been having the same issue on my ICS rom. Happens just randomly and I haven't been able to figure out what it is that's causing it. Fresh load, no other apps aside from barcode scanner, facebook and twitter.
Click to expand...
Click to collapse
The idea that it's the fault of the open source touchscreen drivers doesn't seem to jibe, since it's happening on both Sense and non-Sense ROMs (I'm presuming no touchscreen driver modifications have been made in the Sense ROMs; correct me if I'm wrong.) I reached out to HTC for comment on its Facebook page last week but no one has responded. :sigh:
Can anyone speak to the likelihood of it being some other custom ROM component or an issue with a custom kernel? Has anyone on a stock, unrooted device experienced this problem?

[WARNING!] CM7 Nightly bug, be careful, not booting

Last night I switched my SD card (16GB Class10 Kingston) in my O3D and checked the "Use external/internal sd" in CM settings and rebooted my phone.
The /root/sdcard path was located to the INTERNAL sdcard before the switch.
I think that the option was NOT checked BUT when it check it, it became "Use internal" which is incorrect.
Anyway, my phone wont boot, not even when holding down VolUp+Power.
I will keep trying but just a warning to you all, don't do any hardware change with the Nightly builds (assuming that the sdcard is hardware)!
I'm using linux so I'm not sure that it's possible to use any software like the softwares on windows.
have a look at this thread http://forum.xda-developers.com/showthread.php?t=1433274 , they have the same problem as you. Apparently its because you switched the internal/external.
Flash the rom again ??? Power + vol-down 3d button .. for cwm ??
Sent from my LG-P920 using XDA App
It's very important you report this bug to arcee on http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/
He doesn't follow threads on XDA.
gamesz2 said:
Flash the rom again ??? Power + vol-down 3d button .. for cwm ??
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
Are you seriously answering my thread without reading my entire post?
--------------------------
No worries, I can flash back the stock with lg support tool using windows, but my current rom and settings will be lost.
Just a heads up if any of you would try the same thing.
And mine doesn't go in to recovery mode either. I doesn't boot whatever I try.
Only thing that can be done is what I said above, Holding down VolUp+Power while plugging in the usb in the computer so the computer can find my phone as a Omap4430 device.
KurdX said:
Are you seriously answering my thread without reading my entire post?
--------------------------
No worries, I can flash back the stock with lg support tool using windows, but my current rom and settings will be lost.
Just a heads up if any of you would try the same thing.
And mine doesn't go in to recovery mode either. I doesn't boot whatever I try.
Only thing that can be done is what I said above, Holding down VolUp+Power while plugging in the usb in the computer so the computer can find my phone as a Omap4430 device.
Click to expand...
Click to collapse
Ow iam sorry man i read it wrong iam from holland :0
Sorry
Sent from my LG-P920 using XDA App
Hi guys,
Same problem to me... A dead phone w/e I do. Won't get my PC recognise it as OMAP4430 device (not running XP, but 7)...
Any ideas? Cannot easily get my hands on an XP PC...
lrpvo said:
Hi guys,
Same problem to me... A dead phone w/e I do. Won't get my PC recognise it as OMAP4430 device (not running XP, but 7)...
Any ideas? Cannot easily get my hands on an XP PC...
Click to expand...
Click to collapse
You don't need XP, will work on 7 aswell.
Haven't had time to fix my phone yet but I will fix it through 7 so I can post the result here when fixed.
same problem here, too.
any solutions yet?
omgomg said:
It's very important you report this bug to arcee on http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/
He doesn't follow threads on XDA.
Click to expand...
Click to collapse
I already did that many days ago, but it seems this rootzwiki forum is totally dead. No arcee, no other dev replies. I also reported other bugs, no answer too.
In fact, I´m afraid CM7 development for our device has stopped completely, since all changelog entries we get are for general CM7. Nothing is getting done for the O3D specifically.
I know CM is done by busy developers, who get no money for their work, but they could at least share their knowledge a little more, so more people could jump in to help! I´m trying to do that, but I need some pointers from more experienced people.
What pisses me off is to have an important project like this in the hands of 1 or 2 guys, with bugs that bricks expensive phones, and we have no one to talk to.
Marcovecchio said:
I already did that many days ago, but it seems this rootzwiki forum is totally dead. No arcee, no other dev replies. I also reported other bugs, no answer too.
In fact, I´m afraid CM7 development for our device has stopped completely, since all changelog entries we get are for general CM7. Nothing is getting done for the O3D specifically.
I know CM is done by busy developers, who get no money for their work, but they could at least share their knowledge a little more, so more people could jump in to help! I´m trying to do that, but I need some pointers from more experienced people.
What pisses me off is to have an important project like this in the hands of 1 or 2 guys, with bugs that bricks expensive phones, and we have no one to talk to.
Click to expand...
Click to collapse
My point exactly all these people are getting big headed if they opened it up people can fix stuff and get it done much quicker but i guess they get money for it.. I'm going to have to let go of this phone shame was a good phone though..
I had almost same thing I formatted my ad card on cm7 38 build for p925g. Total brick it's in a disconnect reconnect loop and no comm conection so very. Close to a full brick taking it in tomarow.
Posted from my crap ass slow as f*** 3GS iphone
Phone in unusable state.
Same issue here coming from CM7 build 16. All I see is the disappearing/reappearing OMAP4430 device in device manager.
THIS PROBLEM SHOULD BE STICKIED]
Any idea what to do guys??
Yes it should i was lucky my phone was under the 30 days still so they just handed me a new phone on the spot wich was nice but im going to stay away from cm7 like the plague yes this should be sticked her andin the thrill forum as well.
I had to take mine in there was no way to get the computer to see the phone to flash it.
Guys, don't complain about this here, as arcee already said he doesn't follow XDA threads.
Do report it at http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/ where he reads it.
omgomg said:
Guys, don't complain about this here, as arcee already said he doesn't follow XDA threads.
Do report it at http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/ where he reads it.
Click to expand...
Click to collapse
Indeed, he says he reads it, but that forum is completely DEAD, no posts for 2 weeks. I already reported this bug, had not a single answer. And the nightlies have no P920 specific work for weeks. And since arcee seems to be the only mega-master-guru around, a person no one can talk to, this is what we have: a dangerous half-working CM7 that will destroy many more O3D around, and there´s nothing we can do.
omgomg said:
Guys, don't complain about this here, as arcee already said he doesn't follow XDA threads.
Do report it at http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/ where he reads it.
Click to expand...
Click to collapse
Im. Just posting hear so every one else. Dosent make the same misstake as me and end up with a paper weight on tbere desk.

We may need a campaign of annoyance...

Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
I agree with you. At this point I'd be happy with some sort of update from Samsung/T-Mobile. Even if they just said "we're still working on it" and gave no ETA at least we'd know they hadn't forgotten about it.
If the Blaze Q whatever the hell they've decided to call it launches here in a few weeks with ICS and we still don't get the software I will be ticked.
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Sent from my Samsung Galaxy S Blaze.
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Sent from my SGH-T769 using xda app-developers app
dr4stic said:
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
Click to expand...
Click to collapse
I completely agree with you. To be honest, I am already pissed off that they still havent released it. When I got this phone, T-Mobile promised I was going to get an ICS update in July. Yeah, so much for that. At the very least they could acknowledge our presence and let us know that they havent forgotten about us
Chitown021 said:
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Click to expand...
Click to collapse
The problem is the kernel and libraries specific to our hardware. We have to have a working kernel and libraries before the rest of the rom can come.
I'm not sure why people thought the Blaze Q would've been a good thing for us because unless the hardware was identically similar (which no one had any proof that it was), the releases for that phone would've been useless for ours. The fact that it's now coming with a 720p display (I would've stayed with my Blaze 4G if it had that), and a keyboard tells me that there will be PLENTY different between the phones.
Hardware-wise, the T769 (Blaze) is EXTREMELY similar to the T989 (T-Mo SGS2). How similar you ask? In the original kernel configuration file for the T769, the options are set to build it as a T769 AND T989. There are a few ifdefs that exist purely to stop little snippets of the T989 code from taking effect.
I worked on my own time to try and hack together a kernel from the released sources for the T989 for ICS. Porting specific code from the T769 sources to try to come up with something that worked. Here's the problem: it was stressful and thankless, and at the end of it all I had a kernel that would compile and not boot. No one collected anything to help me attempt this and I was getting tired of having a non-functioning phone that pissed me off. So I ordered me a Galaxy Nexus. I received 2 in a row with screen issues and ended up returning them. I figured I would return to my efforts with the blaze, but at that point I was used to the big phone with a beautiful 720p resolution... so I shelled out the money for a GS3.
I have thought of returning and making a second attempt to port the kernel, and have actually started setting up to do just that. I think I made some mistakes my first time around, so the second time might actually work. But it is A PAIN.
chjema said:
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Click to expand...
Click to collapse
You're right, it isn't... but it's the last time I saw this community bug an outside source for something, aside from buying a couple of guys a phone
Yeah, a 720p screen would have been nice... thanks for the detailed explanation.
I still find it comical that my old HD2 is on the verge of having a fully functional JB rom but my brand new Blaze is still stuck on GB.
Honestly if I could've afforded it I would have probably gone the Nexus or S3 route but given my limited funds and needing to cover two phones (wife needed an upgrade) I thought this was the best value ($30 upgrade cost at Target).
Sent from my Samsung Galaxy S Blaze.
Yes lets please do this.
T-Mobile hasn't updated their page for a month now, and that was for the Gingerbread update they released when they could have been making headway on ICS. I can't find out how to submit any new pages, but I can see two requests for an update that were a couple months old (click on the link, then read on the right side in section "Incoming Links") source = http://support.t-mobile.com/docs/DOC-4182
I went to Samsung's page about ICS updates, and rated it "very dissatisfied," informing them they should have supplied target Year and Quarter (i.e. 2012 Q3) at the minimum, but preferably a specific month. source = http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00046726&fm_seq=49755
Let's continue to put pressure on these assholes, or they will sweep us under the bus while they pursue development of the Samsung Galaxy Supernova 4G Touchwiz Xtra 4.1.
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Dr4stic
If you need want help, testing, anything.let me know of beer more than happy to help.. we need to get ics to this phone
Sent from my SGH-T769 using xda app-developers app
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Click to expand...
Click to collapse
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
I'll be the first to admit I've become a bit jaded because of my experiences with T-Mobile / Samsung and the Samsung Vibrant.
I heard promises about updates to that phone - they even set dates and pushed them back and back and back and finally... nothing.
If anything I think the release of the Blaze Q is a strike against us because our phones are now the "out dated" version of the Blaze and why put development hours into an "old" device.
I'm happy that I have a fully functional phone as it is now (the Vibrant never really had a fully working GPS). An update would be nice but I wouldn't lose any sleep over it because honestly, you may just be setting yourself up for a lot of sleepless nights.
Oh, and on the Vibrant Forum they started a twitter campaign #NeverAgain demanding the promised upgrade or they would never use T-mobile or Samsung again. No one listened.
I know this all sounds cynical but I've seen this show before.
Edit to add: If memory serves correctly this was also the case with the Behold on T-mobile.
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
L7ChrisL7 said:
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
Click to expand...
Click to collapse
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem.
Click to expand...
Click to collapse
What happens when more "cool new apps" are released to the market that require Android 4.0 API's or better? Chrome immediately comes to mind, and there are others with many more on the way. What happens 4 months from now when you are only 6 months into your 2 year contract and you're wondering why you can't realistically run things on your phone that has 1 gig of ram and a dual-core 1.5ghz cpu?
And honestly, btw... I had a myTouch 4G running CM7 that felt miles faster than my blaze. The samsung crapware is not only bloated, but breaks the system in a number of places. You can see this in the fact that you can't have a scrollable wallpaper, or that the system doesn't understand all the loop points in ringtones that work properly in other phones. I can't tell you how frustrated I get by an unlock and/or answer mechanism that can't track my fingers in real time like something as simple as CM7 does.
And don't get me started on the underutilisation of the video hardware.
AwesomeTurtle said:
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
Click to expand...
Click to collapse
No, this phone was released with a promise. When it was released, ICS had been out for 6 months or more, and I'm sure the OEMs had access to the system and API's well before the official release. By the time ICS is released for our phones (IF it is released for our phones), JB will have been out for several months.
This is a matter of support and broken promises. I am NOT just whining. I was sold a phone with a promise of ICS and it has NOT been delivered, and at this point the time has gone beyond reasonable.
If we don't make noise now, it WILL be forgotten and you're going to end up with a phone outdated well before it's time.
dr4stic said:
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
Click to expand...
Click to collapse
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
L7ChrisL7 said:
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
Click to expand...
Click to collapse
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
dr4stic said:
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
Click to expand...
Click to collapse
Well cant you decompile a kernel? or maybe if i get the source of both devices i can use the code to compile a new kernel... hmmm all stuff to try. but compiling a kernel takes a while i think ill update my PC first haha. Im not necessarily worried about the other drivers not working, i just want to make progress, or at least help us make a push in the right direction. Im sorry if im being too optimistic or noobish, i just want to learn what people have and havent tried, so i dont waste my time on what has already been done.
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
here's a thread we can vent at!
spartanerik said:
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
Click to expand...
Click to collapse
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
anactoraaron said:
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
Click to expand...
Click to collapse
http://support.t-mobile.com/people/tmo_erica
Try sending an email to [email protected] and ask (nicely) about a status update on the ICS update for our phone! I just sent one, and hopefully if we send enough we can get some traction

Why aren't there any roms for this device?

Hey guys,
I tried searching for an answer but I can't seen to find one. Why is there close to zero development for this device? I read something about a new kernel coming soon but noone really went into detail..
I came from the HTC One M8 so my expectations were pretty high :crying:
Can someone clear this up for me?
Phone is newly released and not rootable with locked bootloader. Not even sure kernel sources have been released yet.
phil9309 said:
Hey guys,
I tried searching for an answer but I can't seen to find one. Why is there close to zero development for this device? I read something about a new kernel coming soon but noone really went into detail..
I came from the HTC One M8 so my expectations were pretty high :crying:
Can someone clear this up for me?
Click to expand...
Click to collapse
It's been out a couple of days; it's been rooted already but not in a way which lets you save the DRM stuff so you currently lose functionality forever if you do so. I'm sure it'll come with time.

I have a question about Validus-draconis -7.1.1.Release.v13-OFFICIAL-20170128- 0315

I have a question about the charging animation with Validus-draconis -7.1.1.Release.v13-OFFICIAL-20170128- 0315 the charging animation that I mean is the one when the phone is off but plugged in on my zte zmax the backlight won't turn off how do I fix this? I like this ROM a lot I really do and I must say to ground zero u guys did a great job but I really need some help on this one if someone out there can help.
juggalo19076 said:
I have a question about the charging animation with Validus-draconis -7.1.1.Release.v13-OFFICIAL-20170128- 0315 the charging animation that I mean is the one when the phone is off but plugged in on my zte zmax the backlight won't turn off how do I fix this? I like this ROM a lot I really do and I must say to ground zero u guys did a great job but I really need some help on this one if someone out there can help.
Click to expand...
Click to collapse
Official support for that device was dropped a long time ago, no one currently on the team owns one.
Crap and got ya I'm guessing that also means u don't have a direction to suggest for me to look toward to fix that on a phone in general. It honestly sucks that it was discontinued cuz I do honestly like this phone and can't get new one till tax time and wish I could work out the few issues with this ROM on this phone so after I get new phone I can use this one as gameboy etc.... If u know what I mean but anyway ty for the reply and if u think of anything plz feel free to pass idea
juggalo19076 said:
Crap and got ya I'm guessing that also means u don't have a direction to suggest for me to look toward to fix that on a phone in general. It honestly sucks that it was discontinued cuz I do honestly like this phone and can't get new one till tax time and wish I could work out the few issues with this ROM on this phone so after I get new phone I can use this one as gameboy etc.... If u know what I mean but anyway ty for the reply and if u think of anything plz feel free to pass idea
Click to expand...
Click to collapse
Not sure what to tell you, 7.1.1 was a long time ago and I don't remember running into that issue on my devices. I know what it's like having to wait to upgrade, wish I could be more help
I know it's been a while but I have odd request
As I was told a while back no one here has a z970 anymore if I bought a few extras and mailed them to you guys would anyone be willing to help me finish validus for the zmax? I'm paying.... Let me know I Wana finish it but can't alone
So wait I know its been a while since anyone besides me even looked at this but I got last few questions suck as ota update option was there any updates ever? If so how do I download them it just says error downloading when I try. Also is there anyone who would be interested in helping me make this ROM current again and many add to it I'm thinking about buying a few z970s and mailing them out to ppl who would like to if there is anyone else out there except me ice be willing to pay idk why I'm obsessed on this topic but I am lol let me know please and ty
juggalo19076 said:
So wait I know its been a while since anyone besides me even looked at this but I got last few questions suck as ota update option was there any updates ever? If so how do I download them it just says error downloading when I try. Also is there anyone who would be interested in helping me make this ROM current again and many add to it I'm thinking about buying a few z970s and mailing them out to ppl who would like to if there is anyone else out there except me ice be willing to pay idk why I'm obsessed on this topic but I am lol let me know please and ty
Click to expand...
Click to collapse
The zmax has been out for over 6 years now and development for it has been dead since about 2016. As far as the stock firmware goes it was never updated past android 4.4. Everything 5.0 and up came in the form of custom roms. As for buying multiple Z970 phones and sending them to people to try to revive development for it, good luck. It was a budget phone from the moment it came out and by today's standards its specs are abysmal. I seriously doubt any developer worth their salt would be interested. The best advice I can give you is to just get a better, newer phone, and if you want custom roms look for one that's already supported. If you need to go back to stock there should be some stock rom zips you can flash through TWRP. I know at one point I had them on android file host, though I haven't checked in years.
Masterchief87 said:
The zmax has been out for over 6 years now and development for it has been dead since about 2016. As far as the stock firmware goes it was never updated past android 4.4. Everything 5.0 and up came in the form of custom roms. As for buying multiple Z970 phones and sending them to people to try to revive development for it, good luck. It was a budget phone from the moment it came out and by today's standards its specs are abysmal. I seriously doubt any developer worth their salt would be interested. The best advice I can give you is to just get a better, newer phone, and if you want custom roms look for one that's already supported. If you need to go back to stock there should be some stock rom zips you can flash through TWRP. I know at one point I had them on android file host, though I haven't checked in years.
Click to expand...
Click to collapse
Got ya any idea on the backlight issue for charge animations or how to change them on this phone I've tried everything I can think of with no luck

Categories

Resources