[ROM] [Coby MID1042] Alien Droid (Advanced GUI customization) [11.18.12]

whread

Member
Apr 15, 2013
61
3
nobi wrote "I'm anxious to see what you come up with. I went back to stock and loaded market on there manually. Wifi works after restoring the backup I made before flashing AlienRom"


Hey nobi!

can you upload and post a link to your backup made before flashing AlienRom?

I have a very strong feeling that I can figure out the issue by comparing the wifi sections of your backup and the one in AlienRom.
Your 1042 may be one of the newer models which may have different wifi hardware or a different hardware revision.
Was SlideMe Market on it instead of GetJar Market? That would be a very strong indication.

My 1042 was the Christmas bundle w/ 16Gb SD card included and it had SlideMe Market on it
I have tried every available ROM that I can find - a few do not work at all (boot loops) - every dang one of them that I tried that complete the boot will not initialize the wifi.

Some other perhaps helpful info:
tried all 3 livesuit img's uploaded by Mike Hard
- sun4i_crane_mid1042_120701(8GB)V1 will boot but no wifi and boot loop after rooting using the method from this Forum
- sun4i_crane_mid1042_120820Phip-V1 goes into boot loop
- sun4i_crane_mid1042-CrazyHamster-120808-v1 will boot no wifi anoying crazy hamster appears a lot can be rooted and install clockworkmod using the method in this Forum 1042update.zip goes to boot loop can flash stock_1042.zip but still no wifi can flash aliendroid v1 but boot loop can flash alienrom v2 which runs very, very well but no wifi

Got my 1042 4 days ago, bricked it 2 times, boot loop 5 times, now running about as fast as a Galaxy Tab 10.1 with arounf 20% longer battery life.
I want to keep the AlienRom v2 so my approach will be to figure the wifi issue out and write up corrected wifi section.
 

whread

Member
Apr 15, 2013
61
3
Ok I need to see if hashcode can help me see what's up.

System Tuner (logcat)
=====================
U/ 635.200027 [sun4i-keyboard]exec signal_alarm_func
U/ 620.962305 =========== WLAN power off ========
U/ 620.955717 [mmc]: mmc 3 power off !!
V/ 620.952169 mmc1: card 0001 removed
U/ 620.946414 [bcm40181]: BCM40181 SDIO Wifi Power Off !!
U/ 620.940240 [bcm40181]: Succeed to set gpio bcm40181_vdd_en to 0 !
U/ 620.933959 [bcm40181]: Succeed to set gpio bcm40181_vcc_en to 0 !
U/ 620.927902 [bcm40181]: Succeed to set gpio bcm40181_shdn to 0 !
U/ 620.920061 [DHD] dhdsdio_htclk: HT Avail timeout (1000000)
clkctl 0x50
U/ 619.920069 [DHD] dhdsdio_htclk: HT Avail timeout (1000000)
clkctl 0x50
U/ 613.124394 battery vol change: 42->41
U/ 605.120030 [sun4i-keyboard]exec signal_alarm_func
D/ 604.715074 init: process 'wpa_supplicant', pid 1622 exited
V/ 604.715055 init: waitpid returned pid 1622, status = 0000ff00
U/ 604.710703 [DHD] dhd_open: failed with code -19
U/ 604.710655 [DHD] dhd_bus_start failed bus is not ready
U/ 604.710645 [DHD] dhd_bus_init: clock state is wrong. state = 1
U/ 604.710633 [DHD] dhdsdio_htclk: HT Avail timeout (1000000)
clkctl 0x50
V/ 603.697939 init: Created socket '/dev/socket/wpa_wlan0' with mode '660', user '1010', group '1010'
D/ 603.692401 init: starting 'wpa_supplicant'
D/ 589.736089 init: process 'wpa_supplicant', pid 1606 exited
V/ 589.736070 init: waitpid returned pid 1606, status = 0000ff00
U/ 589.710152 [DHD] dhd_open: failed with code -19
U/ 589.710115 [DHD] dhd_bus_start failed bus is not ready
U/ 589.710102 [DHD] dhd_bus_init: clock state is wrong. state = 1
U/ 589.700183 [DHD] dhdsdio_htclk: HT Avail timeout (1000000)
clkctl 0x50
V/ 588.668782 init: Created socket '/dev/socket/wpa_wlan0' with mode '660', user '1010', group '1010'
D/ 588.656522 init: starting 'wpa_supplicant'
U/ 575.040036 [sun4i-keyboard]exec signal_alarm_func
D/ 574.684304 init: process 'wpa_supplicant', pid 1594 exited
V/ 574.678207 init: waitpid returned pid 1594, status = 0000ff00
U/ 574.668598 [DHD] dhd_open: failed with code -19
U/ 574.663209 [DHD] dhd_bus_start failed bus is not ready
U/ 574.657269 [DHD] dhd_bus_init: clock state is wrong. state = 1
U/ 574.650143 [DHD] dhdsdio_htclk: HT Avail timeout (1000000)
clkctl 0x50
V/ 573.628531 init: Created socket '/dev/socket/wpa_wlan0' with mode '660', user '1010', group '1010'
D/ 573.623042 init: starting 'wpa_supplicant'
D/ 559.643118 init: process 'wpa_supplicant', pid 1542 exited
V/ 559.643099 init: waitpid returned pid 1542, status = 0000ff00
U/ 559.607663 [DHD] dhd_open: failed with code -19
U/ 559.607623 [DHD] dhd_bus_start failed bus is not ready
U/ 559.607611 [DHD] dhd_bus_init: clock state is wrong. state = 1
U/ 559.600200 [DHD] dhdsdio_htclk: HT Avail timeout (1000000)




