yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Az Biker:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Make sure you're doing a clean install: factory wipe and system.. Then flash Atom v10, gapps, AK Diamond 29, reboot, let everything load, reboot... I've run Atom since v7 always with AK kernels (pirates, cylon, and diamond) and haven't had ONE bootloop issue, ever. Even if you initially did a clean install... try it once more, see if you still get loops. Please report results :D

Atom v10 + AK Diamond 29 = Gyrannosaurus Nex
[Samsung Galaxy Nexus] nziria:
no way to install over?

i don't want to do a clean installation....
[Samsung Galaxy Nexus] Blackcrx:
you can always try to dirty flash instead of wiping system, see if that works

boot to recovery, flash atom, gapps, ak kernel, reboot with fingers crossed
[Samsung Galaxy Nexus] Az Biker:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Under normal circumstances, flashing a concurrent kernel isn't a problem. But you're having a bootloop issue. Something isn't right. Could be a lot of things... Best way to troubleshoot is to start fresh... Clean install takes a little more time, but running a kernel like AK with Atom with no issues is more than worth it... It's your call of course... Hate to see you miss out on Stefano's magic :D

Atom v10 + AK Diamond 30 = Gyrannosaurus Nex
[Samsung Galaxy Nexus] Shad0wguy:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

V29 fixed the issue I was having connecting to the wifi at my girlfriends house. I guess it was from rolling back the wifi driver. I'm very happy :)
[Samsung Galaxy Nexus] galakanokis:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Did you make the changes to the build.prop that PD suggested in the thread? I got boatloops with Diamond before making that change.
[Samsung Galaxy Nexus] Az Biker:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

^^^Try dirty flash first! ^^^ For some reason I thought you said you already dirty flashed and still had the bootloop... My bad..

Atom v10 + AK Diamond 30 = Gyrannosaurus Nex
[Samsung Galaxy Nexus] thefatalepic:
Same here. I had a bootloop, then the phone got stuck during the optimizing apps before boot. Then I clean flashed and the phone froze during TiBu restore and again during the optimizing apps process after I rebooted. Editing the build.prop solved all my issues. TiBu still took about 4-5 minutes on a couple apps, but no more freezes or hangs during boot.

From PrimeDirective:

"if you're having problems with titanium backup or whatever freezing on dexopts open your build.prop in the ROM zip and modify this line..

dalvik.vm.dexopt-flags=v=n,o=a,u=n,m=y

make it say this:

dalvik.vm.dexopt-flags=v=n,o=v,u=n,m=y

then find that app developer and turn their skull into a cereal bowl. will upload a flashable fix later."

EDIT: I didn't know how to edit the boot.img so I just did another clean flash and went into /system/ and edited the build.prop before restoring or installing any apps (well I had to install Root Explorer to edit the file).
[Samsung Galaxy Nexus] jjhiza:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Try Velis Auto brightness from the Play Store. Your issue is likely a ROM issue versus a problem with the kernel. I haven't used an AOKP build (nor any ROM with AOKP bits included) for a long time, because it's a notoriously buggy ROM. If the problem persists, and you want a ROM with tons of features, try Sourcery, and see if it corrects your brightness problem. :)
[Samsung Galaxy Nexus] thefatalepic:
When I used Auto Brightness it was always too low for me, so I increased the color multipliers by about 80-100 each, increasing overall brightness just a bit. In the end, I got tired of dealing with Auto Brightness and just use Power Toggles to switch between 3 presets settings that I customized.
[Samsung Galaxy Nexus] Shad0wguy:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

We discovered the issue with PowerAmp, and removing the app before flashing fixed the issue. Unfortunately it won't reinstall.
[Samsung Galaxy Nexus] branedamig:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Try wiping cache, dalvik cache, and system (be careful NOT to do a factory reset). Then, reflash ROM, gapps, and kernel of choice. As long as you DON'T factory reset, this will NOT wipe your ROM or app settings. It's a more thorough dirty flash and can often keep you from clean flashing the same ROM base. Hope it helps!

