Database Info

Cannot Install Custom Kernel

This is a strange problem that I only started to have once I installed Team Nekkid 7.2 RC dated 3/29.
I can flash the ROM no problem, wipe dalvik and fix permissions and I'm good to go without any issues. But if I flash the ROM, then either morfic or faux kernel, then gapps, when I go to wipe dalvik, all I get is a quick screen flash with no option to actually wipe dalvik.
I go back and wipe the overall cache completely, fix permissions, the reboot. I am now stuck at the morfic boot animation until i pull battery.
If i try to install a Faux kernel, same thing happens with dalvik, but gets stuck at the blue LG screen.
Once i battery pull and get back to CWM, i wipe everything, reflash ROM and gapps, wipe dalvik and fix permissions no problem and boot up into whatever ROM i choose.
EDIT: Went back and flashed Bionix 1.4.1 and was able to flash a Faux kernel and wipe dalvik. Booting up this ROM now.
I also have NO problem with ICS ROMS/kernels.

When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!

Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium

mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I did all of that. I flashed the kernel before and after gapps but end up with the same result.
I have a feeling there is an issue with the CWM since I am constantly flashing roms/kernels and have never had these problems before. I'm at work so I cant use the Nvidia tool to flash CWM so I have to wait until I get home.

mariuscm said:
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Click to expand...
Click to collapse
I meant I have no problem flashing ICS roms and kernels.

mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
[UPDATE] Ok I got it now. Just read your last message

mariuscm said:
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
Click to expand...
Click to collapse
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.

stevew84 said:
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
Click to expand...
Click to collapse
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.

mariuscm said:
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
Click to expand...
Click to collapse
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.

stevew84 said:
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
Click to expand...
Click to collapse
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!

mariuscm said:
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
Click to expand...
Click to collapse
If the maps shows up and then goes blank, simply close the map and re-open it.

I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.

mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
All the important information will be in the first post of his thread. he doesn't include a change log, though.

mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
Yes, it's 4.0.4 with all of the latest CM9 commits.
Sent from my LG-P999 using xda premium

[ROM][23-03-14][Flinny] Saga - Andromadus - CM11.0 [alpha5]

Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.

Current Build Changelog
Build 16
Rom
Should have fixed the zoom problem with browser some were having with large fingers/thumb presses.
Notification LED should be green again.
Disabled sliding picture animation when taking a picture for now.
Saga, rotation issue should be resolved again.
Everything else synced with CM.
Kernel
Patched to 3.0.66
Saga - S2W should be disabled by default on a clean install
Increased PMEM allocation on both SAGA and VISION as we were having out of PMEM issues sometimes when coming out of standby.
MDDI - sorry still need an updated kernel for you.
Checkout http://andromadus.flinny.org for previous changelogs

So you finally splitted everything up
Tapatalked from Desire S running Andromadus

When can we expect your next 4.2 build?
EDIT: unofficial link build 6
gapps

As said files are uploading both for AOSP AND CM 10.1
The first CM 10.1 build and everything works
Tapatalked from Desire S running Andromadus

suku_patel_22 said:
As said files are uploading both for AOSP AND CM 10.1
The first CM 10.1 build and everything works
Tapatalked from Desire S running Andromadus
Click to expand...
Click to collapse
What you already got your hands on cm10.1 cool
still a noob

niravnn said:
What you already got your hands on cm10.1 cool
still a noob
Click to expand...
Click to collapse
http://andromadus.flinny.org/?q=cm10_1

Except the lockscreen shortcuts/options that are gone (for now)... DAMN!
Camera (including front face camera), GPS, wifi, sensors, sound, ... WORKING!
Stop reading and install this **** !

Great work! Flinny!
can't wait to have a try!
---------- Post added at 06:23 AM ---------- Previous post was at 06:21 AM ----------
the camera seems to have a green line on the left, can anyone else confirm that ?

lhn1989 said:
Great work! Flinny!
can't wait to have a try!
---------- Post added at 06:23 AM ---------- Previous post was at 06:21 AM ----------
the camera seems to have a green line on the left, can anyone else confirm that ?
Click to expand...
Click to collapse
Ah that old bug.... I will nuke it for the next build.
Sent from my Nexus 7 using Tapatalk 2

