I've been successed in x1 nand by flowing Alex&caliban2's instruction,and bring it to my country as the first one,thx to xda.
Now could anyone tell me how can i use "ast-alex-linux-xperia-android-2.6.35.tar.gz" which download from "gitorious.org/~ast/linux-on-qualcomm-s-msm/alex-linux-xperia"
your question leaves two reasons why you're asking this:
a) you want to learn how to develop kernel.
b) you think you're missing out on latest kernel and want to use it on your phone. or "bring it to your country".
well, if it really were a) you wouldn't be asking this in here, but would've found the answer how to compile kernel elsewhere. so let's go with b):
you're not missing out on anything. suspend-bug is still unfixed, flashing android to nand is nice, but even less usable than haret-version. alex was stuck on this, he went back a step and is rewriting lots of kernel-stuff.
quote from irc-chat today:
[22:22] <helicopter88> Alex[sp3dev]: will you continue to work on .35 or since now only 3.1?
[22:23] <Alex[sp3dev]> helicopter88: depends on whether i'll fix wifi on 35 or not. i plan to release a test build without wifi since many people use 3g instead
Click to expand...
Click to collapse
thx a lot! i see
I find good karnel is to be 2.6.27.46 its 890 kb big, you can find it in sensdroid v5 android from jertan93, and in hendroid android..
very good battery consumpiton last two days, charging is also working but not always so that is the issue, and some keyboard freezing sometimes...
Maybe is better kernel out there but i did find where...
nope, no better kernel. you're using ygge-kernel, btw. (zimage is part of kernel too)
there's midnight's kernel on neopeek, based on .27 from xdandroid, adjusted to x1. faster, no bug with hw-keys, charging works in theory.
but:
batt-meter is broken, it always shows 100%. so you never know how much juice is left. and it doesn't shut down the sys when batt gets critical. it runs till it's completely depleted. (=deep discharge = bad thing for the battery)
so you have to choose between the devil and the deep blue sea.
caliban2 said:
nope, no better kernel. you're using ygge-kernel, btw. (zimage is part of kernel too)
there's midnight's kernel on neopeek, based on .27 from xdandroid, adjusted to x1. faster, no bug with hw-keys, charging works in theory.
but:
batt-meter is broken, it always shows 100%. so you never know how much juice is left. and it doesn't shut down the sys when batt gets critical. it runs till it's completely depleted. (=deep discharge = bad thing for the battery)
so you have to choose between the devil and the deep blue sea.
Click to expand...
Click to collapse
Is this kernel "htc-msm-linux @ 20111001_013904" you are talking about?
I download that form neopeek.com but i don't have a link.
That kernel is 2.1 mb big, I just rename it and replace my ygge-kernel with this, i'm now using it for 15 hours.
I found that charging is working only when you leave phone alone, my battery menagment is working it it is not showing 100% all the time.
I charge my phone over night was shown 41 % on evening and 100 % in morning, now is on 82 %.
I also found that my benchamrk result is slightly less than whit 890 kb kernel (ygge) 560 points copared to 490 points whit this in quadrant standard.
Is there a way for fully market working?
Now I get only few app to be able to download couse others are "uncompatible with device"
huh?!
nah, that's original xdandroid-build. ("glemsom") midnight is based on it.
so you're saying they fixed batt-meter?! Oo this would be the best news ever.
i'm gonna test this right now, we'll have a serious talk if it doesn't work!
and yes, kernel being ~2mb is normal, it consists of zimage and modules.tar.gz. (i'm getting a slight feeling you didn't understand this, and just replaced the modules. "main-part" of kernel is in zImage. but let's see...)
yes i didn't replace zimage file i keep old one... but it is working i just rename the image to original.
here is download link of that file
http://xdandroid.com/wiki/Main_Page
and here is jerrytan93 talking about new kernal that is the most stable...
http://forum.xda-developers.com/showthread.php?t=1288765&page=3
post number #29 to #31
well i didn't find zimage of that kernel i'm still new in that
alright, time for serious talk...
of course batt-meter doesn't work. would've been a surprise. by not replacing zImage you kept ygge's kernel, just replacing the modules. (question is if the new modules even got unpacked to system)
thank you, i know where to download glemsom-autobuilds. ^^ but i prefer this link...
so remember, always replace both files! zImage is the more important one.
dunno why you shouldn't find it, it's called zImage_xxx_something_xxx. just rename it to zImage.
problem with most "cooks" here releasing roms is that they never tell which kernel they're uploading with their builds. just useless blabla like "the most stable, the best...!!!"
so here's an easy guideline:
- battery shows correct percentage, charging is buggy, hw-keys stop working -> ygge-kernel (march 2011)
- battery always shows 100% -> xdandroid-build ("glemsom") or a kernel based on it (midnight)
in theory, charging works on glemsom, bug with hw-keys is fixed
the reason why you get higher scores with ygge is because it has gpu overclocked (ygge-turbo < ygge-monster), glemsom doesn't. midnight's kernel has gpu overclocked too, it's faster.
agreeing with you apsolutley 100%
They only upload new build but newer talking about the kernels, few kernels didn't work for me because they are highly overclocked so didn't boot at all, i lost so many time studing for reason but i figured later it is from kernel...
Well keeping than my 11 march kernel 890kb it is working fine but have some bugs that i can handle with...
Thank you about sharing your knowledge and links nobody is talking about kernels and threads and posts are so messy with kernel information...
I have now two androids on 2 separete sd cards on
1. is hendroid here is my comparison with samsung galaxy 3.
http://www.youtube.com/watch?v=xU0dM168DDE
2. is sensdroid v5 which is better it looks good and it stable enough for daily use without need for windows mobile.
Did you try arcdroid v2?
On each android build my market is not working as i should, do you know reason for that and is there a fix?
I download stock gapps with everybuild.
good. but listen, you're mixing things up again.
- i wrote gpu-overclock, as in graphics (not cpu). this has nothing to do with what you set in startup (=cpu-speed), gpu-clock is fixed.
- keep zImage as well, it's the most important part! (kernel-files always have 2.x mb in total)
nope, tried almost none of these roms. if i'm not running nand for fun, i'm running neofroyo.
not interested in themed roms which are based on neofroyo anyway. the android-part in my sig is there for a reason.
I am a newer about this, waiting for a stable nand andriod system.
---------- Post added at 06:25 AM ---------- Previous post was at 06:24 AM ----------
There are so much I can't understand , Admire you so much!
Here is quote from jerrytan93 how to roll back Market to 3.13 version and stop future updates. This is major problem on all android version so i found it to be useful:
"Apps not compatible is because of the lastest version of Market, Market had updated automatically from 3.1.3 (originally in GAPPS package) to 3.1.5 version which was unstable now. I found some a solution for you all:
Use Terminal Emulator (if you don't have it, download in Market),type the following command:
su *PRESS ENTER TO GAIN SUPERUSER PERMISSION*
pm disable com.android.vending.updater *PRESS ENTER AGAIN*
This will disable the Market Updater from updating the Market.
After that, go to Settings > Applications > Manage Applications > Market > 'Uninstall updates' and then 'Clear data'
Your market will roll back to previous version. "
@caliban2 thanks, i messed some things when extracting the glemson kernel, the same problem for me battery is 100 % all the time.
Notify me when there would be best kernel out.
I don't use the market at all....can download apps from many other webs,try to use ucweb.apk which can download from www.uc.cn
haa~~~new nand android can be tested now,for i can't post in XPERIA X1 Android Development,i just say thx to Alex here!!!
Related
Hello all,
I'd like to ask which is the best distribution of Android for Kaiser - I mean everything working fine and so on.
I have HardSPL 3.29 and Radio 1.70.19.09 .. I tried one distro (Froyo 2.2 - Incubus26Jc's Super FroYo RLS14 All Languages) but when I started it.. it runs some time then the screen goes dark like sleep.. but when I press the power the screen image is broken... like white lines on the screen.. (this happens on both Incubus Super FroYo and Myn's Donut) ... I don't know is there some additional software that should be installed...
I use starting with HaReT via SD card...
I appreciate any help... Thanks in advance!
Best Regards,
Dimitar Dimitrov
The screen problem is wrong panel type, edit the default.txt in andboot folder, change the panel type, (board-htckaiser.panel_type=X), it can be either 1,2 or 3, if the display looks fine apart from sleep issues when you press power key, chances are you have a panel type 3, panel types 2 and 3 display the same, but have sleep issues if you choose the wrong one.
As for the best build? That is something you have to find out for yourself, not being funny, just that everyone has a different idea of 'best'
Thanks a lot!
Okay about the distribution... As I am new to Android at all... Can you please tell me your opinion about which distribution is working on kaiser (probably one you have tested and you are happy with it)
Thanks once again!
Kind regards!
Depends on what you want.
If you want speed, go with Myn's Warm Donut.
If you want to more apps, and less speed, go with Eclair.
If you want the latest apps and even less speed, try Froyo.
Thank you I'll try which one is working well on my kaiser and i'll choose one.. sorry for stupid questions anyway just i think it is better to ask someone who passed by those kinds of issues
MykoB said:
Okay about the distribution... As I am new to Android at all... Can you please tell me your opinion about which distribution is working on kaiser (probably one you have tested and you are happy with it)
Click to expand...
Click to collapse
I think I have tried all of them, and only 1 is working fine and fast for me: dzo's froyo (currently 26-08-2010). http://forum.xda-developers.com/showthread.php?t=715402 (get it here: http://sourceforge.net/projects/androidhtc/files/ ) (the latest builds include all of the fixes, you don't need to patch anything after installing).
I am running it with haret on the SDcard. It's so fast and smooth I don't even feel the need to flash it to the nand (which would work even faster).
The eclair builds, (polymod 2.1d, etc...) even with compcache enabled they are too slow. Cyanogenmod is also extremely slow, and it was also freezing while the phone was sleeping). And the Donut builds are lacking features.
On my kaiser the dzo froyo build is at least as fast as the fastest donut builds I have used, and it's rock stable. Far better than the eclair and other froyo builds like cyanogenmod.
PS: do not use any "unodexed" or "deodexed" builds. They are slower.
nemuro said:
Depends on what you want.
If you want speed, go with Myn's Warm Donut.
If you want to more apps, and less speed, go with Eclair.
If you want the latest apps and even less speed, try Froyo.
Click to expand...
Click to collapse
If you want the latest apps and the best speed and the best stability, try dzo's froyo.
On my kaiser this build feels like it came flashed originally instead of windows mobile. In comparison, the other builds felt like "hacks": slow and/or buggy.
Myn's RLS5 is the best for my kaiser.
And what about battery life?, Cyanogen literaly drain power in a few hours, froyo from dzo is better, but still is a problem for these builds.
Any recommendation?, the old Donut build battery lafe is the best (at least for me) but after several days the phone signal drops to zero, and i cant recover it !!
Please, your comments, thanks in advance!
yap i have same problem with phone signal. i wonder why...
Had this problem with a number of builds, turns out that using the 1.71 radio was the problem, reflashing 1.65 radio cured my 'No Signal' problems, sometimes latest is not always best
zenity said:
Had this problem with a number of builds, turns out that using the 1.71 radio was the problem, reflashing 1.65 radio cured my 'No Signal' problems, sometimes latest is not always best
Click to expand...
Click to collapse
I will try this, is terrific news !! at leas for me, haha.
Thank you !!
Regards
BigMango said:
If you want the latest apps and the best speed and the best stability, try dzo's froyo.
On my kaiser this build feels like it came flashed originally instead of windows mobile. In comparison, the other builds felt like "hacks": slow and/or buggy.
Click to expand...
Click to collapse
I downloaded the latest system-WHATEVER for dzo's froyo...on my hd2 you unzip a zip...extract Android dir to SD card and run haret to start android....where exactly is haret and the other things to actually boot the system? It's not in the .tgz's being posted in that sourceforge dir.
zenity said:
Had this problem with a number of builds, turns out that using the 1.71 radio was the problem, reflashing 1.65 radio cured my 'No Signal' problems, sometimes latest is not always best
Click to expand...
Click to collapse
good new, but unfortunatly is not the only problem...did you solved battery draind issue? if yes let me know pls
BigMango said:
If you want the latest apps and the best speed and the best stability, try dzo's froyo.
On my kaiser this build feels like it came flashed originally instead of windows mobile. In comparison, the other builds felt like "hacks": slow and/or buggy.
Click to expand...
Click to collapse
This has been my experience too. I tried several of each of the donut/eclair/froyo builds but the lastest kernel along with dzo's fresh froyo have made a world of difference. Way faster than even the donut builds that had previously been the faster of all of them.
famewolf said:
I downloaded the latest system-WHATEVER for dzo's froyo...on my hd2 you unzip a zip...extract Android dir to SD card and run haret to start android....where exactly is haret and the other things to actually boot the system? It's not in the .tgz's being posted in that sourceforge dir.
Click to expand...
Click to collapse
HaRET is a separate tool, you can get it here.
2011 Builds
Hi
I see that no new builds are posted and for all the latest downloads are from 2010.
I tried using aTools and also downloaded new Froyo from SourceForge.net, but no luck - Android hangs. What other files should be updated to for all to work?
I understand, that aTools ia a mgnificent tool, and everybody can "cook" his own version at home, but it is not totally clear regarding what should be used as basefiles, or if you download a distribution (like i did system-froyo-all-odex-29-08-11_19-patched.tgz) will it properly work, or what should be done to work.
Any advices?
I just erased my CyonogenMod because was a bit slow and as i read, DZO froyo should do it.
Creating the defaul.txt is not a problem. My concern is the zimage, the initrd and the androidinstall to work together properly.
Cheers
---------- Post added at 04:25 PM ---------- Previous post was at 03:31 PM ----------
OK? solved: i had to swith aTools to use a Stable branch and downloaded another initrd. Now all went smooth, and i have latest android on my Kaiser - working fast.
No FileManager, but WiFi works, so as Market, so just download
As a last step, i created with atools an androidupdate file to change my keyboard settings.
That's it.
Astro was not showing up in Market so i went here and downloaded the apps / widgets as a standalone update: forum.smartphonejunkie.com/windows-mobile-apps/202417-dzos-fresh-froyo-2-2-odexed-vanilla-rls6-7-2-10-a.html
I have a single problem now: market does not show all the apps. I search for something, gives me 411 results, but shows only 2 apps. Why is that?
How can market be fixed?
7th September 2010, 01:58 AM
Click to expand...
Click to collapse
This thread is a YEAR old. Of course there are newer roms after that date
I know there are newer roms, but had not been posted. But no problem, i found what i wanted, and i installed Android. Fixed market also.
I have another problem, and maybe i can reformulate the topic's title:
Which Android build is best for Kaiser's battery life?
I mean, the newest froyo drained my battery in one night. Windows Mobile last 3-4 days - depending on the use.
Tough question?
In the androidupdate there are the kernel's modules.
I release only the vogue but you can change device/panel ecc with nbheditor
Remember to install androidupdate for wlan and other parts
Main features
No yaffs2 tragedy and no data loss on nand
Working camera
UP 23-09
n2rjt mod battery for polaris and kaiser (updated)
UP 19-09
Fixed power collapse (new)
using n2rjt mod battery for polaris and kaiser
Make a full charge circle to get good results
TODO
Fix battery
Fix sdhc support
Modules unchange
Download file from here
What is the general difference between this branch and the one that everyone downloads from dzo's site?
Has kalt a similar site for actual downloads like dzo?
Is this nbh restricted to a build like latest fresh froyo/incubus? For what is the update? Could you explain it a bit more detailed?
Thank you for this post ;D
This is the old branch so it's more stable
dzo stopped develop it on 2010-07-25 (and started with 2.6.32)
the updates are:
-> k_k: tether
-> k_k: battery for polaris/kaiser
-> l1q1d: support for lzma initrd
changelog here
l1q1d said:
This is the old branch so it's more stable
dzo stopped develop it on 2010-07-25 (and started with 2.6.32)
the updates are:
-> k_k: tether
-> k_k: battery for polaris/kaiser
-> l1q1d: support for lzma initrd
changelog here
Click to expand...
Click to collapse
Noob question, actually i really wanna ask this since the new initrd released.
What is the difference between the previous initrd and the new one ?
Thanks
support for relocate_apps fixed by k_k
parted inserted by me
could you plz be so kind to timestamp your releases, as it makes things way easier! is this the same kernel you've posted friday in polaris-forum?
just noticed some complete hangups with that one... but didnt loose any data and feels quite good on pola! thought it could be a sdcard-thing, but swithing back to old one didnt solve that... thx anyways, much better (for now!) than the new tree.
alexinc said:
could you plz be so kind to timestamp your releases, as it makes things way easier! is this the same kernel you've posted friday in polaris-forum?
just noticed some complete hangups with that one... but didnt loose any data and feels quite good on pola! thought it could be a sdcard-thing, but swithing back to old one didnt solve that... thx anyways, much better (for now!) than the new tree.
Click to expand...
Click to collapse
+1 to everything you mention here!
The complete hung up is due to battery level:
th battery sensor goes down and android shutdown the system (no data loss).
After one or two complete charging and discharging that problem disappears for me.
Eyecandy lover - Splash screen ?
Suggestion, could this new initrd and/or kernel will support for splash screen or graphical GRUB ? or maybe the new one will support it ? I hope you can develope on this thing, just to make our device more beautyfull.
androidupdate...
Sorry for the very basic question but how to install the androidupdate?
Use atools or boot menu
Battery
Hi,
I used the previous version of the kernel. I experienced that the standby time increased from 1 day to 2 days
I'm curios about the new release ... now flashing ...
Thanks
is there a chance to get the cam working for the pola (100)??
or is the kernel section wrong for this issue (as it already worked some time ago...)?
Use atools and change device. I release only vogue but it works with all devices.
Stable, but battery still on 52%
Hi,
I trying this release for a day (with latest Froyo RLS15) and it is very stable on my Pola100 BUT, the battery percent stops at 52% and it isn't reduced for half day ago. I try to restart the phone, but nothing changes, the battery percent still in 52%. I'm curious when the phone power down
i'll release soon a new version with latest battery update (i'm testing it on 2.6.32)
l1q1d said:
i'll release soon a new version with latest battery update (i'm testing it on 2.6.32)
Click to expand...
Click to collapse
Thank you again for all the hard work.
The latest kernel VOGUIMG-320-FROYO19-09-10.NBH looks like giving my vogue an extra battery life.
After flashing and update .tar file, i think the batterystats.bin file should be deleted, otherwise the battery level will jump over again.
Hope that help someone who want to apply this update.
Btw, in the other thread, someone post about filesystem comparison, nilfs. Is it better than we use now? willing to try that as an experiment ?
The real problem isn't the fs but the nand driver that is buggy.
i did somr test with jffs2 but nand driver isn't complete so we can't format with it
More stable than 2.6.32)
Thanks! I've been running this since yesterday and it's proven much more stable than Dzo's 2.6.32 kernel that I'd been running. I'd had problems with that one going to sleep and not waking. This one doesn't have that problem
Anyone know what I'm giving up by moving back off the 2.6.32 kernel?
This is Froyo Sense coming to Vogue...
Calling does not work!!
The latest kernel 240x320 works the best.
It runs about as fast as Super Hero with no Overclocking when WildVogue is oc'ed to 520 mhz with Rogue tools
It runs from a system.img but i am working to strip it down to NAND
Data should be put on NAND
I have no clue if this will work on Polaris or Kaiser(It'd be helpful if someone could try...)
here are some preliminary screenshots(attached).
This preliminary(Beta) build:
Thanks vellowax for all the help
Thanks Thoughtlesskyle for your kind suggestions
And the whole community for all the previous work that helped me get here.
Its a port from WildPuzzle v8 for Wildfire
the androidinstall.tar is here
I'm looking for help learning and developing it but I'm coming along
This is a Beta I have no responsibility whatsoever if you brick your phone
If you have any suggestions please reply in this thread
Lovely!
jholtom said:
This is Froyo Sense coming to Vogue...
Calling does not work!!
...
I'm looking for help learning and developing it but I'm coming along
This is a Beta I have no responsibility whatsoever if you brick your phone
If you have any suggestions please reply in this thread
Click to expand...
Click to collapse
I will try this when calling works but keep your progress--make it mature!
Your download link doesn't work
I figured it out, but you might want to edit it and correct it.
I'll do some testing with this as I have a spare phone that's not activated.
jholtom said:
I have no clue if this will work on Polaris or Kaiser(It'd be helpful if someone could try...)
Click to expand...
Click to collapse
Excellent Jholtom, I've linked this thread in Kaiser forums, If noone will be brave enough to try it out I will test it in the afternoon. Great job!
link is doesnt work if i download this ill try yhe kaiser but icant download this link
The link is fixed now
can not install kaiser because low memory on nand
What Kernel are you using for this jholtom ?
I tried using the 11/29/10 2.6.32 kernel and was getting an error message.
I'll try again with the 10/29/10 2.6.32 kernel
Will give this a try.
I have it installed on the kaiser. It took a little work but its on. It will only work in 320x240 and with at least 200 mb for sys and then use an ext2.img for data. One problem I am having though is that all the HTC setup apps fc. I am going to try just removing them and see how that works. I used an old october kernel as I tried to update to the 11/29 one and was getting a module error and did try the android update and it didnt solve it so I rolled back.
trashed my super froyo so i guess ill give this a try........
great jobs,i'll give it a try
I managed to actually get into the rom finally. I took a setupwizard from a froyo rom and used it. I had to really fight with it though. The wizard ran poorly, and the date and time settings at the end kept fc'ing looping it back to the beginning of the wizard until finally it went into the rom. Going to test it now. I do not believe its a phone issue but a build issue as of right now. If you could remove the date and time settings it is referring to then I think it might be a bit better.
To run on the kaiser so far i've had to:
Set resolution to 320x240, Change partition to be 200 MB on SYS and rest on DATA via ext2.img . Afterwards I took a setupwizard.apk from a froyo rom and then renamed and replaced the HTCSetupWizard.apk the rom included as that was contributing to FC's.
On the kaiser wifi and the radio are not working. Both get an error when attempting to be used. I am going to try bringing in a etc folder from a working froyo rom and see if that solves the issue.
Lastly there is a power issue on the kaiser. It seems to keep thinking its almost near dead while on usb even though in the kernel it shows the proper power levels.
OK...
Tried this on my Vogue
the 10-31-10 2.6.25 NBH kernel will work.
BUT!!!
Do NOT try this on a class 2 card - OMFG... WAY too slow
Class 4 or class 6 at least...
Hopefully you can fit it in NAND soon?
aceoyame said:
I managed to actually get into the rom finally. I took a setupwizard from a froyo rom and used it. I had to really fight with it though. The wizard ran poorly, and the date and time settings at the end kept fc'ing looping it back to the beginning of the wizard until finally it went into the rom. Going to test it now. I do not believe its a phone issue but a build issue as of right now. If you could remove the date and time settings it is referring to then I think it might be a bit better.
To run on the kaiser so far i've had to:
Set resolution to 320x240, Change partition to be 200 MB on SYS and rest on DATA via ext2.img . Afterwards I took a setupwizard.apk from a froyo rom and then renamed and replaced the HTCSetupWizard.apk the rom included as that was contributing to FC's.
On the kaiser wifi and the radio are not working. Both get an error when attempting to be used. I am going to try bringing in a etc folder from a working froyo rom and see if that solves the issue.
Lastly there is a power issue on the kaiser. It seems to keep thinking its almost near dead while on usb even though in the kernel it shows the proper power levels.
Click to expand...
Click to collapse
@aceoyame
you are on a kaiser right?
Everything works fine on my vogue running 240x320 2.6.32-froyo-09/10/21 kernel
I get through the setup wizard fine and it runs pretty darn fast for sense when overclocked to 545 with Rogue tools
Wifi and radio have not been repaired yet from froyo i'm working on
Remember this is a Beta build
Does_It_Matter said:
OK...
Tried this on my Vogue
the 10-31-10 2.6.25 NBH kernel will work.
BUT!!!
Do NOT try this on a class 2 card - OMFG... WAY too slow
Class 4 or class 6 at least...
Hopefully you can fit it in NAND soon?
Click to expand...
Click to collapse
@Does_it_Matter
What device are you on?
I would try the 240x320 2.6.32 froyo 09/10/21 kernel for vogue(if thats what you have)
I dont know for kaiser of polaris
The build itself is a decent speed but the problem is, your not able to clock up with rogue tools until after you have everything set up. So default were at 400 mhz which is dirt slow. As for the kernel, I don't believe thats going to make a difference here. I did try to merge the etc folder with fresh froyo's and it made no difference. I thought maybe the missing wifi levels folder and a couple other things would help.
That means our problem is deeper somewhere else for those. Also, I would include rogue tools in the build itself to save some hassle downloading it at slow speeds.
fyi, i'm a kaiser developer. I know I never post on the vogue or polaris forums.
jholtom said:
@aceoyame
you are on a kaiser right?
Everything works fine on my vogue running 240x320 2.6.32-froyo-09/10/21 kernel
I get through the setup wizard fine and it runs pretty darn fast for sense when overclocked to 545 with Rogue tools
Wifi and radio have not been repaired yet from froyo i'm working on
Remember this is a Beta build
Click to expand...
Click to collapse
I am using L1qu1ds .32 kernel dated from 10/29/2010. It isn't a kernel issue that I am having but like I said, rogue tools cannot clock up the build until after installation.
aceoyame said:
I am using L1qu1ds .32 kernel dated from 10/29/2010. It isn't a kernel issue that I am having but like I said, rogue tools cannot clock up the build until after installation.
Click to expand...
Click to collapse
> /sys/module/clock_7x00/parameters/ahb_div
echo 500 > /sys/module/clock_7x00/parameters/a11
add that to the top of the userinit.sh to have it overclocked to 500mhz from the getgo. It will be overclocked throughout the boot process.
Thanks mssmison for the info.
incubus26jc said:
> /sys/module/clock_7x00/parameters/ahb_div
echo 500 > /sys/module/clock_7x00/parameters/a11
add that to the top of the userinit.sh to have it overclocked to 500mhz from the getgo. It will be overclocked throughout the boot process.
Thanks mssmison for the info.
Click to expand...
Click to collapse
Thats not the same as overclocking through atools right? I know that through a tools the kaiser gets unstable as all hell. For some reason it doesnt with rogue tools.
is it possible to run a donut rom like superD 1.11 with a 2708+ kernel? has anyone done this? which kernel did you use --- pershoots? ezterrys?
thanks guys
---nevermind, answered. gonna try installing ezterry's original *crosses fingers*
acidwashg1 said:
is it possible to run a donut rom like superD 1.11 with a 2708+ kernel? has anyone done this? which kernel did you use --- pershoots? ezterrys?
thanks guys
---nevermind, answered. gonna try installing ezterry's original *crosses fingers*
Click to expand...
Click to collapse
Good luck but it works so u dont need luck
okay, so im using pershoots latest kernel with superD 1.11
two issues:
1. camera does not work. i expected as much using a kernel that was built to be run with froyo. but is there any way to fix this?
2. awful battery consumption. after unplugging my phone this morning, the phone ate up about 20% of the battery in less than 15 minutes. I am not overclocking at all, and I have setcpu running with conservative profiles enabled.
im gonna try ezterry's kernel and see if it helps with these issues.
anyone have any ideas or solutions?
Ehh even with the 2708 kernel etc battery should last longer look at ur battery is it flat? or a little bulge?
acidwashg1 said:
okay, so im using pershoots latest kernel with superD 1.11
two issues:
1. camera does not work. i expected as much using a kernel that was built to be run with froyo. but is there any way to fix this?
2. awful battery consumption. after unplugging my phone this morning, the phone ate up about 20% of the battery in less than 15 minutes. I am not overclocking at all, and I have setcpu running with conservative profiles enabled.
im gonna try ezterry's kernel and see if it helps with these issues.
anyone have any ideas or solutions?
Click to expand...
Click to collapse
Try flashing the kernel from this post over SuperD. It basically gives the camera app more space, so that it works. As a result, you will have a little less RAM, but the camera should work, as it is designed to be used on pre-froyo ROMs.
I have a question: do you also have awful video performance on every donut rom, when you have 2708 radio? Every donut I flash is extremely fast, but its 3d speed is similar to rom with ramhack. Is there any solution? I used pershoots and ezterrys kernel, but it didn't work
MattDrumz said:
Try flashing the kernel from this post over SuperD. It basically gives the camera app more space, so that it works. As a result, you will have a little less RAM, but the camera should work, as it is designed to be used on pre-froyo ROMs.
Click to expand...
Click to collapse
ezterry said:
If you are trying to get the new radio to work with older roms and experience camera issues: I've a slightly reduced ram version of the kernel that allows camera the full 8MB.
http://sandbox.devnull.name/android/ezOldBuildsKernel-2708_S.zip
MD5: 84cf7c7d2a923eed962aef5e1a6a94e9
This will work on CM4/5 however the install is not as trivial as just flashing some potential problems you may need to solve:
* Different path to the modules (move to correct place or add a symlink)
* old version of rzscontrol giving typewriter errors (pull the binary in recent cm builds and replace)
* modules not loaded by default that are needed (edit an init.d script)
Once these actions are made your rom will likely work as expected. I provide this file to help you port your older roms to the newer radio; not as a quick patch that will make everything work on its own. (For that I make things like the new CM5 2708 port where I manually cleanup the system in the updater.zip)
Kernel source code at:
https://github.com/ezterry/kernel-biff-testing/commit/293de79ddd313bbccb06b6cddd1cdef3de9af797
Click to expand...
Click to collapse
Anyone done this? It's a bit beyond me..
Hello! First timer here to flashing and custom ROMing and have read as much as I possibly can but need some clarification before I proceed.
Background:
Let my family borrow my iPhone 4S while they travel so I'm using this SGH-T679. I have to stay in touch with them via Viber, Skype, and Hangouts (using GVPhone for Google Voice calls). After installing those apps the phone slowed down to a crawl and became a very frustrating experience;
the specs at this time were Android 2.3.5 and Baseband T679UVKJ1, stock and unrooted.
After reading that T-mobile released 2.3.6, I followed the upgrade instructions here;
now the specs are Android 2.3.6 and Baseband T679UVLK2, stock and unrooted.
For awhile I thought it was going well, but now I'm back to having frustrating experiences. It seems like memory management is terrible.
Desire:
I wonder if one of the KitKat roms will help alleviate some of the memory issues and better support the communication apps I need. Any advice? Or should I go with a custom Gingerbread or ICS ROM?
I'm leaning towards CyanogenMod 11 20140714-UNOFFICIAL by jfbs (however I also see a thread for CM11 by cars1189 but I can't figure out the difference, maybe question for a different thread).
[Q]:
I understand the first step is to install a Recovery. In the ROM thread the options are listed as:
CWM 6.0.5.0 md5sum: 4bfb28bcf29dc04243df246860f24940
Recovery for flashing in Odin CWM 6.0.5.0 md5sum: b5856bd395248af1c74dac8b92cd258e
So can I just transfer "Odin CWM 6.0.5.0" to root of device and install via powering on the phone and entering stock recovery by pressing & holding Power + Volume-Down?
When the phone was on 2.3.5, Power + Volume-Down and Power + Volume-Up (ODIN Download Mode from what I understand) yielded different modes. But now on 2.3.6, only Power + Volume-Down yields any kind of recovery option. That's why I'm wondering if installing CWM via stock recovery still holds for Android 2.3.6.
Appreciate you reading and thanks for your help!
ZHXS said:
Hello! First timer here to flashing and custom ROMing and have read as much as I possibly can but need some clarification before I proceed.
Background:
Let my family borrow my iPhone 4S while they travel so I'm using this SGH-T679. I have to stay in touch with them via Viber, Skype, and Hangouts (using GVPhone for Google Voice calls). After installing those apps the phone slowed down to a crawl and became a very frustrating experience;
the specs at this time were Android 2.3.5 and Baseband T679UVKJ1, stock and unrooted.
After reading that T-mobile released 2.3.6, I followed the upgrade instructions here;
now the specs are Android 2.3.6 and Baseband T679UVLK2, stock and unrooted.
For awhile I thought it was going well, but now I'm back to having frustrating experiences. It seems like memory management is terrible.
Desire:
I wonder if one of the KitKat roms will help alleviate some of the memory issues and better support the communication apps I need. Any advice? Or should I go with a custom Gingerbread or ICS ROM?
I'm leaning towards CyanogenMod 11 20140714-UNOFFICIAL by jfbs (however I also see a thread for CM11 by cars1189 but I can't figure out the difference, maybe question for a different thread).
[Q]:
I understand the first step is to install a Recovery. In the ROM thread the options are listed as:
CWM 6.0.5.0 md5sum: 4bfb28bcf29dc04243df246860f24940
Recovery for flashing in Odin CWM 6.0.5.0 md5sum: b5856bd395248af1c74dac8b92cd258e
So can I just transfer "Odin CWM 6.0.5.0" to root of device and install via powering on the phone and entering stock recovery by pressing & holding Power + Volume-Down?
When the phone was on 2.3.5, Power + Volume-Down and Power + Volume-Up (ODIN Download Mode from what I understand) yielded different modes. But now on 2.3.6, only Power + Volume-Down yields any kind of recovery option. That's why I'm wondering if installing CWM via stock recovery still holds for Android 2.3.6.
Appreciate you reading and thanks for your help!
Click to expand...
Click to collapse
install cwm via odin, Jfbs posted link for odin pc app that is needed to do it in one of his rom ops i believe in the same op as the rom your are pondering on upgrading to. either way you need the odin files and usb drivers. as far as a rom with better memory and faster performance well any kk rom will do that or for older roms cars1189 CM Mass OP as cm10 and 10.1. reason being the new hybrid ion/pmem. compared to the old stock pmem based. now if you want battery battery life and even faster performance use a oc kernel and use an app like performance control to change the voltage and cpu frequency settings to your liking you can check my op in gen section for our phones for more details and guide for it.
EDIT yes the files are in the that rom op you mentioned 3 post down xD
I'm not a dev but from my experience with Viber, I have learned that this app uses a lot of memory. I have stopped using it for awhile cuz it was using over 30mb of my ram. So the best advice I have for you is not to install apps that you won't use often. Just use the strict minimum. For the memory management I also use Greenify to put asleep any app I'm not using often. This app in my case doesn't use over 5mb of ram but saves me over 50mb of memory when needed. But just be wise when selecting which apps to put asleep. I also use NovaLauncher as it is faster then any other I've tried and it's not hard on memory cache. Also other adive like @TripFX said, any KitKat rom can help you with memory management and performance. Me i use the lastest build of CM11 by @cars1189 with the Christopher oc kernel.
---------- Post added at 10:59 PM ---------- Previous post was at 10:47 PM ----------
theking1st said:
I'm not a dev but from my experience with Viber, I have learned that this app uses a lot of memory. I have stopped using it for awhile cuz it was using over 30mb of my ram. So the best advice I have for you is not to install apps that you won't use often. Just use the strict minimum. For the memory management I also use Greenify to put asleep any app I'm not using often. This app in my case doesn't use over 5mb of ram but saves me over 50mb of memory when needed. But just be wise when selecting which apps to put asleep. I also use NovaLauncher as it is faster then any other I've tried and it's not hard on memory cache. Also other adive like @TripFX said, any KitKat rom can help you with memory management and performance. Me i use the lastest build of CM11 by @cars1189 with the Christopher oc kernel.
Click to expand...
Click to collapse
Another advice also is to avoid modding too much your user interface cause for a phone like this it will make it slower, from my experience. Hope I could help! . (All these suggestions are from experiences i had and that helped me better manage my phone performances.) ?
TripFX said:
install cwm via odin, Jfbs posted link for odin pc app that is needed to do it in one of his rom ops i believe in the same op as the rom your are pondering on upgrading to. either way you need the odin files and usb drivers. as far as a rom with better memory and faster performance well any kk rom will do that or for older roms cars1189 CM Mass OP as cm10 and 10.1. reason being the new hybrid ion/pmem. compared to the old stock pmem based. now if you want battery battery life and even faster performance use a oc kernel and use an app like performance control to change the voltage and cpu frequency settings to your liking you can check my op in gen section for our phones for more details and guide for it.
EDIT yes the files are in the that rom op you mentioned 3 post down xD
Click to expand...
Click to collapse
Hey! So I wanted to post an update about my experience...
After realizing the reference to Odin is actually a PC application, I decided to just install via Samsung Recovery.
Unfortunately from Power Off, pressing the Power + Volume Up buttons did not start recovery.
I had to use the method from the XDA Exhibit Wiki:
Pull the battery from your phone.
Connect phone to your pc via usb.
Press & hold Volume-up
Insert battery
Click to expand...
Click to collapse
It's weird because on stock 2.3.5 I was able to start recovery from Power Off, but after OTA 2.3.6 baseband T679UVLK2 it no longer works. I wonder if flashing baseband T679UVLG3 or flash2stock will get back that ability. Anyway, I might try that later, right now it's setup with what I need.
I flashed CM11 by jfbs and it's working quite smoothly. Even when free memory drops below 100MB it works well. Amazing what a ROM change can do
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I read your OC and UV to perfection safely and easy guide !!! and I'm definitely bookmarking it for future exploration. Sometimes the battery gets so warm that I'm more comfortable leaving it in stock settings for now.
theking1st said:
I'm not a dev but from my experience with Viber, I have learned that this app uses a lot of memory. I have stopped using it for awhile cuz it was using over 30mb of my ram. So the best advice I have for you is not to install apps that you won't use often. Just use the strict minimum. For the memory management I also use Greenify to put asleep any app I'm not using often. This app in my case doesn't use over 5mb of ram but saves me over 50mb of memory when needed. But just be wise when selecting which apps to put asleep. I also use NovaLauncher as it is faster then any other I've tried and it's not hard on memory cache. Also other adive like @TripFX said, any KitKat rom can help you with memory management and performance. Me i use the lastest build of CM11 by @cars1189 with the Christopher oc kernel.
---------- Post added at 10:59 PM ---------- Previous post was at 10:47 PM ----------
Another advice also is to avoid modding too much your user interface cause for a phone like this it will make it slower, from my experience. Hope I could help! . (All these suggestions are from experiences i had and that helped me better manage my phone performances.) ?
Click to expand...
Click to collapse
Appreciate your tips. You're right about Viber and communication apps, they're all using between 20-30MB each, but I need them so I'm leaving them on for now.
I'll definitely have to check out Greenify.
Also appreciate your tip about NovaLauncher, as I witnessed a few niggling issues with Trebuchet Launcher upon initial boot up after flashing the ROM.
I've limited my UI customization based upon your advice, I just have one page for apps and Google Now page to the left (I initially installed BaNkS GApps Minimal 4.4.4 but then flashed on top GApps Minimal GoogleSearch and AOSP Calendar Sync Addonas I was missing typing by voice and calendar events).
Do you know if there is a post/thread where I can find out the difference between kernels available for this phone?
I see for CM11 by cars1189 that there is ADC/Linaro Kernel and Christopher K^Kernel, but I can't find a comparison between the two.
Thinking of Future: Is it ok to dirty flash CM11 by cars1189 over CM11 by jfbs, or is formatting everything recommended?
Thanks for the replies fellas!
as far as basebands go that jfbs posted. either will work and there really isn't i a difference between the 2 and flashing either one should cause any harm to you phone that i'm aware of as i have personally tried both on same phone.
personally i never dirty flash but thats just my preference. however dirty flashing cross rom authors i would definitely do a clean install even devs would agree with that.
as far as warm battery you could undervolt it without overclocking to reduce the temp more so then how much temp increase you get from upping the frequency. So no matter what i would find my cpu's lowest stable voltage as it will give you longer battery life and lower temps. as long as your stable voltage is under 1.200mhv however i haven't heard anyone not be able to use 1.100mhv at stock frequency. how ever i would still start from stock voltage 1.2mhv and lower by 0.025mhv (1.175) test it out for a bit open and close and so forth. then lower it again by same about. and do so for each frequency below what set max frequency for.
TripFX said:
as far as basebands go that jfbs posted. either will work and there really isn't i a difference between the 2 and flashing either one should cause any harm to you phone that i'm aware of as i have personally tried both on same phone.
personally i never dirty flash but thats just my preference. however dirty flashing cross rom authors i would definitely do a clean install even devs would agree with that.
as far as warm battery you could undervolt it without overclocking to reduce the temp more so then how much temp increase you get from upping the frequency. So no matter what i would find my cpu's lowest stable voltage as it will give you longer battery life and lower temps. as long as your stable voltage is under 1.200mhv however i haven't heard anyone not be able to use 1.100mhv at stock frequency. how ever i would still start from stock voltage 1.2mhv and lower by 0.025mhv (1.175) test it out for a bit open and close and so forth. then lower it again by same about. and do so for each frequency below what set max frequency for.
Click to expand...
Click to collapse
Ok, Clean Install it is.
As far as App + App Data Backup & Restore is concerned when flashing a new ROM, I have read about a variety of methods.
Method 1:
eushaun99 said:
You have to wipe system, cache and dalvik first then reflash your ROM and gapps.
Click to expand...
Click to collapse
Meaning, no need to Wipe Data. So all of your Downloaded Apps + Data will still be on the phone after flashing new ROM.
Method 2:
Wipe Everything.
Flash New ROM and Gapps.
Advanced Restore of Data and Cache Partitions via Recovery.
Method 3:
Wipe Everything.
Flash New ROM and Gapps.
Restore Apps + Data via program like Titanium Backup, ES File Explorer, etc.
I like the idea of Method 1, but I think you recommend Method 3?
What is your current ROM + Kernel setup if you don't mind me asking?
I think I may undervolt using the same settings from your OC and UV Guide. I figure it's the same phone, processor, etc.
ZHXS said:
Ok, Clean Install it is.
As far as App + App Data Backup & Restore is concerned when flashing a new ROM, I have read about a variety of methods.
Method 1:
Meaning, no need to Wipe Data. So all of your Downloaded Apps + Data will still be on the phone after flashing new ROM.
Method 2:
Wipe Everything.
Flash New ROM and Gapps.
Advanced Restore of Data and Cache Partitions via Recovery.
Method 3:
Wipe Everything.
Flash New ROM and Gapps.
Restore Apps + Data via program like Titanium Backup, ES File Explorer, etc.
I like the idea of Method 1, but I think you recommend Method 3?
What is your current ROM + Kernel setup if you don't mind me asking?
I think I may undervolt using the same settings from your OC and UV Guide. I figure it's the same phone, processor, etc.
Click to expand...
Click to collapse
I've had an issue in the past (Being builds of cm11) doing that but not during aoip days and had gapp issues. regardless of the 3 methods. as far as backing and restoring user apps+data. use es file explorer to copy apks to either sdcard. then connect phone to pc and make a new folder on desktop then copy all the apks and data to that folder. then after doing complete clean install and setting up the phone the way like it ( mods, advance settings, oc, uv, etc. then copy back over to sdcard then move the apks back to the original directory you pulled it from. However im just super cautious as it could have just be a fluke bug in cm11 that may have already been fixed. but as far as back up it which ever works best for you.
private testing mahdi build with rom. still using the settings that are in oc/uc guide. as far as kernels my phone does much better with jfbs stock rom kernels as they already have oc/uc support by default and has a much high user ram space that is stable. jfbs roms i think are for the more advance users that like to tweak everything where cars1198 is better for the everyday user. Hence why i use jfbs roms and wife uses cars1198 roms.
TripFX said:
private testing mahdi build with rom. still using the settings that are in oc/uc guide. as far as kernels my phone does much better with jfbs stock rom kernels as they already have oc/uc support by default and has a much high user ram space that is stable. jfbs roms i think are for the more advance users that like to tweak everything where cars1198 is better for the everyday user. Hence why i use jfbs roms and wife uses cars1198 roms.
Click to expand...
Click to collapse
Thanks for all the great info you've been providing!
Which Kernel is she using with cars1198's CM11? ADC/Linaro Kernel, Christopher K^Kernel, jfbs?
Judging from the last few pages of jfbs' CM11 OP, it doesn't appear he will update any longer
ZHXS said:
Thanks for all the great info you've been providing!
Which Kernel is she using with cars1198's CM11? ADC/Linaro Kernel, Christopher K^Kernel, jfbs?
Judging from the last few pages of jfbs' CM11 OP, it doesn't appear he will update any longer
Click to expand...
Click to collapse
K^Kernel hm and as far as jfbs it's hit and miss as far as newer roms and so forth go. Im not in a rush as he has done more than enough for our device and for free along with helping lots of users including but not limited to rude users. So expect him to do what he think is best and if someone doesn't like it they can just deal with it. I'm happy with the phone even as is. I mean this phone is uberly outdated hardware wise and has been really stressed to it limits even beyond anything rom before kitkat roms came out. However that's not to mention it prolly wouldn't have been possible without arco86, adc team, and others. So when/if he does i'm grateful for what he gives us. same for cars1198 and other devs on this site. Not saying anything bad about you but just giving a short version of where things are at.
FYI most people here on xda just prefer you either clicking the thanks button if you the post was useful or if it a bug related then logcats and brief description of the problem and wait patiently for someone who knows to either A) if dev - fixes it or asks for more info. B) if other user- tries to help you out if possible. Also as always even it something isn't to your liking the it would be wiser and nicer to post something like "Hey I really don't like X if you don't mind can you do X. If you are to busy or like X the way it is, that is fine and thank you for helping the community and good luck on you project."
TripFX said:
K^Kernel hm and as far as jfbs it's hit and miss as far as newer roms and so forth go. Im not in a rush as he has done more than enough for our device and for free along with helping lots of users including but not limited to rude users. So expect him to do what he think is best and if someone doesn't like it they can just deal with it. I'm happy with the phone even as is. I mean this phone is uberly outdated hardware wise and has been really stressed to it limits even beyond anything rom before kitkat roms came out. However that's not to mention it prolly wouldn't have been possible without arco86, adc team, and others. So when/if he does i'm grateful for what he gives us. same for cars1198 and other devs on this site. Not saying anything bad about you but just giving a short version of where things are at.
Click to expand...
Click to collapse
Totally agree with you on all points. I'm very happy with the current state - I'm not planning to move to another ROM anytime soon. The way I see it, most of the monthly updates appear to be incremental changes, and not something that will radically alter the core functionality of the phone.
It's amazing development still happening for this 3 year old device.
Alright! Looks like @ZHXS you've found all the answers you needed.
I'm using the latest CM11 build by @cars1189. I don't remember what the difference between both kernels in cars' thread is, but I definitely know that the Christopher kernel is for OC and UV because it is the kernel i'm using right now. I will check it out again and come back at you when I find out.
For flashing one ROM over the other one I have done it many times (I don't know if it is fine or not but from the replies I think that it's not recommended) but i didn't encounter any trouble. Just but sure to nandroid before you flash on top. Also if it is an update of the same ROM you are running, it shouldn't cause any trouble in the future. The only thing is that if you had Xposed framework activated before the update, after the update you will have to reactivate it again because with an update of the ROM, Xposed framework gets deactivated. Also I would recommend a nandroid before the update just in case. :good:
Also for the launcher, I have just found out that the home launcher of the Z3 has been ported and I tried it out. And I got to say, it is definitely faster than NovaLauncher in my phone. It takes less more time to go back when I press the home button from anywhere I'm in the phone. It doesn't have too much tweaks and personalisation like NovaLauncher, but hey with this phone the simpler the faster. The only down side with this launcher is that there is an empty spot under the dock that creates a waste of screen space. Here is one of my screenshot:
Click to expand...
Click to collapse
The thread author said that he(she, I don't know) is working on it so we might see a fix for it. But if you want to check it out, here it is: http://forum.xda-developers.com/crossdevice-dev/sony/port-xperia-z3-home-7-0-0-14-t2868655
That's all I had to say, happy to help you if you have any other question that I can answer.
I tested both kernels and it turns out that the ADC kernel looks like just a regular kernel. I had to do the flashing of the kernels on the 7-7-14 build because the ADC kernel was not available for the 8-28-14 build, and for the replies in the thread, the kernels for the 7-7-14 build and previous builds are not compatible with the 8-28-14 build. But I flashed it on the 7-7-14 build it did not show me any OC or UV settings and options. But I think that there is something else about this kernel that I don't know the presence of. But the Christopher kernel showed me OC and UV options so this kernel is definitely for OC and UV. There are also different versions of the Christopher kernel so you can check them out if you want.
And also the Xperia Z3 launcher port has been updated! The empty space under the dock has been removed. Looks like this now.
Click to expand...
Click to collapse
If you want to check it out make sure to download the Home-superuser-nonav.apk . It's done by @Sahaab (just wanted to s/o him)
theking1st said:
I tested both kernels and it turns out that the ADC kernel looks like just a regular kernel. I had to do the flashing of the kernels on the 7-7-14 build because the ADC kernel was not available for the 8-28-14 build, and for the replies in the thread, the kernels for the 7-7-14 build and previous builds are not compatible with the 8-28-14 build. But I flashed it on the 7-7-14 build it did not show me any OC or UV settings and options. But I think that there is something else about this kernel that I don't know the presence of. But the Christopher kernel showed me OC and UV options so this kernel is definitely for OC and UV. There are also different versions of the Christopher kernel so you can check them out if you want.
Click to expand...
Click to collapse
Wow @theking1st, going above & beyond testing the kernels! Thanks for the info man.
I'm kind of eager to OC now since after adding Google Search it's a bit slower again. I think I'll do that tonight, start fresh.:good:
ZHXS said:
Wow @theking1st, going above & beyond testing the kernels! Thanks for the info man.
I'm kind of eager to OC now since after adding Google Search it's a bit slower again. I think I'll do that tonight, start fresh.:good:
Click to expand...
Click to collapse
besides the oc and uc there they both use different optimizations and default kernel tweaks. Personally i like having the oc and uv option. you can make it run faster then stock while having lower temps and longer battery life as well as faster charging wile the phone is actually on. Powered off its the same no matter what ya do as far as how fast it charges. also if your fine with the speed i;d still recommend undervolting as you can run at stable at lower mv then stock. How low you can goes varies from person to person but in general im sure you can run 1.2GHZ @ 1.150mv compared to stock 1ghz @ 1.200mv. if ya can go lower stable then kudos for getting a lucky kudos for getting a decent made chip. follow my oc/uv guide in the gen section if your new to it and you will be just fine and safely.