[Q] AOKP Milestone 3 + Franco Kernel Random crashes w\ bug report - Samsung Galaxy Nexus

Hi there,
Me and a friend both installed latest Franco kernel and AOKP Milestone 3 (including respective gapps).
I however seem to be seeing random crashes whenever I use my applications. Seems to be as a result of the keyboard, as it starts to get sluggish right before the crash.
What's odd is my friend isn't experiencing no such issues.
I've included the bug report is e-mails out after the crash. Anyone have any ideas?
[Details]
Android OS: 4.0.3
Baseband: I9250XXKK6
Kernel Version: 3.0.21-franco.Kernel-nightly-17.2
Build number: IML74K
Mod version: aokp_maguro_milestone3

I'm using milestone 3 and Franco 13.1. My phone has only crashed once however I do get the random bug report emails that generate every now and again.
Sent from my Galaxy Nexus using xda premium

I had the same issues, but mine glitched alot. I switched over to gummy, and both myself and my phone are happy.
Sent from my Galaxy Nexus using XDA App

Just odd since nothing is different between my and my friends gnexus.
I kinda like having AOKP though because its sorta 'official' ROM.... well future offocial

Related

Wifi problem

Hey guys am running Franco nightlies with aokp milestone 5 and am having major wifi problems. After a couple of hours of being connected my wifi will go grey and my whole net connection will drop requiring a reset of my router. Any ideas on how to fix?
Sent from my Galaxy Nexus using Tapatalk
Maybe your router is faulty? I don't see how your phone would crash the router.
Sent from my Galaxy Nexus running AOKP+Franco on Tapatalk 2
I dont know why people goes with nihgtlies.. Those a are for beta testers..
Ill explain some.. Franco wants to add a new feature.. So he code it and compile the new nightly but then as a result when testers flash the nightly the new feature its causing some problems with other stuff like making wifi drops..
So the testers report and then franco try to fix and so on.. Until he releases a MILESTONE (bugless version of the kernel)
I really encourage you to only use milestone roms/kernels unless you wanna be a beta tester / bug reporter for devs... Wich in that case you shouldn't be reporting your wifi issue here but to franco
Cheers
Galaxy Nexus AOKP m5 Franco kernel m3

[Q] Screen goes pink with AOKP

I have an issue with my galaxy nexus that baffles me whenever it pops up. I am using AOKP build 37 with the franco kernel and whenever I try to reflash the rom or flash a new version of the rom (build 39) everything goes smoothly until the phone has been back on after rebooting for a few seconds. Once I am on my home screen, it flickers off and then everything is tinted pink. After updating to build 39 the screen first goes fuzzy like an old television set with no channels tuned in for 1-2 seconds and comes back on, again everything tinted pink.
To fix this I have tried:-
- rebooting
- wiping cache
- wiping data
- reflashing rom
- flashing a different kernel (GLaDOS)
In the end the only thing that worked was restoring a nand backup.
I am using AOKP's option to change the screen dpi to 280, and it seemed like build 39 was behaving until I accessed this option and tried to change the dpi again.
I also tried a different rom, and cyanogenmod 9's latest nightly performed perfectly fine, but it does not have the same capabilities that AOKP offers.
I have tried searching for problems with pink or purple screens and AOKP on Galaxy Nexus but so far I have returned no exact matches, and nothing that sounds similar to my problem.
If anyone has an idea of what this issue could be, I would greatly appreciate their advice.
Thanks.
Are u flashing franco nightlies or his stable kernels?
Sent from my Galaxy Nexus using XDA
Stable versions.
I seem to have fixed it for now by installing the new build of AOKP, a new kernel (GLaDOS) and build.prop editor from the market.
Thanks anyway.
I would use the trinity kernel by morfic.. It has color correction and gamma tuning built it
Sent from my Galaxy Nexus using Tapatalk 2

GN Screen occasionally becomes less responsive