Flinny said:
Ah that old bug.... I will nuke it for the next build.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
All I have to say is WOW, best ROM ever! Thanks, only bug I get is that camera one

Flinny said:
Ah that old bug.... I will nuke it for the next build.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
+1 for a fast release!
Thanks flinny!

Just installed this rom over AOSP 4.2 v3 with cache&dalvik wipe.
Lockscreen widgets are now not oversized, that's good.:good:
The bug I have is with the AOSP keyboard, it doesn't show up (black screen instead, see the screenshot) and then FCs. Tried clearing data and cache, but it didn't work.

giant_karlik said:
Just installed this rom over AOSP 4.2 v3 with cache&dalvik wipe.
Lockscreen widgets are now not oversized, that's good.:good:
The bug I have is with the AOSP keyboard, it doesn't show up (black screen instead, see the screenshot) and then FCs. Tried clearing data and cache, but it didn't work.
Click to expand...
Click to collapse
Flinny already has said in the OP that he will only count as a bug when we have it in clean install. Make nandroid than clean install if it's there than its a bug
still a noob

niravnn said:
Flinny already has said in the OP that he will only count as a bug when we have it in clean install. Make nandroid than clean install if it's there than its a bug
still a noob
Click to expand...
Click to collapse
ah! sorry, didn't read the OP, rushed to download and test the CM10.1 =)
I've tried another JB keyboard from the forum and it works!:victory:

giant_karlik said:
ah! sorry, didn't read the OP, rushed to download and test the CM10.1 =)
I've tried another JB keyboard from the forum and it works!:victory:
Click to expand...
Click to collapse
Clean installed here and both the AOSP and Swiftkey 3 keyboards show up! I realy can't believe how great and stable CM10.1 already is for our Desire S!

sammyke007 said:
Clean installed here and both the AOSP and Swiftkey 3 keyboards show up! I realy can't believe how great and stable CM10.1 already is for our Desire S!
Click to expand...
Click to collapse
yes, it's amazing!
thanx for the info about clean install, I think I'll do it later today. Just have no time for reinstalling and restoring stuff now.

sorry... post to wrong forum~

Try clicking build 10 times in about phone...I guess it should work
Strange Android

vampire36 said:
Try clicking build 10 times in about phone...I guess it should work
Strange Android
Click to expand...
Click to collapse
no guess... it works...

[Q] please help cm10 have to reboot to recieve text messages

Excuse me if I'm doing this wrong I just really need help and I am new to posting on CDs but not new to rooting anyways I am running cm10 the latest nightly February 3rds nightly and it seems like at times my texting works other times it doesn't same thing with calls the only thing that seems to temporarily fix the problem is if I reboot but then it happens again I have wiped and factory reset flashed different radios and I always seem to have the same problem never have I experience such a problem with rootinformation and flashing it's always been easy breezy any help much appreciated

