The Sad truth, a little update on the status of things.
I know everyone is wondering what the status of ICS, or even aosp for the warp is, if it will happen, when and so on.
Sadly, i just dont think its going happen. we have tried our best. we just dont have what we need AKA Zte Ril Source and some other things.
The reason we dont have ics or jellybean already is Zte's fault. This phone uses Cheap DDR memory. We have had a 3x Kernel working for a while. the problem. our 2.6 kernels do not see most of the ram with ics or jb, Nor does the 3x kernel, this is because ics/jb devices are DDR2/3 memory.
it just doesnt read the memory right. and we just dont have the coding knowledge to overhaul the code like that. we havent given up. still trying to find help. i just figure it has been in the dark long enough and you should know why.
the best we can do for now is to make a crazy hybrid rom. Some closed source and aosp apps.
Device(s): ROOTED! Force with Boost Mobile....yes I said Rooted
Carrier: Boost at $40/month
Thanks: 28
Thanked 28 Times in 13 Posts
Quote:
Originally Posted by Dm47021
I know everyone is wondering what the status of ICS, or even aosp for the warp is, if it will happen, when and so on.
Sadly, i just dont think its going happen. we have tried our best. we just dont have what we need AKA Zte Ril Source and some other things.
The reason we dont have ics or jellybean already is Zte's fault. This phone uses Cheap DDR memory. We have had a 3x Kernel working for a while. the problem. our 2.6 kernels do not see most of the ram with ics or jb, Nor does the 3x kernel, this is because ics/jb devices are DDR2/3 memory.
it just doesnt read the memory right. and we just dont have the coding knowledge to overhaul the code like that. we havent given up. still trying to find help. i just figure it has been in the dark long enough and you should know why.
the best we can do for now is to make a crazy hybrid rom. Some closed source and aosp apps.
Of course I'm not calling anyone wrong here, but it just doesn't make sense to me. In the PC world (I know this isn't quite a PC we're dealing with here, lol) I know it doesn't matter what kind of memory you have in the box - you write all the code the same. The differences in hardware are handled by the memory controller. Now, I believe Snapdragon has a memory controller included on-chip, and therefore shouldn't care what kind of memory it's attached to. A further illustration of this point can be found in the case of the Warp versus the Sequent. Both run the MSM8655, and both therefore have the same memory controller. Yet the one runs ICS, the other GB.
The Linux kernel should see all memory just the same, shouldn't it? I can see where not having all the source is a huge issue, but I just don't get how the memory type could be affecting the code.
Like I said, I'm not starting an argument here, I'm just trying to understand things better, and maybe help out if I can.
Of course I'm not calling anyone wrong here, but it just doesn't make sense to me. In the PC world (I know this isn't quite a PC we're dealing with here, lol) I know it doesn't matter what kind of memory you have in the box - you write all the code the same. The differences in hardware are handled by the memory controller. Now, I believe Snapdragon has a memory controller included on-chip, and therefore shouldn't care what kind of memory it's attached to. A further illustration of this point can be found in the case of the Warp versus the Sequent. Both run the MSM8655, and both therefore have the same memory controller. Yet the one runs ICS, the other GB.
The Linux kernel should see all memory just the same, shouldn't it? I can see where not having all the source is a huge issue, but I just don't get how the memory type could be affecting the code.
Like I said, I'm not starting an argument here, I'm just trying to understand things better, and maybe help out if I can.
A hybrid rom can spark the motavation for others on the warp. I say release one and let the snow ball roll.. ill do what i can to help as well
Quote:
Originally Posted by Dm47021
I know everyone is wondering what the status of ICS, or even aosp for the warp is, if it will happen, when and so on.
Sadly, i just dont think its going happen. we have tried our best. we just dont have what we need AKA Zte Ril Source and some other things.
The reason we dont have ics or jellybean already is Zte's fault. This phone uses Cheap DDR memory. We have had a 3x Kernel working for a while. the problem. our 2.6 kernels do not see most of the ram with ics or jb, Nor does the 3x kernel, this is because ics/jb devices are DDR2/3 memory.
it just doesnt read the memory right. and we just dont have the coding knowledge to overhaul the code like that. we havent given up. still trying to find help. i just figure it has been in the dark long enough and you should know why.
the best we can do for now is to make a crazy hybrid rom. Some closed source and aosp apps.
I know everyone is wondering what the status of ICS, or even aosp for the warp is, if it will happen, when and so on.
Sadly, i just dont think its going happen. we have tried our best. we just dont have what we need AKA Zte Ril Source and some other things.
The reason we dont have ics or jellybean already is Zte's fault. This phone uses Cheap DDR memory. We have had a 3x Kernel working for a while. the problem. our 2.6 kernels do not see most of the ram with ics or jb, Nor does the 3x kernel, this is because ics/jb devices are DDR2/3 memory.
it just doesnt read the memory right. and we just dont have the coding knowledge to overhaul the code like that. we havent given up. still trying to find help. i just figure it has been in the dark long enough and you should know why.
the best we can do for now is to make a crazy hybrid rom. Some closed source and aosp apps.
iam sorry guys. but this is what it is
This is the reason I got the sequent, I felt this thread coming ( or something similar ) and I didn't want to be around with a dead device wondering what's next. And DM, your right I don't know exactly what a hybrid rom is but I am down for whatever if it keeps a community from dying!
Of course I'm not calling anyone wrong here, but it just doesn't make sense to me. In the PC world (I know this isn't quite a PC we're dealing with here, lol) I know it doesn't matter what kind of memory you have in the box - you write all the code the same. The differences in hardware are handled by the memory controller. Now, I believe Snapdragon has a memory controller included on-chip, and therefore shouldn't care what kind of memory it's attached to. A further illustration of this point can be found in the case of the Warp versus the Sequent. Both run the MSM8655, and both therefore have the same memory controller. Yet the one runs ICS, the other GB.
The Linux kernel should see all memory just the same, shouldn't it? I can see where not having all the source is a huge issue, but I just don't get how the memory type could be affecting the code.
Like I said, I'm not starting an argument here, I'm just trying to understand things better, and maybe help out if I can.
I have to agree. It defies all logic. Example. 2.6.35.7 kernel works fine in gingerbread.. we set up for ics and the memory is missing. We port the sequent kernel... same result.. so thought it was the rom... port the sequent rom.... same result... I have built gingerbread aosp ... memory is fine.. we tried caf ics ... same result.. something is funny
Re: The Sad truth, a little update on the status of things.
Coming from the PC world...memory makes a huge difference. The sequent does NOT use the same ram. Likely due to the same reason. It has slightly more but the big diff. is that its faster... likely to the same issues cheap zte opted for the better ram to make ICS run.
If the sequent goes on sale again soon for the 99$ price I may jump but if not, once I get my tax return comes I'll likely upgrade to a better phone. I love my warp. Its my first android but eventually we will all be upgrading.
Coming from the PC world...memory makes a huge difference. The sequent does NOT use the same ram. Likely due to the same reason. It has slightly more but the big diff. is that its faster... likely to the same issues cheap zte opted for the better ram to make ICS run.
If the sequent goes on sale again soon for the 99$ price I may jump but if not, once I get my tax return comes I'll likely upgrade to a better phone. I love my warp. Its my first android but eventually we will all be upgrading.
So, What it boils down to then is the warp doesn't have the hardware to run ics or jb.
Yeah, ive looked at the code many times. the only thing i can figure out is it is because ddr2 is dual channel and ddr is single channel, still it shouldnt make a difference. but zte hard coded something into the board file.
I will post it on here so those of you how know C can look at it, maybe even figure it out.
do a search for #ifdef CONFIG_ZTE_PLATFORM
and you will likely see the memory hack,
Yeah, ive looked at the code many times. the only thing i can figure out is it is because ddr2 is dual channel and ddr is single channel, still it shouldnt make a difference. but zte hard coded something into the board file.
I will post it on here so those of you how know C can look at it, maybe even figure it out.
do a search for #ifdef CONFIG_ZTE_PLATFORM
and you will likely see the memory hack,
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,491 Times in 771 Posts
Re: The Sad truth, a little update on the status of things.
As dm said, its the phone. That's the conclusion that we came to. Now though we said its probably not gonna happen, both dm and I usually just don't give up. So maybe someday. Anyways, there are other things in the works.
Soon
Device(s): ZTE N860 Rooted With Voltron OC,
ZTE N762 Rooted With Voltron rev4
Carrier: Public Mobile
Thanks: 164
Thanked 209 Times in 148 Posts
I'm not ready to give up... just picked up a kyocera rise c5156 it to has the snapdragon 1ghz and ics and what seems to be 512 mb of ddr... I just just picked it up... I'm trying to root it.... or at least pull the system from it.... there is a lady singing but I cant see her and I'm not sure shes fat...
I'm not ready to give up... just picked up a kyocera rise c5156 it to has the snapdragon 1ghz and ics and what seems to be 512 mb of ddr... I just just picked it up... I'm trying to root it.... or at least pull the system from it.... there is a lady singing but I cant see her and I'm not sure shes fat...
As dm said, its the phone. That's the conclusion that we came to. Now though we said its probably not gonna happen, both dm and I usually just don't give up. So maybe someday. Anyways, there are other things in the works.
Soon
BTW, we still hate eachother.... the Feud continues lol......inside joke
The Following User Says Thank You to Dm47021 For This Useful Post:
So, What it boils down to then is the warp doesn't have the hardware to run ics or jb.
Well, it can run ics and jb very nicely. but something just isnt right.
we have determined ZTE are master Hackers. The code for the memory is very hacky, to boil it down into simple terms, ZTE hacked the kernel to run on Cheap DDR Memory, Where ICS/JB are meant for Higher End Device with DDR2/DDR3
if anyone out there has knowledge enough to help, feel free to contact Me or Downthemachine.
Re: The Sad truth, a little update on the status of things.
Quote:
Originally Posted by Skinnyjeans21
I know this will probably sound very absurd but.... why not just ask ZTE how they did it or ask for the working source??? its worth a shot :P
Just as example for you...so far I've seen zte release source on the warp and sequent.... neither was working and took Devs time to fix the crap code zte intentionally made nonfunctional
Does that answer your question?
Just as example for you...so far I've seen zte release source on the warp and sequent.... neither was working and took Devs time to fix the crap code zte intentionally made nonfunctional
Does that answer your question?
That was true for the initial release of the source and we were using modded blade/fury source...but the source currently provided by zte is compilable as is and I believe is the base for both custom kernels.
Re: The Sad truth, a little update on the status of things.
Quote:
Originally Posted by drewhill77
That was true for the initial release of the source and we were using modded blade/fury source...but the source currently provided by zte is compilable as is and I believe is the base for both custom kernels.
My point is not really that they finally provided working source but the unlikely scenario where zte gets there head out there arse and actually helps the end user
My point is not really that they finally provided working source but the unlikely scenario where zte gets there head out there arse and actually helps the end user
Well the problem isn't zte but boost and more specifically the contract preventing them from providing non-approved updates for our phone. Not to mention the funky hybridized caf source code zte used lol...I did see a rom for another phone with an msm cpu that had a hybrid caf/aosp/cm source...
Device(s): ZTE N860 Rooted With Voltron OC,
ZTE N762 Rooted With Voltron rev4
Carrier: Public Mobile
Thanks: 164
Thanked 209 Times in 148 Posts
Quote:
Originally Posted by drewhill77
Well the problem isn't zte but boost and more specifically the contract preventing them from providing non-approved updates for our phone. Not to mention the funky hybridized caf source code zte used lol...I did see a rom for another phone with an msm cpu that had a hybrid caf/aosp/cm source...
I was thinking about that and what about public mobile....the phone was just released a few months ago...
Device(s): ZTE N860 Rooted With Voltron OC,
ZTE N762 Rooted With Voltron rev4
Carrier: Public Mobile
Thanks: 164
Thanked 209 Times in 148 Posts
nope... there are actually competitors to the Canadian sister company which is Telus/Mike/koodo... Public Mobile is a very small company compared to Telus Sprint or Rogers or AT&T... Their network coverage area, is Only in Two cities... Montreal and Toronto... and NOT the way in between either... Montreal is in Quebec and Toronto is in Ontario... It's a four and a half hour drive while speeding ... That's why the Public Mobile ROM has roaming...
Ok cool...wondered about that but never enough to bother really research it lol. It may be possible for you guys to get ics or jb as an official update...
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,491 Times in 771 Posts
Re: The Sad truth, a little update on the status of things.
Quote:
Originally Posted by smartmanvartan
I'm not ready to give up... just picked up a kyocera rise c5156 it to has the snapdragon 1ghz and ics and what seems to be 512 mb of ddr... I just just picked it up... I'm trying to root it.... or at least pull the system from it.... there is a lady singing but I cant see her and I'm not sure shes fat...
Root and restore by binary will work. Seriously smartmanvartan? You didn't see me over in the kyocera rise/hydro section?
Last edited by downthemachine; January 11th, 2013 at 10:21 PM.
The only reason that I haven't gone to the sequent yet is because I don't have a year yet with this phone also because I'm waiting for more support to go to that phone.
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,491 Times in 771 Posts
Quote:
Originally Posted by drewhill77
That was true for the initial release of the source and we were using modded blade/fury source...but the source currently provided by zte is compilable as is and I believe is the base for both custom kernels.
The base for both custom kernels is Hroark13's modified source,
as it was posted back then when zte rereleased our source, it still had headset audio issues. I prefer the hroark source, as i am sure dm does also..
the Sequent source needed to be fixed. I myself, fixed that source. Mind you it was minor issues, but none the less, needed to be fixed
The base for both custom kernels is Hroark13's modified source,
as it was posted back then when zte rereleased our source, it still had headset audio issues. I prefer the hroark source, as i am sure dm does also..
the Sequent source needed to be fixed. I myself, fixed that source. Mind you it was minor issues, but none the less, needed to be fixed
My bad...guess I must have assumed that since the stock source had finally been successfully compiled that was what you guys were using as your base now
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,491 Times in 771 Posts
Quote:
Originally Posted by drewhill77
My bad...guess I must have assumed that since the stock source had finally been successfully compiled that was what you guys were using as your base now
it does work, but i like giving hroark credit for my work
also, I still have the belief that zte took his source, and released it. But who knows
Device(s): ZTE N860 Rooted With Voltron OC,
ZTE N762 Rooted With Voltron rev4
Carrier: Public Mobile
Thanks: 164
Thanked 209 Times in 148 Posts
Quote:
Originally Posted by downthemachine
Root and restore by binary will work. Seriously smartmanvartan? You didn't see me over in the kyocera rise/hydro section?
yea I saw ya there ... I just got the phone yesterday... I can't seem to get the root to work tho i think it's a driver issue... Public mobile once again managed to give us a modified version of a phone that exists... every android device they released except for the warp is only available at public mobile...
30Likes
The Sad truth, a little update on the status of things.
its worth a shot :P
