Mako Android L B4 causing problems? - Nexus 4 Q&A, Help & Troubleshooting

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

Related

gen2 and reflash to cyanogenmod 7,0 ??

so, ive did the upgrade to gen2, and installed 7.0.3 cyanogenmod..
BUT the resets when i charge it, is annoying and i belive that wasnt an issue at 7.0.0? or was it??
can i reflash it back to the 7.0 now? or what about the 7.0.2? is that any better??
also- my phone is gettin slow... i really dont know why..
got like 4 giga available space at sd, and all apps are moved to sd..
Use the latest nightly (N100) and full wipe and flash.
The bug is fixed in later releases after stable.
oki. i will dl and flash it now..
is there gonna be a new cyanogenmod stable flash soon?
ps- many thanks!!
also--- what IS nightly builds anyway?
are they all different or are they finished roms?, but lets say 99 has the reset error and the 100 is the one that fixes it..
is the 87 or whatever build pre100 not as good as the latest 100 in today case?
Not that I know of.
They're usually experimental, but for the Blade they're probably as stable as Froyo ROM's.
They're like all the latest changes the CM team have made to the ROM.
Possibly, however N100 could have another bug instead (although this is not the case).
Refer to this for more info: http://wiki.modaco.com/index.php/ZTE_Blade_CyanogenMod
a new bug.. i like having an gps, so i use Sygic, and when i turn on Sygig, it makes the phone reboots..
so ill guess... hmm.. reset when charging or having a gps...??
any fix for this one?
EDIT...
just started up a compassapp that uses gps as well, found my location, went back in and started Sygic and starts up fine and no reboot..
lol... some things are random..
CM7 should reboot once when using GPS and then be fine.
many thanks!!
all good today..

CM9 samsungs i9000 problems

I have updated with nightly cm9 for samsung s i900, all day long, and I have time to see some lags:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
I have downgrade to XXJVU, and problems was foxed, for the moment
But when I try to got back to cm9 nightly 19.06.12, the problem appeared again.
The solution was to come back to xxjvu, gone to dark night and after that come back to cm9..very hard problem. I was very afraid.
Have someone sow other problems? Because I want the developer to know all this thins to improve its!
The best!
mishulake said:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
!
Click to expand...
Click to collapse
#1 is something i haven't experienced at all, in fact wifi became faster and better with CM9
#2 happened to me a lot when I ran CM9 with their stock kernel, i use a Semaphore kernel now, and the phone works p much flawlessly. Reboots very rarely while I listen to music (Apollo & Spotify)alltid
#3 is just odd, going from stock 2.3.5 my phone sped up like crazy..
#4 what the hell
Sent from my GT-I9000 using xda premium
Samsung ICS yelow
Hr Kristian said:
#1 is something i haven't experienced at all, in fact wifi became faster and better with CM9
#2 happened to me a lot when I ran CM9 with their stock kernel, i use a Semaphore kernel now, and the phone works p much flawlessly. Reboots very rarely while I listen to music (Apollo & Spotify)alltid
#3 is just odd, going from stock 2.3.5 my phone sped up like crazy..
#4 what the hell
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I can I do? I cant all ICS that I tried to install made the same, the screen became in yelow shades, darky, and big cotrast, imediately after instaling, with the animation!!!
Any advice will be apreciated!
when you have flashed, have you did all the Wipe ?
Before your flashing, did you a proper base ? (GB 2.3.6 for exmaple ?)
for the color of the lockscreen, i have the same 'problem' but that persist during 1s, so i don't care
mishulake said:
I have updated with nightly cm9 for samsung s i900, all day long, and I have time to see some lags:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
I have downgrade to XXJVU, and problems was foxed, for the moment
But when I try to got back to cm9 nightly 19.06.12, the problem appeared again.
The solution was to come back to xxjvu, gone to dark night and after that come back to cm9..very hard problem. I was very afraid.
Have someone sow other problems? Because I want the developer to know all this thins to improve its!
The best!
Click to expand...
Click to collapse
1. Yeap, I have the same problem with the signal but still I can surf with it in any place at my home + the wifi itself is better (My surfing is smoother and download speed is max)
2. Never happened to me (yet), which kernel are you using? I'm using Semaphore I think it's the best
4. WTF? never heard about this, I didn't update my Rom for two weeks so maybe that's why I don't have this problem, try to go back to 2.3.X Reroot & Semaphore kernel and try again installing that Rom
CM9 color screen problem
mishulake said:
I have updated with nightly cm9 for samsung s i900, all day long, and I have time to see some lags:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
I have downgrade to XXJVU, and problems was foxed, for the moment
But when I try to got back to cm9 nightly 19.06.12, the problem appeared again.
The solution was to come back to xxjvu, gone to dark night and after that come back to cm9..very hard problem. I was very afraid.
Have someone sow other problems? Because I want the developer to know all this thins to improve its!
The best!
Click to expand...
Click to collapse
After first restart, my scree become yellow. I want to put a video but the system cant give access. Right now I'm in cm7, and everything works, fine. No one know what is happen, because I want to install CM9, please!
REefault CM9 samsungs i9000 problems
Can say I have only experienced the restart issue, frequently, sometimes while the phone is sitting idle, and sometimes during calls, while on stock. Currently on July 02 CM9 and to solve the restart/reboot issue, I have been using MNICS kernel, and as of yesterday, the new MACKAY kernel. Hope this helps you with one of your problems. Also use jvu modem.
mishulake said:
Right now I'm in cm7, and everything works, fine. No one know what is happen, because I want to install CM9, please!
Click to expand...
Click to collapse
Stay on CM7 (are you on the latest CM7 build or an old one?) and retry this:
- First please, download the latest available nightly for CM9 link here!
- Then follow the step written by devs:
The thread for CM9 with instructions to flash is here: link !
- Upgrading from CM7?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Click to expand...
Click to collapse
Be sure to do all this step and flash the latest nightly.
I already had to update from CM7 to CM9 twice and, each time, I got it working without problem. So please, try again, make sure to follow the steps and tell us if you're experiencing the same troubles again.
GuillaumeVDH said:
Stay on CM7 (are you on the latest CM7 build or an old one?) and retry this:
- First please, download the latest available nightly for CM9 link here!
- Then follow the step written by devs:
The thread for CM9 with instructions to flash is here: link !
Be sure to do all this step and flash the latest nightly.
I already had to update from CM7 to CM9 twice and, each time, I got it working without problem. So please, try again, make sure to follow the steps and tell us if you're experiencing the same troubles again.
Click to expand...
Click to collapse
Hi guys, I have the exact same issue.
updated from MIUI to CM9 and got yellow screen. Tried different ROMs and Kernel but no solution. Eventually I went back to CM7 and yellow gone away.
but when I try to flash CM9 .... here it comes again! I followed step by step flashing instructions.
any suggestion please?
@mishulake did you solve? how? thanks in advance!!

