Related
I don't know why the person asking about an accelerometer failure had their thread closed after a single response suggesting banging the G1. In fact, failure of the accelerometer usually *is* a software failure, and is usually fixed with a factory reset. I just went though this on my unit two days ago!
I just did a wipe yesterday to rid that same issue.
I am not so fortunate. My accel and compass sensors have remained non-working despite several wipes and re-flashes. Here is my thread, if anyone has any ideas for me.
http://forum.xda-developers.com/showthread.php?t=533749
And yes, the hardware is fine, as they both work great in pre-cupcake firmwares (RC29 and RC33), but not at all in any (ADP, JF 1.51, Cyan's mod, etc) cupcake build.
Any help is appreciated!
way to fix without wipe?
well is there? i dont feel like wiping and then reseting my settings from b4. the issue just happened when u updated to cyraogen 3.6.8.1 with the help of the download like from the kspec kustom threAD to get the rom update, theme, and htc music in one flash.
Fixed it! (All by my self....... kinda)
pistol4413 said:
well is there? i dont feel like wiping and then reseting my settings from b4. the issue just happened when u updated to cyraogen 3.6.8.1 with the help of the download like from the kspec kustom threAD to get the rom update, theme, and htc music in one flash.
Click to expand...
Click to collapse
I should have searched his thread.... ran the script in the fq to fiv my issues.
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?
Apologies for another GPS thread but i have tried all suggestions in popular threads using methods such as faster fix and GPS status's A-GPS tools and the method posted in "GPS CM7 fix".
Im currently running CM 7.02 (Stable) and radio 26.08.04.07_M3, which i was told had great overall performance including GPS. Ive tried using different ROM's and different radios but had no luck in finding a secure GPS lock. Recently i have been unable to even find even a single satellite using GPS test or GPS Status.
Before rooting and flashing new ROM's i used to get a fairly consistent GPS lock but even returning to the default HTC Sense ROM now does not return the GPS to working order. I also used to get a lock when i first flashed CM but since flashing various radios and ROM's ive been unable to get GPS working properly and I think this is partly to blame.
Ive done a fresh wipe and wiped dalvik cache but this has also not helped. Any suggestions or full methods on how to restore GPS would be greatly appreciated. Thanks.
If you've tried every suggestion and tried the radio / Kernel recommended for your ROM by the ROM Creator then you may have to consider it being a hardware fault.
Sent using witchcraft via XDA Developers App.
Im hoping this isn't the case but perhaps you be may right. The only reason im hopeful of a software fix is that i have had sporadic cases of GPS working using different ROM's in the past and theres no sign of external or damage to the phone in any other way.
Would there be a way to test it if a hardware fault was the cause of the problems?
It won't be hardware issue I have the same problem, there is a file you can fladlsh that fixes it but I cannot find it
Im hoping thats the case, also does anyone have any experience with RIL's that work with CM7? im not sure if they may help with the problem as it does seem as if there could be a problem lying between the radio and the ROM.
Is this file you mentioned anything to do with RIL's or is it a GPS log file flash or something along those lines?
I'm sure it was a .lib file, from the android revolution or leedroid thread agggges ago ill have q.look if I can find it
ok thanks, im assuming this could work with CM7 aswell then?
Yeh its the only way I could get GPS working on cm7, now I can't find it I have no GPS lol so I need it aswell
Ha, well let me know if you manage to find it. Do you know why this happens on CM7 and why not many people seem to know about it?
I think its something to do with drivers, some.peoples chips are different and the normal drivers aren't fully implemented
think i found it, just about to give it a whirl
http://forum.xda-developers.com/showpost.php?p=12208708&postcount=425
Ok then, so im guessing i just adb push the first file (gps.spade.so) and as im in Europe (UK) i flash the EU_GPS_HD.zip in recovery as a zip file?
yeh, just follow the instructions and it should work
Seems to have improved things, got 3 satellites in view but still no lock, il leave it to search for a while. Thanks
Try going into recovery and wiping cache and dalvik cache I got instant lock
Yep this seems to have worked, still abit inconsistent with the locks but i get about 5/6 satellites but not too accurate (60ft range). Can anyone recommend a Radio to work with CM 7.02 for GPS. Im on Orange UK if this alters things. Currently using 26.04.02.17_M2 but im sure there will be a more reliable one out there. Thanks.
sorry if this is the wrong thread but i thought not to clutter the dev one with this.
1. I flashed randomblames rom and love it for the most part much improvements but my sound will randomely quite working causing me to reboot it. After reboot it works fine again.
2. My wifi gets stuck at obtaining ip address if i go to settings and enable it but if i turn it on from the homescreen it connects fine?
was just wandering if anyone has found a fix for this and was willing to share ill provide log cats if needed.
I made sure to do all wipes and flash the right gapps.
Thanks
It appears that the work is wonky. It is likely not something you can fix without getting into the code.
qualification said:
It appears that the work is wonky. It is likely not something you can fix without getting into the code.
Click to expand...
Click to collapse
You could try factory reset.
https://download.mokeedev.com/?device=zoom
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.
stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?
Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?
linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)
has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing
Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.
The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st
bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.
Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?