I have had a GSM Galaxy Nexus for quite a while. I've had Stock ICS on it, as well as many different non-stock ICS and JB ROMs running on it.
I've noticed that, from time to time, the screen will become considerably less responsive than it usually is. I usually notice when trying to swipe down the Notification Window. I will have to swipe several times to get it to actually work, when it usually works every time, easily. If I swipe slower and apply more pressure, it works. Also, typing on the on-screen keyboard when this issue is occurring is a disaster. The system misses about a third of my touches, and mistypes every word practically.
If I reboot or wait a while, it goes away. I've been trying to shut down various often-used apps while it's occuring to see if I can remedy the issue, but so far I haven't found an app that might be causing the problem.
Anyone else have this issue? It's so noticeable for me that I can try to do the usual motion I do to bring down the Notification Window over 10 times before it will actually respond.
It's either something basic with Android, or my hardware has a little bug. Not sure which.
I see a few posts on the forums of other phones about this, but not on here with the Galaxy Nexus.
I'm having the exact same issues. Its also very noticeable in the keyboard as well. Sometimes in the app drawer. Its extremely obnoxious and only seems to do it on jelly bean Roms... may I ask what kernel you're running? I'm on Franco 223 384mhz gpu
hey man, i've noticed this same thing on mine running Jb (joel's bamf jelly)...i notice it when typing, though. a lot of times i just completely MISS keystrokes, and my words come out all ****ed up. i honestly was starting to think i'm crazy, but i'm glad to see others with JB are having this issue! again, if i reboot as well, it goes away. wtf?
i'm running whatever kernel joel has stock in hsi rom, which i beleive is just the stock JB kernel.
Exactly same issue here, but simply turning screen off and back on solves it. No need to reboot.
susejchristo said:
I'm having the exact same issues. Its also very noticeable in the keyboard as well. Sometimes in the app drawer. Its extremely obnoxious and only seems to do it on jelly bean Roms... may I ask what kernel you're running? I'm on Franco 223 384mhz gpu
Click to expand...
Click to collapse
Running one of the early loads of 4.1.1 that required you to load 4.1, then overlay 4.1.1 over it to get get camera working properly. But it's stock minus being rooted/busybox loaded on it. Running the stock kernel with the JB baseband that released, btw.
Before that I was running AOKP and CM9, both of which did the same thing to me - which is what made me think it was an app that was interfering, but I haven't been able to prove that.
Search my thread called touch sensitivity, I wrote all about this. Its an annoying bug that has no fix. Lock then unlock the screen resets it and makes it return to normal. But it eventually happens again.
I also had this issue, and as someone said earlier, just switching the screen off and then back on fixes it for a while. But I recently updated my baseband to XXLF1 (yes, I'm from Europe) and switched to AndroidME CM10 Rom and the issue is gone (had been using the one from team inferno before). Don't know if it was the Rom or the radio...
Sent from my Galaxy Nexus using xda app-developers app
Since alot of users are saying it was non existent in 4.0.1 and 4.0.2 was wondering if someone could look into the touchscreen drivers?maybe there is a glitch.btw sometimes it would not appear for a day
Galaxy Nexus w/ 4.1.1 and trinity
dark06 said:
Since alot of users are saying it was non existent in 4.0.1 and 4.0.2 was wondering if someone could look into the touchscreen drivers?maybe there is a glitch.btw sometimes it would not appear for a day
Galaxy Nexus w/ 4.1.1 and trinity
Click to expand...
Click to collapse
Yes, that's a good point to start.
I originally thought this issue was due to a kernel malfunction, but looking at the replies here, apparently not. I don't remember it happening on ICS at all, but with jelly bean and project butter being so smooth and all, I have recently become much more attentive to the responsiveness of my screen so it's much more noticeable. I guess the best thing to do is try different Roms and see if the problem persists.
---------- Post added at 07:41 PM ---------- Previous post was at 06:42 PM ----------
Well, as stated above, CM10 seems to eliminate this problem completely. I just flashed a CM10 ROM and man is there a difference. It is extremely smooth and battery life seems significantly better than others ROMs on jelly bean right now. I highly suggest giving it a go. I upgraded my cwm recovery to 6.0.Something too. Dunno if that's relevant, but just thought I'd say.
Are you using the euroskank one? If yes then thats what im using too and still have this problem tho not worse than others, my keyboard works properly.just that my scrolling and swiping tightens up a bit which forces you to swipe longer and more pressure than normal
Galaxy Nexus w/ 4.1.1 and trinity
Here's my thread on this bug. Lots of posts.
http://forum.xda-developers.com/showthread.php?t=1576739&page=15
dark06 said:
Are you using the euroskank one? If yes then thats what im using too and still have this problem tho not worse than others, my keyboard works properly.just that my scrolling and swiping tightens up a bit which forces you to swipe longer and more pressure than normal
Galaxy Nexus w/ 4.1.1 and trinity
Click to expand...
Click to collapse
I can confirm that on AndroidME CM10 the issue is gone. Personally, I didn't hear anything about the one you said you are.
Sent from my Galaxy Nexus using xda app-developers app
lorin_93 said:
I can confirm that on AndroidME CM10 the issue is gone. Personally, I didn't hear anything about the one you said you are.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I will try this today.what kernel are you using?
Galaxy Nexus w/ 4.1.1 and trinity
dark06 said:
I will try this today.what kernel are you using?
Galaxy Nexus w/ 4.1.1 and trinity
Click to expand...
Click to collapse
I'm on default now, probably going to flash Franco's later on.
dark06 said:
I will try this today.what kernel are you using?
Galaxy Nexus w/ 4.1.1 and trinity
Click to expand...
Click to collapse
Did you find anything fix the sensitivity issue? It's super annoying. Screen off and back on fixes it temporarily.
thanks
I had this issue on 4.0.4 with the Linaro franco kernel and am now having it with JB and the Linaro franco kernel. I too thought it was just maybe my imagination!

Has anybody tried official CM11 nightlies?

Hi,
I am talking about those cm-11-201312??-NIGHTLY-maguro.zip from: http://download.cyanogenmod.org/?device=maguro&type=nightly
Maybe something is completely broken there?
Runs faster than CM10.2 stable?
bat0nas said:
Hi,
I am talking about those cm-11-201312??-NIGHTLY-maguro.zip from: http://download.cyanogenmod.org/?device=maguro&type=nightly
Maybe something is completely broken there?
Runs faster than CM10.2 stable?
Click to expand...
Click to collapse
gots it on my toro as of today. wanted to check out the screen record feature/app but cyanogen still says i dont have a device capable of running it lies
Running CM11 Nightly since 7 december.
Everything is working, its stable and smooth.
For my daily use it's ok.
Had only problems with auto-restore, solved with the right gapps package.
Try SlimKat
I tried the CM11 and wasn't impressed. Try the latest SlimKat Beta. I've been running SlimKat since their first Alpha release, and it has improved significantly over the past couple weeks. SlimKat Beta is updated to the latest Android 4.4.1 software which improved the camera's functionality. Only issue remains an occasional random reboot...maybe once per day, if that.
bat0nas said:
Hi,
I am talking about those cm-11-201312??-NIGHTLY-maguro.zip from: http://download.cyanogenmod.org/?device=maguro&type=nightly
Maybe something is completely broken there?
Runs faster than CM10.2 stable?
Click to expand...
Click to collapse
I've been running the nightlies since they became available and I've never had any problems. No reboots, graphic glitches etc.
-----------------------------------------------------
Sign up for COPY with this link, and we'll both get 5 GB of free cloud storage in addition to the usual 15 GB: https://copy.com?r=m3arsR
Free GiffGaff SIM with £5 credit: http://redir.info.giffgaff.com/r/?id=h4d8d850,c0e1337,c0e139c&p1=d3xp2pc
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Using the 1209 nightly, and the stability improved significantly compared to Euroskank's CM11 KitKang. That's all I can say, since performance stays largely the same.
Sent from Samsung Galaxy S Relay 4G @ CM11
I am running swordrune10's version for toro. I am having some trouble with the wifi switching, google backup/auto install apps on wipe and google play killing my battery but it runs great with art besides those issues.
I can say they work flawlessly. Huge improvement from 4.3, never had a crash / freeze, etc. It does lag a bit on received call, not a major issue for me though.
I've had wifi switching problems since 4.3 dropped. Its ok on CM11 but just barely
CM 11 nightlies since 12-6 have a major issues with LTE. Some users are either not getting it at all or having issues toggling between 3G and 4G in which 4G will not turn back on.
I have been using cm 11 since unofficial alphas and have had very minimal issues. I think the hand off issue fix was merged in the latest nightly as in the one you can flash tomorrow.

[Q] Bluetooth on Unoffical Liquid smooth

Does any one know if there's an issue with Bluetooth on the 2/3 build of the Unofficial Liquid Smooth? The processes crashes and resets every time my phone connects to car. the 1/18 build is the last one that worked for me.
54852845511
fryediablo said:
Does any one know if there's an issue with Bluetooth on the 2/3 build of the Unofficial Liquid Smooth? The processes crashes and resets every time my phone connects to car. the 1/18 build is the last one that worked for me.
Click to expand...
Click to collapse
I Have had no problems with bluetooth with the 1/18, 1/25, 2/3 or 2/5 builds . I have not tried the 2/6 build yet. Though I did dirty flash the 2/3 And 2/5 builds. Then when connecting to the car I found every there already
where did you download theese unofficial liquid builds?
erghetto said:
where did you download theese unofficial liquid builds?
Click to expand...
Click to collapse
I loaded the unofficial nightlies from the forum [ROM][Unofficial] LiquidSmooth v3.0 (KitKat4.4.2) TORO This is a great active forum for the Galaxy nexus. The present on on page 1 of that forum is dated 2/6.
The 1/25 version is an official nightly found from the LiquidSmooth G+ community
Thanks for the reply. Every build after 1/18 crashes on me, even the 2/13 I dirty flashed yesterday. Every time I get on my car it connects, then resets. I've tried deleting and repairing my phone, I tried both dirtyv and mpokang kernels. And I've cleaned flashed a couple of builds, but still nothing.
Sent from my Galaxy Nexus using xda app-developers app
Tried a clean flash if the latest build and still no go. Can't seem to figure out why the process keeps crashing. Even a Google search showed little information. Best I could find was this was an issue of some earlier version of 4.4 builds of various roms, but they all say they were fixed around mid January.
Sent from my Galaxy Nexus using xda app-developers app

Categories

Resources