Hi all,
I'm not sure this thread goes here, sorry if it doesn't.
I bought a Chuwi V88 tablet one month ago. When i received it, everything was running ok. About a week later, WiFi started to fail, i couldn't click the "no/yes" switch to enable it (in the best case, when i could click it, only "enabling wifi" message appeared indefinitely). I tried to flash OMA (http://forum.xda-developers.com/showthread.php?t=2310818) rom to solve it but anything changed. Now i have time again to try to repair the chuwi, but i don't know how to continue.
My actual status is:
V88 S/N (in the backside): 16G2131100086
ROM: Oma_RK31_Chuwi_V88_JB_4.2.2_windoof_v5.2 (multiwindow version)
Kernel: bob #445
WifiFix installed
Factory wipe done (no changes)
When I connect the tablet to ADB, logcat says:
E/WifiHW(412): Timeout to wait for Wifi interface within 15 seconds.
D/WifiHW(412): wifi_unload_driver
D/WifiHW(412): Check driver status: not loaded
E/WifiStateMachine(412): Failed to load driver!
E/WifiStateMachine(412): DriverFailedState
Could someone helps me to solve the problem? I've read the original thread, but i can't post there by now.
I have the exact same problem, hopefully me posting this here will give it more chance of someone more knowledgeable finding it. I'd ask Oma but I first need 10 posts. 9 to go I suppose...
Related
I updated my A70H to 2.4.65 and now in the settings under wifi (where you usually enable it) and it says "error".
Reboot does not fix it.
Any other ideas to fix it without losing data?
I fixed it by deleting the multimedia database. Don't ask me how that is related but it helped.
Also I realize now that I probably posted in the wrong forum. But I wanted the solution either way.
Moved to proper forum
I had same problem.
Wifi worked fine in Android, but got 'Error' every time when booted to developer menu.
Fixed this by installing firmware manually again.
Probably failed because made my Firmware upgrade when system was booted to developer/rooted.
Hello, all ROM makers, developers, hackers and advanced users.
I have a problem and hope you can give me some good advice.
Here is my sad story
You can read the full description if you want. Or you can skip it - the main question in the end of this post..
I have bought a new Sony ericsson Live! with walkman (wt19i) phone during my newyear holydays in Prague. It seemd to be working fine.
It is from rev.3, manufacture date 11/49 (mounth/week)
When I came back home and started using it, I saw that after some inactivity period (about couple hours or maybe more) the touch screen, back and menu snsor buttons stops any responsing. Hardware buttons (home, volume, camera, walkman and power) are still working. The system also continues to work as usual, so I can turn it on (but can not slide to unlock), I can hear if somebody calls me (but can not answer). Alarms, notifications and all another functions are still working.
Once or twise it started to work again (by itself, without any actions by me) but after few time the problem repeated. I was very unhappy and sure it was a hardware problem (and of course the Czech warranty does not work in Russia), but now i'm not so sure.
The phone had 4.0.2.A.0.58 firmware (android 2.3.4) from the box. First of all I tried to install SE PC Companion software, connect phone with usb and make factory reset... touchscreen started to work! But soon I saw this problem again.
The next day a new update was released and installed it (firmware .62). My phone was working again, but with the same result after some time.
You shoud know, that simple softreset (or ejecting and inserting battery) has absolutesy no effect on problem. After system starts I can not even unlock it. But flashing a new (or even the same) firmware (with flash tool or SE PCC) makes touchscreen and buttons working for some time. Have no idea why, but installing ROM with CWM (even with full wipe) does not make touch working.
Then I tried to use another custom kernels and ROMs. I unlocked the bootloader with fastboot tool, flashed one of custom ROMs from this forum (pre-rooted and with CWM). Then tried to use CM7.2 ROM... then another kernel and another ROM. Official, official-based, totally unofficial. The problem was with me each time after couple hours
I thought it is because some troubles in lock screen. Tried to install "no lock" app, so my phone did not use lock... but after some time touch freezes in home screen.
I disabled screen off while charging in settings and tried to leave the phone "wired" for some time... actually it worked fine all the time, and when I dicsonnected it it was still working... for couple hours.
I tried to install "no sleep" applications that does not allow CPU and screen to suspend. But it have no influense.
I even flashed CM9.0 ICS (very) beta ROM with the same result.
If it is just hardware problem - why it solves (for some time, but solves) with flashing? If it is a software problem - why it doesnt solve with new kernels and ROMs? My brain is ready to explode.
Now I have only one last idea and ask you to help me.
The question is:
How can I use adb or adb shell comands to get more information about the problem with touch?
I saw there is some log (logcat, stderr) tools, debug tools. I saw working lsmod, dmesg and mount commands in shell.
I think I shoud get all this information when all is ok. And then get it again when touch stops working and then compare, is it a good idea?
Where exactly shoud I see? How to test or get some touch input device info with adb? Is there any item in /dev that i can explore? Or something in dmesg? Where are touch driver located and how can I check if it is working?
I have some basic linux and andriond skills, but have not enought expierence.
I very (VERY) hope somebody can give me any useful advice to continue solving the problem. Where to see, what to do?
Thank you
P.S.: and sorry for mistakes, of course. English is not my native language.
P.P.S.: i am not sure where is the best place for this question: here or in xperia subforums. But I decided that this question is not xperia-specific and can be useful for other people in future.
Anybody? I have Lenovo Yoga B6000 with touchscreen problem and will be good if anyone know how can i test TS through ADB or shell.
Hello there and please excuse me for my bad english! As the title says, I can't connect to wifi network. Well, I can but it just work sometimes and works weird. Here's the scenario:
MIUI 3.6.7 rom on a Motorola Atrix 4G.
Android 4.1.2 JZO54K
Baseband N_01.77_38P
Kernel 2.6.32.60-MB860-CM10-ged7b511
On last sunday I tried to connect to a open wifi network, all week I was connecting to my home network. The status of wifi kept on "Turning on wifi..." for a while, but nothing happened. I restarted the phone and happened the same thing. At home, the connection worked but suddenly it closed for no reason. I tried to connect it again but kept again on the "Turning on wifi..." thing and suddenly the phone restarted! Not enough, it got stucked on the very first screen (the one with the "unlocked" text and Motorola logo), so I had to do a battery pull.
I've wiped Dalvik cache, cache partition, did some full wipes, installed again the rom (I was on 3.5.31 for then, updated yesterday to 3.6.7 and still the same), changed the Baseband, installed another kernel and I'm in the same situation. It's driving me crazy.
Got a logcat with Catlog, and found some (maybe interesting) lines (you can find the whole file in ge.tt/36KSn9j/v/0 -- sorry for be unable to post a link or uploading a file here):
06-11 15:21:54.508 W/CommandListener(1415): Failed to retrieve HW addr for eth0 (No such device)
06-11 15:21:54.508 D/CommandListener(1415): Setting iface cfg
06-11 15:21:54.508 E/WifiHW (1714): Unable to open connection to supplicant on "eth0": No such file or directory
06-11 15:21:54.508 I/wpa_supplicant(11001): rfkill: Cannot open RFKILL control device
06-11 15:21:54.508 E/wpa_supplicant(11001): Could not read interface eth0 flags: No such device
06-11 15:21:54.508 E/wpa_supplicant(11001): WEXT: Could not set interface 'eth0' UP
06-11 15:21:54.508 E/wpa_supplicant(11001): eth0: Failed to initialize driver interface
06-11 15:21:55.508 E/WifiHW (1714): Supplicant not running, cannot connect
06-11 15:21:59.508 E/WifiStateMachine(1714): Failed to setup control channel, restart supplicant
Googling about this got me to this thread (drakaz.com/forum/viewtopic.php?id=120... again sorry for the links thing) and got me thinking why the net interface is listened as 'eth0' and not 'wifi0' or something. I'm pretty noob to Android but I'm sort of an average GNU/Linux user, so I checked for what is going on in the dhcpcd.conf file and founded there the hostname was writed as 'wifi0' so I changed to 'eth0'... but this thing is still the same. Can you give me a clue about what the hell is going on? Thank you so much!
Make a nandroid backup and try a different ROM (preferrably a GB/CM7 based one).
ravilov said:
try a different ROM (preferrably a GB/CM7 based one).
Click to expand...
Click to collapse
Thank you so much for your answer! I tried CM7 (both stable and nightly, I heard the last one was a bit more stable than the first one) doing full wipe, of course. But when restarting, on both cases they only reached the very first screen (the one with the Motorola logo) and after like 5 seconds the phone rebooted automatically.
The thing is I really don't want to change MIUI. I've been using it since august, 2012 and I'm in love with it. This is the first time I got an issue so serious. Is there anything else I can do? Thank you so much!
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
ravilov said:
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
Click to expand...
Click to collapse
After the millionth full wipe I just got to install CM7 nightly and a clean reboot. But the wifi thing is still there... Well, a fc popup dialog appears after like 10 seconds: "Sorry! Application Settings (in process com.android.settings) is not responding.". I'm going to install MROM and catch a logcat, will be back then with a logcat. Thank you so much!
So I finally could get MROM working (I guess the thing about all GB roms rebooting when are just installed is about CWM). There's still the same thing I got with CM7. I have a logcat under MROM, and another I catched before I flased MROM (using MIUI v5): As I couldn't got MROM working just after wiping all when I was with CM7, I tried flashing MIUI. It flashed normally and at startup wifi was working, but after a while the connection closed suddenly. I got a logcat from that.
So the logcat with MIUI v5 (2013-06-14-02-26-28.txt) is here: ge.tt/6AQdiSj/v/0
And the logcat with MROM (2013-06-14-15-32-55.txt) is in ge.tt/7slxiSj/v/0
Hope this can help, I will keep pending so if you want to know something just let me know. Thank you so much for your help!
Seems that this is a problem about planned obsolescence. I'm such a noob, I hadn't seen this thread before (http://forum.xda-developers.com/showthread.php?t=1656760) where they explain many people had this issue. I can't post to that thread, but seems that they never got their wifi working again as I do sometimes. This is the weirdest s**t I've ever had with an electronic device.
Hello! this is my first thread.
Normally I wouldn't take the trouble to write about a problem of this sort and just search for a similar and resolved one in forums, but this time I couldn't find any.
My tablet is a Polaroid a900x, used mostly for work and social media. It was working incredibly fine before I installed Xposed and an Xposed module along with it over a year ago. Now every time I boot it, it shows the logo and never arrives to the home screen, instead there appears constantly these error messages:
"Unfortunately, Stresstest for 5.0 has stopped.
"Unfortunately, the process com.android.phone has stopped.
"Unfortunately, the process android.process.media has stopped.
Click to expand...
Click to collapse
Even if I click "Ok" on all of them, they keep appearing.
So far I have tried to wipe data/factory reset and wipe cache partition without success.
Could someone help me find a solution or explain to me what happened?
I already took it to a "Technic" which just told me I should better buy a new one, preferably of a "better" brand...
Thanks in advance! (and I hope this is the right forum)
Say94 said:
Hello! this is my first thread.
Normally I wouldn't take the trouble to write about a problem of this sort and just search for a similar and resolved one in forums, but this time I couldn't find any.
My tablet is a Polaroid a900x, used mostly for work and social media. It was working incredibly fine before I installed Xposed and an Xposed module along with it over a year ago. Now every time I boot it, it shows the logo and never arrives to the home screen, instead there appears constantly these error messages:
Even if I click "Ok" on all of them, they keep appearing.
So far I have tried to wipe data/factory reset and wipe cache partition without success.
Could someone help me find a solution or explain to me what happened?
I already took it to a "Technic" which just told me I should better buy a new one, preferably of a "better" brand...
Thanks in advance! (and I hope this is the right forum)
Click to expand...
Click to collapse
Hi what is you model name and build number from the back cover?
Teddy Lo said:
Hi what is you model name and build number from the back cover?
Click to expand...
Click to collapse
Hello! the model is A900 and BN (which I think is Build Number) is: 01.01.008.091.01
Say94 said:
Hello! the model is A900 and BN (which I think is Build Number) is: 01.01.008.091.01
Click to expand...
Click to collapse
Sorry for late respond , I can't find any of rom for your device , so try to contact support to provide you stock firmware for your device.
https://polaroid.com/support
Good Luck
Hi everybody, excuse me because i'm a newbie.
After many tries, i have been able to flash a new rom on my Galaxy J320FN (if uou are interested on the method and toos that i used :
Install Twrp 3.0.2 (the only one i have been able to download using Odin, all the other newer releases seemd good downloaded but in the reboot were replaced by original Samsung recovery).
After the install of Twrp i followed the procedure, cleaning data, cache and flashing Lineage OS214 and in a second moment the Gapps package.
The phone is much more better than with old Android 5.1 originally installed and everything works fine except the Wifi.
I can see all the ssids near to me but when i try to connect i can see that the devices makes many tries (i see Connecting) and after a while writes (Saved).
The tries continue and while the device says Connecting i see a toast message (Password may be incorrect) but the password is good because with the same password i connect with my notebook.
I have googled and i found someone that had my same simptoms after flashing Lineage Os214, in some cases one of them solved with some tips in developer section, in other cases , changing the Country in the advanced section of the wifi Menu, but noone of these solutions worked for me.
Is there someone that can help me to solve the problem ?
Another question, is Lineage Os14 the newer rom for my Galaxy SMJ320FN ?
Same here!
maurososcia said:
Hi everybody, excuse me because i'm a newbie.
After many tries, i have been able to flash a new rom on my Galaxy J320FN (if uou are interested on the method and toos that i used :
Install Twrp 3.0.2 (the only one i have been able to download using Odin, all the other newer releases seemd good downloaded but in the reboot were replaced by original Samsung recovery).
After the install of Twrp i followed the procedure, cleaning data, cache and flashing Lineage OS214 and in a second moment the Gapps package.
The phone is much more better than with old Android 5.1 originally installed and everything works fine except the Wifi.
I can see all the ssids near to me but when i try to connect i can see that the devices makes many tries (i see Connecting) and after a while writes (Saved).
The tries continue and while the device says Connecting i see a toast message (Password may be incorrect) but the password is good because with the same password i connect with my notebook.
I have googled and i found someone that had my same simptoms after flashing Lineage Os214, in some cases one of them solved with some tips in developer section, in other cases , changing the Country in the advanced section of the wifi Menu, but noone of these solutions worked for me.
Is there someone that can help me to solve the problem ?
Another question, is Lineage Os14 the newer rom for my Galaxy SMJ320FN ?
Click to expand...
Click to collapse
I am in a similar situation with my OnePlus.