Sent from my Commotio Gnex with AK Kernel on Tap2
[Samsung Galaxy Nexus] Blackcrx:
quick question: is diamond 29 running the same voltages as diamond 20? it seems that 20 is more battery friendly

I looked at the voltages on trickster and they seem to be the same as 20, but my memory sucks.

battery difference could be related to wifi drivers?

---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------

Are you sure? I thought wiping the "system" completely wipes the ROM?
[Samsung Galaxy Nexus] zandander:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Just had my first freeze up on v32

Its probably some tweaks that I've done to it though. Will report back if it happens again on closer to stock settings.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Az Biker:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

As best as I can remember, the default voltages remained the same from 20 to 29 (when applying my usual -50 to 29 I remember the same final voltage for 180 was 780 (or 830 default) that's from memory so don't hate me if I'm wrong) maybe let it settle in a bit longer. I know my third full charge was much closer to my v20 results than my first...

Atom v10 + AK Diamond 30 = Gyrannosaurus Nex
[Samsung Galaxy Nexus] Blackcrx:
That's what I thought. The MPU, IVA and Core voltages all look the same visually but I also recall AK mentioning that he was going to revert back to stock voltages shortly after 20 was released

Also if I remember correctly the MPU voltages stayed the same it was the IVA and Core voltages that got lowered in 20. Please correct me if I'm wrong

---------- Post added at 04:37 PM ---------- Previous post was at 04:35 PM ----------

Not to be a troll or a **** or a wonder nobody (did I use it correctly), but I thought people were not suppose to talk about beta kernels anymore?
[Samsung Galaxy Nexus] Az Biker:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Was this the same issue caused by power amp? I'm curious since I've not had this issue ever and have been with atom for some time flashing ak kernels...

Atom v10 + AK Diamond 30 = Gyrannosaurus Nex

---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------

Could be a Project Chicago beta tester...

Atom v10 + AK Diamond 30 = Gyrannosaurus Nex
[Samsung Galaxy Nexus] jjhiza:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

^agreed... Giving Anarkia and the team, feedback on test kernels is fine... Posting links to said kernels is not. Sometimes, a team's IRC channel is dead, and members will drop a line in the forums, so they can make bugs/issues known quickly. No biggie. :)
[Samsung Galaxy Nexus] thefatalepic:
Well I think PowerAmp was the app causing the issue. But the only way around it was to edit the build.prop. I deleted my TiBu backup for PowerAmp and restored all apps after editing build.prop. Then I installed PowerAmp via the Play Store, now it's working just fine. There may be more apps like this, I'm not sure what it was exactly that made it incompatible with v10.

I knew I noticed some changes since I've been gone. I noticed the extra links in the OP about beta discussions. "Wonder nobody" LMFAO Thanks, I almost forgot about those golden moments.

I've never had the issue up until v10. Something must have changed that made the "Optimizing Apps/Android is upgrading" process incompatible with certain apps, mainly PowerAmp.
[Samsung Galaxy Nexus] Blackcrx:
Again, I am not trying to cause trouble in any way. I just want to prevent any problems that might come up or have the past repeated.

I thought all beta kernel talk was only suppose to take place in the private G+ community?

Feel free to delete any of my posts that you guys feel are causing a problem. I just want to keep this thread on track so AK does not leave XDA as threatened previously.

---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------

If this is the case than please delete all my posts relating to this subject. I was under the impression that all beta talks were suppose to be done in the private G+ community

I just don't want to lose the AK kernel team... I love you guys.... No homo

---------- Post added at 04:53 PM ---------- Previous post was at 04:53 PM ----------

If this is the case than please delete all my posts relating to this subject. I was under the impression that all beta talks were suppose to be done in the private G+ community

I just don't want to lose the AK kernel team... I love you guys.... No homo

maybe a little....
[Samsung Galaxy Nexus] Az Biker:
Afaik, beta testing related talk in the kernel thread is cool, I have no doubt if it wasn't, we would already know :D

The BIG change Stefano wanted implemented is the general questions, totally off topic chatting, and sig/avatar comments to be posted in the proper threads linked on OP...

"maybe a little" :D :D :D
[Samsung Galaxy Nexus] sruel3216:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I have something to say...

God damn I love this kernel
[Samsung Galaxy Nexus] ciprianruse88:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

This kind of OT is accepted anytime :D .I am really happy when I see happy users.Great job guys on keeping the thread clean and helping users!:thumbup::D

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] branedamig:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

