i just rooted and install rom i00 true sense 3 rom it' s work fine .but I need to calibrate g-sensor . after I press calibrated button seem to be work and the end of calibration is showing calibration aborted. please help me.
maow59 said:
i just rooted and install rom i00 true sense 3 rom it' s work fine .but I need to calibrate g-sensor . after I press calibrated button seem to be work and the end of calibration is showing calibration aborted. please help me.
Click to expand...
Click to collapse
does anyone can help?
maow59 said:
does anyone can help?
Click to expand...
Click to collapse
I flashed the rom and the g-sensor is ok for me. But there is the same problem with my phone it starts to calibrate and says "aborted" ?
Most likely due to the ROM originally being for a different phone entirely. Likely to be not very high on any DEVs priority list either, however, let i00 know and he might get round to trying to fix it.
I just inform to Kris now and this problem list in issued thread already.
Hope Kris will be fix this issued soon.
Related
I tried flashing diff roms with full wipe. No luck
Is this hardware fault u think? Where is the sendor located?
Download this app, called Sensor View:
https://play.google.com/store/apps/details?id=com.bytemystery.sensorview&hl=ro
and switch to accelerometer, orientation, and gyro, and see if it shows anything when you move the device. If it doesn't, it probably is a hardware problem.
Had this once
Hi,
I also had this once with Android Revolution HD (4 or earlier..) Programs like the suggested showed absolutely no reaction from the gyroscope so I really thought I ruined something.
Wiped everything and flashed a stock rom, that helped at last.
It might however actually be the gyroscop defect...
sandulea said:
Download this app, called Sensor View:
https://play.google.com/store/apps/details?id=com.bytemystery.sensorview&hl=ro
and switch to accelerometer, orientation, and gyro, and see if it shows anything when you move the device. If it doesn't, it probably is a hardware problem.
Click to expand...
Click to collapse
I tried the app. The values didnt change.
My gyroscope isnt working either btw tried few games and can steer to left and right.
Im gonna do a stock flash and if it still dont work, deliver it in for warranty fix.
I'll let u know if its a software issue.
I am running stock rom and I don't know if the Note 2 is supposed to work upside down (I use it like that all the time when I am charging it in portrait mode) but it doesn't so I installed Ultimate Rotation Control (a hold over from the stock nexus 7 rom days when it wouldn't autorotate). It should work in your situation, try it and let us know.
Same thing happened to me but i found out it was kernel related, im on omega rom and im now using neak, all ok now.
Sent from my GT-N7100 using XDA Premium HD app
I flashed omega 7 and it worked. but then i flashed redpill kernel and it didnt work again
good thing it aint the hardware fault!
toofank said:
I flashed omega 7 and it worked. but then i flashed redpill kernel and it didnt work again
good thing it aint the hardware fault!
Click to expand...
Click to collapse
that's good
Ok here's the dilema..
perseus and redpill give the autorotation/gyroscope problem. while Neak, Notecore and other kernels that dont have fatex support dont give that issue!
The sad part is that I MUST have fatex support so i can swap my ext sd with int sd.
any other kernels besid eredpil & persues that lets me do that??
also .. the main q is... why did this suddenly start happening? I used those kernels before without any gryo/rotation issues.
ok... flashed a few times and now its working as it did before.
running wanam rom + perseus and ext/int sd swap!
toofank said:
I tried flashing diff roms with full wipe. No luck
Is this hardware fault u think? Where is the sendor located?
Click to expand...
Click to collapse
Had the same issue...i was swapping between cm 10.1 and jb leak and suddenly autorotation was all over the place(not coming back to portrait) even after reflashing clean instal(cm10.1 or jb leak)...for me the fix was kind off lucky...disabled(unselect) calibration in cm10.1 under system settings/system/calibration and it all came back to normal...
may come handy for others too
Hello. I have a problem whit my galaxy nexus maguro device. When i install something different then stock google images 4.1.2 or stable "cm-10.0.0-maguro.zip" i have a problem whit screen when i'm during my phone call. Every time i install something different for exp: stock 4.2.1 or 4.2.2 or every custom rom (xylon,pa,xenon,slim bean etc. etc. ) and when i starting a conversation my screen of course is off but when i geting off my phone from ear screeen whant to turn on and it is almost every single time i having a phone call.I was trying every basband,rom, kernel and always i the same result -screen issue. Of corse when i'm on 4.1.2 or cm-10.0.0-maguro.zip there is no problem. so my question is WTF ? Please try to forgive me for my english - this is not my thing
?
I've tried auto-brightness off and on etc. there is no solution .... fuc.... any sugestion ?
?
ryza666 said:
I've tried auto-brightness off and on etc. there is no solution .... fuc.... any sugestion ?
Click to expand...
Click to collapse
And i've changed animation window to 0.5 and it's not working. PLS help MEEEEEEEEE !
Ok so from what i understand you mean that the screen doesn't turn on after you hang-up a call? or during a call? if it's during a call make sure you aren't covering the sensor on the right side of the ear piece .. also if thats not that problem it might be highly possible that your proximity sensor is broken :-S
irizwan said:
Ok so from what i understand you mean that the screen doesn't turn on after you hang-up a call? or during a call? if it's during a call make sure you aren't covering the sensor on the right side of the ear piece .. also if thats not that problem it might be highly possible that your proximity sensor is broken :-S
Click to expand...
Click to collapse
So if my proximity sensor is broken why i don't have a problem whit this on CM 10 ( stable realese ). Screen doesn't turn on if the person from the other side hang-up me first. An update of my screen problem : i'm on Paradigm 3.1 right now and diamond044 kernel from AK and so far my screen doing great ( the autoBrightness is turn on ). Xylon, Xenon HD,Puity etc - every kernel, clean install bla bla bla thre is a screen issue... I don't get it ?
ryza666 said:
So if my proximity sensor is broken why i don't have a problem whit this on CM 10 ( stable realese ). Screen doesn't turn on if the person from the other side hang-up me first. An update of my screen problem : i'm on Paradigm 3.1 right now and diamond044 kernel from AK and so far my screen doing great ( the autoBrightness is turn on ). Xylon, Xenon HD,Puity etc - every kernel, clean install bla bla bla thre is a screen issue... I don't get it ?
Click to expand...
Click to collapse
And sorry for your "quick" response:angel:
Are you using stock dialer?
Try: Upgrade to 4.2.2.
And paste a logcat (people need to start doing this before opening a thread)
Sent from my Nexus
bk201doesntexist said:
Are you using stock dialer?
Try: Upgrade to 4.2.2.
And paste a logcat (people need to start doing this before opening a thread)
Sent from my Nexus
Click to expand...
Click to collapse
I always use stock dialer. Before I've done a lot of up pure upgrade to stock 4.2.2 and downgrades to 4.1.2. and I've installed every coustom rom on stock 4.2.2 or 4.2.1 and result is the same. Like as I said only Cm 10 stable i out of screen issue. I've installed yesterday CM 10.1 M3 and try some thing with another dialer from market and there is a chance of success. And what about catlog - i will try but as you see I don't have a lot of time to solve my problem.... work work work. I'm grateful for your interest of my case
ryza666 said:
I always use stock dialer. Before I've done a lot of up pure upgrade to stock 4.2.2 and downgrades to 4.1.2. and I've installed every coustom rom on stock 4.2.2 or 4.2.1 and result is the same. Like as I said only Cm 10 stable i out of screen issue. I've installed yesterday CM 10.1 M3 and try some thing with another dialer from market and there is a chance of success. And what about catlog - i will try but as you see I don't have a lot of time to solve my problem.... work work work. I'm grateful for your interest of my case
Click to expand...
Click to collapse
Is your screen protector covering the proximity sensors? My screen protecter once covered them and I had the same issues but when i removed it, it worked again
If you are using a custom kernel, try up-ing you min screen off setting in trickster mod.
I used to get a lot of these problems. But not any more since I am on Diamond series of AK kernel.
I am using these settings: http://forum.xda-developers.com/showpost.php?p=38030897
Hi all, I'm just wondering if there are others that have similar issue than mine?
The problem is that after updating my phone to CM13 20160922 version and any newer version, the touch screen would not work anymore on the ROM. Touch screen would still work in recovery.
I've tried to clean wipe before installation of ROM and the same problem persists.
If it helps, when I tried to install a new kernel (Xcelerate one) on the working ROM, the touch screen would also break.
Any help would be appreciated.
Do a clean install (by wiping cache, system, data) if you havent, and see if it helps. Can only suggest to take full logs (incl dmesg, and lastkmsg) and fetch it to fefifofum on the respective thread. Is the behaviour consistent or random? I face it randomly but I guess mine is a hardware fault.
The behavior is consistent. It always breaks the touch screen on the newer roms. I'll try to fetch the logs and maybe it would help. Thanks.
Anyone can help me with getting logs without a touch screen? ADB can't seem to connect and the device is unauthorized. Thanks for any help.
Well you are not the only one. Its all about drivers in kernel. I changed my digitizer and then with 6 or 7 touchscreen does not work although all fine in TWRP 3.0.2 Someone has to port those drivers to new kernel used in Android 6. i have little knowledge about it but i will try to fix it and if it works i will post it here-
mobaddict said:
updating my phone to CM13 20160922 version and any newer version,
Click to expand...
Click to collapse
wait do you mean it was working on cm13 before those versions ???
bauuuuu said:
wait do you mean it was working on cm13 before those versions ???
Click to expand...
Click to collapse
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
... i will check
mobaddict said:
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
Click to expand...
Click to collapse
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
bauuuuu said:
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
Click to expand...
Click to collapse
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
mobaddict said:
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
Click to expand...
Click to collapse
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
bauuuuu said:
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
Click to expand...
Click to collapse
Thank you. I'll try to check if this would work.
mobaddict said:
Thank you. I'll try to check if this would work.
Click to expand...
Click to collapse
I'll just wait for a kernel build since I don't know how to do this hehe
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
debasarkar said:
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
Click to expand...
Click to collapse
I think we just need to wait for a new build of the kernel and test if this solves our problem. I'm also waiting for a kernel build and will test it out if this would fix the issue. :good:
I don't know if the commit that was made by @bauuuuu was used in the new build of CM14.1 but the latest rom still has the touch screen issue. The new TWRP 3.0.2-1 is now also facing the same problem.
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
mobaddict said:
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
Click to expand...
Click to collapse
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
bauuuuu said:
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
Click to expand...
Click to collapse
Oh, wow! Hope that the 100Hz does the trick for my touchscreen and for others that are facing the same issue as me. Thank you for posting that. :good:
TWRP test build
Here is a test build for those with touchscreen issues. Please let me know if it works:
https://www.androidfilehost.com/?fid=313042859668276642
Hello , everyone
First i wanna thank this guy for posting this ROM
The ROM was installed correctly and worked fine a long time even though , there're some mini issues showen like (system has been stopped / Mail has been stopped) I've made some settings to get ride of Mail has been stopped (Disable it and Delete it after )
But when i've kept my phone on charging in the night and woke up for checking it , it's only some secondes before the system shutdown without reason without even showing something else and this reboot loop continue and i can't use my phone anymore Please help me out ..
did you manage to solve it?
tberma said:
Hello , everyone
First i wanna thank this guy for posting this ROM
The ROM was installed correctly and worked fine a long time even though , there're some mini issues showen like (system has been stopped / Mail has been stopped) I've made some settings to get ride of Mail has been stopped (Disable it and Delete it after )
But when i've kept my phone on charging in the night and woke up for checking it , it's only some secondes before the system shutdown without reason without even showing something else and this reboot loop continue and i can't use my phone anymore Please help me out ..
Click to expand...
Click to collapse
I'm facing the same issue and I dont know what to do! I tried several ROMs, and problem persists!
ggonmar said:
I'm facing the same issue and I dont know what to do! I tried several ROMs, and problem persists!
Click to expand...
Click to collapse
The problem is because of a bug between the upgraded android app and CM based ROMs.
Since the problem hasn't been solved on either part. people are experiencing this on many other devices that are running CM based ROMs. Use any other ROM and you should be fine.
I too faced this problem, when I had marshmallow. Then I switched to Android KitKat ( This one https://forum.xda-developers.com/showthread.php?t=2627818 to be specific )and my phone is perfect now. Maybe galaxy grand cant handle ROMs above KitKat. I think any KitKat variant will be fine.
kundank191 said:
I too faced this problem, when I had marshmallow. Then I switched to Android KitKat ( This one https://forum.xda-developers.com/showthread.php?t=2627818 to be specific )and my phone is perfect now. Maybe galaxy grand cant handle ROMs above KitKat. I think any KitKat variant will be fine.
Click to expand...
Click to collapse
Aosp 6.0 Works fine, No bootloop like on other CM based ROMs, it's CM compatibility issue here is the link for others who want to stick to Marshmallow, this one is very stable for daily driver.
I think I have an answer. The culprit is your battery. Try a new battery and see if the problem exists. With the passage of time, the battery degrades and is no longer able to support demanding ROMs and thus the mobile shuts down.
how to fix? , i bought this phone for cheap price is this a software problem or a hardware issue? if i root my device and give it a new custom rom will it fix the problems? pls i will appreciate any opinion given
Deathpact231 said:
how to fix? , i bought this phone for cheap price is this a software problem or a hardware issue? if i root my device and give it a new custom rom will it fix the problems? pls i will appreciate any opinion given
Click to expand...
Click to collapse
Hi, fortunately it's a software issue, all you would want to do is to just Unlock the phone's bootloader, flash TWRP recovery, root the stock rom with magisk and finally install a good custom rom such as Free Roms or Infinity Os, all of which would remover this issue permanently....
Clifton1933 said:
Hi, fortunately it's a software issue, all you would want to do is to just Unlock the phone's bootloader, flash TWRP recovery, root the stock rom with magisk and finally install a good custom rom such as Free Roms or Infinity Os, all of which would remover this issue permanently....
Click to expand...
Click to collapse
thanks for the reply , i have forgot to mention that also the mic doesnt work , and when i plug in a headset only the right side works so i suspect that this is a hardware problem specifically the charging board i have ordered a new one and plan to change it i hope this will fix my problem , cheers!
Deathpact231 said:
thanks for the reply , i have forgot to mention that also the mic doesnt work , and when i plug in a headset only the right side works so i suspect that this is a hardware problem specifically the charging board i have ordered a new one and plan to change it i hope this will fix my problem , cheers!
Click to expand...
Click to collapse
My pleasure! Yeah try that out n hope it works, as for me, I've switched from the A50 to the OnePlus 6 n man, this phone is way better n awesome in every way, just loving it n the developer support ....