=====================
E/10:28:47.079 wpa_supplicant( 1527)
wlan0: Failed to initialize driver interface
E/10:28:47.079 wpa_supplicant( 1527)
WEXT: Could not set interface 'wlan0' UP
E/10:28:47.079 wpa_supplicant( 1527)
Could not set interface wlan0 flags: Operation not permitted
D/10:28:46.179 dalvikvm( 1434)
GC_CONCURRENT freed 1649K, 10% free 16351K/18119K, paused 2ms+10ms
I/10:28:46.039 wpa_supplicant( 1527)
rfkill: Cannot open RFKILL control device
E/10:28:46.019 WifiStateMachine( 144)
Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to set ipv6privacyextensions - com.android.server.NativeDaemonConnectorException: Cmd {interface ipv6privacyextensions wlan0 enable} failed with code 400 : {Failed to set ipv6 privacy extensions (No such file or directory)}
E/10:28:46.019 CommandListener( 83)
Failed to open /proc/sys/net/ipv6/conf/wlan0/use_tempaddr: No such file or directory
D/10:28:46.009 NetworkManagementService( 144)
flags <[down broadcast multicast]>
D/10:28:46.009 NetworkManagementService( 144)
rsp <213 00:90:4c:11:22:33 0.0.0.0 0 [down broadcast multicast]>
D/10:28:46.009 CommandListener( 83)
multicast flag ignored
D/10:28:46.009 CommandListener( 83)
broadcast flag ignored
D/10:28:46.009 CommandListener( 83)
Trying to bring down wlan0
D/10:28:46.009 CommandListener( 83)
Setting iface cfg
E/10:28:46.009 WifiStateMachine( 144)
Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
D/10:28:46.009 WifiHW ( 83)
Enter: wifi_get_fw_path function, fw_type=0,
E/10:28:46.009 WifiStateMachine( 144)
Failed to setup control channel, restart supplicant
E/10:28:46.009 WifiHW ( 144)
Supplicant not running, cannot connect
E/10:28:45.009 WifiHW ( 144)
Supplicant not running, cannot connect
E/10:28:44.009 WifiHW ( 144)
Supplicant not running, cannot connect
E/10:28:43.009 WifiHW ( 144)
Supplicant not running, cannot connect
E/10:28:42.009 WifiHW ( 144)
Supplicant not running, cannot connect
E/10:28:32.079 wpa_supplicant( 1525)
wlan0: Failed to initialize driver interface
E/10:28:32.079 wpa_supplicant( 1525)
WEXT: Could not set interface 'wlan0' UP
E/10:28:32.079 wpa_supplicant( 1525)
Could not set interface wlan0 flags: Operation not permitted
I/10:28:31.019 wpa_supplicant( 1525)
rfkill: Cannot open RFKILL control device
E/10:28:30.979 WifiStateMachine( 144)
Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to set ipv6privacyextensions - com.android.server.NativeDaemonConnectorException: Cmd {interface ipv6privacyextensions wlan0 enable} failed with code 400 : {Failed to set ipv6 privacy extensions (No such file or directory)}
E/10:28:30.979 CommandListener( 83)
Failed to open /proc/sys/net/ipv6/conf/wlan0/use_tempaddr: No such file or directory
D/10:28:30.969 NetworkManagementService( 144)
flags <[down broadcast multicast]>
D/10:28:30.969 NetworkManagementService( 144)
rsp <213 00:90:4c:11:22:33 0.0.0.0 0 [down broadcast multicast]>
D/10:28:30.969 CommandListener( 83)
multicast flag ignored
D/10:28:30.969 CommandListener( 83)
broadcast flag ignored
D/10:28:30.969 CommandListener( 83)
Trying to bring down wlan0
D/10:28:30.969 CommandListener( 83)
Setting iface cfg
E/10:28:30.969 WifiStateMachine( 144)
Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
D/10:28:30.969 WifiHW ( 83)
Enter: wifi_get_fw_path function, fw_type=0,
D/10:28:30.969 WifiHW ( 144)
insmod okay,try_time(0)
D/10:28:22.999 NetTrafficLogic( 422)
logic 173:[CELL[rmnet0, pdp0, ppp0, pdp_ip0, wimax0, vsnet0, ccinet0, ccmni0, qmi0, bond1, rmnet1, usb1, rmnet_sdio0]: (0/0)]
D/10:28:22.999 NetTrafficLogic( 422)
logic 160: 0 : 0
D/10:28:22.999 NetTrafficLogic( 422)
logic 152: 0 : 0
D/10:28:22.959 NetTrafficLogic( 422)
daoImpl 174: LastTraffic: 0 : 0
D/10:28:22.959 NetTrafficLogic( 422)
daoImpl 227: device_t: 0
D/10:28:22.959 NetTrafficLogic( 422)
daoImpl 226: device_r: 0