It does wipe the ROM but maintains all ROM and app settings. I do it all the time. It's the only way I dirty flash. I've never had any issues. My bro in law also dirty flashes that way on Toro with no issues.

Sent from my Commotio Gnex with AK Kernel on Tap2
[Samsung Galaxy Nexus] ciprianruse88:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

In twrp a clean install of rom plus kernel that you want means: wipe cache,dalvik cache,factory reset,system,flash rom,flash gapps(optional),flash kernel(optional but always ak kernel),reboot,enjoy smoothness:D:thumbup:

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] Az Biker:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

So if I do a factory reset and a system wipe I still need to wipe dalvik and cache? Oops :D

Atom v10 + AK Diamond 30 = Gyrannosaurus Nex
[Samsung Galaxy Nexus] zandander:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

No more freeze ups after I tweaked my settings a touch. Running extremely well

And yes, I am a beta tester for AK...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] szucsgf:
180Mhz voltage was 810mV on v020.
[Samsung Galaxy Nexus] ciprianruse88:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Theoretically no but i like to do it :)...pressing two more times the screen isn't hurting :)

Sent from my Shining Nexus using AK DIAMOND ED.

---------- Post added at 03:04 AM ---------- Previous post was at 03:01 AM ----------

What kind of freeze did you had? I had a freeze(slowdown) on latest test diamond when unlocking the screen...everyting went in slow motion but resolved when i locked and unlocked again.this is the first time happening since pirates ed.

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] zandander:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

It wouldn't respond to anything. It basically locked up and shut down.

Only thing that fixed it was a battery pull :/

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] m0bstr:
can i know why i was removed from the g+ page??
[Samsung Galaxy Nexus] ciprianruse88:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Sounds like a sod.what where your kernel settings when this happened?

Sent from my Shining Nexus using AK DIAMOND ED.

---------- Post added at 03:48 AM ---------- Previous post was at 03:47 AM ----------

Because a guy posted a link of ak test kernel from g+, Stefano did some clean up and removed all users that weren't active.

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] Blackcrx:
Learn something new everyday. Haha.

When I dirty flash I don't wipe anything.

I was always under the impression that system wipes everything
[Samsung Galaxy Nexus] m0bstr:
i always tried the beta kernels and I only posted when i had something to say and never shared the links......
[Samsung Galaxy Nexus] akellar:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Pretty much every rom install script wipes system so you're likely wiping it and don't know it already.
[Samsung Galaxy Nexus] Blackcrx:
When flashing a new ROM or restoring a backup I always wipe all 4
[Samsung Galaxy Nexus] zandander:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Was using Nephilims settings to the letter

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] butikofer08:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

On this note...

To those dirty flashing....save yourself the time and don't post issues you have because the universal troubleshooting advice you will receive will be...."do a clean install"

Not trying to be a Richard. Just want to keep this thread as efficient as possible.

I would ask this be added to the OP (shouldn't have to be as it should be common sense), but i doubt that would do much good as most users go right to the end of the thread.

---------- Post added at 04:08 AM ---------- Previous post was at 04:05 AM ----------

Come on bro....wonder no body? Lets not go back there. For the well being of this thread please think (and search) before posting....

On the maps topic....i followed the users tips and disabled all auto starts for maps. Still showing under "running apps". Should i be concerned if its not registering under the "battery" tab?
[Samsung Galaxy Nexus] musashihatred:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Latest one :)

Stock 1750mah maguro OC 1350

Min 230

Fsync Off.
[Samsung Galaxy Nexus] butikofer08:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

On screen time?