Nexus 7 PA 2.12 Wifi issues..

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

Oppo find 7

Hi,
Any suggestion for a stable ROM ?
Thank you all
You are asking what ROM to run in the paranoid android forum section.... What rom do you think we would suggest? Paranoid android of course....
#stayparanoid
Sorry and thanks
Paranoid is by far the best rom I had
Can't live two days on the stock rom (Sony)
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
ma8ash said:
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
Click to expand...
Click to collapse
I'm using The latest version of PA 4.6 beta on my find 7 QHD as my daily driver and love it.
Haven't noticed any major issues, battery life is really good. Wifi, 3G, and bluetooth all work flawlessly. (I haven't tried LTE because I haven't got it on my mobile plan)
The only issue that I've encountered is that, on a couple of games I have, sometimes they become slow and unresponsive (family guy game and 2014), I didn't have these problems on ColorOS.
PA 4.6 is currently beta so I'm not really concernecd and I think the minor issues will be ironed out in future updates.
Thank you very much
I have tried PA 4.6 Beta 5 today
My story here
T
Paranoid and mahdi room
ma8ash said:
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
Click to expand...
Click to collapse
Had a very bumpy ride with the first installation. I think I forgot to reset to factory settings, so it might be my fault.
Second installation was better. There are certain things I don't love:
Chrome browser runs on windowed version, no matter what setting you try to change.
Battery seems very short. I need to recharge halfway through my day.
I can't get the gestures to work when the screen is off. (double tap works great, nothing else).
Everything else is buttery smooth. Maybe I'm just unlucky with a few glitches here and there.
Chrome issue happens on any ROM with floating mode implemented. Its a google chrome issue. They have fixed it in their latest beta.
#stayparanoid
I just can advice you to use PA. It's my personal favorite
PA Lollipop where?
I have searched high and low. Where can I find PA 5.0.x for my Find 7?
flemmingski said:
I have searched high and low. Where can I find PA 5.0.x for my Find 7?
Click to expand...
Click to collapse
We haven't released any pa 5.0....on any device.
#stayparanoid
Error downloading rom
Whenever I try to download the latest paranoid android rom for the find7s (qhd), I get an "error executing updater binary" message. I looked up and saw that you had to install the latest cyanogenmod nightly first, which I did, but I still couldn't get it to work. I first wiped everything (data,dalvik,cache) then I installed the cyano nightly, then I wiped the data, then I installed paranoid android and I still get the error. I am also running the latest twrp recovery (2.8.6.0). Thanks in advance for anyone that can help me out
chair96 said:
Whenever I try to download the latest paranoid android rom for the find7s (qhd), I get an "error executing updater binary" message. I looked up and saw that you had to install the latest cyanogenmod nightly first, which I did, but I still couldn't get it to work. I first wiped everything (data,dalvik,cache) then I installed the cyano nightly, then I wiped the data, then I installed paranoid android and I still get the error. I am also running the latest twrp recovery (2.8.6.0). Thanks in advance for anyone that can help me out
Click to expand...
Click to collapse
Use the legacy build.