justanizfamouz said:
Excuse me if I'm doing this wrong I just really need help and I am new to posting on CDs but not new to rooting anyways I am running cm10 the latest nightly February 3rds nightly and it seems like at times my texting works other times it doesn't same thing with calls the only thing that seems to temporarily fix the problem is if I reboot but then it happens again I have wiped and factory reset flashed different radios and I always seem to have the same problem never have I experience such a problem with rootinformation and flashing it's always been easy breezy any help much appreciated
Click to expand...
Click to collapse
Try other nightly. But since you're really looking for a daily driver use stable and stable only.
As far as i understand nightlies are experimental and not meant for daily use.
You say that you have tried several radios, have you tested UCLL3 (that's a link)? Thats the latest (and imho best) radio yet. It's a native jellybean radio so it should work well with CM10.
Also wipe cache & dalvik cache not only factory reset (dalvik is under advanced in cwm).
Good luck

lingowistico said:
Try other nightly. But since you're really looking for a daily driver use stable and stable only.
As far as i understand nightlies are experimental and not meant for daily use.
You say that you have tried several radios, have you tested UCLL3 (that's a link)? Thats the latest (and imho best) radio yet. It's a native jellybean radio so it should work well with CM10.
Also wipe dalvik cache (under advanced in cwm).
Good luck
Click to expand...
Click to collapse
It happens with any nightly or stable ever since I upgraded from cm9 to cm10 but the radio you listed is the one I have I also notice it tends to lag slot no matter what the performance is set at

justanizfamouz said:
It happens with any nightly or stable ever since I upgraded from cm9 to cm10 but the radio you listed is the one I have I also notice it tends to lag slot no matter what the performance is set at
Click to expand...
Click to collapse
Well then i'm out of ideas. Wait for someone else too reply.

Have you tried going back to the beginning? Go back to stock and then flash CM10 Stable. Using the radio that was listed in post good luck.
Sent from my SAMSUNG-SGH-I727 using xda premium

ozziedog said:
Have you tried going back to the beginning? Go back to stock and then flash CM10 Stable. Using the radio that was listed in post good luck.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
+1
This is a good idea. You should try this.

[Q] Wifi issue with CM11

Hi everyone, I'm new on XDA
I currently have a ville (S4) with the latest snapshot of CM11 (M6) and I'm experiencing some issues with wifi signal:
When i connect to my router wifi works flawlessly, but after some hours it drops and seems like it can't reach any signal, neither from other router (my neighbours). If i reboot it, than it starts to work again.
This happens on any CM I've tried (10.1, 10.2, 11 various) and also on Pacman Rom but not with stock or sense based ROMs.
Is there anyone who has ever had this kind of issue or better a solution? Any help would be very appreciated
HBoot: 2.15
TWRP 2.7
ROM: CM11 (M6)
Radio: 1.20 (the one that comes with 2.16 package seen on MaximusHD install package)
SuperCID
PS: Sorry for my bad English, I'm italian...

I've experienced the same thing and it seems to be a common problem on this device outside of stock,
wifi will be working fine but then randomly drop all of a sudden and won't show any networks until you restart the phone. It will do it again after a little while from the restart. I came across a solution to this after trying so many different things, give it a shot.
http://forum.xda-developers.com/showthread.php?t=2769977
Let me know if it works for you and/or if you need help.
Good luck
---------- Post added at 02:52 AM ---------- Previous post was at 02:48 AM ----------
Pily95 said:
Radio: 1.20 (the one that comes with 2.16 package seen on MaximusHD install package)
Click to expand...
Click to collapse
You might first want to try flashing a different radio, I've had nothing but bad luck with 1.20 on both sense and cm... random boot loops, gsm signal drops, etc...
Give this a read,
RADIO 1.35a.32.45.27, WCNSS, ADSP
Q. Why is this radio recommended?
A. This radio has been proved better then the 1.20 radio by some of the users of One S and enables HSPA in 4.3 Sense based Roms like liberty.
Click to expand...
Click to collapse

Thank you very muck! I've just falshed the 1.35a radio and all what comes with that and now it seems to have no issue at all [emoji2] I'll keep testing for some days and I'll post here my results.
Inviato dal mio One S utilizzando Tapatalk

Hello,
I am quite new here and don't have permission to post in development section, but this topic seems to fit.
I am running CM11 nightlies with good success (very few reboots) since February. With all nightlies since June 14, WiFi cannot be activated anymore.
Some other users seem to have the same problem, some don't. I usually do "dirty" flashes with CM Update, but clean flashes don't help.
I can't find information about greater WiFi changes in log files. Any ideas?
Greetings from Germany
Matthias

Found the answer. Had to reflash boot.img because my One S is S-On. Now WiFi works as usual.
Greetings from Germany
Matthias
Gesendet von meinem One S mit Tapatalk

Ok, after more than 20 days, I can say that the new radio (1.35a) posted by @nSavage works better with WiFi on my One S.
Again, thank you very much! [emoji2]
Inviato dal mio HTC One S utilizzando Tapatalk

Sound is too loud even when it's set really low.

This phone is pretty good and it's getting better every day. But one thing is really annoying and that is the sound of ringtones and notifications.
It is really loud when it's set to the lowest setting (right before it goes into vibrate). Is there something I can do about it? I must add I'm on CM11 M9, but I think it's like that on stock too. If I'm wrong, please let me know.
Verstuurd vanaaf miene Oneplus One mit CM11 M9

This isn't the case. Try updating your rom alongside the kernel if you use a custom kernel. M9 is a very old version.
Sent from my One A0001 using Tapatalk

Maybe I'm missing something, but I can't find anything more recent then the M9 except for the nightly builds. But I don't trust the nightly builds to be a stable choice...
-edit- btw, the kernel I'm using is the one that comes with M9
Verstuurd vanaaf miene Oneplus One mit CM11 M9

Lex_Michdeandroid said:
Maybe I'm missing something, but I can't find anything more recent then the M9 except for the nightly builds. But I don't trust the nightly builds to be a stable choice...
-edit- btw, the kernel I'm using is the one that comes with M9
Verstuurd vanaaf miene Oneplus One mit CM11 M9
Click to expand...
Click to collapse
What I'm saying is to flash the nightlies. Nightlies are stable.
The upgrade is worth it.. many many changes are made incl. touchscreen fix.

Ok, I'll try. The latest is the one you'd recommend? Will I lose anything when I flash it? I just got done with laying out my home screens and installing my apps, fine tuning my settings...
Verstuurd vanaaf miene Oneplus One mit CM11 M9

I don't use CM11. Do a nandroid backup and flash the newest nightly.
It should work but considering you've been on such a old version, it could be a conflict but if it does then nandroid restore your backup.
No you will not lose anything.

I'm still a little hesitant, because last time I flashed it, it broke my camera. After flashing CM I put back the original camera app. It didn't really went the way it should.
But you're right, a backup should be a safe trip.
Verstuurd vanaaf miene Oneplus One mit CM11 M9

Lex_Michdeandroid said:
I'm still a little hesitant, because last time I flashed it, it broke my camera. After flashing CM I put back the original camera app. It didn't really went the way it should.
But you're right, a backup should be a safe trip.
Verstuurd vanaaf miene Oneplus One mit CM11 M9
Click to expand...
Click to collapse
If it said, "Cannot connect to camera" its because you're using a gapps that includes AOSP Camera which is incompatible with this phone.
I recommend http://forum.xda-developers.com/showthread.php?t=2397942 pico version.
Just flash it and test the sound.

My route: flashed M9, smallest PA GApps, flashed Google's camera, "cannot connect", flashed stock camera, still nothing.
Then I wiped all but my storage and started all over again: M9, smallest possible PA GApps, stock camera. I'm really a happy camper with this thing like it is now, it's just that sounds are too loud.
-edit- That didn't go well. It went haywire, but luckily I made a backup. I guess the past two days were a waste of time, I'm going to have to start all over again if I choose to go with the nightly builds...
Verstuurd vanaaf miene Oneplus One mit CM11 M9

Like I said above, do not flash Google camera. It doesn't work with the OnePlus One, you need to just flash Pico and download the CameraNext apk (find it online, its in this forum).
You wiping storage has nothing to do with it. All I told you to do was to flash the nightly, that was it. You didn't have to do anything else.
And if you're going from 1 gapps to the next with a dirty wipe, then read the PA Gapps thread on the instructions on how to do that properly.

I only flashed the nightly... No way, José. The route I explained was what I did two days ago.
Verstuurd vanaaf miene Oneplus One mit CM11 M9

I tried all kinds of stuff, but still no latest nightly. It gives me the same error every time I boot the latest nightly. Of course I made a screenshot, but the awesome XDA app is giving me an error when I tap the little camera button to add a picture.
Anyway. It says: "Unfortunately, the process com.android.systemui has stopped."
That's it. I can click OK, but it pops back immediately. So I put back my backup for now. I'm a little annoyed by the fact that CM goes out guns blazing about how they have their own phone with stock CM, but then they fill it up with loads of Google cr-p!
So I still have to fiddle with flashing custom roms and as a result I spent the last four days trying to get this thing running without problems.
-edit- According to the guys using the nightlies, the latest (30th) is having issues. So it wasn't me.
Verstuurd vanaaf miene Oneplus One mit CM11 M9

Lex_Michdeandroid said:
I tried all kinds of stuff, but still no latest nightly. It gives me the same error every time I boot the latest nightly. Of course I made a screenshot, but the awesome XDA app is giving me an error when I tap the little camera button to add a picture.
Anyway. It says: "Unfortunately, the process com.android.systemui has stopped."
That's it. I can click OK, but it pops back immediately. So I put back my backup for now. I'm a little annoyed by the fact that CM goes out guns blazing about how they have their own phone with stock CM, but then they fill it up with loads of Google cr-p!
So I still have to fiddle with flashing custom roms and as a result I spent the last four days trying to get this thing running without problems.
-edit- According to the guys using the nightlies, the latest (30th) is having issues. So it wasn't me.
Verstuurd vanaaf miene Oneplus One mit CM11 M9
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-one/help/android-systemui-stopped-cm11-nightly-t2891608
People say 28th works.
But yeah its a nightly, bugs are to be expected. Usually things are smoother on the nightly side of things.

I've got the same problem I'm on stock 4.4.4. The ring tone is silly loude on the lowest setting.

Now running the 29th nightly, but still having trouble with the loudness. I guess I am going to have to live with it.
Maybe I'm asking a very stupid question, but what is Dalvik and what is Cache? Should it always be wiped? What happens if I do(n't)?
Verstuurd vanaaf miene Oneplus One mit CM11 M9

Lex_Michdeandroid said:
Now running the 29th nightly, but still having trouble with the loudness. I guess I am going to have to live with it.
Maybe I'm asking a very stupid question, but what is Dalvik and what is Cache? Should it always be wiped? What happens if I do(n't)?
Verstuurd vanaaf miene Oneplus One mit CM11 M9
Click to expand...
Click to collapse
Do you have a custom kernel or something boosting the speakers? It's not loud for me. Something is causing it.
For dalvik and cache, it's best for you to Google search that instead of someone explaining what it is. And no, most roms when you flash it. It will wipe for you so there's no need to manually wipe dalvik and cache. And a misconception is that dalvik and cache relates to kernel, this is untrue. It has no effect on kernels, only roms.
Sent from my One A0001 using Tapatalk