---------- Post added at 04:35 AM ---------- Previous post was at 04:33 AM ----------

His point exactly....

---------- Post added at 04:36 AM ---------- Previous post was at 04:35 AM ----------

Delete
[Samsung Galaxy Nexus] musashihatred:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Sorry

Here mate.
[Samsung Galaxy Nexus] butikofer08:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Delete
[Samsung Galaxy Nexus] musashihatred:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I think system doesnt sync when closing an app. Its justs call system storage.

It only syncs when cpu gets idle and going on deep sleep.

-_-.
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

What would cause one kernel to use significantly more or less Ram than another? Like, what factors are at play?
[Samsung Galaxy Nexus] musashihatred:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I really cant say but a good kernel comes to play when it can save as much data as it can in a ram while preventing file system datas from getting hungry over it. Where as it manages each division to give data samples at right interval l. So even at low ram available it can do well :)

I always have 150-130mb ram on AK. Buy it doeant affect me in anyway. Linux was that way. Put more on ram. Load faster. Run faster. If ram not efficient, kill some and get some :)
[Samsung Galaxy Nexus] buggerthis:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

You know, I just realised this yesterday too. The damn maps app is always in the running apps list. I think it gets called by other apps that need to know your location - for me that would be the dash clock weather extension. So I've re- enabled all it's receivers and uninstalled autorun manager. I'll post if there's any noticeable difference in battery life.

---------- Post added at 08:43 AM ---------- Previous post was at 08:32 AM ----------

Where are my manners?

Thank you, anarkia for this awesome kernel series, and thank you thread regulars for already having answered almost every conceivable relevant question.

I switched to AK two weeks ago for the new WiFi drivers, but I don't think I could switch back now even if you took then out. Thanks.
[Samsung Galaxy Nexus] butikofer08:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

My theory is just because it's running doesn't mean it's using any significant amount of your battery. Excited to hear your results. Thanx buddy :beer:

Edit: i also love this thread and with the new direction its going, i vow to help other users out more (i also plan on abusing the thanks button)
[Samsung Galaxy Nexus] PatimusXPrime:
solution: uninstall maps -> download waze and use it.

you'll be glad you did
[Samsung Galaxy Nexus] buggerthis:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I've tried that. Waze is all but useless here in India, unfortunately.
[Samsung Galaxy Nexus] PatimusXPrime:
aww didnt know youre in india :/ well you could use this :

https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en

what you do is add it to the app and when it says it's "pending" just tap maps then the pause button on bottom and itll hibernate it. when i did this my wakelocks went down to maybe 3 or 4 in a few hours. it's an improvement ya know?

the nice thing is that maps will work perfectly fine if you open it yourself, only thing you have to do is manually hibernate it after youre done. you can actually create a shortcut on the homescreen so when you tap the shortcut it hibernates any pending apps.

good luck! :D
[Samsung Galaxy Nexus] Az Biker:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Did another nearly constant use beat down, this time of AK Diamond 30.. Same settings as last heavy test (click link under sig)... 3hrs 40 min unplugged, 3 hrs sot... This was Internet, camera, text, music, Tapatalk, xda, games, voice calls, gps location, anything I would do on a normal day, just pretty much non-stop (47min per hour constant use)... Again, not scientific, maybe not useful for much else other than knowing you CAN get 3 hrs sot with AK Diamond 30 even beating your batt to death with extreme malice :D Imagine what results I'd get if I actually had to work at work today (instead of play on my phone) and only used the phone 13min each hour rather than 47min each hour ...

Atom v10 + AK Diamond 30 = Gyrannosaurus Nex
[Samsung Galaxy Nexus] butikofer08:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I know its been mentioned before and doesn't address the root of the problem but i haven't turned back from DS battery saver since my initial download.

Yes texts/calls come through and even emails/alerts with some light customization.

To sum it up it not only turns data on/off but also forces apps into deep sleep, thus eliminating all worries of wave locks.

Some users have reported issues but most trash talk about it is ignorance due to lack of research....

