As some of you know, I have encountered some problems while developing this ROM. Some very bad problems actually. Even though I've managed to fix them, it's not enough for me. The only way we can all enjoy VanillaEclair at the moment is to use 3.0, which has the most stable kernel yet, but unfortunately I haven't got the sources anymore.
I will continue my work on the OTA updater, on the kernel, on the framework and on A2DP. Also, I want to improve the VanillaEclair website, so that it can be a useful tool for us all. As I'm working alone, I can't do many things at a time. So please understand that this little break has a good reason behind.
Below you can find the links to VanillaEclair 3.0. If you want something more functional, I suggest you try MaXo64's aHero 1.0. I really do understand that you need a functional phone, and I am exactly in the same position, since the Hero I'm using for development is my everyday phone.
The ETA of VanillaEclair 3.3 is Sunday the 6th. Please post here for apps suggestions, feature requests and wish me luck! Cheers!
DOWNLOAD VanillaEclair 3.0
VanillaEclair 3.2 "Let me put a smile on that face" is the latest VanillaEclair build. For those of you who didn't flash the previous versions, this is the fastest and most stable vanilla 2.1 out here.
NOTE: From 3.1 I won't be supporting any issues if you're using JIT. If you're using it I assume that you are an experienced user. This ROM gives you enough performance, and you won't feel a performance boost after flashing JIT anywhere else than Linpack.
See posts #2 and #3 for more info related to the ROM. Discussions about 3.2 start from here.
Based on the latest 2.6.29 sources, provided by behnaam. Thanks.
Changelog:
- fixed battery issues
- added a few modules
- fixed auto brightness(it seems that this works only for newer phones)
- added EXT4 support
I would also like to say thanks to all users that have been reporting bugs, creating bootanimations and posting fixes. You have helped me improve this! You are great!
For info regarding overclocking, battery and such read posts #2 and #3.
Features:
- GPS & A-GPS
- 100% working youtube
- 100% working camera
- 100% working gallery
- facebook sync(100%)
- busybox
- root
- a quite large APN list
- VPN
- HUGE performance
Benchmark results * without JIT, [email protected]:
- Linpack: 3.35MFolps
- Neocore with sound: 30.1FPS
- Neocore without sound: 33.3FPS
Issues:
- A2DP(will be fixed soon)
If you're not using A2SD, you might get an insufficient storage error when trying to install apps from market. You can fix that in two ways:
1. wipe again after flashing the ROM
2.
adb shell
chown system.system /data/app
Click to expand...
Click to collapse
What's next?
- OTA updater after everything is 100% stable (if you can help me please let me know)
- A2DP, button lights
- backport BFS
- froyo
Because of the bad battery life and some other problems, I've decided to take the link down for the moment. The updated fixed version will be available tomorrow, the 1st of June. Sorry for the inconvenience.
{
"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"
}
Click to expand...
Click to collapse
If you like VanillaEclair, please help me buy a GSM Hero for Dev only.
HOW TO OVERCLOCK - noob-friendly tutorial with recommended settings.
Experienced users might use other settings.
1. Download OverclockWidget from Market (it's free)
2. Put the widget on your screen and make sure you allow it when the Super User permission request comes up(also check the remember option).
3. Reboot
4. Tap it once and select Advanced Setting
5. Check Differ Freq Screen off
Recommended settings:
Screen on: min- 691200 max- 691200
Screen off: min- 245760 max- 245760
6. Check auto start on boot and press save.
Notes:
- overclocking gives you a huge performance boost
- overclocking does not break your phone; it doesn't cause overheating
- overclocking will not affect your battery life(i've taken care of that)
Apps 2 SD FAQ:
1. How do I enable it?
It enables automatically is you have an EXT partition on your SDCARD.
2. Can I use EXT4?
No, sorry. Only EXT2/3 are supported at the moment.
3. What about dalvik cache?
Dalvik-cache is automatically moved on your EXT partition.
Battery tip
IF you're using VanillaEclair 3.1, you shouldn't need to recharge for about 3 days. If you can't get that much, follow the steps:
- wait until the battery is 5-10% left
- go to your recovery image and wipe battery status
- recharge your phone using the wall charger for 4-5 hours or so - you can leave it overnight
That's all!
More about Overclocking(for experienced users):
In VanillaEclair 3.1 I've included a wide range of frequencies that you can use. Here it is - Overclocking widget gets it automatically:
122880
160000
245760
352000
400000
480000
576000
595200
614400
652800
691200
768000
806400
Click to expand...
Click to collapse
I've been able to run at 806MHz, but the phone got VERY hot and sometimes unresponsive. The highest save to run in daily use frequency is 768MHz, but not all phones can go that far!
Downloading now!
Very curious about this one. Will report when I got it booted!
gawd!! i'm wetting LOL
did u try to turn on JIT on this rom? and what is result of linpack on jit?
is it based on cyanogen?
No JIT package?
I don't think you need jit @691MHz, but the JIT package and AS package will come in 30 minutes.
RaduG said:
I don't think you need jit @691MHz, but the JIT package and AS package will come in 30 minutes.
Click to expand...
Click to collapse
I can only OC @ 670, so I need it
I am flashing just now, I hope that will be your perfect build since on 2.0.3 I had a lot of problems
20Mhz won't make any difference
trashed78 said:
is it based on cyanogen?
Click to expand...
Click to collapse
+1
Thanks by the way
The kernel is based on benhaam's sources
I don't think speed is the real reason why adb not working. compares to nexus, hero's speed are very slow
Downloading now
Will try it out and post the feedback... can't wait!
witysimon said:
I don't think speed is the real reason why adb not working. compares to nexus, hero's speed are very slow
Click to expand...
Click to collapse
I didn't say that speed caused ADB not to work...
OK here goes
Please report if A2DP works... it should.
restoring my apps ....
damn i so feel like a 3 yrs old opening christmas pressie!!
RaduG said:
20Mhz won't make any difference
Click to expand...
Click to collapse
I was just kidding
Since I don't use application that seems to have problems with JIT, I always used it.
Related
THIS ROM IS NOT SUPPORTED ANYMORE FOR AN UNDETERMINED PERIOD OF TIME.
This is a 2.2 Sense ROM. Unfortunately, it still has two bugs, but even so it is usable, stable and fast.
ATTENTION! For those who already have 1.0-rel1 flashed, make sure you backup your data because flashing the ROM will wipe data even if you don't do it from recovery.
Note: There will be no other update until the Camera is fixed. Also, don't expect any updates in the next 1-2 weeks.
See post #2 for changelog and critical information.
{
"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"
}
What does not work:
- Camera
- Bluetooth audio WITH SOME DEVICES
Just so you know, I'm working hard to fix those issues, so don't panic, this will be updated soon. You might help me find other bugs if you test it. I can guarantee that if you don't need the camera, this ROM can work as an everyday ROM just fine.
What works:
- flash 10
- EXT-A2SD
- Calls, SMS, MMS
- Internet 2G/3G
- WiFi
- GPS/AGPS
- OpenGL
- lights
- accelerometer, sensors
- wired/wireless tethering
... everything else
+ Teeter - I've packed it so you can have a bit of fun?
Instructions:
Flash it and make a cup of coffee because the first boot takes AGES. Don't panic, it will eventually start ).
The custom kernel included is compiled from Erasmux's FlyKernel 12a. I've just enabled my dual-governor configuration and made the changes required by that. Nothing much, so credits to him.
Credits also go to the CDMA Hero devs which made this in the first place.
ChocolateFroyo 1.0-rel2(multiupload)
MD5: d08fb202c3bde7fd5bfb4751bd961fed
READ!!!
1.0-rel2
- fixed lights
- cleaned system - boots faster, runs smoother
- adjusted dalvik heapsize
- added custom kernel with dual-governor configuration(read below for more info)
1.0-rel1
Initial release
About the Dual-Governor configuration:
The default settings are: 352/691 ondemand screenon, 176/352 conservative screen off. This way the battery is conserved while the performance is at its best when you need it. If your phone can't run @691MHz, all you have to do is download the attached file, unzip it, and edit it as following:
echo 691200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Click to expand...
Click to collapse
This line tells the kernel what's the max frequency when the screen is on. Here you can edit with one of the following values:
518400
576000
614400
633600
652800
672000
691200
Click to expand...
Click to collapse
After you edit it accordingly, save it and push the file to /system/etc/init.d:
adb remount
adb push 90governor /system/etc/init.d
adb reboot
Click to expand...
Click to collapse
Now you're good to go!
F**k yeah!
Please man, try to fix the camera
That's what I'm doing, don't panic.
No problem m8 , I won't
Could you guys post linpack and neocore results?
Does the old style Apps2SD work in this (the one with an EXT partition)?
No, it does not, even though I've included it.
What a pity Is there a way to fix it?
Go for it RaduG!
Running CE 2.0 for ages!
Thanks.
you're a good guy Radu, I'm so happy to see you back to work on the hero
This will be a lot of fun!
RaduG said:
What does not work:
- Camera
- Bluetooth audio
Click to expand...
Click to collapse
BT audio works on Sengle, if that helps you somehow.
About the camera I really have no ideas, to solve it on ASOP/CM they needed to backport the camera interface from eclair - something you can't do on Sense cause you don't have sources. This is what made me give up.
I really hope you can get this working, because I think no one else is working on these issues.
Good luck.
Thanks for the A2DP tip
As for the camera, I've got to the point where the image is clear, but it does not refresh(although it doesn't behave like that with the uploaded version). So I'm pretty confident that with a bit of work I will fix it eventually.
I hope you don't mind that I'm using your kernel.
RaduG said:
Thanks for the A2DP tip
As for the camera, I've got to the point where the image is clear, but it does not refresh(although it doesn't behave like that with the uploaded version). So I'm pretty confident that with a bit of work I will fix it eventually.
I hope you don't mind that I'm using your kernel.
Click to expand...
Click to collapse
np. Whatever works best for you
Is there a difference between this rom and these: http://forum.xda-developers.com/showthread.php?t=838730
I guess yes , but what makes this rom different?
Is this ROM Legend port?
Aw, crap. I just posted how stable and good (perfect) Floyo 1.2.0 was and now you went and released yours, lol.
Back-up and here I come.
I'm going to backup to my sd card and save it and start fresh with a new card. Hopefully that way I can restore quicker and without any hicups.
Thanks RaduG
@GZFan
I don't know how that ROM works, but from the description I can tell you that the GPS is not working there. Otherwise I have no idea, as I haven't tried it.
@tomekk_nt
It's an Aria/Legend/Hero hybrid.
Anyone can port sense hd from desire hd or it is impossible?
GZFan said:
Is there a difference between this rom and these: http://forum.xda-developers.com/showthread.php?t=838730
I guess yes , but what makes this rom different?
Click to expand...
Click to collapse
RaduG is building it, the man behind vanillaEclair 4 (still imho the most flawless and responsive rom for the hero, old though it may be), vanillaEclair 5 (newer sourcecode than ve4, better than the other roms based on those same sources, not quite as good as ve4 though on my particular phone), and chocolateEclair 2 (a wonderful 2.1 sense rom that many feel is best of breed on the hero). He knows how to assemble and mess with the code in hero android roms exceptionally well and has a longer success rate with single-handed rom creation on the gsm hero than anyone else that I'm aware of.
This is all just my personal opinion and experience; I don't actually know the guy (hey Radu ;-)
Aside from that, literal differences are that he's building it himself based on some cdma stuff so will be undoubtedly bringing in different sources, and probably difference bits of sense executable stuff, to try and get things like camera working. Oh yea, and as noted he's actually working on this rom actively where the rom you linked to was great but is now abandoned due to a feature implementation stalemate and work on other time-consuming exciting projects by the same developer.
{
"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"
}
***Built for 3G/4G and Wifi-Only Xoom's running 3.2.0, 3.2.1, and 3.2.2.***
-Rogue v1.4.3-
Rana
Presented By-
TDR
Bazar6
Steady Hawkin
Install Instructions-
-Make a nandroid in your current recovery then proceed
-Download zip file from link below
-Place zip on Micro SDcard
-Reboot into existing recovery
-Choose install zip and select the Rogue Kernel
-Confirm file, wait for it to finish flashing, then reboot
-Enjoy the Rogue Glory!!!
Download's:
Kernel-
Rogue 1.4.3 Rana
or
Rogue 1.4.3 N Rana (Stock clocks for GPU and some other core clocks (sclk, hclk, vde)
Add On's-
Flash any of these after the kernel
USB WWAN
Charge Light Toggle
Source-
Can be found on Github- HERE
Thank You-
Bigrushdog
Coolbho3000
Solarnz
Kcrudup
Cybertronic
Donate to TDR HERE
Stay Tuned For Future Releases!!!
-Partial Changelog-
1.4.3 Rana (Official Release)
+4G Xoom LoS fixed (synced patches from official Google/Moto source tree - Huge thank you to kcrudup!)
+Some other upstream patches
**Note: tun.ko module is now included with the kernel
**Possible issue: Xoom may lock up if suspended with USB OTG HDD connected
1.4.1 Electra (Official Release)
-No more support for Android 3.1
+Revamped installer, works on Android 3.2 and above (including Tiamat ROM 2.2.x)
+SIO (Simple I/O) I/O scheduler by default (CFQ and noop also available)
+SLQB (Queued Allocator) slab memory allocator
+Update modem driver from Qualcomm source
+Tegra framebuffer copy patch (via kcrudup)
*Configuration update with support for 4G Xooms (NOTE: there are reports of problems with some VZW Xooms)
*Fix tegra asm typo
*Fix typo in MDM6600 driver (thanks kcrudup)
1.3.1 Arcturus (Official Release)
+Rogue branding
+A bunch of upstream patches
+Handle corner case of non-US Android 3.2
+Added support for Android 3.2.2
+Even more upstream patches (thanks kcrudup and solarnz)
*Overhauled installation script (better detection of non-US Xooms, can force installation by toggling script asserts)
**Android 3.1 support is frozen and will be removed in future releases
-Special Instructions-
This version of Rogue comes packed with a maximum CPU frequency of 1.7GHz and user adjustable voltages for each frequency. Use these features responsibly! Do not select "Set on boot" unless you are confident the settings you chose are stable! Always make backups!
How to use the voltage control:
The stock frequencies and voltages in a kernel are not optimal for everyone. Userspace voltage control lets you either 'undervolt' (to save power) or 'overvolt' (to try and stabilize) any given CPU frequency to meet your needs.
Undervolting-
The easiest way to adjust these voltages is by using the app "Pimp my Cpu", available either from the Market or xda ([APP] 24 June 2011 : Pimp My Cpu 3.0 (OC/UV kernel control tool) - xda-developers). This app will let you to set an undervolt amount for each possible frequency, as well as fill some of the basic overclocking roles of a tool like SetCPU or Droid Overclock.
Note: at this moment, the app "Voltage Control" is not compatible with Launchpad 1.2.0.
Overvolting-
Unfortunately, Pimp my Cpu does not do overvolting, so you need to execute a shell command to set an overvolt amount.
Say for example 1600MHz isn't quite stable, and you want to give it a little help. From either adb shell or Terminal Emulator, execute the following commands:
su
echo "0 -25 0 0 0 0 0 0 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
The second line has a series of 13 numbers, mostly zeros. They represent the number of millivolts to subtract from the default voltage of each possible frequency, starting from the higest (1700MHz) to lowest (216MHz). So in the above example, we apply a negative 25 millivolt undervolt ( which transleted to a 25 millivolt overvolt) to the second fastest CPU frequency (1600MHz). Note that the minimum voltage is 770 millivolts and the maximum voltage is 1400 millivolts. If your new voltage exceeds these limits, it will not work.
Here is an example of bumping up 1500, just so you get how its done:
su
echo "0 0 -25 0 0 0 0 0 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
In Pimp my CPU, you will see the following as a result of the first command
Sweet man! Thanks for the hard work! I will give this a test run now.
Call me Noob but will this kernel work for Hammerhead 2.1?
diablo2224 said:
Sweet man! Thanks for the hard work! I will give this a test run now.
Click to expand...
Click to collapse
Thanks for the support bro!
Genshard said:
Call me Noob but will this kernel work for Hammerhead 2.1?
Click to expand...
Click to collapse
Yes it sure will
diablo2224 said:
Sweet man! Thanks for the hard work! I will give this a test run now.
Click to expand...
Click to collapse
let us know if you find a better stability with higher clock than 1.5 with voltage tweaks
joshndroid said:
let us know if you find a better stability with higher clock than 1.5 with voltage tweaks
Click to expand...
Click to collapse
That all depends on the Xoom...
Steady Hawkin said:
That all depends on the Xoom...
Click to expand...
Click to collapse
So true. The Xoom I use primarily has no issue at all running 1.7 Ghz night and day (it's the 3G model, although that doesn't really matter) but my wifi model (both bought on the same day) acts very poorly above 1.504. So, it's more luck than anything else, based on what others have posted as well, as to what speeds your Xoom will support. Goes without saying, be careful... I bricked an epic pushing it to far and foolishly ignoring the warnings it gave me where i could have prevented the expensive paper weight I ended up with.
The kernel seems to be working very well as expected. I've been running it for a bit now, and I am undervolted at -25 mV, and it's doing just fine. Can't tell if it's more stable than the previous build though because the previous build was pretty solid. No issues so far. Thanks again!
Awesome!!!
I flashed it.
Thx!!
I can't understand
what dose it mean
'Android 3.1 support is frozen and will be removed in future releases'
So this kernel are not currently support the Android 3.1??
or support now??
Hi, any instructions on how to use USB_wwan after insmod with
a 3g USB dongle?
Thanks!
Enviado desde mi MB860 usando Tapatalk
kokjsch said:
I can't understand
what dose it mean
'Android 3.1 support is frozen and will be removed in future releases'
So this kernel are not currently support the Android 3.1??
or support now??
Click to expand...
Click to collapse
It is supported in this kernel, but in the future we likely will not support it.
Thanks to answering my question.
lhurtado said:
Hi, any instructions on how to use USB_wwan after insmod with
a 3g USB dongle?
Thanks!
Enviado desde mi MB860 usando Tapatalk
Click to expand...
Click to collapse
Hi, I'm still not sure about using a 3G USB Dongle, but it should work with wired tethering from a phone.
Here are the instructions from bigrushdog.
USB Tether: Plug OTG cable into Xoom. Plug phone with microUSB cable into OTG cable. On phone, enable USB Tether. On Xoom, run the following in terminal or script manager (Scripter, GScript, Tasker) of your choice.
dhcpcd usb1
setprop net.dns1 8.8.8.8
The Xoom will not show any indication that there is a network connection. But pull up your browser and surf away.
Click to expand...
Click to collapse
Thanks Steady, stable as always
thanks.
one question, can not access wifi with HC3.2.2 on wi-fi only xoom(MZ604) whether this kernal can resolve that or we need to wait for new rom based on 3.2.2?
also which governor/scaling is best for your kernal?
musashiken said:
Hi, I'm still not sure about using a 3G USB Dongle, but it should work with wired tethering from a phone.
Here are the instructions from bigrushdog.
Click to expand...
Click to collapse
Thanks! I misunderstood the use of this module.
I flashed the 'N' version of this kernel and then I flashed the Charge lite toggle. Is there anything else I need to do to enable this? I flashed twice and the light still isn't on while charging.
One other thing, the only reason I haven't tried the non 'N' version of the kernel is because I use SetCPU instead of PimpMyCPU. Can you use SetCPU in order to set the overclock freq or is there a specific reason for using PimpMyCPU? I have done overclocking on my Droid Incredible so I am not a noob at it but at the same time I just wanted to ask before hand.
Xoom 3.2
Bricked-Kernel One X (endeavoru)
The first 100% stable kernel for the HTC One X (endeavoru)
(thx HTC for the screwed source btw, fixed it ^^)
Replaced NVIDIA's strange hotplug manager with my own: tegra_mpdecision
Features:
Based upon HTC source
Fixed all stability issues from the HTC source
Fixed all section mismatches
Various other fixes
Sweep2wake
tegra_mpdecision, which completely replaces nvidias hotplug manager (better battery life + performance)
extensive sysfs interface for mpdecision with all the tuneables you want
modified ondemand governor for tegra3 & mpdecision (this is the only recommended governor atm)
fixed sound playback while screen is off
GPU OC (484Mhz)
Variant free CPU OC for all phones (51 - 1600Mhz)
Compiled with gcc4.7
fixed max cpufreq resets throughout the kernel
all cores now use the max freq (before: only in singlecore, otherwise -100Mhz)
Undervolting (faux123)
Check the changelog for the rest
Changelog @ bricked.de
What is sweep2wake?
How to install?
!!!!IMPORTANT!!!!Flash through recovery. But:
Since the htcdev unlock prevents us from flashing the boot partition from recovery, the installer will ONLY INSTALL THE MODULES & disable the HTC screenshot! (needed as a fixup for sweep2wake, use the AOSP screenshot pwr+vol.down instead)
_YOU_ will need to flash the boot.img within the zip (folder: kernel) yourself! (extract it to your desktop so you can use the commands given to you here)
I can't stress enough how important this is. _YOU_ will need to flash it.
How to do that (full guide, if you use the reboot option given to you by the installer you will only need steps 1 & 4-7)
1. Install HTC drivers (how to do that is explained a hundred times all over the web)
2. Reboot
3. in the boot animation, connect your phone to your computer and do:
adb reboot-bootloader
4. You should now see "FASTBOOT USB", if that is the case:
fastboot flash boot %USERPROFILE%\Desktop\boot.img
5. fastboot reboot
6. check with: adb shell uname -a if it says bricked.
7. enjoy
ofc these steps can also be done before the installer is executed from recovery. Just be sure to complete both.
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://code.google.com/p/bricked/issues/entry
[email protected]
IRC Chat: Freenode IRC #bricked
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
>>> DOWNLOAD <<<
Donor List:
> Hall of fame <
With special thanks to all piggy bank donators!
Thank you very much!
Source:
Battery life
{
"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"
}
(InsertCoin)
Performance:
Knowledge base:
(under construction)
tegra_mpdecision manual:
coming soon(tm)
Why only clock with 1.4 Ghz max?
That's not a fix, just a point of opinion. I provide stock or close-to-stock kernel settings in regards to UV/Clocks. Usually I don't take HTC's 'stock' but the manufacturer of the component. In this case the soc, so NVIDIA.
Our stock-phone is clocked with 1.5Ghz single core and 1.4Ghz multicore (as soon as the 2nd core comes up). Usually, whatever you do, you will instantly trigger the second core to come up, if even only for a short time. This would effectively limit the cpu clock speed to 1.4Ghz for that time.
Since I overwrote the clock reduce, our phone will clock with the set max at all times. Which, in this case, is overclocking.
So I just reduced the clock back to it's "stock" setting and please trust me that you won't notice the difference to stock in Benchmarks, UI performance, or anywhere else. Not only because it is only 100Mhz on ONE CORE, but also because that core seldom runs alone and therefore can only use the 1.5Ghz for a very short time.
You are ofc free to clock it back to 1.5Ghz again. Please note that this counts as overclocking and the same rules as undervolting apply to it.
Soon to be tested will post results...
Sent from my HTC One X using XDA
Will it work with all the builds say 1.29, 1.28, 1.26?
Sent from my HTC One X
THANHVO31 said:
Will it work with all the builds say 1.29, 1.28, 1.26?
Click to expand...
Click to collapse
I am on 1.29, that's what I have tested. Chances are it will work fine with all builds, test it and report back
got excited and flashed the kernel,
no luck, stuck on htc splash screen
- 1.28 firmware(coredroid 2.1 ROM)
show-p1984!!!!!!!!!!!!! im so happy to see you here!!!!!!!!!!!! love your work on the bricked kernel for the hp touchpad!!!!
cant wait to get stuck into this one!!!!!!!!!
also will you be adding otg support?? just seen it in the changelog for the eternity kernel.
once again so glad to see you working on this awesome device!!!!!!!!!!!!
Buhhhuuuhhhuuuuuuu.... No pc atm.
Download your kernel right now, flash @ 6:15 dhft! (deagleonehomecommingflashtime)
Thanks show, will report
InsertCoined from my nearly"bricked" One X (thanks show, for doing your business^^)
after test eternity project i will test yours. Thanks for your work!!
Just pushed this. Booted just fine. No freezes or reboots. But I do have WiFi error
Sent from my HTC One X using xda premium
Can i install it tru CWM ?
wolfraim said:
Can i install it tru CWM ?
Click to expand...
Click to collapse
TRY reading the OP bro.
I just flashed it and flashed the Boot.img no WiFi. I flashed it through recovery twice. And manually flashed the Boot.img. Still no go. Any idea?
EsHi sir ......hopefully you Will support call recorder....please any chance to provide this feature to one x owners....thanks again in advanced
rayford85 said:
TRY reading the OP bro.
Click to expand...
Click to collapse
Sorry about it. Now im flashing.
---------- Post added at 10:47 PM ---------- Previous post was at 10:37 PM ----------
Installed without problems... no wifi problems for now.
i just do an full wipe with my VillainRom, then i flash the boot and start all again.
Any issues i will put here.
Thanks for now hahaha
rayford85 said:
Just pushed this. Booted just fine. No freezes or reboots. But I do have WiFi error
Click to expand...
Click to collapse
ShyamSasi said:
I just flashed it and flashed the Boot.img no WiFi. I flashed it through recovery twice. And manually flashed the Boot.img. Still no go. Any idea?
Click to expand...
Click to collapse
I am seeing this too in the latest version. I forgot to include some modules :/ Gimme a few.
hasan_abeer said:
EsHi sir ......hopefully you Will support call recorder....please any chance to provide this feature to one x owners....thanks again in advanced
Click to expand...
Click to collapse
I don't mean to sound rude. But you REALLY don't need to post this everywhere! The devs are aware it's a feature people want, but the reality is that getting things STABLE first is the highest priority.
It's not point getting call recording added if the phone doesn't work properly. Please just be patient and stop spamming every thread with your requests.
M.
+1 for Wifi error (maximus 1.3)
+ Led Notify always ON (red)
I had Flash boot.img + copy modules at CWM.
Sweep2Wake is cool but sorry.
Man, sweep2wake its amazing!
Now with no problems about wifi, its weird :s im using VR 2.
Bricked-Kernel One X (endeavoru) AOSP (CM10/etc)
The first 100% stable kernel for the HTC One X (endeavoru)
(thx HTC for the screwed source btw, fixed it ^^)
Replaced NVIDIA's strange hotplug manager with my own: tegra_mpdecision
Features:
Based upon HTC source
Fixed all stability issues from the HTC source
Fixed all section mismatches
Various other fixes
Sweep2wake
tegra_mpdecision, which completely replaces nvidias hotplug manager (better battery life + performance)
extensive sysfs interface for mpdecision with all the tuneables you want
modified ondemand governor for tegra3 & mpdecision (this is the only recommended governor atm)
fixed sound playback while screen is off
fixed bluetooth toggle with gps active
GPU OC (484Mhz)
Variant free CPU OC for all phones (51 - 1600Mhz)
added init.tegra.post_boot.sh support
Compiled with gcc4.7
fixed max cpufreq resets throughout the kernel
all cores now use the max freq (before: only in singlecore, otherwise -100Mhz)
Undervolting (faux123)
Check the changelog for the rest
Changelog @ bricked.de
What is sweep2wake?
How to install?
!!!!IMPORTANT!!!!Flash through recovery. But:
Since the htcdev unlock prevents us from flashing the boot partition from recovery, the installer will ONLY INSTALL THE MODULES & disable the HTC screenshot! (needed as a fixup for sweep2wake, use the AOSP screenshot pwr+vol.down instead)
_YOU_ will need to flash the boot.img within the zip (folder: kernel) yourself! (extract it to your desktop so you can use the commands given to you here)
I can't stress enough how important this is. _YOU_ will need to flash it.
How to do that (full guide, if you use the reboot option given to you by the installer you will only need steps 1 & 4-7)
1. Install HTC drivers (how to do that is explained a hundred times all over the web)
2. Reboot
3. in the boot animation, connect your phone to your computer and do:
adb reboot-bootloader
4. You should now see "FASTBOOT USB", if that is the case:
fastboot flash boot %USERPROFILE%\Desktop\boot.img
5. fastboot reboot
6. check with: adb shell uname -a if it says bricked.
7. enjoy
ofc these steps can also be done before the installer is executed from recovery. Just be sure to complete both.
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://code.google.com/p/bricked/issues/entry
[email protected]
IRC Chat: Freenode IRC #bricked
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
>>> DOWNLOAD <<<
Donor List:
> Hall of fame <
With special thanks to all piggy bank donators!
Thank you very much!
Source:
Battery life
{
"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"
}
Performance:
Knowledge base:
(under construction)
tegra_mpdecision manual:
coming soon(tm)
Why only clock with 1.4 Ghz max?
That's not a fix, just a point of opinion. I provide stock or close-to-stock kernel settings in regards to UV/Clocks. Usually I don't take HTC's 'stock' but the manufacturer of the component. In this case the soc, so NVIDIA.
Our stock-phone is clocked with 1.5Ghz single core and 1.4Ghz multicore (as soon as the 2nd core comes up). Usually, whatever you do, you will instantly trigger the second core to come up, if even only for a short time. This would effectively limit the cpu clock speed to 1.4Ghz for that time.
Since I overwrote the clock reduce, our phone will clock with the set max at all times. Which, in this case, is overclocking.
So I just reduced the clock back to it's "stock" setting and please trust me that you won't notice the difference to stock in Benchmarks, UI performance, or anywhere else. Not only because it is only 100Mhz on ONE CORE, but also because that core seldom runs alone and therefore can only use the 1.5Ghz for a very short time.
You are ofc free to clock it back to 1.5Ghz again. Please note that this counts as overclocking and the same rules as undervolting apply to it.
Finally ! Showp did it again ! Awesome work mate ! cant wait to test and report back !
First. Let the force be with u
Edit: damn neo bet he used the red pill
Sent from my ICJ One X powered by pure smooth power NCX
Goku80 said:
First. Let the force be with u
Click to expand...
Click to collapse
Nah, second!
May the force be with you too.
Your 8 Hours Early
show-p1984 do we need repack??? :cyclops:
wow,a new bricked kernel,really exited about that one,hope i get it flashed correct on my rom
TAGTRAUM said:
show-p1984 do we need repack??? :cyclops:
Click to expand...
Click to collapse
It is using a modified CM10 ramdisk, should work across all aosp roms, except there are some strange ramdisk edits in you rom.
show-p1984 said:
It is using a modified CM10 ramdisk, should work across all aosp roms, except there are some strange ramdisk edits in you rom.
Click to expand...
Click to collapse
sounds good,so maybe no need for deleting those lines in init.endeavoru.rc.
Will try now
This is exciting. I'm going to wait on a few reviews though as I'm happy with Faux for now.
Thanks for all your hard work!
:good::good: great!!! thank you Show!
Woooow! Coming from neo's v7 which is stable, pretty fast and is supposed to have good battery also (as far as I experienced with former versions) .
But I have NEVER seen a HOX kernel that has so many 51mhz cpu times w/o lags.
This kernel is pure awesomeness, really a new feeling how cold a HOX can be and i bet the battery life will be outstanding
Good to have you back mate
Cheers Pete
ptr_hamilton said:
Woooow! Coming from neo's v7 which is stable, pretty fast and is supposed to have good battery also (as far as I experienced with former versions) .
But I have NEVER seen a HOX kernel that has so many 51mhz cpu times w/o lags.
This kernel is pure awesomeness, really a new feeling how cold a HOX can be and i bet the battery life will be outstanding
Good to have you back mate
Cheers Pete
Click to expand...
Click to collapse
Well here is the magic wand I used:
https://github.com/showp1984/bricked-endeavoru/blob/exp/arch/arm/mach-tegra/tegra_mpdecision.c
show-p1984 said:
Well here is the magic Light Saber I used here
https://github.com/showp1984/bricked-endeavoru/blob/exp/arch/arm/mach-tegra/tegra_mpdecision.c
Click to expand...
Click to collapse
Fixed.
Show is losing it after doing all night sessions making this happen.
@show-p1984,
Earlier tonight I flashed repacked Bricked_onex_v0.3 for CyanogenMod 10 Nightlies - 4.1.1 by TeamNDVRu.
@First impression all is working perfect; wifi, bluetooth, compass, gps and the rom flies, no delays in end call it's just wonderful.
Going to update asap LoL, thanks for your hard work.
Is it necessary to repack it to use in ICJ AOKP?
rpmfc36 said:
Is it necessary to repack it to use in ICJ AOKP?
Click to expand...
Click to collapse
no ,works fine as it is
rpmfc36 said:
Is it necessary to repack it to use in ICJ AOKP?
Click to expand...
Click to collapse
Nope.
Running it now.
Make sure you flash the zip provided in recovery and reboot into fastboot usb to flash the boot.img
Thanks to showp for the aroma love, made it super easy to flash this.
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
The following versions with changelog are available:
* boot-tetra-LDZ22D-r5.img
Enable ZRAM to increase the available virtual memory space
Enable KSM
Configure the interactive cpufreq governor better
Add bfq io scheduler (although it's not being used any more)
Fix cfq to be more performant for SSDs
Modify the Android Low Memory Killer to work correctly with swap enabled
Note: this combined with enable zram seems to fix one of the major 5.1 battery drains for me. Please let me know if that's not the case for you.
* boot-tetra-LDZ22D-r3.img
Disable modules (free up more kernel memory)
Disable extra debugging (free up more kernel memory)
Disable NFS (fre up more kernel memory)
Enabled compiler optimizations to speed up the kernel (uses more memory)
Disable "adaptive low memory killer" (seems like the stock kernel is killing too many processes, this may help that)
* boot-tetra-LDZ22D-r2.img
Updated to Linux 3.10.86
Enable all 4 cores
Installation:
* Reboot to fastboot and then
Code:
fastboot flash boot boot-tetra-LDZ22D-r<whatever>.img
.
Warnings:
* This probably breaks your ability to accept OTA updates.
Source:
* github : the repos you need are all explained there along with how to compile it
XDA:DevDB Information
crpalmer's Tetra Kernel, Kernel for the Sony Smartwatch 3
Contributors
crpalmer
Kernel Special Features:
Version Information
Status: Stable
Created 2015-08-14
Last Updated 2015-08-17
Thanks for posting! Watch is charging now; but while it charges... any anticipated impact on battery life either way? And its probably worth noting if this will result in having to reset the watch or not..
Awesome! Thanks! gonna try this one out later today
Divine_Madcat said:
Thanks for posting! Watch is charging now; but while it charges... any anticipated impact on battery life either way? And its probably worth noting if this will result in having to reset the watch or not..
Click to expand...
Click to collapse
I am not sure on battery life because I'm running a newer version than what I have released...
The next version: I have used it for 7 hours while out at an amusement park with my family and it is down 20% (just less than 3% per hour). I'm actually hoping I have fixed the massive random battery drain in this unreleased version too, but only time will tell for sure.
Hmm.. thinking i might wait to give this unreleased version a try...
Thanks for the update!
Thank you for greate works!
r3 works fine. Good response and battery life no problem.
{
"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 haven't been able to find a copy of the stock kernel for LDZ22D, only for LWX48p.
Any chance you could post please.
Legend, Just flashed so will report back..
Any chance on setting to govenor to hotplug like it was on my LG G Watch, so it only uses the cores it needs when it needs?
Thanks for your work!
karl0ss said:
Legend, Just flashed so will report back..
Any chance on setting to govenor to hotplug like it was on my LG G Watch, so it only uses the cores it needs when it needs?
Thanks for your work!
Click to expand...
Click to collapse
As far as I could tell, the bcm SoC in here is very different. It has very different dormant states used to simulated hot-plugging and when I tried to do my own hotplugging, I found that the hardware would sometimes hang and you had to hard reboot it. If you ran it without the hardware hanging then hot-swapping the cores actually made battery life worse. It seemed like the power consumption was the same regardless of the number of cores online.
After wasting a lot of time on that, I'm not planning on trying again as I think it's a dead-end.
OK cool, Very glad you did the work for the new kernel...
Thanks so much
Kernel seems to be working quite well so far, I have noticed my arm getting hot now and again, but thats to be expected with the extra cores...
is R3 the "unreleased" build you are talking about in your early posts?
Thanks
karl0ss said:
Kernel seems to be working quite well so far, I have noticed my arm getting hot now and again, but thats to be expected with the extra cores...
is R3 the "unreleased" build you are talking about in your early posts?
Thanks
Click to expand...
Click to collapse
Nope, that was r4 which I never released because it didn't actually fix the bad battery drain I was trying to fix. The bad battery drain that I was hitting is caused by memory running out and android constantly killing and then starting and then killing and then starting the google framework. I thought I had fixed that by enabling ZRAM and KSM (aka, following the low-memory device best practices that Google publishes) but it didn't because the ALMK seems to be stupid. I fixed that in r5 which I just released.
New version released:
* boot-tetra-LDZ22D-r5.img
Enable ZRAM to increase the available virtual memory space
Enable KSM
Configure the interactive cpufreq governor better
Add bfq io scheduler (although it's not being used any more)
Fix cfq to be more performant for SSDs
Modify the Android Low Memory Killer to work correctly with swap enabled
Note: this combined with enable zram seems to fix one of the major 5.1 battery drains for me. Please let me know if that's not the case for you.
crpalmer said:
New version released:
[/LIST]
Click to expand...
Click to collapse
Excuse me sir .. how to know if the watch is LDZ22D or something else ? and can you give me the link to any website that teach how to go fastboot/flashmode etc for this watch ..searched on google but not found anything..hopefully you answered my humble question..thanks
3vilArt_ said:
Excuse me sir .. how to know if the watch is LDZ22D or something else ? and can you give me the link to any website that teach how to go fastboot/flashmode etc for this watch ..searched on google but not found anything..hopefully you answered my humble question..thanks
Click to expand...
Click to collapse
On the watch, go to settings, click on about, and then you will find the build number.
In the description I don't see if this kernel include recovery.
sekac55 said:
In the description I don't see if this kernel include recovery.
Click to expand...
Click to collapse
No. Recovery and kernel are completely different things.
crpalmer said:
No. Recovery and kernel are completely different things.
Click to expand...
Click to collapse
I know, and the next question is if you can add, twrp into the ramdisk ?
I have now flashed the kernel and the watch is now smoother i like it.
Many thanks for your work. Keep it uptodate
sekac55 said:
I know, and the next question is if you can add, twrp into the ramdisk ?
I have now flashed the kernel and the watch is now smoother i like it.
Many thanks for your work. Keep it uptodate
Click to expand...
Click to collapse
Nope, but you can flash twrp independently of the kernel. They each have their own ramdisk.
So, with the new firmware rolling out, will we need to revert kernels (if so... anyone have the stock link?) to get the OTA?