Database Users

[Q] Very Strange Issue with Custom Roms, please help

Hello everyone,
I've tried several different roms on my X5, and some weeks ago I had a strange issue.
I had just installed MIUI 2 or 3 days before, and decided to change back to CM7.
Since I've done that my phone randomly freezes and restarts, sometimes even in the recovery. I've tried all the custom roms and they ALL have this issue now. System boots and 2 to 5 min later it just freezes and reboots.
Also I've noted that when it's booting it takes significantly more time than any other x5 (i've turned 2 iDeos X5 on at the same time and this one takes 2 more minutes to boot).
Now for the really weird part...
If I restock it with the official 2.2 rom I have absolutely no issues at all! Phone runs perfect, never freezes and never breaks.
I've tried everything, multiple kernels, multiple roms, played around with processor speed, reformatted internal SD, repartioned, fixed the permissions.... I'm at a loss, I have no idea what else to try, and since my phone is perfect on stock rom I cant really send it back to "fix" because apparently nothing is broken...
Anyways, help would very much be appreciated
Thanks

Did you totally reset the phone?
So when you open recovery:
* wipe data/factory reset
* wipe cache partition
* Advanced -> Wipe Dalvik Cache

Yep, did that everytime.
Also, the phone sometimes freezes on installing in recovery rom. mid-installation it just reboots...

which recovery version are you using?

I've tried 4.0.1.5 by Geno and 5.0.2.6.
also I've tried the others, but recovery freezes mid-installation

This doesn't seem to have an easy solution.
Try to use the powerful logcat utility to investigate what causes the problem. You can run it from a command prompt window(pc) with command:
adb logcat
or
adb logcat > log.txt
if you want to create a log file to C drive instead of display the output to command prompt window. Post the logfile here.
Maybe then someone can find the issue and hopefully a solution to your problem

thx for the idea, i'll try it when I get home and post the log when I have it

Hello again, haven't had the change to do the log, but I just found out something really strange.
I have here 2 iDeos x5, one works one freezes. What I just found out is that the one that works shows 353mb of RAM, i've researched online and says that this is normal because the rest of the memory is allocated for the GPU.
What is strange is that the one that freezes shows 512mb of Ram, making me believe that it has no video memory hence freezing the phone when I try to do something graphics wise...
Anyone know if this ever happened? or ideas on how to fix it?
Thank you so much

n9005 big problem - all sensors stop working

Hi, I was using rooted n9005 with fahadali s5 custom rom. All working excellent.
Last evening I installed this program http://forum.xda-developers.com/gal...-galaxy-sensors-temperature-humidity-t2828815 (I am not sure is this problem). Installation was not normal (it said it is installed although was not)
After some time I noticed that auto rotation, temp sensors, proximity, auto brightness- nothing is working...
I reinstalled totally with odin, full wipe- still nothing...
Is phone killed or there is some solution, I do not know what to try else more then normal odin reinstall...
help...

ivanox1972 said:
Hi, I was using rooted n9005 with fahadali s5 custom rom. All working excellent.
Last evening I installed this program http://forum.xda-developers.com/gal...-galaxy-sensors-temperature-humidity-t2828815 (I am not sure is this problem). Installation was not normal (it said it is installed although was not)
After some time I noticed that auto rotation, temp sensors, proximity, auto brightness- nothing is working...
I reinstalled totally with odin, full wipe- still nothing...
Is phone killed or there is some solution, I do not know what to try else more then normal odin reinstall...
help...
Click to expand...
Click to collapse
Need your version of rom modem bootloader. Maximum info
No fonctionnally backup????

ivanox1972 said:
Hi, I was using rooted n9005 with fahadali s5 custom rom. All working excellent.
Last evening I installed this program http://forum.xda-developers.com/gal...-galaxy-sensors-temperature-humidity-t2828815 (I am not sure is this problem). Installation was not normal (it said it is installed although was not)
After some time I noticed that auto rotation, temp sensors, proximity, auto brightness- nothing is working...
I reinstalled totally with odin, full wipe- still nothing...
Is phone killed or there is some solution, I do not know what to try else more then normal odin reinstall...
help...
Click to expand...
Click to collapse
i replied in the app thread, you had a previous version installed right? it was installation or update? and, if i can suggest you, have you tried hw test for sensors? ( *#0*# )

Thanks, friends I was so busy last evening on job.
I am afraid it is hardware damage http://forum.xda-developers.com/showthread.php?t=2428732
I hope I will not be forced to change logic board (then almost no sense), I do NOT have warranty.
 @rayman95- I want make one last software attempt: please tell me what wipes/ formats to do and I will install your v13 slim.
 @ale32thebest- I do not say your app killed it. It is fact that I noticed errors just after unsuccessful try to install your app. My last hope is
that it locked some system calls (maybe I am wrong). Remember, I was using fahadali s5 rom and plays store sees my phone as s5. Do you have any suggestion to try something about that
thanks again.

in recovery go to monts and storage and format system, data, cache, data and /data media + factory reset and wipe cache+dalvik
then reboot recovery and flash a rom

@rayman95 First, how to back dpi to stock in your rom 13
NOT WORKING
I have different behaviour when try *#0*# last 2 days on different roms and kernels for sensor hub test
mostly I got
FAIL and MCU Firm Version : AT0113122000 | Bin Firm Version : AT0199999
few times I got (but again go to fail)
PASS and MCU Firm Version : AT0113122000 | Bin Firm Version : AT0199999
after last install (v13 and all formats) I even can not execute*#0*# (nothing happens)

ivanox1972 said:
@rayman95 First, how to back dpi to stock in your rom 13
NOT WORKING
I have different behaviour when try *#0*# last 2 days on different roms and kernels for sensor hub test
mostly I got
FAIL and MCU Firm Version : AT0113122000 | Bin Firm Version : AT0199999
few times I got (but again go to fail)
PASS and MCU Firm Version : AT0113122000 | Bin Firm Version : AT0199999
after last install (v13 and all formats) I even can not execute*#0*# (nothing happens)
Click to expand...
Click to collapse
It smell not good.... modify build.prop with root explorer and reboot

You think it is killed. Do I must change whole motherboard or maybe only som chip?
Sent from my SM-N9005 using XDA Premium 4 mobile app

Have the same problem.none of the sensor works tryed flashing still no use.just wanna know is this the problem of Cert file/qcn file or hardware?

Same problem!
I have the problem here. I've tryed everything: full wipe, custom rom, return to stock, downgrade, upgrade, etc.
I believe it's a hardware problem, I've bought both note 3 (mine and my wife's ) at the same time, but suddenly all sensors stop working. No root, nothing. I restore factory configuration many times, trying everything, including format and jump all account registration and don't installing nothing after format. Useless. Every time, after a few minutes, all sensors stop again.
---------- Post added at 10:01 AM ---------- Previous post was at 09:44 AM ----------
Only mine have the problem, my wife's working perfectly.
Both phones without root. I only rooted after The problem appear and try everything.

[Q&A] CyanogenMod 11.0 for Galaxy S4 LTE-A (GT-I9506)

Q&A for CyanogenMod 11.0 for Galaxy S4 LTE-A (GT-I9506)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

rtc clock not working properly
I cant change rtc clock time, I tried -w and -systohc, but nothing

I have 20141013 installed
---------- Post added at 05:58 PM ---------- Previous post was at 04:58 PM ----------
Dsp manager also not working. When I change sound compression it works, but at next song it sounds normal, like if it wasnt activated.

RTC can't be set directly on all newer Qualcomm devices.
DSP Manager most likely will be changed in CM. Anyway its DSP Manager bug and not ROMs itself. So if you want look through CM JIRA and if there no such bug report. You can report it.

solk2 said:
RTC can't be set directly on all newer Qualcomm devices.
DSP Manager most likely will be changed in CM. Anyway its DSP Manager bug and not ROMs itself. So if you want look through CM JIRA and if there no such bug report. You can report it.
Click to expand...
Click to collapse
Ok, I'll report that. I also noticed that recovery backups dont have rtc time. I did some research on the internet and I found something about newer qualcomm devices have recovery time kept in a file in /data/time. I could check this by reading the file time_log.1.
I did know this coz one day recovery bacckups were changed from 1970 to 2014, but with wrong date, so I think I would have to do a full wipe, format data and system and reinstall the rom, I think this could work. I also read someting in the changelog like rtc showing correct or something like this. Maybe same time is kept coz I dont do wipes while installing a new nightly. I really appreciate your work, I love your rom.

It is set to 2014 in kernel. That what Samsung made in KK opensourced kernel. And dont be surprised if it will be set to 2014 next year. Day, month isn't changed forcefully. So thats why you see such date in recovery. While in normal boot mode time_daemon starts and sets date and time. So wipe don't change anything. These RTC changes related to normal boot mode only. Particularly to time_daemon.
And yes, recoveries like Philz support setting correct date.

Ok, thanks

Is screenshot function working for you?
Sent from my A0001 using XDA Free mobile app

Dialer
First of all, thank you for a great ROM. The only problem I have, is when I am calling someone. The screen just goes black. Is there any trouble with the proximity sensor?
When I take the phone away from my ear the screen is supposed to light up right? Mine doesn't do that...
Thanks!
B

Hi, is screen mirroring working with CM11 nightlies?
Gesendet von meinem GT-I9506 mit Tapatalk

Hi!
I've been having an issue ever since I started using one of the first nightlies of this ROM: After a random time both my WIFI and phone signal icons turn orange and the proces Android OS starts draining my battery together with having no signal at all. Turning off WIFI at that point doesn't seem to work anymore but can be done by putting the phone in airplane modes. When I disable airplane modes and have my WIFI disabled I can browser through my phone network but Android OS still drains the battery. After I reboot everything is back to normal, as long as I leave my WIFI off.
- I've installed various nightlies and have had the same problem on all of them.
- I've done both a firmware update and a factory reset of my wireless router: Linksys E2000.
- I've both enabeld and disabled the Google Location reporting.
The problem still occurs and I can (with a random time) reproduce it. If anyone can help me debug or solve this problem that'd be great!

Assuming you have CWM in use as recovery, enter CWM. Do a format on /system from mounts menu. Then do a factory reset. Install latest nightly from SD and voila. That worked for me a while back.

TonskuDaigle said:
Assuming you have CWM in use as recovery, enter CWM. Do a format on /system from mounts menu. Then do a factory reset. Install latest nightly from SD and voila. That worked for me a while back.
Click to expand...
Click to collapse
I'll give this a try and let you know if it helped. Thanks!

TonskuDaigle said:
Assuming you have CWM in use as recovery, enter CWM. Do a format on /system from mounts menu. Then do a factory reset. Install latest nightly from SD and voila. That worked for me a while back.
Click to expand...
Click to collapse
That did not work. Just got the orange icons again.
I'm open to suggestions.

(It's not exactly a question, but since I have less than 10 posts)
Hi, I've installed the 20141106-NIGHTLY yesterday, everything was working great, I updated to the 20141107-NIGHTLY today and now I don't have notification sounds, vibration and light, most of the audio files I select under Notification Sound are detected as Unknown Ringtone, the battery notification light is not working too, I wiped and restored factor settings through recover and installed the 20141106-NIGHTLY but its still the same, changing the color of the light confirms that the notification light is still working but does not activate wen it should.
Nevermind, I cleaned all my setting and reconfigured, it solved the problem

Hi friends, how can we root this ROM?
Thanks

As other users in the thread about solks2 CM11, I am affected by thebrandom reboot thread. I thought it might help to let you know that those reboot often occur when using waze (while charging the phone in my car). Sorry to post here but I do not have the 10 required posts to reply in the right thread.
---------- Post added at 11:08 PM ---------- Previous post was at 11:02 PM ----------
Hello,
I also have a bug when trying to use google now via bluetooth (stuck on a screen with "initializing" written). I tried several workarounds from the internet but without success. Some suggest that a2dp should be disabled but I didn't find an option to disable it... Anyone managed to make google now work with bluetooth?

I am unable to record videos, anyone else having this issue?
EDIT: I just updated to the latest NIGHTLY, still unable to record videos, in a week or so I'll go on vacation for the holidays and I really need to record some videos, so if someone knows whats wrong please help me, thank you

Revolted5 said:
I am unable to record videos, anyone else having this issue?
EDIT: I just updated to the latest NIGHTLY, still unable to record videos, in a week or so I'll go on vacation for the holidays and I really need to record some videos, so if someone knows whats wrong please help me, thank you
Click to expand...
Click to collapse
I accidentally pushed some wrong commits. Will push fix today.

solk2 said:
I accidentally pushed some wrong commits. Will push fix today.
Click to expand...
Click to collapse
Thank you, you're a life saver
EDIT: Back from work and what do I get? An amazing update, I'm finally able to record videos, thank you very much solk2.

[Q&A] [ROM][5.0][CM12][F320][BETA][Dec 25]CyanogenMod 12 For G2 Korea-Variant

Q&A for [ROM][5.0][CM12][F320][BETA][Dec 25]CyanogenMod 12 For G2 Korea-Variant
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0][CM12][F320][BETA][Dec 25]CyanogenMod 12 For G2 Korea-Variant. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Can you make it compatible with EDGE and have more LTE bands, like B20 (800mhz)?
Thanks for your hard work.
best regards.

falafel666 said:
Can you make it compatible with EDGE and have more LTE bands, like B20 (800mhz)?
Thanks for your hard work.
best regards.
Click to expand...
Click to collapse
I dont know how to support Band20 or EDGE.

F320L
Hey i have the F320L and I'll be happy to report feedback for you if you need any
Just nothing too excessive as i cannot brick my G2

f320l Tester
I'm here for F320L tester

f320L
WIFI is not working and random reboots (f320L)

nguyenxuanthanh said:
WIFI is not working and random reboots (f320L)
Click to expand...
Click to collapse
Mine is functioning well so far. Re Flash the zip again and check after at least 3 day usage.

always restart when screen OFF on my F320S ..

支持你！
谢谢韩国的朋友

look guys
These solution is not mine i found it xD but i dont remember where sorry
-If wifi is mad with you
install "F320-Philz-touch_Cloudy" / Wipe dalvik cache then flash su-v2.40 (Do this step each time that the phone turns off ) maybe you will have to try this many times before it work
-If soft reboot when the screen is sleeping or when press power button
install "wake lock - PowerManager" set ~PARTIAL_WAKE_LOCK then go to options (in the nav bar) and set autostart on boot you can turn off notifications too
note: when you turn off the screen useing the power button it turns on back so you have to wait for until it shuts
2nd note: i'm just learning English (sorry)
And what about the rom?
Is there some news?

the Rom's download link is not work

okay i've found a fix fall pretty much every issue present in the f320k build. it's ridiculous and makes no sense, but it works for me and after working this out i haven't encountered a single problem apart from the battery drainage (i can probably get maybe 3 hours of light usuage, but im using some battery calibration app which i've never heard of but is supposed to work wonders) and the render kernel flashing but bringing all the old bugs back.
so basically what i did was factory reset the phone to jellybean (4.2.2 11E to be exact) via flash tool, attempted to install the omni lollipop rom. it worked, but no wifi, constant soft reboot, and no access to sd card within the rom. so i wiped that and gave this rom a try. for some reason, if you install any lollipop rom (so far ive tried ressurection remix and omni) straight after flashing JB, and then wipe that and run this rom, wifi works, no soft/hot reboots, and access to the sd card is present. it works vice-versa as well! flashing this rom, followed by Omni just fixes all the bugs (although the other two roms i tried do not have access to sd-card which is a bummer because all of my music and files are saved there).
after getting CM12 to boot and run fine, i created a backup of everything in TWRP in case something went wrong, which did happen.
while setting the device up, getting some apps installed, something triggered the wifi and hot reboot issue again. i wasn't sure what it was but there's no way i'd be cool with having to wipe the phone to stock jelly bean and redo this entire method to get the wifi fixed again, so i booted recovery, hit restore backup, and ONLY selected Modem in the things to restore. booted back up and its literally fixed the issues again. im still unsure of what's causing the bugs, but at least i know how to fix it and it only takes a minute and no data is lost at all.
i hope this helps anyone looking to get this rom working for them!
EDIT
i just unplugged the phone to go out and the wi-fi almost immediately cut off and the phone hot rebooted, so i think it might have something to do with that.
just tried recovering the Modem again and it's not working while flashing off or on charge.
just figured out that if you turn off wi-fi before unplugging device from charge it doesn't make phone hot reboot when pressing the lock button

Promlem
I have a few problems:
1) The phone sometimes restarts itself, so I noticed a reboot after you connect your phone to the charger (Render Kernel 10)
2) Quick battery drain.
With WiFi seems to be no problems

Fix
Hello. Can you take me link on WiFi Fix?

I was downloading

12.1…I can't use it. It can't boot…

320S ， booting ··booting···
---------- Post added at 04:28 AM ---------- Previous post was at 04:20 AM ----------
320S···My phone can not boot···maybe there are some errors，you can fix it·
---------- Post added at 04:36 AM ---------- Previous post was at 04:28 AM ----------
@parkjh0821 maybe there are something wrong in your rom，can't boot

Work great
This rom is stable. Work very great on my device. Haven't found any issue so far. Love it!!!:good::good::good:

Why network disk falters ah ah ah ah ah！！！！！！！

Download links are not working....
Please add mirror or update download links...
tried with VPN too... little urgent please

Home button not working at all (tried several fixes)

(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro

Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro

I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users

Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....

DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk

these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.

LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.

faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.

pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.

can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english

I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also

i've turned to stock i've updated to oxygen 3.0 bet and the button worked again

i think rooting installing twrp and installing different roms may be the cause of this issue

faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.

pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue

faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.

Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.

Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.

For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?

Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max