DS battery saver is not the same as Juice defender. do your research people before criticizing....:beer:

:honestly i cant believe this isn't a part of android or some custom rom . i mean i know it's not for everybody but a simple on/off toggle would solve that.

Anyway....back to the greatest kernel of all time....:beer:
[Samsung Galaxy Nexus] Citizen_Snips:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Okay I guess it was an issue on the ROM or maybe the kernel just doesn't play well with PA 3.15. Getting deep sleep just fine on Xylon 2.4 beta :)
[Samsung Galaxy Nexus] Az Biker:
A few pages back, there is a list of boxes to uncheck on your MAPS app to keep it from auto starting UNLESS you activate it. Something like unchecking boxes 1,2,4,7 and the last 2... May want to give that a try as well ( I did)...
[Samsung Galaxy Nexus] butikofer08:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Tried it. Even unchecked all map boxes. Rebooted. Immediately checked running apps....maps was running. And that's with GPS off....

And just to be clear....the boxes he's referring to are found under the auto start section of an app you have to download. Auto start manager hasn't been updated so i use ROM toolbox based on a users suggestion
[Samsung Galaxy Nexus] MaLiXs:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

For me greenify work very well

Send from my Ak Sniper GNex
[Samsung Galaxy Nexus] Az Biker:
What were your results when using ROM toolBox? I'm using Rom ToolBox Pro and my MAPS isn't running on boot ...
[Samsung Galaxy Nexus] Wh1t3Rose:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I had some pretty serious wakelock issues today. I still got pretty decent battery life but can anyone tell me what caused the messaging wakelock? Nothing shows in BBS.

Can't post screenshots for some reason

Toro | Xylon | AK Diamond
[Samsung Galaxy Nexus] Wh1t3Rose:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Help with messaging wakelock?

Toro | Xylon | AK Diamond
[Samsung Galaxy Nexus] butikofer08:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Those are my results with rom toolbox lite.
[Samsung Galaxy Nexus] ketann:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Getting sod with 180mhz on latest diamond
[Samsung Galaxy Nexus] MBQ_:
Raise your min screen on frequency a step or two up.
[Samsung Galaxy Nexus] ak:
I use PA3.15 and all works very well .. i have disable fsync and is it is very smooth.

MSG wakelock isnt a problem of kernel.

Thanks a lot for your hard work!

Poweramp have a problem with some rom opt .... at the library level ... i have the same problem.

Solution: send email to develop for fix compatibility

Wifi drivers is 3.4.x version ... probably fix the problem because i have upadate the version to last 1.88.6

https://android.googlesource.com/kernel/common.git/+/android-3.4
[Samsung Galaxy Nexus] ak:
You have to follow the rules my friend, go to the first page and use the trouble list for post problem! :fingers-crossed:
[Samsung Galaxy Nexus] ketann:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

I am just informing bro, maybe you can remove 180mhz step so that we noobs don't sod :D

Now I'm using 230-1350 since yesterday and it's all good :thumbup:
[Samsung Galaxy Nexus] MBQ_:
Re: [KERNEL] [TUNA] [3.0.70+][4.2.2] [DIAMOND v029**] [27/03] AK

Its not his fault when and if people mess up their phone. If a good amount of people were complaining, then he may consider taking it out.. But one little complaint from one user isn't going to make a dev take something out a good amount of users may use.
[Samsung Galaxy Nexus] vivekbalan:
Xylon 2.4 beta :eek: Share the line plz. I could not find it.
[Samsung Galaxy Nexus] ak:
Why i have to remove a freq slot that work very well for me!

As mentioned earlier, information such as this aren't helpful to anyone!

Follow the rules ... because now this is the line for all!

No noobs here only beta testers! tech line is your way .... live comment to users on others threads please!
[Samsung Galaxy Nexus] MBQ_:
Made by yours truly:

http://xdaforums.com/showthread.php?t=2168067

---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------

You rock AK. :victory: :highfive:

to stay relevant... flashing 032 with my latest toro XYnightly in a few. Im so excited :)