Do you need more?
 

whread

Member
Apr 15, 2013
61
3
Hey!

RE: no wifi

Just tried-

FXR WiFi fix and rescue 1.5.0
Fix.My.WiFi.2.9.Android
Wifi Fixer

All failed - logs no significant difference as previous post (starts with System Tuner (logcat))

Also tried slowing CPU Clock as well as speeding it up - changed governers - removed all tweaks previously applied - no effect whatsoever.

Think I have to see dumps from factory fresh 1042 from same manufacture period.
Pretty dang sure a comparison the sun4i_crane_mid1042-CrazyHamster-120808-v1, AlienRom v2, posted Stock-1042.zip and factory fresh dump from same manufacture period will do the trick.
The sun4i_crane_mid1042-CrazyHamster-120808-v1, AlienRom v2 and posted Stock-1042.zip are all pretty dang close to each other, some differences that would not seem to be significant.

Excellent puzzle!

Have A GRRRRRRRRRREAT Day!
 

whread

Member
Apr 15, 2013
61
3
I realize I screwed a ton of people over on this rom and I appologize. I no longer own the device but if someone owns the device with screwed up wifi due to my rom then I want to try and see if i can try to fix the issue(do not get your hopes up though). Starting off with a logcat from someone with the screwed up wifi problem. You could try turning wifi on / off while gathering it... also someone with broken wifi and someone with nonbroken wifi, I need the output of blkid from in adb shell.

Hey! actually you did excellent work. While perfection is to be desired having a functional tablet w/o wifi is far superior to haveing an attractive paperweight.

Being able to use my 1042 - THANX! TO U - to not being able to use it and having thoughts like 'what can I use the parts of this thing for now that I nuked it.

As I mentioned elsewhere in this forum - mine really runs faster and the battery lasts longer on AlienDroid V2.

You made the ROM, that was pretty dang awesome. Fixing the WiFi and touch screen stuff is elusive but not unobtainable.

You can do this Dude! Broadcom is like sand, it's everywhere but some of it itches and some of it dosen't.

In the mean time for those of you with bricks or loops - it can be easily brought back except for some of us get touch screen issues and othere get WiFi BUT NOT ALL OF US.

D/L some torrents and hook that baby up with wire or use a mouse until the superb people here work this out. Superb is inclusive for all of you here. If I had not stumbled into this Forum I would have a 3 day old heavy mouse pad or strange, dark mirror or a nice prop to carry around sort of like glasses with no glass.

It was all of your writings in all the threads (including the irate, blown away by worry persons) that led me to the correct conclusion that a slightly unconventional, advised against course of action would get the little wench back to life.

I was a dash dissapointed when I first got my 1042, beautiful little thing but a little too slow and unresponsive and the app store was eating doo doo.