zephiK said:
Do you have a custom kernel or something boosting the speakers? It's not loud for me. Something is causing it.
For dalvik and cache, it's best for you to Google search that instead of someone explaining what it is. And no, most roms when you flash it. It will wipe for you so there's no need to manually wipe dalvik and cache. And a misconception is that dalvik and cache relates to kernel, this is untrue. It has no effect on kernels, only roms.
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
I'm using the kernel that came with the nightly, don't know if it's possible to adjust that one. Maybe my ears are *******?
Should I try that Franco kernel everyone is raving about? Will it hurt?
Verstuurd vanaaf miene Oneplus One mit CM11 M9

Lex_Michdeandroid said:
I'm using the kernel that came with the nightly, don't know if it's possible to adjust that one. Maybe my ears are *******?
Should I try that Franco kernel everyone is raving about? Will it hurt?
Verstuurd vanaaf miene Oneplus One mit CM11 M9
Click to expand...
Click to collapse
All kernels are included with the rom otherwise the phone wouldn't boot. Might as well give it a try, it will not hurt. Use aosp variant of Franco kernel
If worst comes to worst. You can go into /system/etc/mixer_paths.xml and modify the speaker to be lower volume. It should be defaulted to 82 could be possible you flashed something that made it to be the loudest such as the value of 92. It should be under speakers but as I'm on mobile I can't be for certain, but I'm pretty positive that's the one you're supposed to modify.
Sent from my One A0001 using Tapatalk

Running franco-r20 now. Home screens are a little less lagging (ADW), but it's not as snappy as on M9. Also because Antutu (I like to stay quantitative, for what it's worth) said: M9 - 42000, Nightly29th - 39000, Nightly29th+franco-r20 - 40000.
But still the volume isn't what I'd like it to be. Don't think we're going to get that into quantitative research...
Perhaps I should call it a day and roll with this setup for a while. See if the flickering wifi/roaming annoyance and the ghost touch is gone.
Verstuurd vanaaf miene Oneplus One mit CM11 M9

Benchmarks don't mean anything. Ghost touches are for sure gone. I'm not sure whether or not you'd get graphical glitches as you're running m9 it is old and I don't think it has the commits to run the new touch screen firmware. Try the mixer paths method. Edit the file only change the numbers within the quotations and lower it. Try the alerts and repeat until you get it to where you want it to be.
Sent from my One A0001 using Tapatalk