Note 3 - Air Command - Touch unresponsive

Hello,
I've tried searching for this issue but didn't find the same issue, although there were issues where finger touch didn't work but s-pen did.
I have a Note-3 and got a recent patch update from Samsung after the release of 5.0. I believe from then on, the below issue started occurring.
At any screen, if i remove s-pen, the 'air command' comes up and the screen goes completely unresponsive to finger as well as s-pen. After few seconds, i get a pop-up saying "Process system isn't responding, Do you want to close it". I'm able to touch 'wait' or 'ok' but no matter which option i choose, within 3 second the phone does a quick reboot. in that 3 seconds the screen is still unresponsive to touch.
If i leave the s-pen out while reboot, everything is fine until i press the button on the s-pen to bring the 'air command'. If i change the option under 'detachment options' to any thing other than 'air command' the phone is normal while removing the s-pen and i can use s-pen until i press the button on the s-pen to bring 'air command'.
Note: I've not rooted this phone since 5.0 got released/installed.
Any ideas people?
Regards,
Rubert.
Hi, thank you for using XDA Assist. The best place to ask questions about your device in it's specific forum here, http://forum.xda-developers.com/galaxy-note-3 I'm going to ask a moderator to move this question to, http://forum.xda-developers.com/galaxy-note-3/help
jd1639 said:
Hi, thank you for using XDA Assist. The best place to ask questions about your device in it's specific forum here, http://forum.xda-developers.com/galaxy-note-3 I'm going to ask a moderator to move this question to, http://forum.xda-developers.com/galaxy-note-3/help
Click to expand...
Click to collapse
Thanks a lot mate.
Delete
rubertjack said:
Hello,
I've tried searching for this issue but didn't find the same issue, although there were issues where finger touch didn't work but s-pen did.
I have a Note-3 and got a recent patch update from Samsung after the release of 5.0. I believe from then on, the below issue started occurring...
...Note: I've not rooted this phone since 5.0 got released/installed.
Any ideas people?
Regards,
Rubert.
Click to expand...
Click to collapse
You could try clearing the Data/cache for anything in Apps that looks like it belongs to the SPen - I haven't used TW Stock for some time so can't check the options.
Journyman16 said:
You could try clearing the Data/cache for anything in Apps that looks like it belongs to the SPen - I haven't used TW Stock for some time so can't check the options.
Click to expand...
Click to collapse
Forgot to mention in the original post. I've actually did a factory reset and still the problem persists.
rubertjack said:
Forgot to mention in the original post. I've actually did a factory reset and still the problem persists.
Click to expand...
Click to collapse
You probably won't like this but go CM and buy the SPenCommand app - works great! (sorry - I'm not big on Sammy ROM's but you might try Alliance...?)
I would love to use CM. But unfortunately my phone is n900 and still there are no aosp roms. I don't want and like to use modified stock rom.
rubertjack said:
I would love to use CM. But unfortunately my phone is n900 and still there are no aosp roms. I don't want and like to use modified stock rom.
Click to expand...
Click to collapse
Before I started on Temasek's CM ROMs I was using Alliance - stock/modded ROM. You could give it a try and see if it helps?
Journyman16 said:
Before I started on Temasek's CM ROMs I was using Alliance - stock/modded ROM. You could give it a try and see if it helps?
Click to expand...
Click to collapse
I shall give it a try. just wondering, are you guys aware of any good and working aosp roms out there for n-900 exynos?
rubertjack said:
I shall give it a try. just wondering, are you guys aware of any good and working aosp roms out there for n-900 exynos?
Click to expand...
Click to collapse
You could try on the cyanogen site. Or do a search at the parent forum Galaxy Note 3
There's a Q&A thread for Dr.Ketan's ROM for n900 - try in there for a link to the ROM? http://forum.xda-developers.com/galaxy-note-3/help/qa-k14-dr-ketan-custom-control-rom-t2914663 Not sure if it's AOSP or not but Dr.Ketan seems to know what he's doing from other threads I have seen.
As of now only CM team is building beta ROM for n900. Per my findings, many failed because of the octa core and too many issues. Will wait for CM to release an official one. I too hate Sammy. poor DPI.

Categories

Resources