• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root cm10.2

no threshold im aware of, and lte worked out of the gate before? like when i first announced it was working? kuz mouse was telling me that the default network mode had to be 9 instead of 8 but if 8 works better ill go with 8. or maybe its just cycling through the apn trying to get things to work before giving up who knows. i had it set up with an apn that didnt have the extra crap in there before, now its set to have a modified copy of the cm one
 
4g works fine, idk if speed changed because the speed is always different, but data is not completely dropping anymore, only between 3g and 4g transition, which will cause things like videos to restart.
Oh, and I meant on stock it would be readily available, I don't remember about any previous version of cm10, I'm gonna have to find some time to test that if I still have a copy of the previous build.
 
i figure stock is better optimized for things like that. cm is more straight forward, either its connected or its not, and there is probably going to be a lag between mode switched they just compensated for that on stock
 
ugh, anybody wanna donate a boost force? lol. can someone do me a favor and go to /sys/devices/platform/msm_sdcc.4/mmc_host/mmc2 in a root browser of some sort, and check that there is a folder in there thats name starts with mmc2: and then has 4 hex digits(hex digits are numbers and letters up to F) then back out of that directory, pull your sd, then go back in and see if that folder disappears...
can be done on any rom, stock or cm doesnt matter itll all be the same at that level
if that doesnt have a folder that comes and goes with the sd, check for something similar in
/sys/devices/platform/msm_sdcc.3/mmc_host/mmc1

i need to find the proper vold mount point and to do that i have to find the disappearing folder

was gonna have mouse figure it out but he seems to have pulled a disappearing act of his own... so im kinda stuck and its really frustrating knowing what you need to test and not being able to test it
 
ugh, anybody wanna donate a boost force? lol. can someone do me a favor and go to /sys/devices/platform/msm_sdcc.4/mmc_host/mmc2 in a root browser of some sort, and check that there is a folder in there thats name starts with mmc2: and then has 4 hex digits(hex digits are numbers and letters up to F) then back out of that directory, pull your sd, then go back in and see if that folder disappears...
can be done on any rom, stock or cm doesnt matter itll all be the same at that level
if that doesnt have a folder that comes and goes with the sd, check for something similar in
/sys/devices/platform/msm_sdcc.3/mmc_host/mmc1

i need to find the proper vold mount point and to do that i have to find the disappearing folder

was gonna have mouse figure it out but he seems to have pulled a disappearing act of his own... so im kinda stuck and its really frustrating knowing what you need to test and not being able to test it

K it worked with the second one (msm_sdcc.3) pulled the SD card and the folder msm1:aaaa disappeared. There was no folder msm_sdcc.4 on my system.
 
sdcard thing? if you are referring to what i may have mentioned about what mouse and i are currently working on that has nothing to do with cm10, it only applies to cm10.1+ or the cm10.2 version of cwm. we were trying to get an official version. the only difference in the newest release from the one before it was the addition of some wifi parameters that dont seem to do anything. it was worth a shot but it didnt work

need to find out why its looking for disable_ipv6 and cant find it
 
/proc/sys/net/ipv6/conf/ should have a wlan0 folder in it that represents the wifi, and inside there should be disable_ipv6. its not there though, might have something to do with the kernel, might have something to do with the kernel module not loading right, might just be the wpa_supplicant or the netmgr or netd or something. its down to a guessing game at this point
 
I may be getting a new computer soon, ours is 10+ years old :p and a dell, I will be building it and plan on dual booting Ubuntu and win 7. You think I could help some how with development when I do? Never done any android development, so if you could point me in the right direction, and maybe I could help with the small things?
 
well i mean i can point you in the right general direction on how to set up to build. the rest is kinda up to you though. i just need to do some testing and figure out what is causing it to not populate that directory properly which i cant do myself without a unit to test on, if someone wants to research it and/or try some stuff out, that might help but its very difficult to even have the slightest clue whats going on blind like this
 
the wifi issue is probably in the boot.img to where it can be unpacked and fixed manually, either one of the rc files or a bad kernel. or it could be we are using the wrong file in bin for ip6tables, or it could be the wrong or a bad netmgrd or netd or wpa_supplicant or misuse of the wlan.ko file, i really have not a clue
 
the "option" is either in the network selection menu i think its called, or there is a menu you can get to through dialing a certain code, youll have to get the code from mouse or the avid forum though. it is supposed to be enabled by default though via the build.prop
 
the one built from the avid kernel source. may not be right... though if wifi works in stock using it which as far as i know it does kuz the matrix kernel uses the same source, i dont see that being the issue. you CAN however test it with the stock kernel. get a copy of the android kitchen up and running, unpack a stock boot.img take the zimage file from there, unpack the cm boot.img, replace the zimage in there, repack and flash it to your phone
 
Matrix is modified from the avid source. There are no issues with it on DSF which is basically a stripped down stock with some extras thrown in. I haven't made a zip for cm10 since it is still in development, and don't want to further complicate things for you guys
 
well, some of the 10.1 or 10.2 issues are possibly able to be fixed by upgrading to 3.4 but i dont think that will help things like wifi even if the kernel is the issue, the problem there would be the fact that the kernel being built isnt the same as the one that came with the phone, it may very well be missing things or have something extra that conflicts with other things
 
We can start bugging zte for the source code to 3.4 if an official JB update ever happens. Much to my surprise the avid source worked out of the box. Who knows maybe we will get lucky twice
 
yea we can only hope some device comes out with a hayes config. might look into jellybean devices with the 8960 chipset they already have source out for, if you can find a hayes config file in there it might work for us

but on an unrelated note, ive made a small change to the wifi, see if that works... though its doubtful, you never can tell

all i did was swap out the wpa_supplicant.conf with the one from the sequent. its not really device specific per say, and i couldnt find all the same setting in the one on there already, though it was hundreds of lines of code 99.9% of which was commented out... the one i put in there just has the necessary lines and one thing commented out that was a test run at one point
 
Back
Top Bottom