Related
Posting here as I'm a noob, and consequently can't post to the P.A page directly.
Since this 2.12 update i've been having wifi issues, like from where i am positioned normally I get 1 bar, but its a steady one bar, now i'm often finding i have no internet connection in the same places as i would before.
I did do a dirty flash, so that is most probably where all my problems are arising from, but i'm still really new to this, and any step i take, i worry and fret over.
had some tablet ui bugs after running games, along with all applications running twice when i open recent apps. I don't know where why or when this recent apps double bug occurs, but i've come across it a few times. I believe the tablet ui bug may be related to when i set bobclock (widget) to force, adjusted the size on restart, but then would encounter the icons dropped off bottom of screen, and everything just out of place, like its reverted to old ui.
oh another issue, which has been mentioned many times before, is inability to use google play store, i've fiddled with all the different dpi settings and size, nothing seems to work.
a clean wipe would include
backing up apps/data/p.a sys pref(?)
wiping
cleaning cache's
flashing the same 2.12 p.a zip i dirty flashed before
caches again? or gapps
any dumbing down would be greatly appreciated
Just to say version 2.13 is out. You might want to try updating in the first instance...
Sent from my Nexus 7 using xda premium
StrangerWeather said:
Just to say version 2.13 is out. You might want to try updating in the first instance...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
oh.. so there is. well i guess i can just skip over 2.12
if doing a dirty flash, when reinstalling gapps, do i have to have deleted them prior to this? or will it just replace/update the old files?
No, you don't need to. Just wipe both caches and install the new version and gapps.
Sent from my Nexus 7 using xda premium
StrangerWeather said:
Just to say version 2.13 is out. You might want to try updating in the first instance...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
oh cool.... is there a change log? or the question is, where would i see the change log?
Updating ... nevermind, i got what i need
we got any paranoid android avid fans here? running on the nux 7, ofc.
and by avid fan i mean, quite knowledgable, maybe able to help with some issues that may arise, being under 10 post count, there very little i can do it actually get any relevant help, ie to p.a
there is just so much information here, and being new to the android scene, consequently rooting roms and such as well. quite a bit is over my head but i'm doing my best! or well trying
`etcH said:
we got any paranoid android avid fans here? running on the nux 7, ofc.
and by avid fan i mean, quite knowledgable, maybe able to help with some issues that may arise, being under 10 post count, there very little i can do it actually get any relevant help, ie to p.a
there is just so much information here, and being new to the android scene, consequently rooting roms and such as well. quite a bit is over my head but i'm doing my best! or well trying
Click to expand...
Click to collapse
What sort of help are you looking for? I can try to answer any questions you might have, but your best bet is to search the paranoid android forum in the 'Original Development' section.
Sent from my Paranoid Nexus 7
RockNrolling said:
What sort of help are you looking for? I can try to answer any questions you might have, but your best bet is to search the paranoid android forum in the 'Original Development' section.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
i shall head over there and have a browse. will report back, need to get myself to 10posts so i can share bugs and such that i've encountered
Wouldn't Kernel be more specifically tied to WiFi issues? I don't know what PA does to the kernel they include, but if your up to it, you could try another kernel, like franco.Kernel
Oh. Yes. i've been on that page and have trolled through a few hundred pages.
I think I just need to become a bit more familiar with everything in regards to roms flashing and such, its not difficult but i fear i'm sure to do something in the wrong order,
yes i've read guides before you point me there.
gosh this 5 min wait timer for new people is getting on my nerves i didn't think i'd be wanting to reply so fast, but when you guys are on it like this, i can't turn down that kinda service!
another question while i wait for my timer to finish.
initially i flashed pa. 2.11 then gapps along with doing cache business.
since then i flashed 2.12, but not gapps, and consequently having issues with play store (cant open)
can i just go to flashing 2.13 when it finishes downloading and then flash gapps after?
is the latest gapps jb-20120726-signed?
espionage724 said:
Wouldn't Kernel be more specifically tied to WiFi issues? I don't know what PA does to the kernel they include, but if your up to it, you could try another kernel, like franco.Kernel
Click to expand...
Click to collapse
a kernel is one of these things i have no clue about.
i had a mac many years ago, and that got a kernel error, so my knowledge is limited to that its something root related, or there abouts anyway xd
How does one go about implementing one of these kernel do-hickeys?
on a side note, my wireless icon used to show grey and blue.
blue meant connected, grey, i'm not sure.. sometimes worked sometimes didn't
ever since going to 2.12 i've had nothing but grey, seem to have connection as i am downloading from goo, but as mentioned in initial post, connection is definately worse than it was before hand.. any ideas?
`etcH said:
can i just go to flashing 2.13 when it finishes downloading and then flash gapps after?
is the latest gapps jb-20120726-signed?
Click to expand...
Click to collapse
Sorry I took a while, I was in class. First, you always have to reflash gapps when you flash an update or a new ROM.
When you change to a different ROM (i.e. from Slim Bean to Paranoid) it's recommended to do a full wipe/factory reset before flashing the new ROM.
So the procedure for new ROMs is this. Factory reset, wipe cache, wipe dalvik cache, flash ROM, flash gapps, reboot.
The procedure for a ROM update is the same, you just omit the factory reset.
The latest gapps is gapps jb-20120810. You can download it in Goo manager.
`etcH said:
a kernel is one of these things i have no clue about.
i had a mac many years ago, and that got a kernel error, so my knowledge is limited to that its something root related, or there abouts anyway xd
How does one go about implementing one of these kernel do-hickeys?
Click to expand...
Click to collapse
A kernel is what governs your CPU clock speeds and voltage levels, as well as some other things. To flash a kernel, you don't have to wipe anything, just flash the zip file. Whenever you flash a new ROM, it changes your kernel to whatever is stock for that ROM. So if you use a custom kernel, you will have to reflash it.
Sent from my Paranoid Nexus 7
p.a 2.13
might anyone have any idea why after;
wiping both cashes and installing p.a 2.13 then gapps
my youtube comes up with an error from the beginning, unable to start, same goes for if you click it in the app drawer.
i fiddled about with dpi size force and such, but to no avail.
some settings transferred but not all, like the ui, after switching ui back to what i wanted, tab small/mid
i started to recieve trebuchet has stopped working, this keeps popping up but you can just leave it in the back ground and work around it..
wish i could post this in the correct thread..
ah well.
thinking of just re-flashing them both, will do whatever i did this previous time, see if the error returns.
edit: just finished the reflashing of both, no trebuchet error as expected, the youtube one is back, same as the previous flash.
i really don't think i've done anything wrong, but i haven't seen anyone else reporting this error..
edit edit: simple uninstall and reinstall for youtube and problem solved.
hope its an issue localised to me.
`etcH said:
might anyone have any idea why after;
wiping both cashes and installing p.a 2.13 then gapps
my youtube comes up with an error from the beginning, unable to start, same goes for if you click it in the app drawer.
i fiddled about with dpi size force and such, but to no avail.
some settings transferred but not all, like the ui, after switching ui back to what i wanted, tab small/mid
i started to recieve trebuchet has stopped working, this keeps popping up but you can just leave it in the back ground and work around it..
wish i could post this in the correct thread..
ah well.
thinking of just re-flashing them both, will do whatever i did this previous time, see if the error returns.
Click to expand...
Click to collapse
Yeah I would reflash. It could also be a corrupted download, try re-downloading paranoid android 2.13 and then flashing the newer zip to see if that fixes it.
Sent from my Paranoid Nexus 7
Latest Downloads
CM10.1 http://d-h.st/i3V
CM10.2 https://drive.google.com/file/d/0B1V_hMyelDz0Rm1nenlqT2JKWkE/edit?usp=sharing AS OF 21.11.2013
UNOFFICIAL FAQ FOR CM10.1/10.2
DOWNLOAD AND INSTALLATION
Q: Where’s the download?A: The initial FXP release had an incorrect kernel – you can download a working version of ROM from here. http://d-h.st/TPT
This ROM has since been updated a download can be located here. http://d-h.st/i3V
If you wish to try a CM10.2 (that’s Jelly Bean 4.3 – have Sony actually released a 4.3 ROM yet?) one can be downloaded from the link above.You can also download the correct version of GAPPS for Jelly Bean 4.3 here. http://brintaylor.info/Android/CM/gapps/
For the CM10.2 build you should use this link to report bugs. https://docs.google.com/forms/d/185s...9UINQ/viewform
Uberlaggydarwin plans to take a 'light touch' approach to support via XDA, so don't necessarily expect an answer to a query if you post in this thread
It seems like FXP have delayed releasing for our device for now, but information about CM builds that are being actively supported and developed can be found in this thread for now.
Q: How do I install?
A: You need an unlocked bootloader and an installed recovery. BACK UP your current ROM to your external SD card. Put the ROM and GAPPS on your external SD card. Boot into your recovery, do the necessary wipes, flash the ROM, flash GAPPS, reboot, victory. Disclaimer: if it breaks your phone, it’s your fault.
Q: Do I need to install the supplied kernel before installing the ROM?
A: No, unlike older xperia models CWM is able to flash both the kernel and the ROM at the same time. There is no need to use fastboot or flashtools to flash the kernel first, just a working recovery and an unlocked bootloader on your phone.
Q: Can I use another kernel instead?
A: No, for now only the supplied kernel will work.
Q: I’ve installed the ROM but can’t find the play store?
A: Immediately after installing the ROM you should install the 4.2.2 version of GAPPS (Google Apps) – this installs the play store and several other applications that Google regard as essential to the Android experience. This can be found here – http://goo.im/gapps/gapps-jb-20130812-signed.zip
Q: How do I update to the latest version of the ROM?
A: Once you’ve downloaded the latest version to your SD card, boot into recovery. No need to wipe your data, though you probably should wipe cache and dalvik cache (I don’t know whether this is done automatically as part of the installation but it can’t do any harm). You don’t need to install GAPPS again as this is a firmware update, not a new installation.
However if you’re moving between versions i.e. 10.1 to 10.2 you should definitely do a factory reset – the ROM may well work fine without a data wipe, but it may not and any problems might not be immediately noticeable (making bug tracking difficult). I would advise you NOT to report bugs if you’ve moved between android versions without a factory reset.
Q: When will they release a version that works on a locked bootloader?
A: Never. Some the features of the ROM simply won’t work very well/at all on a stock kernel. If you are rooted you can simulate some of the features with apps and mods though.
POST-INSTALLATION QUESTIONS
Q: I’ve installed the ROM – I can use Titanium Backup to reinstall all my apps right?
A: Yes and no. They may work fine, they might not – you are better off letting Google’s back up service restore all your apps. If you restore an app using Titanium or similar software and it’s buggy, there’s no point reporting it – re-install the app instead, perhaps even the ROM.
Q: 4G isn’t working – what do I do?
A: It’s not enabled by default on CM10.1 so you must do the following.
Go to the dialpad/phone.
Dial in the this number: *#*#4636#*#* (This will bring up "Phone info").
Tap WCDMA from under "Set preferred network type".
Select "LTE/GSM/CDMA auto (PRL)".
The 4G LTE network should now be activated.
Q:Where’s USB mass storage?
A: After ICS Google stopped including it in their Android builds, as such mass storage mode is not a feature that was kept by CM for Jelly Bean. Individual manufacturers do what they want though, which is why Sony, Samsung and others still have it. Skilled modders may be able to add to ROMS based on this development, I reckon they might be able to patch this one to include it too
Q: This ROM is buggy as hell and drains my battery – how do I let the developers know?
A: Logcat and/or a kernel log - or it didn’t happen for bugs.
Better battery stats for battery drain.
There are lots of guides out there showing you how to take logs and how to record battery stats.
Anecdote – I activated Google+ yesterday as I like the auto-photo upload feature but wakelock detector revealed it was killing my battery (I think it’s dodgy on stock too). The choice was the app or the ROM, I chose the ROM.
Q: After installation something random doesn’t work – what do I do?
A: Check the thread to see if other users have mentioned the issue and to see if the developer has posted a solution. Also, you’re on XDA, you’re an advanced user, you have unlocked your bootloader, thrown out your warranty and accepted the consequences. So please try to resolve the issue yourself. In general if you are having a problem and no one else is, it will be a problem with your phone/download/installation.
Phone - obviously a hardware fault can't be foreseen by the developer and have you unlocked your bootloader!
Download - Most downloads are fine. But I've flashed enough ROMS to know that sometimes a file gets corrupted and sometimes they say they are complete when they are not. Sometimes I've been careless and clicked on the wrong download, sometimes the website hosting the site is haveing a a bad day, sometimes the developer puts the download in the wrong place too The first things to check are the name and size of the file - if these tally you're probably fine to install. If you want to be extra cautious you can check the MD5 hash to see if your download matches. Sometimes the file gets corrupted on upload - nothing anyone can do about that...
Installation - (Please back up your orignal ROM). Typically you'll be installing this ROM using a recovery from another ROM/kernel/MOD - so if you have problems installing , it might be that you have a bad recovery.
The wipes really need to be done to ensure the smooth running of your phone, but as you've backed up, the 15 seconds you spend properly wiping should not be much of a chore.
If you're one of the first downloaders, I guess there is some merit in saying you couldn't install, but if it's been out for a while and there are loads of posts saying 'what a great ROM' there's little point posting 'won't install'. Describe exactly what you've done and someone might help.
Bear in mind there are apps/hardware that the developers of this ROM won’t have heard of/care about - so if something doesn’t work properly on your phone it could be for numerous reasons. Either way, this may be something you have to live with. Alternatively, if the app is essential to you, you’ll have to return to a backup.
Remember this ROM is in development, there are no promises of perfection and no one is forcing you to use it. However, the right kind of feedback is always welcomed by the developers and may be acted on – the wrong kind will often be ignored.
Q: What does a perfect bug report look like?
A: Go here. http://forum.xda-developers.com/showpost.php?p=46935640&postcount=313
Q: What are the known bugs?
A: FM radio doesn’t work.
A: Attempts to offline charge cause the phone to boot.
A: 4G activation is not remembered between boots for CM10.1.
A: For 10.2 there is a known battery drain issue related to WiFi. See the solution here. http://forum.xda-developers.com/showpost.php?p=46923723&postcount=301
The following issues have been reported by some users, but others say it doesn’t affect them. They are regarded as hardware issues – anecdotal ‘me too’ posts will be ignored. However, supply a log and your phone’s date of manufacture and the developer may look into it (this might help you prove that your phone is faulty, so it’s a worthwhile exercise).
Erratic touch screen response.
Reading external SD Card in recovery and in use.
As others have said this is possibly the most stable first CM build they’ve encountered and I agree – it’s definitely suitable for daily use. I've been using it from release and haven't had a single reboot/app crash or freeze.
http://uploaded.net/f/q3au96
CM 10.1 released for huashan
Its cm for our phone right?!??
Sent from my ZTE Blade G using xda app-developers app
Thanks for sharing. I saw yesterday in the changelog that both 10.1 and 10.2 where announced on FXP 242 (10.1 in beta and 10.2 in alpha), but I can't find the 10.2 download anywhere.
Maybe they don't publish public download links for alpha versions ?
Parkside said:
...no announcements, I can't keep it to myself. You'd do the same right?
Click to expand...
Click to collapse
Its safe to download huanshan cm file for our phone.(know that huanshan is code name for our phone)????
Sent from my ZTE Blade G using xda app-developers app
Yes take a look
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Wooohooooo im so happy i cant wait to test itThanks to FXP team !
When i flash it im gonna make review wohoooooo
Sent from my ZTE Blade G using xda app-developers app
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Can you tell me what file to download??
Sent from my ZTE Blade G using xda app-developers app
Download this :- http://uploaded.net/file/7ntq0zp6/from/q3au96
Flashed and booted. Its nice. But some screen flickering while scrolling. Like in settings etc etc. But that can resolve with enable the " Disable Hardware Overlay" option from Developer Settings
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Are mirrors allowed? Can somebody mirror this file? Im sorry but uploaded has failed me several times already...
mmm273 said:
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Click to expand...
Click to collapse
Now only i flashed this. I dont have any apps installed. So performance is awsom now. Free RAM is 509 and used 333
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Screen Flicker
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
I have the flickering too ! And the phone often soft freezes. Seems like the app isnt updated anymore on screen. It can also be just the keyboard for example. Hiting recent tasks unfreezes it but systemui sometimes freezes until reboot.
Sent from my C5303 using xda app-developers app
uberlaggydarwin said:
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
Click to expand...
Click to collapse
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
mmm273 said:
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Click to expand...
Click to collapse
I'd like to see a screen of that score. Seems a bit too high. Sure you have the SP ?
You're using V4 ofcourse, my bad.
Bootloader
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Hey, Make a backup, you need an unlocked bootloader for this. Then wipe all cache and data etc. then flash the rom on your phone
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Well asfaik CM requires a custom kernel which can only be installed on a phone with unlocked bootloader. Hope ive helped.
Rajeev said:
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
Click to expand...
Click to collapse
LOG"S OR IT DIDN"T HAPPEN . I'm serious.
I'm downloading this release to test but I can't help much if you don't provide logs.
Are you sure its not auto-brightness being turned on as auto-brightness doesn't work very well in stock so the changes are probably more noticeable.
Reboots work perfectly fine for me..
On the recent test builds I haven't had a reboot issue but as you know the kernel is temporary so I'll redo it when 4.3 comes out....
WE NEED LOGS.
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
ilum90 said:
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
Click to expand...
Click to collapse
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Rohit02 said:
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Click to expand...
Click to collapse
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
ilum90 said:
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
Click to expand...
Click to collapse
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Rohit02 said:
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Click to expand...
Click to collapse
At first, i installed another rom like paranoid 4.45 20140729 and it didnt work, it got worse.
When i would make a call, the screen would turn off and couldnt get to back on and it does but not even for a sec so it kept remaining wit a screen off but the call was still going.
The next step i tried AOSP build 12 rom, with same kernel and it also didnt work. Same as before when i had CM 11.
I just installed CM 11 rom with hellscore b55 CM anykernel and it does the same thing.
My only next step based on your opinion is trying AOSP rom with hellscore kernel (not the CM version).
Is there anything else i can try if the aosp wit hellscore kernel doesnt work?
could you indicate me where to get the stock kit kat because i see versions of them and im not sure if their stock or not.
is it also possible to use stock with hellscore kernel?
Much appreciate for all the help you have given me so far.
Same problem with simple AOSP with hellscore b55 anykernel.
Any other ideas?
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
RolF2 said:
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
Click to expand...
Click to collapse
I can't believe it! After all this time, blaming on the software so hard and for the last resort I actually did dissembled my N4 to check the sensors and everything but did nothing. But dude, you solved the mystery! Everything is working perfectly now. I can't appreciate how thankful I am. Many thanks
Hi all,
I have a Galaxy Note 3 with the latest Resurrection Remix ROM installed. Installed the ROM with a clean flash and everything was working fine (I thought...). Now, every time apps crash. For instance: when I want to upload a video on Instagram, everything works fine but when I hit the ''cut'' button to cut the video, it crashes. Every time at the exact same moment. Same goes for Snapchat when I want to upload a photo or video, it immediately crashes. I have installed the ROM multiple times, I have reinstalled the apps, but nothing works. I'm not using exessive amounts of RAM, so that's not the problem either. I don't see other people with the same ROM having these problems, so I really don't know where to look for a solution. Hoping you guys could provide me with an answer!
Edit: also worth noticing: my phone automatically restarts at least 3 times a day when I'm in the middle of something (like writing a message in WhatsApp).. Never found a solution for that either!
Thanks in advance!
Wipe cache and dalvik?
Ma3lish said:
Hi all,
I have a Galaxy Note 3 with the latest Resurrection Remix ROM installed. Installed the ROM with a clean flash and everything was working fine (I thought...). Now, every time apps crash. For instance: when I want to upload a video on Instagram, everything works fine but when I hit the ''cut'' button to cut the video, it crashes. Every time at the exact same moment. Same goes for Snapchat when I want to upload a photo or video, it immediately crashes. I have installed the ROM multiple times, I have reinstalled the apps, but nothing works. I'm not using exessive amounts of RAM, so that's not the problem either. I don't see other people with the same ROM having these problems, so I really don't know where to look for a solution. Hoping you guys could provide me with an answer!
Edit: also worth noticing: my phone automatically restarts at least 3 times a day when I'm in the middle of something (like writing a message in WhatsApp).. Never found a solution for that either!
Thanks in advance!
Click to expand...
Click to collapse
Wipe cache and dalvik?
trying a different Kernel?
checked with the ROM Dev in ROM Thread?
nijom said:
Wipe cache and dalvik?
trying a different Kernel?
checked with the ROM Dev in ROM Thread?
Click to expand...
Click to collapse
I wiped cache and dalvik before installing. I have also checked in de DEV thread, but there I see no one with the same issues. I have not tried a different Kernel, how can I do that?
Ma3lish said:
I wiped cache and dalvik before installing. I have also checked in de DEV thread, but there I see no one with the same issues. I have not tried a different Kernel, how can I do that?
Click to expand...
Click to collapse
You can find Kernel threads also in Development Forum. Make sure to flash Kernel Cleaner zip file before changing back to stock Kernel. You can flash Kernel zips via recovery. (search the Kernel Thread)
nijom said:
You can find Kernel threads also in Development Forum. Make sure to flash Kernel Cleaner zip file before changing back to stock Kernel. You can flash Kernel zips via recovery. (search the Kernel Thread)
Click to expand...
Click to collapse
Okay thank you will try that! Do I need a specific Kernel which fits my ROM? (sorry for noob questions lol)
Ma3lish said:
Okay thank you will try that! Do I need a specific Kernel which fits my ROM? (sorry for noob questions lol)
Click to expand...
Click to collapse
There are Kernels for 5.0 TW, CM and also 5.1.1 ROMs. Download the proper one.
Hello,
first of all, hey, I'm new to this community.
Second of all, I want to explain my situation here:
Oke so what's up, after updating Cyanogenmod from cm-12.1-20151226-NIGHTLY-jfltexx to any later nightlies it works well, well, when I don't have my google apps installen (OpenGapps pico). I tried multiple ways of installing, full reset, normal update, full reset and Gapps 5.0 and then update them, normal update and opengapps update.
My ROM does for some way not like Opengapps, my google services keep crashing after I installed them as soon as I start up my phone.
So my question is: "Do you guys know if this is a known bug/problem and/or do you know a problem fix for this?".
I hope I explained my problem well, if I did not just reply with what you need to know and I will better myself!
Kind regards, Joost (jiji32112)
jiji32112 said:
Hello,
first of all, hey, I'm new to this community.
Second of all, I want to explain my situation here:
Oke so what's up, after updating Cyanogenmod from cm-12.1-20151226-NIGHTLY-jfltexx to any later nightlies it works well, well, when I don't have my google apps installen (OpenGapps pico). I tried multiple ways of installing, full reset, normal update, full reset and Gapps 5.0 and then update them, normal update and opengapps update.
My ROM does for some way not like Opengapps, my google services keep crashing after I installed them as soon as I start up my phone.
So my question is: "Do you guys know if this is a known bug/problem and/or do you know a problem fix for this?".
I hope I explained my problem well, if I did not just reply with what you need to know and I will better myself!
Kind regards, Joost (jiji32112)
Click to expand...
Click to collapse
The problem here that you installing the wrong GApps, You should install 5.1 GApps not 5.0 GApps.
shark jungle said:
The problem here that you installing the wrong GApps, You should install 5.1 GApps not 5.0 GApps.
Click to expand...
Click to collapse
Hey,
Pardon me for saying the wrong version but I used 5.1, afterwards I use 6.0 ofcourse.
So, anybody else has an idea of what is happening?
Kind regards, Joost (jiji32112)
Opengapps are updated daily. Some packages work and others don't. It's pretty much hit and miss.
Download another package from a different day. And If you find one that works, stick with it.
Alternatively, you could try A-gapps. It's even smaller than the pico gapps and it also has google play services battery optimization. Opengapps don't have it.
jiji32112 said:
Hey,
Pardon me for saying the wrong version but I used 5.1, afterwards I use 6.0 ofcourse.
So, anybody else has an idea of what is happening?
Kind regards, Joost (jiji32112)
Click to expand...
Click to collapse
As GDreaper said: Opengapps is bugged. Sometimes it works, sometimes it won't.