Now after a bunch of bricking and boot loops (started by following some other forums' advice) I have a sweet little honey that is fast, responsive and gets 7 to 8 hours of fairly intense use to the charge.

So the AlienDroid effort is coming out unbelieveably well but like every other thing anyone ever did needs some adjustment at first.

When one of the people here gets this done AD will be a measurably and signicantly superior alternative to the basic Coby included.
Looks great, works great needs a couple of adjustments which certainly could be set up to recognize the variants (3 or 4 it seems) and do the right thing for each.

Aagin for those bricked or boot looped - Even when the OS is DOA and the tablet seems to be unsalvageable the hard wired stuff will allow you to wake it up again, so unless you smash or cook something you have nothing to lose by trying a few things until it's back.

BTW mine, a friends that I rooted, CWMed, Google Stored today following this Forums clear and easy advice to do can run at 1156MHZ w/o problems , excessive heat or battery use. They get real snappy at that clock speed. I adjusted ONLY the CPU clock so I have not a clue what other OverClockings would do.
 

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
I haven't had much time to mess with this tablet, I did check out two livesuites both are junk, guess I will make my own and go from there.
 

whread

Member
Apr 15, 2013
61
3
Mine is Coby Kyros MID 1042 8BG WiFi 124120085516 bought as used from a store return. The only other 1 I have access to is my friends - will try to get the S/N.
Thanks for the dump in advance.

For sure livesuit is not ready for prime time in general, is surely not an example of elegant programming and ALL the versions I found had been rezipped with whatever 'original' package inside. Most had no button labels which seems to be an indication that it had been used before. I did finally find one that had ladels on the buttons and words inside the messages by peeling down thru the layers of zipped then rezipped (and in one case rezipped again). The one with labels on the buttons worked. The others did not or caused bricking. 1.07 worked more reliably then 1.09.

A script or batch file depending on O/S would have been adaquate for what the exe does.

BTW: have Sunn Spark WS floping around here somewhere. May fire it up and see what can be done under UNIX - should be similar or same under any OS but sometimes not.
 

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
I use 1.09 livesuite, to get a good image they need to be based on ployer images.
I have made images for coby 7042, 8042, 9742 and will now have to make one for 1042, try to base off of the 9742.
 

whread

Member
Apr 15, 2013
61
3
After I read your post referencing livesuit 1.09 I looked furthe and found one that had not been used before - a fresh livesuit 1.09 is better than 1.07

With the experience that I gained since last Friday going back and forth thru the roms is quick and easy - and so far bricking is quickly resolved

If we can determine the 1042 variants and have both livesuit img's and CWM zips for those variants it would seem any soft-bricked or boot looped 1042 or 7042, 8042, 9742 would be fairly easy to get back

It would appear that there are 4 variants from the current circumstantial evidence - 3 are indicated by the Mike Hard UL's and the 4th indicated by mine

I will look at the roms I have accumulated when I get back tonight as well as search this forum for .img's and .zip's for those you mentioned - seems like it can't hurt to try them
 

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
I will be testing this rom tonite, note this rom by itself isn't the cause of the wifi problems. People need to backup their tablet before installing any rom. Some Coby tablets use different wifi modules then this version, so wifi is lost cause wrong module is being loaded.
 

whread

Member
Apr 15, 2013
61
3
I LIKE the AlienDroid V2 - that is not the cause of the problem - AD V2 is just another indication of the problem.
To be fair to Coby it looks to me like they responded to user pressure to put a stronger signal WiFi module in there as indicated by the many complaints over the past year about weak and intermittant WiFi and the sudden drop off of those complaints around January.

I like my 1042 a LOT. It is a snappy machine with AD V2. Excellent work and who knew about the variants when it was done.

Mine was just as good as my ASUS laptop, my sons iPOD touch G4, my wifes HP laptop or any of the other equipment flopping around here (we are old tech nerds - time ='s more stuff - you'll see when you get to where we are).

I did do a dump and install of my friends ROM - he has the weak intermittant issue and his dump has the same Broadcom drivers as AD V2. It is an older model that he got last September. His serial number is obscured by scratches but mybe I can read it with a really stron magnifier - will try this weekend. Perhaps S/N's can indicate revisions or manufacture dates - many do.

I agree that I should have made a dump first - unfortunately the instructions I followed left that part out and I had no reason to believe that there were different revisions. Not all of the information on the internet is as solid as yours.

I originally bricked my 1042 by following instructions gotten from a completly different source than androidtablets.net to get Google Store on it.
androidtablets.net's method is spot on and works perfectly IF the correct ROM is installed.

I also agee that the ROMs and IMGs I have used are for different WiFi modules - the clock issue you can see in the log files I posted tell us this as well as the systems reads of the modules errors.

The AlienDroid V2 would have produnced the same results for me in any case - we know this to be true because WiFi does not work on my 1042 when running that ROM.
The WiFi module is alive and well because the system is reading it's error messages.

What may well result from this exercise is a list of known WiFi modules and an addition to the custom roms that can identify the WiFi and utilize the correct drivers - the module will come on if the drivers are correct and the system can see that.

I am going to search this Forum to find possibly applicable dumps now.

Whether or not I find any applicable here I will install ALL the images and Zips I already have this weekend one after the other (that part is the easy part) and note what modules they are for as well as save logs to determine the errors generated.

BTW - my old Sunn Spark Workstation may prove to be of little or no assistance unless I can learn enough LINUX in a short while to use that OS's driver code as takeoff point for my UNIX Android Tablet Drivers. It has been a trial to write drivers for the Serial to USB adapter all by itself. Back then USB was not even a blip on the RADAR also took a while to find the balance point between too fast for serial and too slow for USB, found a driver for a PS2 keyboard that gave me the some clues (all 3 are dang close to the same anyway) . It is cool to see that 26"fixed frequency CRT and pust that pen around again though!
 
Top