Keeps crashing at random points cant be any more speficic had to take battery out 4 times now since 2.02 update.
hmmm had another idea about these random crashes (which dont affect me oddly)
i am beginning to suspect something rather different, not kernel related. Perhaps the modified libsqllite.so i am cooking in is the culprit. Will upload the original version in a little bit for you guys to check out
i am beginning to suspect something rather different, not kernel related. Perhaps the modified libsqllite.so i am cooking in is the culprit. Will upload the original version in a little bit for you guys to check out
Try current widget, it log current in text file and graph.
I'm afraid not. every time after I changed the kernel in your build with the other kernel, random crashes disappeared.
Hi, did you format your SD card or did task 29 before flash the ROM? I wonder the existing previous data cause the problem. If the under voltage make application crash, it should be randomly. But for me, it always happen on the same step.
Sent from my HTC HD2 using XDA App
Does there anyone have frozen camera problem? I have to take out the battery every time.╯▽╰
Please see one of the crash log:
Version: TripViewLite-Android/1.1.162 (Android 2.2.1; HTC HD2)
java.lang.NoClassDefFoundError: com.grofsoft.tripview.lite.StreetMapActivity
at com.grofsoft.tripview.lite.SelectMapActivity.onItemClick(Unknown Source)
at android.widget.AdapterView.performItemClick(AdapterView.java:284)
at android.widget.ListView.performItemClick(ListView.java:3515)
at android.widget.AbsListView$PerformClick.run(AbsListView.java:1742)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
at dalvik.system.NativeStart.main(Native Method)
Sent from my HTC HD2 using XDA App
Please see one of the crash log:
Version: TripViewLite-Android/1.1.162 (Android 2.2.1; HTC HD2)
java.lang.NoClassDefFoundError: com.grofsoft.tripview.lite.StreetMapActivity
at com.grofsoft.tripview.lite.SelectMapActivity.onItemClick(Unknown Source)
at android.widget.AdapterView.performItemClick(AdapterView.java:284)
at android.widget.ListView.performItemClick(ListView.java:3515)
at android.widget.AbsListView$PerformClick.run(AbsListView.java:1742)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
at dalvik.system.NativeStart.main(Native Method)
Sent from my HTC HD2 using XDA App
Last edited:
I am currently updating my autobuild scripts so that ALL future relaseses will contain three boot.img files in the main download. You can then simply delete the two you dont want and rename the one you do to boot.img and flash away
the three boot.img's will be:
1) NO_Undervolt_1190
2) Norm_Undervolt_1190
3) Max_Undervolt_1305 (for extreme 1305mhz speedy goodness)
i think this is the best solution.
now, just gotta merge and update all my scripts
This is an very great idea and solution. Thx forward.
Let me explain:
- i want an running build-in FMRadio Version (only coping does not running)
- so i install always your CWR Version (zeam is also my favorite )
BUT one Problem i have with your CWR´s
Keyboard in SMS --> Background is black -> this is o.k.
Keyboard in "internet" --> Background in 2nd and 3rd line is white
Keyboard in marked --> Background in 2nd and 3rd line is white
Last edited:
Never change a winning team
After testing all builds up to 2.02 on several T8585's, CleanDroid 1.30 is still my favourite in terms of stability, speed and battery consumption. Its running the original ocm kernel, not the kernel compiled by the chef himself, g.lewarne.
Now that several of you experience crashes with the current 2.0x builds, it might be a suggestion to give 1.30 a second chance, if you not already had a closer look at it, but need a build for daily use.
Therefore I've temporary added a CWM zip of build 1.30 here, so you can give it a (re)try.
Because of other commitments, I'll keep myself low-profile for a while, so help each other
After testing all builds up to 2.02 on several T8585's, CleanDroid 1.30 is still my favourite in terms of stability, speed and battery consumption. Its running the original ocm kernel, not the kernel compiled by the chef himself, g.lewarne.
Now that several of you experience crashes with the current 2.0x builds, it might be a suggestion to give 1.30 a second chance, if you not already had a closer look at it, but need a build for daily use.
Therefore I've temporary added a CWM zip of build 1.30 here, so you can give it a (re)try.
Because of other commitments, I'll keep myself low-profile for a while, so help each other
@piotv .... think I will be going back to 1.3 tonight .... thanks for your valueble comments.
2.02 the way forwards
Hi G.
For me 2.02 is giving me less battery drain than I experienced with 1.30, even after 1 cycle, so am interested to see how much it will improve.
Unlike with 2.0 I am now experiencing no crashes, GPS working well, Camera functioning properly, phone not crashing when receiving/after ending calls...
A much faster, smoother ROM, maybe 2.02 is the mecca of ROMs for my phone. Will be interesting to see how you can top this one
After testing all builds up to 2.02 on several T8585's, CleanDroid 1.30 is still my favourite in terms of stability, speed and battery consumption. Its running the original ocm kernel, not the kernel compiled by the chef himself, g.lewarne.
Now that several of you experience crashes with the current 2.0x builds, it might be a suggestion to give 1.30 a second chance, if you not already had a closer look at it, but need a build for daily use.
Therefore I've temporary added a CWM zip of build 1.30 here, so you can give it a (re)try.
Because of other commitments, I'll keep myself low-profile for a while, so help each other
Hi G.
For me 2.02 is giving me less battery drain than I experienced with 1.30, even after 1 cycle, so am interested to see how much it will improve.
Unlike with 2.0 I am now experiencing no crashes, GPS working well, Camera functioning properly, phone not crashing when receiving/after ending calls...
A much faster, smoother ROM, maybe 2.02 is the mecca of ROMs for my phone. Will be interesting to see how you can top this one
Hi G.
For me 2.02 is giving me less battery drain than I experienced with 1.30, even after 1 cycle, so am interested to see how much it will improve.
A much faster, smoother ROM, maybe 2.02 is the mecca of ROMs for my phone. Will be interesting to see how you can top this one
I agree. Even with previous builds I didn't have issues (except known bugs).
So this build si awsome. And I hope to see new even better builds.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
118CleanDROIDFollowing on from my WM 6.5 ROMs for the HD2, I now present my first NANDroid ROM. Built for speed, space and maximum customisability to be decided by you - the users!
Main Features:
- Extreme speed and responsiveness
- Froyo 2.2.1
- CyanogenMOD 6.1.1
- ADW Launcher
- Standard Framework
- Ultra Tiny, 320mb free space after flash on Euro HD2
- Gingerbread Keyboard
- LCD Density is 190 for the true HD look
- Custom initrd for performance
- Custom kernel for max performance and battery life
The ROM is small because it is stirpped of all Google applications and varoius other features, such as wallpapers. No wallpapers are supplied other than the one it comes with so you must provide your own. Everything that has been removed is freely available from the Market, so you can choose what you want and nothing is forced upon you
The ROM is completely rooted and SU is working correctly so you will easily be able to change animations, framework, system APKs etc
Installation:
MAGLDR 1.11 or greater required, Radio 2.12.50.xx is reccommended. Load phone in MAGLDR menu mode, select USB flasher. Connect phone to PC with USB cable (allow it to install drivers if necessary) and flash the ROM with the supplied DFT flasher. Its that simple
Kernel changelog + Download + GPL compliance information:
Kernel : GL_Core_v5b
Built from latest master GIT git://gitorious.org/linux-on-wince-htc/linux_on_wince_htc.git
OC 1190/1536mhz added to acpu file, Added IO optimisation sourced from hastarin, Added latest YAFFS + cpufreq drivers from tytung GIT.
The kernel code is not modified in any way from what is available on the below linked repositories + patch file, the only difference being the custom build configuration. All credits for kernel modifications go to hastarin, tytung, cotulla, DFT, markinus and anyone else listed as contributing on the commit list and changelogs
- Latest Patches
- Automatic overclock scaling up to 1190mhz / 1536mhz
- Interactive governor as default
- No Undervolt 1190, No undervolt 1536 and Undervolt 1190 kernels availbale
- Reverted to no-op (better IO performance)
- Reverted to SLUB (better system latencies)
- Added htcleo.board.c tweaks from hastarin
- EXT 2/3/4 support
- Added netfilter for WiFi tethering support throught 3rd party apps
- Fixed 60ma after call drain
- Fixed LED notifications
- Pulled latest commits and rebuilt
- Improved compatability for more devices with Undervolt_1190 and 1536mhz kernels
- Slight performance increase over v4
You can download the complete patch set i use here http://htcfanboys.com/CleanEx/Kernel/KERNEL PATCH.7z
You can download a complete ready to use build for other roms and chefs to use here http://htcfanboys.com/CleanEx/Kernel/DISTRIBUTION KERNEL.7z
Download:
NAND DFT FLASH >> http://htcfanboys.com/CleanEx/CleanDROID 2.55.7z
Build info
~~~~!!!! IMPORTANT - READ !!!!~~~~
From now on, the rom .7z you have downloaded will contain 3 boot.img files. Choose which one you want to try and delete the other two, then rename the one you have chosen to "boot.img", then flash. If you have windows set to auto hide file extensions (99.9% people do) renaming the file to "boot" will be sufficient, otherwise it will end up being called boot.img.img and DFT wont see it!
The three choices are:
- 1190mhz No Undervolt (most stable)
- Undervolt 1190mhz (battery saver - might not work on all devices)
- 1536mhz No Undervolt (Will consume more battery, but faster, compatible with most devices)
Changelog: v2.55
- Ditched undervolting for all but 1190 kernel (for battery saving)
- Added 1536mhz kernel, will work on most devices but use more battery
- Kernel voltage changes should fix FC for everyone whose phone can handle the undervolt 1190 / 1536 kernel
- Flash keep data supported from 2.51/2.50
Changelog: v2.51
- Kernel changes, increased min voltage on UV kernels
- More devices (almost all) should work with UV1190 and UV1305 kernels
- Some minor tweaks
- lil bit faster
- Battery drain should be improved
Changelog: v2.50
- Added 3 different boot.img files to archive (see above)
- Pulled latest commits from GIT, kernel patches and updates
- Rebuilt rom, stability improved
- Updated to CM 6.1.1 from stock Desire build
- INIT changes for uber fast booting
Changelog: v2.02
- Fixed LED notifications
- Several kernel changes for performance
- Switch to interactive governor for better battery life and improved IO
- INIT changes to decrease boot time slightly
- Added SMU (super mega ultraness)
- Reduced by 2mb
- Fixed netfilter and 60ma after call drain
Changelog: v2.00
- Totally rebuilt from the ground up from latest stable Desire CM build
- Completely removed compcache service for more performance
- Smallest build yet - 321mb free on euro HD2!
- Newer custom kernel + accompanying INIT
- Fastest ROM yet!
Changelog: v1.40
- fixed the broken apps to SD feature
- recompiled kernel with latest GIT commits
- tweaked kernel, rom now more responsive, less battery drain, fixed various issues
- fresh flash required
(old changelogs removed)
Additional Info!
Attached to this post is the "LiveWallpaperPicker.apk" install it to be able to set your homescreen wallpaper to any live wallpapers you may have installed
Also attached is GenieWidget for those that want the standard news+weather widget (which is rubbish IMO)
---------------------------------------------------------------------------------------
Credits and Thanks
OCM7, Fadzy, JoPlayer, The_Scotsman, Jan-Willem, Cotulla, Bepe, DFT team and anybody i have forgotten!34
All CWM recovery zip files below have been tested on several T8585's
The Edify scripts will be streamlined as soon as time allows...
LATEST CWM build
CleanDROID 2.5x ROM BUILD = BOOT_ zip + SYSTEM_ zip
--------------------------------------------------------------
CleanDROID CWM zip SYSTEM install only:
SYSTEM_CleanDROID_CWM_FM_2.55.zip
recommended partition size: 85M+
CleanDROID CWM zip BOOT install only:
If you've no intention to use the CleanDROID build but would like to try a GL_Core kernel update for your specific ROM, go away, go HERE
GL_Core v11 No Undervolt 1190mHz (extended battery support)
BOOT_GL_coreV11_CleanDROID_CWM.zip
GL_Core v11 Normal Undervolt 1190mHz (extended battery support)
BOOT_GL_coreV11_UV_CleanDROID_CWM.zip
GL_Core v10 No Undervolt 1190mHz
BOOT_GL_coreV10_CleanDROID_CWM.zip
GL_Core v10 Normal Undervolt 1190mHz
BOOT_GL_coreV10_UV_CleanDROID_CWM.zip
OCM 1190mHz
BOOT_OCM1190_CWM_1.30.zip
this is the original kernel from ocm7. If you're not happy with the GL_core kernels, try this one.
It's rock solid and still one of my favourites.
tytung R6 1190mHz
tytung series
Another pretty good alternative, working great for me.
If all other kernels fail, give this one a try
If you download a CWM recovery zip file and appreciate the efforts, click the [THANKS] button* at the bottom of this message , so I can keep track if there is still a demand for a CWM zip or if I'm doing this all for jack s*** *(if you're not logged in, you wont see this button)
ARCHIVED CWM builds
--------------------------------------------------------------
CleanDROID_v2.02_cwm_fm.zip
needs a minimal 83M system partition.
For safety 85M+ as a bottom line is highly recommended. Keeps you still living on the edge..
CleanDROID_v2.00_cwm_fm.zip
includes themed FM radio which fits the beautiful MontAlbert theme (themed by FrAsErTag)
needs a minimal 86M system partition if you flash the MontAlbert theme afterwards with metamorph...
CleanDROID_v1.30_cwm_fm.zip
needs a minimal 85M system partition
needs some manual tweaking to reduce battery consumption, but still pretty good for daily use.
All CWM zip's (except BOOT_ zip's) include some personal preferences, i.e.
--------------------------------------------------------------- Zeam launcher instead of ADW launcher
- Dialer One
- FM radio thanks FrAsErTag
- lcd density set to 216 ppi (true HD2 display density)
- dns set to OpenDNS to speed up ip resolving
Before flashing, always do a magldr hard reset and wipe dalvik cache!
Suggestions for a partion layout, see HERE
If you download a CWM recovery zip file and appreciate the efforts, click the [THANKS] button* at the bottom of this message , so I can keep track if there is still a demand for a CWM zip or if I'm doing this all for jack s*** *(if you're not logged in, you wont see this button)17FAQ
Q: How to change homescreen dpi?
A: Install Ted (text editor) from market and edit your build.prop or use LCD Density from market.
Q: I have problem with resolution in games.
A: Uncheck compatability mode in spare parts and reboot.
Q: How to keep all the app and settings of the old version?
A: Use MyBackup Pro from Market.
Q: When will FM radio work?
A: When i can get it to work - thats why it has been removed
Q: How to activate battery %?
A: Go to Settings/CyanogenMod settings/user interface/status bar/then click battery %
Q: I'm noticing more battery drain than usuall.
A: You will need to drain/recharge battery before you get full life expectancy out if it - just like any flash.
Q: If you completely run down the battery, would you be able to charge it with the phone again?
A: If your battery is dead, press and hold Vol Down and plug in USB cable / charger at same time. Phone will boot into bootloader and charge there just fine. Leave for 20 mins, pull battery, reboot and charge normally. If phone has just run down, plugging in the charger will usually turn it on.
Q: does it has htc sense?
A: No.
Q: Screenshots?
A: No need, its standard Froyo with ADW launcher6
the way my kernel+init is set up all setCPU / CPUTuner type apps are going to do is replicate the functionality - kinda pointless.
The INIT i supply automatically sets the correct scaling, and the correct governor to go with my kernel. In my testing, i prefer interactive governor over smartass (i just find it less laggy at times even though smartass is meant to be superior, but then again it wasnt bulit with the HD2 CPU in mind)
more info-
Kernel i supply does boot time CPU lock, and then passes frequency control over to userspace (the INIT). When the system sleeps, or is at idle, the kernel regains control and clocks down very rapidly to 245mhz and stays there unless some background process (such as mail download) occurs.
I have also tweaked the kernel frequency scaling for a less aggressive ramp-down when phone is active, meaning that it wont immediatly jump down the frequency scale after 0.8 seconds of relative inactivity. By keeping this ramp-down time higher, the CPU is more responsive when activity occurs within the set timeframe (hope your following me here) since its already running in the higher frequency bands.
In short, the only thing that you can really change any more with CPU apps is the scheduling governor (smartass / interactive / permformance etc). But, as i just said, its not really worth bothering with that any more either.
I believe that most of the recent kernels by other chefs also behave in a similar manner, although probably not to the same degree as mine behaves.
Its easier for me to apply this sort of system to my specific rom as i also build the init myself, so can match them both perfectly.
Hope that explains it
Some of you newer to this rom/thread might not be aware that i have actually, physically measured battery drain (with a USB logging multimeter) and regardless fo what your phone reports as current draw (with current widget or similar) that ACTUAL drain @ the battery is quite different.
Most CPU frequencies only have very very minor voltage jumps, the minimum @ 245 being 950ma and the max at 1190 is 1100ma
And more importantly, if the CPU is say at 998mhz but not doing anything, it will use no more power than at lower speeds due to internal CPU power control systems, as i also confirmed with multimeter.
basically what im trying to say is, flash the rom, calibrate battery (full charge then delete the battery stats.bin) let it drain, and after that you will have excellent battery life
EDIT:
by the way, the easiest way of calibrating the battery for android is to make sure phone is absolutely fully charged before you flash the rom
New posts
-
General [OnePlus 12][ROM][OTA][BOOT][Oxygen OS] Repo of Oxygen OS Builds- Latest: snowwolf725
