Skinnyjeans21
Android Expert
Maybe someone's telling you to stay away from the warp 
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [Boost Mobile] [ Team Osiris ][ Linaro ] CyanogenMOD 10 Beta 2.0 Camera WORKING ( Jellybean 4.1.2 ) for ZTE WARP
- Thread starter Dm47021
- Start date
-
- Tags
- zte warp (n860)
Blyss
Android Enthusiast
Frankenwarp... LOL
rickpcb
Android Enthusiast
PandaKom
Newbie
I know it's a work in progress, i was just asking because i can't find anything about it in the OP. it's not listed as not yet working or completed (unless its there and i'm blind, which is completely possible), its a completely valid question.
mercury0x000d
The ultra-modern operator
No problem, I find myself stricken with a bit of blindness now and again!
It's right there above the thanks section:
DM47021 said:
But yeah, DM and the rest of Team Osiris has been working very hard on this. In fact, right now I do believe he is the only one currently pouring time, effort and talent into the project. It is a work in progress, but he's the dedicated sort and has already said he'll keep working on it as long as there's demand for Jellybean on the Warp.
Oh, and last but not least... welcome to Android Forums, Panda!
Good to have another member of the Warp family aboard. 
Just wanted to say thanks for all of the time and effort you have expended to make this venture a reality. My wife and I just closed on our very first home so we're pretty well stuck with our Warps until they die, at which point we can justify buying a new phone. We're looking forward to the finished product as having Jellybean on our Warps would be just like having a new phone. Please keep up the great work you've done so far.
smartmanvartan
Android Expert
I got one N860 with a brand new digitizer that wont work... and three untested Warps coming today... I sould be able to sent you a digitizer at the very least... shoot me a pm with your shipping info...
Blyss
Android Enthusiast
I know it's early to be asking this since it's still not complete but would it eventually be possible to incorporate Dizzle's adreno tweaks into CM10? Just curious because as of now I'm torn between two worlds... I mean two roms, lol. CM10 is awesome but so is double the performance on my adreno 205. I haven't hit 8000 in antutu like some but I've pulled 7700.
Btw you guys remember "back in the day" when we got psyched for 5000 in antutu? You guys have nearly doubled the warpiness of the warp. So for all of you:
*cheer*
Keep up the awesome work!
Btw you guys remember "back in the day" when we got psyched for 5000 in antutu? You guys have nearly doubled the warpiness of the warp. So for all of you:
*cheer*
Keep up the awesome work!
smartmanvartan
Android Expert
Skinnyjeans21
Android Expert
I think not since this is meant to be pure cyanogenmod, but the Adreno tweaks are already in a flashable. There's even different versions of the tweak available like battery saver and performance booster
Blyss
Android Enthusiast
The tweaks are flashable? So I can flash them into ctmod? I'I've been all over this board and not seen that ! Please point me to it!
Skinnyjeans21
Android Expert
I think it's somewhere in the Alliance ROM thread, merc posted a link to the thread on xda... and hey another CTmod user! I thought not many people were still on it....
I thought not many people were still on it....
Blyss
Android Enthusiast
I think it's somewhere in the Alliance ROM thread, merc posted a link to the thread on xda... and hey another CTmod user!
I used it on the prevail and when I got my new warp and saw it had been ported it was an easy choice. Back with my first warp when they were new I used shinjitsu.
My only complaint with ctmod is how long it takes to boot. Minor thing though.
Blyss
Android Enthusiast
I think this is it:
http://forum.xda-developers.com/showthread.php?t=2167228
It says gingerbread only though.
Edit : I'm making a new thread to stop derailing this one
http://forum.xda-developers.com/showthread.php?t=2167228
It says gingerbread only though.
Edit : I'm making a new thread to stop derailing this one
rickpcb
Android Enthusiast
Bro, I've been picking things apart with wifi, bt and sensors... and not seeing errors... I'm thinking it's a dependency issue or it's out of my league LOL On a lighter note I have found a bunch of cam files - I just need to know what exactly I'm trying to find... I think I know what we don't need, but that leaves alot out there that could help. The day job gets in the way, but I'm trying when I can...
Blyss
Android Enthusiast
I've seen multiple posts of cm9 and 10 ports on phones that never officially got ics our jelly bean. They all have camera issues. DM had mentioned maybe a wrapper approach? I understand that from being a computer programmer. Did you look in to that? Basically what you are trying to do is intercept the commands written for one device and translate them otf to another. Right ?
As for the sensors, I can't believe they haven't used these sensors on any other chipsets, why is it exactly they are giving you trouble? Or do you know? Maybe they haven't used it on any chipsets that have working sensor modules with an API level of JB? That is to say, is there no phone with those sensors that has an official or unofficial ICS/JB port where they are working that we could look at?
I'm really grasping here, trying to pull anything out of my head to give you an idea.
As for the sensors, I can't believe they haven't used these sensors on any other chipsets, why is it exactly they are giving you trouble? Or do you know? Maybe they haven't used it on any chipsets that have working sensor modules with an API level of JB? That is to say, is there no phone with those sensors that has an official or unofficial ICS/JB port where they are working that we could look at?
I'm really grasping here, trying to pull anything out of my head to give you an idea.
Blyss
Android Enthusiast
Oh and on Wi-Fi... the fact that it works eventually or with DHCP off tells me it's more of an issue with how it's setup. I know some have said that they can't get it to work at all and forgive me for this, not trying to be rude, but maybe they just didn't follow DM's directions or don't know how to manually ip address their phone. I was in a 200 level network class with 15 people in college and halfway through the term the instructor brought in thousands of dollars of equipment and said build me a network. Off topic: the topology was cool, Ethernet to fiber and we had to also connect legacy coaxial devices. Anyway, we got it all setup hardware wise and then people were stumped. All of the equipment needed to be manually ip address, both the pcs and the router s and switches. The instructor asked who knew how to do that... there were two of us counting me out of 15 seeking computer science degrees. So it eludes even people in that field too. Also I saw that issue on another ics port somewhere. Enter Information, fail, reboot, work. Maybe it's hanging on the initial handshake? I need to flash cm10, do the initial Wi-Fi where it hangs and go get on my mom's computer and see if it shows up in the connected devices area. If it does then see if it has an ip address. If it does then the phone is not accepting it for some reason. Maybe I can do that later.
mercury0x000d
The ultra-modern operator
That was exactly my thought. But I tried a bunch of different configs and still no go... I know I'm at a loss. I figure if it is a config issue, it may be one that needs fixed via recoding, not the actual setup of the system or DHCP. I do know it works slightly different than GB's DHCP. On JB you have to specify the interface (wlan0) to activate the service for, which you never had to do on GB.
As you said, I'm just throwing info out there in case it helps someone more familiar with how Linux handles things than am I, because I'm completely lost with the whole JB thing... Stick with what you know, Merc lol
Hope it helps.
Blyss
Android Enthusiast
I had a laptop once that would occasionally reject the DHCP address it was given and you had to cycle the wlan off and on.
I've not seen the code but my suspicion is it's working like this with DHCP on:
Phone to router:
Hey I'm a phone with Mac address xyz, can I connect?
Router to phone:
Do you have the network key?
Phone:
Yes it's blah blah blah
Router: accepted, DHCP or static?
Phone: DHCP
Router: *checks routing table*
192.168.1.21 is available, is this acceptable?
Phone either never respond or fails assigning the address.
Here is an interesting thought. A routers DHCP table doesn't update instantly on wireless. What if the router is assigning the ip address, then the phone does whatever silliness it's doing. Reboot phone and if it's before the router had refreshed its table the phone still has an ip. The phone sends it's Mac address and instead of a dhcp handshake, the router just says your are already connected to xyz address. The phone goes "oh" and addresses itself statically without ever invoking dhcp. After running this through my head step by step I'm almost certain it's a problem with how dhcp is being handled. The handshake sPecifically.
I've not seen the code but my suspicion is it's working like this with DHCP on:
Phone to router:
Hey I'm a phone with Mac address xyz, can I connect?
Router to phone:
Do you have the network key?
Phone:
Yes it's blah blah blah
Router: accepted, DHCP or static?
Phone: DHCP
Router: *checks routing table*
192.168.1.21 is available, is this acceptable?
Phone either never respond or fails assigning the address.
Here is an interesting thought. A routers DHCP table doesn't update instantly on wireless. What if the router is assigning the ip address, then the phone does whatever silliness it's doing. Reboot phone and if it's before the router had refreshed its table the phone still has an ip. The phone sends it's Mac address and instead of a dhcp handshake, the router just says your are already connected to xyz address. The phone goes "oh" and addresses itself statically without ever invoking dhcp. After running this through my head step by step I'm almost certain it's a problem with how dhcp is being handled. The handshake sPecifically.
Blyss
Android Enthusiast
Useful info I found elsewhere:
The request from DHCP client to a server involves a "four-way handshake." First, the client boradcasts a "DHCPDISCOVER" message to the local subnet asking for configuration information. In this message, the client fills in the 'xid' field with a unique identifier (usually a randomly generated number). It also fills in the 'chaddr' filed with its hardware, or MAC, address. It may request additional information as described above. The client then collects one or more "DHCPOFFER" messages from one or more DHCP servers with matching values in the 'xid' field. The client chooses one to accept based upon the offered configuration parameters. The client then sends a "DHCPREQUEST" message specifying its selected server. Servers not selected use this message as notification that the client has declined their offer. The selected server then responds with a "DHCPACK" message if the requested parameters are acceptable, or a "DHCPNAC" message if they are not.
____________________________________
See how it says the client receives the DHCPOFFERS and chooses one and replies which with DHCPREQUEST? I am pretty sure that's where it's going bad here. What that means for DM I dunno. Can you compare the dhcp handshake from a gb Rom and a jb Rom and see what's different?
The request from DHCP client to a server involves a "four-way handshake." First, the client boradcasts a "DHCPDISCOVER" message to the local subnet asking for configuration information. In this message, the client fills in the 'xid' field with a unique identifier (usually a randomly generated number). It also fills in the 'chaddr' filed with its hardware, or MAC, address. It may request additional information as described above. The client then collects one or more "DHCPOFFER" messages from one or more DHCP servers with matching values in the 'xid' field. The client chooses one to accept based upon the offered configuration parameters. The client then sends a "DHCPREQUEST" message specifying its selected server. Servers not selected use this message as notification that the client has declined their offer. The selected server then responds with a "DHCPACK" message if the requested parameters are acceptable, or a "DHCPNAC" message if they are not.
____________________________________
See how it says the client receives the DHCPOFFERS and chooses one and replies which with DHCPREQUEST? I am pretty sure that's where it's going bad here. What that means for DM I dunno. Can you compare the dhcp handshake from a gb Rom and a jb Rom and see what's different?
Blyss
Android Enthusiast
I'd like to take a look at a logcat for when the Wi-Fi fails initially and when it subsequently succeeds to get more information. I know I could flash cm10 and get it myself but I've flashed a ton of roms today...okay well three with restores in between. Still I'm ready to just kinda chill for a bit. Hopefully you've got a dev unit with cm 10 you can pull it from easily. If that's not possible then I'll do it myself tomorrow when I am hopefully feeling better.
mercury0x000d
The ultra-modern operator
