uRBANmIX_froyo_2.2.2 rom for huawei u8120,u8110 - Android General

Hey guys,this is a rom that i have worked on for a couple of days.Its based on cas_xp but with more tweaks and mods.
List of tweaks include:
1)compiled new wifi driver
2)new kernel (2.6.32.9) with overclocking to 768Mhz max with smartass_v2 governor
3)Added symlinks in busybox for terminal commands
4)modified framework for black pop-up menus and darker taskbar
5)created my own urbanmix style eye candy and revamped bootanimation.
6)google goggles now works well.
7)up to date apps
Iam using the old recovery 1.8 because i frequently use update-script instead of updater. Anyways if you get a problem installing just use the oldskool recovery
Working:
======
Everything: Fm_Radio,terminal,adb,usb tethering etc
Bugs:
=====
1)do not reboot phone with wifi on.
update 1 link:
http://www.mediafire.com/?nvcn4xsl3fotkf4
link to kernel source=======>http://www.mediafire.com/?oubwkd0ih6c87f9
update 2
=======
==>recompiled kernel again
==>fixed symlinks in busybox
==>fixed lights
==>added no frills for overclocking settings
==>revamped menus
==>fixed ADB Logcat on phone and pc
notes
1)swipe at the botom of the screen near the dock bar to flip between home screens.
2)do not set overclock after first install.reboot phone and set it then.
3)do not reboot phone with Wifi still on or you will enter into a bootloop.
i am facing the same problem cas_xp had. The driver was meant for eclair but somehow it manages to work.
Only huawei has the recent code and i don't think they have shared it.Stupid company.
4)do not overlock past 672Mhz.if you do expect ANR errors or a system not responding error during reboot.
you can just ignore it.
I added no frills CPU control because of its failsafe feature.
here is the link to update 2
http://www.mediafire.com/?64gmc661s9lx26w
full camera and video recording fix:
Some screen shots
Added a framework fix
update 3
========
This is a minor kernel update
1)added smartassv2 governor
2)fixed usb,adb issues.now you can take a screenshot of your phone using software like (wondershare)
3)removed lag in (no wifi kernel) and significantly reduced stickiness in (wifi kernel)
==>The small lag in video playback is as a result of mmc wireless extensions working around the atheros driver.phones that have Broadcom chips like IDEOS,u8160 don't have these kind of problems.
==> Broadcom chips are much better that is why most manufacturers prefer to use this on all or most phones.HTC and others seem to have adopted this.
==>The only solution i have found is gingerbread that seemed to have addressed these wifi issues
The bootimages are flashable so just put them on your sdcard and just flash them as you see fit.Boot time will not be affected so do not worry about long boot times after installing either kernels.
I haven't upgraded to gingerbread because of the FMRadio which i use alot.
This will be the final update.i am planning to upgrade to a much better phone.
see attachment called kernels.zip extract it and just copy the individual kenels to your phone and flash
here is the link to the kernels ==> http://www.mediafire.com/download.php?t3ri90tx77vetid
system internals
I decided to open up this old phone and see the internals
the images i took are big because i did not want to reduce resolution and remove the minute details like chip ids.
go to these links for the images:
==>http://www.mediafire.com/?hubb9x13fs76mm7
==>http://www.mediafire.com/?awza5dadm2d3mzh

Touch Screen not working on U8110!

Does this ROM has same bugs like all clocked 2.2 - reboots and problems with wifi ?

Please include your kernel source with your post in order to be GPL compliant.
Thread moved to the Android forums.

i have not had any problems with my over clocking i have a u8120. the problem is that i only have one device to test
the only issue with the rom is the video recording because i dont have the android sources.They are like 5-6gig and i have very poor internet
i have uploaded the kernel source so feel free to tweak and even rename it as much as you want.
my (.config) is also located there so try and replace it with yours
Here are the simple steps to compile for beginners.
==>cd into working directory
==>type (export ARCH=arm)
==>open makefile and edit the path to your cross compiler. just search for this string (CROSS_COMPILE ?= ) and replace the path with yours.
==>type (make xconfig)
==>add or remove whatever you want
==>type (make -j2) to take full advantage of core2duo or (make -j4) for those guys with quad cores.
changes done to kernel
=================
1)replaced the whole folder under(drivers/usb) to enable mass storage.psykes or joi's kernel are updated versions for gingerbread thus if you compile and run it, when you enable usb storage,the phone will freeze. backward compatibility was added in gingerbread to fix such issues
2)under (drivers/input/touchscreen) i replaced (msm_touch.c) to improve calibration.
things to do
=========
i will try to fix the sensors.

why you developing 2.2?? 2.3 is better and newer
Sent from my U8120 using xda app-developers app

sikiko , maybe i have something interesting for you , i 'll sent you pm

hmmm don't know 'bout you, but wifi doesn't seem to work on this ROM.... Flashed it with cwm 5.0.2.7 by the way. For the rest ROM is buttery smooth!

Wifi don't work !
p.p. I have working combination from this and cobaltium v14 ROMs. Still testing ...
I'm not sure but is this clocked core from dimonchik230 (from 4pda forum)?
p.p. Clocked core + wifi = reboot

touch Screen U8110
Dear sikiko, in my U8110 is not working touch screen. Can I fix it?

Gena79 said:
Dear sikiko, in my U8110 is not working touch screen. Can I fix it?
Click to expand...
Click to collapse
Ditto

==>i have fixed the lights issue and is now working
==>i was initially using a limited kernel to filter out some unwanted modules so i will try and make it s generic as possible to fix screen issues.
==>trying to fix wifi issues. It seems that if you reboot the phone with wifi turned on you enter a bootloop.
remember after first install do not overclock immediately. overclock after second reboot.
ill upload a second update soon
tip
in the adw launcher try swiping down on the dock bar to switch screens if you find screen is not responsive

Is it going to work on u8110 or not ?Imeen on touch screen problem.

screen is not responding: Плакать:

I try update2 on u8110and touch screen not working!

default kernel patch
try this small patch and see if it fixes the touchscreen

sikiko said:
try this small patch and see if it fixes the touchscreen
Click to expand...
Click to collapse
It is working now on u8110 with defailt_kernel.zip .
---------- Post added at 07:26 PM ---------- Previous post was at 06:40 PM ----------
@sikiko:Overcliking is max 600mhz now.

I test it and on u8110 everything working except video recording.I put adw ex launcher and it is much faster then adw standalone.
edit:grey camera.fix must flash with 1.8.14 cwr

Videocam illusion apk working and you can take a video with this applikations.

camera and video recording fix
goran gena and others.I have replaced the fix gray patch with a full patch which fixes color and video recording issues

Related

[ROM] [Huawei U8100/U8110/U8120] [Eclair] The Celestial Teapot RLS4d [2010-12-19]

The Celestial Teapot RLS4d
DOWNLOAD: TCT_RLS4d.zip
A ROM for made for and tested on Huawei U8100 Expert Sweden but has been confirmed to work on most, if not all, U8100/U8110/U8120 phones. T-mobile pulse mini U8110 needs an update after install (se end of this post).
This ROM was previously known and developed under a different name in the Swedroid forums and the Modaco forums
(btw, can we PLEASE get at least a generic Huawei forum at xda-developers?)
RLS4d
- RLS4d = RLS4b/c + overclocking fix
RLS4c overclocking fix
- There's a mistake in the frequency tables in RLS4c and the RLS4b camera fix that seems to affect some phones. This fix (attached) can be used on both RLS4b and RLS4c and will fix both the camera issue (RLS4b) and the overclocking issue (RLS4c).
RLS4c
- RLS4b + camera fix
RLS4b camera fix (attached)
- The camera fix replaces the kernel with one that uses the same PLL for overclocking as RLS3 did (PLL2). Appearently PLL1 is used by the camera so it wasn't safe to change it.
RLS4b
- New (QVGA hacked) version of market... propably needs a wipe.
RLS4
- New overclocking code in kernel, default speed is 633.6MHz but can be tweaked with SetCPU.
- Updated (and hacked) Market
- Updated several apps to latest version
- Removed Facebook (download it from Market if you need it) to free up some space in /system
- Replaced brut maps with latest official Google Maps (5.0.0)
- Propably something more that I've forgotten...
It's propably a good idea to wipe, since Market and Maps has been replaced.
RLS3
- Changed bootlogo
- Changed bootanimation
- Replaced Google Maps with modified version (brut17) Seems you need to do a full wipe after upgrading because the replaced Maps apk
- Updated DocToGo to latest version
- Added Flash Lite support
- Most likely updated something more that I've forgot
- Fixed a tiny error in the installation script that could kill USB-mounting if you go from stock ROM to my ROM without wipe:ing data.
RLS2
- Made overclocking code in kernel to be aware of those phones that runs at 600MHz with stock ROM.
- Added support for U8120 optical d-pad in kernel
- Added tun.ko module for OpenVPN users
- Updated LauncherPro
- Updated Roadsync
Kernel
- 2.6.29 based on kernel source released by T-mobile UK for the pulse mini.
- Slightly modified to work on non T-mobile Android builds.
- Added overclocking based on HTC Hero code by phhusson. Default install is NOT overclocked. Add overclocked kernel with update.
- Added swap support.
- Added compcache 0.6.2 swap free notify patch.
- Added LZO support (needed by compcache)
- Added EXT3 support (for better A2SD)
- Removed unused stuff, like PS2 mouse drivers, non-used touchscreen drivers and NFS support. The result is a smaller, but more useful kernel than before.
Android
- Android 2.1 based on the official U8100 Expert Sweden ROM
- Rooted with latest Superuser Permissions
- Fully odexed (system apps will not use dalvik-cache = more space on /data)
- Removed Launcher2
- Removed MyWeather widget.
- Removed TouchPal and AndroidKeyboard
- Removed ServoSearch
- Hacked a way around the "cust" system making Wifi work on other phones than just expert/se phones.
- Moved autorun.iso to /system freeing up 25Mb for apps on /data
- Added Darktremor A2SD 2.7.5.2 + swappiness bug fix.
- Compiled and added compcache kernel module + script to enable/disable compcache.
- No JIT by default but can be added with update.
- Hacked Vending.apk (Market) version 2006 that will greatly increase the number of available apps by faking HVGA (320x480).
- Fakes autofocus and more for more apps in the market
- Updated to latest Google Maps
- Updated to latest Google StreetView
- Added Launcher Pro
- Added Home Switcher
- Added the last flip-clock versionen of Weather widgets (yr.no).
- Added Googles News & Weather app/widget.
- Added HTC_IME & an AndroidKeyboard with Voice input support (also adds VoiceSearch).
- Added busybox with symlinks
- Added nano (texteditor)
- Added bash
- Replaced bootanimationen with a Nexus animation I resized for QVGA for another project.
- Replaced RoadSync with the offical upgrade you are allowed to download.
- Adjusted wallpapers in the original launcher to correct sizes and ascpect ratio for a QVGA device. May make them look a bit weird in the original launcher.
Installation
See post #2
Overclocking
See post #3
Compcache
See post #4
A2SD
See post #5
T-Mobile pulse mini users
UPDATE 2010-10-10: New zip file attached that also fixes the GPS. (TCT_tmo_u8110_update_2.zip)
If you can't get a phone network connection after installing, install the attached TCT_tmo_u8110_update.zip. That update replaced the ril libs with libs that are compatible with your phone.
JIT
Adding JIT gives a performance boost but I choosed to make it an optional update as it can cause problems with some apps. So far we know some apps that uses the google maps framework crashes if JIT is eanbled. Use the attached TCT_JIT_update.zip to enable JIT. There is also an update to go back to non-JIT if you change your mind later.
Installation
1. Flash a recovery image (tested with AmonRA.)
2. Copy the .zip file to your MicroSD card and boot the phone into recovery mode (call+volume-up+power)
3. Choose "Flash zip from sdcard" and choose the zip you just copied.
4. (optional) Wipe data+cache before rebooting. It may or may not work OK to not wipe data but it's propably best to wipe.
Overclocking
EDIT 2010-12-17: Removed all overclocking addons as they are now(with RLS4) obsolete
EDIT 2010-11-09: Updated all overclocking files with the new bootlogo.
EDIT 2010-10-11: Updated all overclocking files with the optical d-pad fix för U8120 phones.
EDIT 2010-10-27: Updated all overclocking files with support for phones that run 600MHz with their stock ROMs
Overclocking code has been rewritten in RLS4. The new kernel defaults to 633.6MHz which I believe should work on all phone. Let me know if it does not.
Use the app SetCPU if you want to overclock above the default 633.6MHz(default in RLS4) overclock.
SetCPU can be bought on Market or downloaded from XDA developers
Be careful with the "Set on boot" checkbox untill you know for sure if a speed is stable our not. Most phones will propably find a stable frequency in the 672-710.4MHz area but some can go higher. The highest allowed in the kernel is 748.8MHz.
Compcache
If you are using are allready using a swap partition on your SD-card, then you most likely shouldn't enable compcache. But if you do not want to partition your SD-card then compcache can be a good alternative.
Read more about how Compcache works here: http://wiki.cyanogenmod.com/index.php?title=Compcache
Enable compcache
In a terminal or using an adb shell type this:
$ su
# compcache.sh enable
Type free to confirm you now have 32Mb swap
Disable compcache
In a terminal or using an adb shell type this:
$ su
# compcache.sh disable
Type free to confirm you now have 0Mb swap
Advanced users
Compcache size, settings and swappiness is setup in /system/bin/compcache.sh
If you are an advanced user, you'll know how to proceed from here...
A2SD
(Only tested with AmonRA recovery image)
1. Backup your MicroSD card (IMPORTANT!)
2. Boot into recovery mode (see Installation instructions)
3. Choose to partition your SD card.
I recommend 32Mb for Swap and unless you plan to also move the dalvik-cache to the MicroSD card anything more than 512Mb for applications will be pointless as you will still be limited by the internal space for the dalvik-cache. You can of course use more space for swap if you have a large MicroSD card but I don't think it will make much difference but sure 64Mb won't hurt and on a 8Gb card you can afford it.
4. (optional) Convert EXT2 partition to EXT3 (EXT3 is an improved filesystem compared to EXT2).
5. Reboot the phone.
A2SD will now automaticly move your apps to the SD-card partition and enable your swap partition.
To change how a2sd works see this guide: http://forum.xda-developers.com/showpost.php?p=7021609&postcount=5
(a2sd jit is NOT supported in my ROM as I've choosed to provide JIT as an update instead)
NOTE: If you intend to use A2SD it's propably a good idea to enable it early. Some apps (at least my banking app) doesn't like being moved and have to be uninstalled and reinstalled if you move it from internal to SD or the other way around.
NOTE2: Don't EVER remove your SD-card while the phone is turned on if you use A2SD and/or swap.
NOTE3: Having your apps on the slower (compared to NAND) SD-card propably have a performance hit but I can't say I've noticed it when testing it. However I believe that if you also move the dalvik-cache the performance hit may be noticable.
Reserved for the future...
Hi there,
I saw you're post about the overclocking issue I have with the Vodafone 845 (huawei 8120) thanks for that.
So this rom should also be compatible with the 8120 ?
It seems you have added a lot of good stuff and I am going to try you're rom really soon.
I am also wondering if the overclock will work or do I still need to flash a 'stock rom' first?
Thanks for the hard work !
Xylograph said:
Hi there,
I saw you're post about the overclocking issue I have with the Vodafone 845 (huawei 8120) thanks for that.
So this rom should also be compatible with the 8120 ?
Click to expand...
Click to collapse
I believe it should. The kernel config from a stock U8120 that I recieved when doing the overclocking was identical to the one from a stock U8100 so I believe the phones uses the same hardware.
It seems you have added a lot of good stuff and I am going to try you're rom really soon.
I am also wondering if the overclock will work or do I still need to flash a 'stock rom' first?
Click to expand...
Click to collapse
Yes, if you did the 600MHz hack your phone will use the wrong frequency array and I haven't adjusted that array. Also I am not sure what other effects it can have by using the wrong frequency array and I do not even now why the hack makes it use the wrong array. Likely some firmware has changed when you flashed the wrong UPDATA.APP and it's propably a good idea to get back to the one that was intended for your phone.
Thanks for the hard work !
Edit : Maybe it is me beeing not so smart again,but I don't really understand which .zip file gives exactly what speed in post #3
Click to expand...
Click to collapse
652800 = 652.8MHz and so on... it's the speed i KHz as it is the format used in the frequancy arrays. Having digged into the acpuclock.c quite a few times now I took it for granted that everyone could see the connection but I guess I could make it more clear. Thanks for pointing it out.
I did a full wipe and partition sd with 32mb swap,512mb ext2,ext2 to ext3.
Flashed you're rom and everything seems to work great
You were right about the cpu reading though (still @ 600 Mhz) ..now installing 'stock rom' and hope the readings return to normal again.
Thanks again !
Edit : Tried to flash 'stock rom' but the update failed hlaf way,anyway my cpu readings were back to normal after flashing back you're rom (528 Mhz that is) after that flashed you're 691 Mhz zipfile and... It works !!!
Thanks a lot for the explanations ! really helpfull (I understand things a bit better now)
Now I have to do some testing if 691 Mhz is stable for this phone.
Do you have any recommendations (apps) for stress-testing ? (is setcpu stress test any good?)
I will report back with my findings.
Thanks once again
Xylograph said:
Now I have to do some testing if 691 Mhz is stable for this phone.
Do you have any recommendations (apps) for stress-testing ? (is setcpu stress test any good?)
Click to expand...
Click to collapse
Not sure about stress testing, haven't done much of it myself really. But if 691.2MHz is stable then you may want to try 710.4. If you are familiar with fastbooting you can extract the boot.img and do a fastboot with a different boot.img without flashing it.
I suppose Neocore could be a good stress test on our phones since they lack hardware 3D and have to do all the 3D rendering in software.
flashing atm on U8110. greetings from modaco
Gjole86 said:
flashing atm on U8110. greetings from modaco
Click to expand...
Click to collapse
Let me know how it goes, it should work fine just like old version unless the U8110 needs one of the touchscreen drivers I disabled in the kernel, but I really doubt it.
works fine for now .. gonna do stress test soon.
kallt_kaffe said:
if 691.2MHz is stable then you may want to try 710.4.
Click to expand...
Click to collapse
I did some testing and the 691.2 Mhz seems stable on my phone (VF845 - 8120) and since other available roms here are using you're 691.2 Mhz 'mod' we can safely say it is stable for this phone I think.
I also tried the 710.4 zip-file,but this resulted in a lockup in the boot-animation
A bit to much I think.
Anyway 163 Mhz more as stock speeds is still pretty amazing
btw. I was wondering if it is possible to uninstall some apps that come with you're rom ? I can't find them in the 'uninstaller'
Thanks
EDIT : Talking about overclocking got me thinking..Do you think it would be possible to undervolt in some kind of way to gain more battery-time (on lower cpu-speeds) ?
Hi,
Flash it to my U8100 but unfortunately it stuck on the booting animation.
Even when I flash the 633.6MHz update.
The phone works fine with your previous ROM (rls6_JIT I found at Modaco) and 633.6 MHz update.
Need your help to make A2SD works.
Thanks.
HI,
Works well on my t-mobile pulse mini,but gps not working.
runs fast at 652 speed ,please can you fix gps.
kallt_kaffe said:
Overclocking
Here are a bunch of different updates with different overclocking speeds.
As far as I know most phones works fine with 652.8MHz. My phone works pretty good ad 691.2MHz but I had at least one random reboot so I went down to 672MHz. Some phones may even be stable at 710.4MHz but mine isn't.
If anyone needs a lower speed or even wants to try a higher one, let me know and I'll compile and update for you.
I recommend the app SetCPU if you want to do some tweaking like setting up different speed profiles.
SetCPU can be bought on Market or download from XDA developers
Explanation about the filenames.The numbers are the speeds in kHz. So 672000 means 672MHz and so on...
Click to expand...
Click to collapse
dose these work on the pulse mini?
gareng007 said:
Hi,
Flash it to my U8100 but unfortunately it stuck on the booting animation.
Even when I flash the 633.6MHz update.
The phone works fine with your previous ROM (rls6_JIT I found at Modaco) and 633.6 MHz update.
Need your help to make A2SD works.
Thanks.
Click to expand...
Click to collapse
Have you tried to wipe data?
popred said:
HI,
Works well on my t-mobile pulse mini,but gps not working.
runs fast at 652 speed ,please can you fix gps.
Click to expand...
Click to collapse
I'll have a look at it as soon as I have time.
rickwyatt said:
dose these work on the pulse mini?
Click to expand...
Click to collapse
Yes, with my rom but gps is broken on pulse mini at the moment.

[ROM] [Huawei U8100] Froyo Wifi enabled version (Beta12)

I am not responsible for any damage or brick your phone. It is all at your own risk!
It is based on kallt_kaffe's Climbing Mount Impropable. Thanks Kallt_kaffe.
Update_wifi_U81xx_beta3.zip - 85.92 MB
Improved:
1) Calibration: Status bar click is better now
Fixed:
1) WIFI signal display
2) WIFI suspend will cause phone reboot
Updated:
1) Add RomManager
2) GMail, Maps, Youtube updated to the latest version
Maybe fixed:
1) DPad issue on u8120
Issue:
1) Wifi not working properly on multi AP BSSID
Also, I included the ClockWorkMod recovery image if you want to use it.
Edit on June 15:
1) Wifi driver upgraded to 2.2.1.151 from 2.2.1.25
2) Better Calibration hack
3) Some kernel fix from other developer
Issues:
1) Wifi is more stable now, but sometimes it has "Wifi turn off..." message
2) Hotspot is still not supported
update_u8100_froyo_beta4.zip - 86.26 MB
Recovery 2.5.1.8 is no longer supported, please use the newer one in post #2
Edit on July 08:
1. Wifi tethering support
2. Add TSCalibration app from 2.1 ROM, so you don't need to worry about calibration any more!
3. Add Huawei Launcher, if you don't like it, replace with your favorite.
4. Overclocking.
It is based on ShiftOK's beta2. Thx ShiftOK.
Issues:
Video recording, but I don't care this feature.
Huawei_U8100_Froyo_FRG83_beta5.zip - 78.58 MB
Edit on July 11:
1. Missed call /SMS reboot issues fixed.
2. CPU default freq 600MHz
3. aGPS.conf ( I didn't test it)
It is based on ShiftOK's beta2. Thx ShiftOK.
Huawei_U8100_Froyo_FRG83_beta6.zip - 78.58 MB
Edit on July 14:
Based on u8180 2.2.2 version, FUSIONideos mod
1. Wifi tethering supported
2. Miss call reboot fixed
3. CPU freq set 600MHz by default
Huawei_U8100_Froyo_2.2.2_beta8.zip - 83.67 MB
If you have update issue, you could use Nand backup and restore. Try my backup
nandbackup.froyo-b8.zip - 103.35 MB
Edit on July 15:
Based on beta8. Google account login issue fixed and wifi reconnect after idle is still working.
Huawei_U8100_Froyo_2.2.2_beta9.zip - 83.02 MB
Kernel source, the config in your /proc/config.gz
kernel.u81xx.tar.gz - 93.92 MB
Edit on Aug 02:
Beta 10:
1. Kernel is not overclocked for stable issue.
2. Improved WIFI performance.
Huawei_U8100_Froyo_2.2.2_beta10.zip - 82.84 MB
Edit on Aug 16:
Beta 11:
1. Use Huawei's kernel and Wifi module, so no overclock. And DPAD may have issue too.
2. Google login issue fixed.
3. Some app update
update_beta11.zip - 92.07 MB
Edit on Aug 19:
Video camera fixed. Please download the attachment libaudio.zip to extract and replace /system/lib/libaudio.so
Beta 12:
1. Private call no ring issue fixed.
2. Data plan icon on status bar is cleared.
3. Integrated with libaudio.so for video camera
Download the attachment View attachment update_beta12.zip and install it on top of beta11. It won't erase any data.
My CM7 build.
Link is removed because the version is not stable.
FM Radio is not working.
Boot frozen should be gone. U8120 DPAD issue should be gone too. Please report it. Tired of the calibration.
EDIT:
CM7 on u81xx has a lot of issues, like system lag, boot frozen, USB tethering etc. So I am not going to work this anymore.
gonna try it now
Vodafone 845 (Huawei U8120)
Me too. I'm on Huawei U8110... Reporting soon !
downloading and testing on U8110 begins now.
thanks on the progress i hope there is real chance to make froyo to be stable on our phones
It looks good and works faster than before!
One thing bothers me, i need to calibrate screen but i cannot find that option in settings>display ?!
Wifi works, bluetooth works ... that's for now !
DJ_Uro_UE said:
One thing bothers me, i need to calibrate screen but i cannot find that option in settings>display ?!
Click to expand...
Click to collapse
That's because there is no calibration tool for Froyo, yet. The Huawei own won't work.
Thanx for a quick reply! I will keep that in my mind
just installed and having a few random lockups and reboots so far.... Vodafone 845/Huawei U8120
DJ_Uro_UE said:
It looks good and works faster than before!
One thing bothers me, i need to calibrate screen but i cannot find that option in settings>display ?!
Wifi works, bluetooth works ... that's for now !
Click to expand...
Click to collapse
u said that ur phone is U8110? is it the t-mobile pulse mini or from other carrier? mine is u8110 and doesnt connect to network(expected, that prob was present in other roms for U8100)
from running the rom for a few minutes, I have found a few things:
Random lockups, resulting in the phone reboot (to be expected for a 'new' build)
No touchscreen calibration (but again I'm assuming that is being worked on)
Battery appears only 50% but is deffo fully charged up (according to the previous rom I had installed)
At the moment, I think I will personally revert back to my previous rom until there are more updates for Froyo on our U81xx devices
Testing on U8110 (spain)
wifi : ok
calibration: not work properly
notification bar: not open
blueto...: ok
wifi icon: level wrong
battery level: ok
no file manager?
no radio?
no contacts from SIM
also, nice try!
Gjole86 said:
u said that ur phone is U8110? is it the t-mobile pulse mini or from other carrier? mine is u8110 and doesnt connect to network(expected, that prob was present in other roms for U8100)
Click to expand...
Click to collapse
It's the Huawei U8110! It's connecting normally to my MT:S Telekom Serbia carrier.
Still no loockups after 9 hrs since the last boot. Wifi reports error after turning off, but it works. I'll gonna test it in further days!
Wifi doesnt work on u8120. When i try to start the wifi, it says error :/
dylan2009 said:
Testing on U8110 (spain)
wifi : ok
calibration: not work properly
notification bar: not open
blueto...: ok
wifi icon: level wrong
battery level: ok
no file manager?
no radio?
no contacts from SIM
also, nice try!
Click to expand...
Click to collapse
Random lockups are the d-pad... kaltfamme can fix this he said.
calibration meaby try HTC calibrate
work on my U8110 few bugs but great finally froyo
this should mean that we get our own forum section but we won't most likely
link is dead
edit: can anyone to upload it again somewhere?
I have slow upload ... it will take two hours to upload it
huh its so strange .. why it have network on other U8110 models but not on mine .. id kill to know why WHYYY
link is dead
edit: can anyone to upload it again somewhere?
[/quote ]
nobody ?
Click to expand...
Click to collapse

[GB][08-09-2012] CyanogenMod 7 for Motorola Milestone 2 (Android 2.3.7)

Cyanogenmod 7 for Motorola Milestone 2
This is an unofficial Milestone 2 port of CM7.
[ Downloads | Google apps ]
Known limitations
720P recording is not working
ALT lock does not work
Click to expand...
Click to collapse
Changelog:
08.09.2012 - Upgraded CM sources
01.09.2012 - Added OTA updater, upgraded CM sources
21.02.2012 - Upgraded CM sources (fixed blank screen after unlocking issue)
09.02.2012 - Upgraded CM sources
22.01.2012 - Backported ICS animations, UK 2.3.4 fingerprint, fixed Exchange FC for polish locale
04.01.2012 - Upgraded CM sources (e.g. T9 dialer)
29.11.2011:
Moved device specific settings to its own tree in the settings
Added lower backlight level
New multitouch module (no delay at startup)
Stock compass callibration app and audio effects
20.11.2011 - Hopefully fixed some wifi issues
18.11.2011 - Wifi tethering does not need DUN APN anymore
18.11.2011 - Fingerprint changed to UK 2.2 (fix Market from hiding some apps)
12.11.2011 - Tweaked CPU, camera, build.prop and recovery settings (Endless7);
settings for Droid2Bootstrap (will not destroy 2nd-init anymore)
11.11.2011 - Added keyboard switching, option to force PLMN display, more multitouch points
08.11.2011 - Fixed camera's photos
08.11.2011 - Initial release
Click to expand...
Click to collapse
Note:
If you have updated to stock gingerbread, you can't use this rom until you downgrade.
Instructions for upgrading from stock ROM:
1) Install Droid2 Bootstrap Recovery
2) Boot into recovery
3) Optionally: create a backup of your data
4) Choose Install zip from sdcard -> Choose zip from sdcard and select downloaded ZIP file.
5) Optionally: install Google Apps the same way
6) Wipe data/factory reset
7) Wipe cache partition
8) Reboot and enjoy
9) Optionally: use attached Baseband switcher app if you have troubles with phone signal.
Click to expand...
Click to collapse
Instructions for subsequent upgrades or upgrade from any CM7.x ROM:
1) Boot into recovery (long power off -> Reboot)
2) Choose "Install zip from sdcard" -> "Choose zip from sdcard" and select downloaded ZIP file.
3) Advanced -> Wipe battery stats
4) Advanced -> Wipe dalvik cache
5) Reboot and enjoy
Click to expand...
Click to collapse
As you can see, the update from the stock ROM requires a complete wipe, so be sure to backup your important data!
GIT sources:
repo init -u git://github.com/tezet/android.git -b gingerbread
Any collaborators are more than welcomed!
Click to expand...
Click to collapse
Donations
If you like and appreciate my work, and you may donate here (now in English).
Click to expand...
Click to collapse
Many thanks to Quarx for his Defy port and all folks involved in [email protected]
Looks very promising. Browsing your github right now.
Edit: Thanks for your effort. I was trying to start a similar project but some events IRL left me with NO free time at the moment. If there's any info you'd like to get from me just let me know.
What is the difference between this and the CM made by Endless7?
If this is really based on m2 files, that is a great progress
How is hardware video decoding working?
Edit: Difference is that there is no need to patch every build to make it work, and fixing things like video or 720 will be more easy to do.
And the really big difference, is that this way, we can get official cm7 support.
Yes, DSP decoding is working, including 720P.
I got lot of troubles with 720P encoding and gave up for now. Maybe I will come back to the topic, but for now I have already spent too much time on this...
Nice work, thanks!
Will I get anything extra in compare with Endless7 build? I mean, if I will now use your build instead CM7 from Endless7, will I get any perfomance boost or anything else than 720p decoding (can it hw decode same formats as stock firmware btw?).
Just asking.
Anyway thanks for this - official cm7 support would be nice.
I would say the most noticable difference is a better touch screen. Also the battery seems to be slightly better, but that may be very subjective opinion...
I'm not sure how about general DSP decoding, but at least h264 720P decoding didn't work in Defy build.
And I'm not sure what is the current state of Endless7's ROM, but this is the most noticable difference when I switched to this ROM.
From the APPs point of view, it is pure CM7.1, without any addons, so you may miss some Endless7's extra stuff...
Edit: I haven't verified lot of formats, just few 720P videos. If you notice anything missing in comparison to the stock rom, it may be probably fixed easily...
Forgot that, this roms uses another kernel
UK kernel should improve touch
Wonder if we can make it boot with a 2.3 kernel...
Another thing, phone will be listed as a953 on pc instead of 722, with uk kernel.
I guess I will wait for UK version of GB release before I will attempt to switch into GB kernel. I would like to use the same source of kernel and bpsw. There's no big gain in running GB kernel, really.
Yep, we are just a few days away from uk release.
2.3 kernel improve touch significantly from uk 2.2. Besides that not much more.
Is the multi touch working properly?
Yeap, the same as stock froyo.
I mean, the gingerbread roms here have 6 points multi-touch, is it the same here?
No, I haven't included that. You may add it by yourself, it's just a matter of module. Maybe I will include in the next builds, but it will be disabled by default. I'm not sure if it doesn't have any negative impact on touchscreen responsiveness...
Edit: why would you need that anyway? Is there any real-life use case other than keyboards?
As far as I see:
# use default multitouch configuration
ro.product.multi_touch_enabled=true
persist.sys.multitouch=2
You could change to 6 and you will get 6 points touch (maybe you have to add the module)
But, dont use anything higher than 4. It makes cpu consumption higher and laggy response in ALL roms.
Thank you for this great work !
A lot of people will be interested to know that it's possible to install your update.zip without data wipe when coming from Endless's CM7.
Forgot about it. It's perfectly OK to update from any CM7 rom without wipe. Just follow the usual upgrade procedure.
Could you consider adding a keyboard layout option in your nexts builds?
Also, alt-lock is not working at the moment. It's not critical though...
I also noticed bad 3d performance in Quadrant.
On the "planets" test, using Endless cm7 i get something like 60fps, but 10 with yours. Didn't notice any change when playing with n64oid/ogl-es though.
Edit : Scored 13.6 at Nenamark2, 21.6 at Nenamark1. Could somebody compare with Endless's CM7?
Edit2 : Concerning Quadrant, I remember getting 10fps too when on stock french 2.2.2 rom.
Thanks. Keyboard switch is on the top of todo list
I will look into 3D performance and compare it tomorrow with stock 2.2.2. Perhaps that's the UK's libs issue...
As for the ALT lock, that is on the very bottom of todo list I believe it does not work on Droid 2 either.
Edit: just confirmed the same result (10FPS) with stock 2.2.2 UK rom. Anybody could confirm it is really faster on Endless7's ROM?
I have a major bug with the camera : files created are 0byte large.
Video recording works fine.

[9001][KERNEL][GB] SkyHigh V1.5 [Updated 08-02-13] [Additional BigMem edition]

This is the official thread of my SkyHigh kernel for the Samsung Galaxy S Plus aka GT-I9001. V1.5 is my final release, please read the FAQ in post #2 for more details. Please refer to post #3 for changelogs of new releases, all available downloads are at the bottom of this first post. If you don't know how to get back to stock kernel you MUST NOT install this !
Disclaimer: this piece of software is not for the unexperienced and might bring you in a situation you can't resolve yourself. So don't use it if you fear the potential danger of bricking your device. I am responsible for nothing related to this kernel and therefore won't help. If you decide to use it anyway you agree to be ultimately responsible for all consequences that may occur. So you have been warned !
Terms of use: Remember the power of reading ! If you can't find some particular information on the first page use the search function, it is your best friend.
Besides there are even guides and tutorials all over the forum and in most cases your question was already answered.
If you take a moment and read through the WHOLE post below and a few more moments to read some of all the stuff in other device related threads of this forum, you will find ALL you need just there.
It's not invisible so you CAN find it. And forum rules and good manners tell you to do it exactly like this. And I WILL ignore every question that is already answered here.
Obey the rules !
Kernel feature list
- OC up to 1.8 GHz, UC down to 122 MHz (customisable eg. via AnTuTu CPUmaster/SetCPU)
- Undervolted (750 mV minimum) with VDD support (customisable eg. via AnTuTu CPUmaster/IncrediControl)
- many CPU governors included, smartassV2 is default
- many I/O schedulers, SIO is default
- optimized for high performance AND extreme low battery usage
- JFS and CIFS support
- TUN included (VPN support)
- cleancache (up to V1.4d)
- increased loudness
- all useful Thunderbolt and Adrenaline Shot main tweaks combined, optimized for I9001 and integrated
- init.d support (use carefully, because tweaks are already integrated, installing/executing them twice can result in strange failures)
- Thunderbolt's LMK60 addon (aka adrenaline shot's supercharger V6 tweak) already built-in, DO NOT install separately !
- Thunderbolt's remount script integrated
- Thunderbolt's zipalign script integrated
- Thunderbolt's graphics addon integrated
- Thunderbolt's binary addon integrated
- Thunderbolt's sqlite addon integrated
- Thunderbolt's screenstate_scaling script not included but compatible
- enhanced 3D graphics (updated internal kernel drivers)
- I8150 GPU libraries included in CWM package up to V1.4d, optional in V1.5
- custom bootanimation support (animation NOT included, place your own here: /system/media/bootanimation.zip)
- custom bootsound (/system/etc/PowerOn.wav)
- sdcard speed increased
- improved jpg quality for better camera pics
- GPS faster fix in V1.4x only
- in V1.5 stock GPS files are untouched
- and some more which I already have forgotten
​
This kernel is meant for use with ANY Gingerbread stock ROM and custom ROMs as well (i.e. Android V 2.3.x only !). To prevent compatibility problems with custom ROMs that include system tweaks like Thunderbolt and Adrenaline Shot any existing init.d folder will be purged while installing the SkyHigh kernel. This is not a bug but a mandatory feature !
If you think you have an important script you will still need with SkyHigh like the screenstate_scaling script, copy it to your (internal) sdcard first then copy it back to the empty init.d after installing SkyHigh.
init.d support means that SkyHigh kernel will execute any scripts inside a folder /system/etc/init.d automatically but obviously only if these exist.
If you are using a custom ROM without init.d folder or any stock ROM you might have to create the init.d folder yourself. For more details there are tutorials in this forum.
Install instructions:
1. If you don't have CWM (FeaMod Recovery) install this first. If you never heard of that learn all about it here:
http://forum.xda-developers.com/showthread.php?t=1331164
2. Now make a complete nandroid backup of your phone with CWM
3. Download the attached CWM zip package
4. Copy it to your internal sdcard
5. In CWM choose "install zip from sdcard", then "choose zip from internal sdcard"
6. Select the downloaded file "GT-I9001_SkyHigh_kernel_V1.x_CWM_signed.zip"
7. Confirm install with "Yes"
8. Wait till you see the message "Reboot to use SkyHigh kernel V1.x !"
9. Do so like the message says.
10. On first boot this may take a while. You will see the Samsung logo and then a black screen for at least 2 minutes up to 5 minutes. If this happens hang on, don't touch anything and don't switch the phone off or pull the battery. This would most probably break your ROM !
11. Usually many files and databases are optimized on first boot but eventually you will see the lock screen or PIN dialog. Then you are all set and beginning with the next boot this will be much faster, promised
Remark: especially on preoptimized (custom) ROMs this won't happen since there's not much to optimize. So it's no bug but a feature when it doesn't happen and your phone boots up in less than a minute
​
If you want FeaMod Recovery together with SkyHigh kernel just follow the install instructions above. Install desired version of FeaMod first and then SkyHigh. You will end up with the combination you wanted.
If anything went wrong during install just try again.
If you have any issues with your sdcard(s) this is not due to SkyHigh or its install procedure. I will never ever even touch your sdcard(s). But it is always a good idea to have a rather current backup of the sdcard(s) handy. CWM makes no backup of these, so you have to do that manually.
If your phone doesn't boot even after 10 minutes waiting (see step 10.) or you end up with a damaged system because you didn't wait long enough just go back into CWM and restore the backup you made.
If you can't boot into recovery anymore just install FeaMod 1.2 via Odin again.
If you got severe errors AND didn't make a backup because you knew better than the developer don't even dare to beg for help.
If you encounter any other errors report them here but be sure that this is no feature or problem that was already described above or in the FAQ below.
While V1.3 lacks some of the features above (especially the Thunderbolt/AS tweaks) it is totally safe with sd cards, at least I never got a single report on that issue. The older V1.3 is still added as attachment for your convenience although V1.4d already fixes all sd card problems.
FAQ
For personal reasons resulting in a tremendous lack of time I have to pause all my xda development for an indefinite time. Sorry about that, but I also really can't answer all the questions you might have so please stick to this FAQ and otherwise ask other experienced users/developers in Q&A section.
Besides I'm planning to get a new phone device in just some months so this also means that SkyHigh V1.5 is my last contribution to the i9001 development section. So SkyHigh V1.5 is provided AS IS and there will be no further support whatsoever on my behalf. But V1.5 was beta tested thoroughly for about 3 weeks by several experienced users here before it was published so it is very unlikely that there are still any crucial bugs in SkyHigh V1.5.
Last but not least broodplank1337 offered to maintain SkyHigh in the future but since he is also quite busy please don't press him and give him the time he needs to answer any requests.
Thanks to all members who respect the work of the developers and obey the forum rules for a great time and experience, maybe we will see again one day in another device section on xda-devs.
1. Q: I have sd card issues with SkyHigh kernel, what can I do ?
A: This was fixed in V1.4d, don't use any other 1.4 version ! For more details please refer to post #190 (http://forum.xda-developers.com/showpost.php?p=24247858&postcount=190) first, then have a look at the changelog (V 1.4d) below in post #3.
2. Q: What's the status of my CM7 port ?
A: this is a very complex topic and I paused the development in mid March in favor of this improved kernel. I continued on CM7 for about two weeks in April but now I had to stop it permanently (see first sentence of this FAQ).
I lost any contact to YardE since months so I guess he also surrendered his i9001 development. I still supported some very dedicated users with my knowledge and experience to help them to continue the CM7 porting project but none of them is an advanced developer or even coder so they are all still in learning phase.
3. Q: What about the car dock recognition ?
A: The card dock is not recognized correctly in any custom i9001 kernel that is compiled from Samsung's original i9001 source codes (Linux kernel version 2.6.35.7). However the phone will be at least charged in the car dock with kernels that are compiled from Linux version 2.6.35.14. SkyHigh V1.5 is mainly based on 2.6.35.14 (with some exceptions for Gingerbread compatibility reasons) so the charging works with SkyHigh V1.5 (only). This was tested and verified by Rhonin86, thanks mate.
4. Q: How do I provide a log for debugging ?
A: You must be familiar with adb to do so, if you are not you can only read the adb guide and learn everything about it here:
http://forum.xda-developers.com/showthread.php?t=879701
Then use the following commands to generate two different log files:
Code:
adb shell "dmesg > /sdcard/log.txt"
adb logcat > logcat.txt
If the first command results in a permission error try this:
Code:
adb shell su -c "dmesg > /sdcard/log.txt"
5. Q: Is Script Manager needed to run any scripts in init.d or bolt_scripts or somewhere else ?
A: Not at all. You can delete bolt_scripts if you still find that on your sdcard or somewhere else. You can uninstall Script Manager if you like. And screenstate_scaling script (or any other) will run automatically if copied to init.d with correct file permissions (755 or rwxr-xr-x)
6. Q: May I use SkyHigh kernel with my own custom ROM and publish that on xda-dev ?
A: Of course you can if you don't ask for money for your ROM. This is not a piece of proprietary commercial rip-off nonsense and must not be (re)selled. I am glad if you find it useful, but leave it well alone if you don't like it
7. Q: What are the best cpu governors, i/o schedulers, overclocking and undervolting settings and so on ?
A: the default ones ! Don't touch anything here if you are not 100% sure what these settings do and how they will help you. The given settings base on over 5 month experience and testing on my own i9001 and some others. But as stated in post #190 no two phones are exactly the same so not all of our phones work best with the very same settings. Therefore I added the possibility to customise all these settings if really necessary. But you shouldn't change any of these settings at all if you don't have severe kernel related problems with your phone.
8. Q: The feature list says that bootanimations are NOT included but supported. After I installed version 1.4/1.5 I've got a new bootanimation
A: that's not a new animation, that is just one that was already in your ROM before (in /system/media/bootanimation.zip) but never showed up so far. Most probably it got there with a custom ROM or UOT kitchen or any other mod/app that supports the android default animations. This file normally isn't used on the i9001 because Samsung implemented a proprietary bootanimation method. SkyHigh reverts the Samsung bootanimation procedure to the android default one which is also used on AOSP ROMs like CyanogenMod. So this is also one of many necessary modifications to make a kernel AOSP compatible !
9. Q: How do I install a custom bootanimation ? All my attempts failed.
A: look at FAQ #8 above and at kernel feature list in post #1 !
​
Changelog
Final update to V1.5 and V1.5bm [08-02-13]:
- source files updated from original patch level 7 (Linux kernel version 2.6.35.7) to patchlevel 14 (Linux kernel version 2.6.35.14). This can be regarded similar as a service pack release of Windows (more stability and less bugs overall)
- especially kernel GPU drivers for the Qualcomm Adreno 205 chip are more stable on my device (had some issues with one app that was solved by this update)
- also the car dock driver is improved, battery is now charged in Samsung's original car dock (though car dock mode still isn't activated, see also FAQ #3 above)
- EGL graphics libraries that come with SkyHigh V1.4x (these libraries are OUTSIDE the kernel, but included in the CWM install package) are EXCLUDED now and only come in an optional library pack (because these are the only ones that have at least significantly better performance in benchmarks, but some users say they are more laggy in everday use).
This means for V1.5 that everybody can decide for himself if he wants to use the EGL libraries that come with his ROM or the i8150 libraries or even any other versions that he will just install himself. More details can be found in post #566 http://forum.xda-developers.com/showpost.php?p=37391142&postcount=566
- faster GPS fix that comes with SkyHigh V1.4x was also EXCLUDED since it didn't work for some people. SkyHigh V1.5 doesn't even touch any GPS related files or drivers, there is just the original Samsung stock driver inside the kernel, nothing else.
But after installing a new kernel or ROM the first initial sat fix usually takes really long (2-5 minutes). This is normal ! But after that it should be faster, about 5 to 60 seconds depending on factors like position, movement, shielding and so on.
So if you have any GPS issues it is NOT due to the kernel but due to your (custom) ROM or any other GPS related factors (and there are many). Please refer to the following posts to learn more about possible GPS issues. These posts were only meant for V1.4x since only this version replaces gps.conf but they also provide some general details about GPS issues: http://forum.xda-developers.com/showpost.php?p=24301498&postcount=205 and here: http://forum.xda-developers.com/showpost.php?p=24565586&postcount=319
- finally there is a separate BigMem edition of SkyHigh called V1.5bm
This BigMem edition provides 376 MB available internal memory but breaks 720p video recording on some devices. While it still works on some devices there are rumors that it is also still possible on any device but by some alternative method. I never tested nor even used 720p recording on my own device since with such a poor camera it is totally pointless to even try HD recording IMHO. So if you want SkyHigh V1.5 WITH 720p video recording you have actually 3 choices:
1. you are lucky and everything works with V1.5bm anyway
2. try to find an alternative solution for video recording, maybe another camera app or a custom ROM is the solution. BTW: hiej claims that it works on his device with BigMem edition, maybe it's a feature of his GingerRevenge ROM so you should test that one first
3. just use the normal V1.5 of SkyHigh, it has 359 MB available memory which is still better than the stock kernels
Update to V1.4d [06-04-12]:
- sdcard problem fixed
In prior 1.4x versions the external SD card is suspended ("ejected") when the phone goes into sleep mode. On some phones the automatic re-detection of the SD card fails several times at wakeup so that it can't be accessed any longer. No data is corrupted though and reboot of the phone or reinsertion of the card are possible workarounds. As this is not practical in everyday use V1.4d solves this sdcard issue by reverting the sdcard power management routines to the original Samsung source version.
Just to be on the safe side I recommend everyone to use this modified V1.4d instead of V1.4 even if you have no sdcard issues so far. At least I do so
Update to V1.4c [06-04-12]:
- obsolete
Update to V1.4b [05-04-12]:
- obsolete
Update to V1.4a [02-04-12]:
- obsolete
​
Awesome! This is without doubt the best i9001 kernel so far, I really like it in my ROM, thanks for this great kernel
(by the way, is this version different then the one you send me to use in the kernel?)
Sounds amazing! This is the same one in broodrom 4 or is this updated?
So far it is working perfectly for me.
Thanks!
Richie
Sent from my GT-I9001 using XDA
no good for me.. hangs and reboots with simplistic F1
broodplank1337 said:
Awesome! This is without doubt the best i9001 kernel so far, I really like it in my ROM, thanks for this great kernel
(by the way, is this version different then the one you send me to use in the kernel?)
Click to expand...
Click to collapse
The kernel is the same but I fixed the install script
skywalker01 said:
The kernel is the same but I fixed the install script
Click to expand...
Click to collapse
Ok great won't need to change it then for now ^^
carlese said:
no good for me.. hangs and reboots with simplistic F1
Click to expand...
Click to collapse
AFAIK simplistic F1 uses FeaCore kernel nonOC which means your phone doesn't like OC/UV kernels. As SkyHigh is OC/UV you can't use it unfortunately, sorry.
skywalker01 said:
AFAIK simplistic F1 uses FeaCore kernel nonOC which means your phone doesn't like OC/UV kernels. As SkyHigh is OC/UV you can't use it unfortunately, sorry.
Click to expand...
Click to collapse
cranium v6 works good with simplistic..
carlese said:
cranium v6 works good with simplistic..
Click to expand...
Click to collapse
OK, if you can provide me some logs I can have a closer look into that, maybe it also applies to others.
But I will need the output of these two adb commands:
Code:
adb shell "dmesg > /sdcard/log.txt"
adb logcat > logcat.txt
If the first command results in a permission error try this:
Code:
adb shell su -c "dmesg > /sdcard/log.txt"
WOW - THX for your work
Hi Skywalker01,
nice to see the resuts of your intense work. Will try it later due to the fact that work is calling
By the way did you find a way to make the kernel recognize the original charging dock meanwhile ? Or if not is it still in your focus ?
I wish you success porting CM and keep on your good work.
Cheers
Rhonin
thanks for the kernel
i can't mount my sdcard in cwm. i currently use this kernel with brood rom.
first time i had this problem was after installing vitaliys kernel. changing kernel and doing a hard reset via *2767*3855# helped (as you can imagine you can't reset it in cwm since you have to mount the sdcard which doesn't work). so i got the suspicion that this is a kernel issue.
i know you said
If you have any issues with your sdcard(s) this is not due to SkyHigh or its install procedure
Click to expand...
Click to collapse
but i'm not sure if this is what you mean since you made mods on the sdcard.
your kernel is amazing sky. i think you made the best kernel for 9001. my phone is like an f-16 because of your kernel
awesome kernel <3 (i got a little question how is the CM7 development going?) (offtopic)
skywalker01 said:
...
- init.d support (use carefully, because tweaks are already integrated, installing/executing them twice can result in strange failures) ...
Click to expand...
Click to collapse
So this means we don't need SM to run all init.d scripts run at boot?
Sent from my GT-I9001 using Tapatalk 2 Beta-2
Hi
Tq for ur kernel...its very amazing the music sound wad better..keep it up bro...
Sent from my GT-I9001 using xda premium
Seems like i am building a new version of Simplistic afterall. Thanks a lot for the great kernel!
Sent from my GT-I9001 using Tapatalk
Woow this sounds promising. Im gonna use it for my ROM if you don't mind...
Sent from my GT-i9001 @ LionROM
How's the battery like with this one?

[KERNEL][9305] HboKernel v0.3 - 02.02.2015 (NamelessRom 5.0)

Hi all​
Introduction
I cannot call myself a developer or a kernel master at all. I'm just good at discovering and learning new things and in fact that's the way my journey with kernels started. At this point I want to start a new thread for something different from my earlier work, porting Boeffla kernel.
Features included:
Compiled with 4.9 Linaro toolchain
CPU OC up to 1600Mhz
ZZmoove as default governor (with moderate profile) - best for smoothness/battery life
Zen and Row I/O schedulers
Undervolting interface introduced
Configurable Touchboost
Configurable Touchwake
Charging interface
Boeffla Sound 1.6.6
Dynamic Fsync
Switchable Sharpness Tweak
Led configurable (fading, strength)
Configurable Android logger
Configurable printk logging
Readable: asv level, CPU temperature
Disabled some debug
Few minor tweaks (check github if interested)
If I forgot something - Github is up !
What kernel features may we expect?
F2FS support
Dualbooting support (if I can handle it properly)
What you say?
Compatibility
Flash only on proper roms!
As for now we have only Lollipop version, compatible with NamelessRom (you may try with others LP).
Download
You can download the most recent kernel here -> Click
Source
Github link - Click
Credits
These men never refused to give me a helping hand, advised me what to do and, more important, without their work this kernel wouldn't even exist (opensource doesn't mean no respect!).
@JustArchi
@Lord Boeffla
@Yank555
@ZaneZam
@arter97
Samsung :good:
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can't and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash anything.
Camera bug info: (hidden, only applies to Samsung ROMs)
It appears that some people (like me) have problem with camera. In exactly THIS situation: do full wipe, flash sammy rom+boeffla kernel, reboot and launch camera. Effect? Camera closes with "camera failed" popup.
Possible solutions:
Option 1 is good for people that rarely change their ROMs (and it fixes EVERYTHING), whether option 2 is better for people changing their ROMs more frequently (however, it's always good to have backup of your SlimISP on sdcard).
Option 1. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my HboKernel
Option 2. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, grab file (SlimISP_XX.bin, where XX differs between phones) from /data/cfw/ and backup it where you want. Then if you can always copy it to /data/cfw if your camera doesn't work with my ported kernel. (ATTENTION: Unfortunately this file does not always appear - still don't know why )
Option 3. Read this thread and follow steps --> click
Possible explanation, my own research:
I found out that people with ZD and GD will have camera working always. Why? Because these (SlimISP_XX.bin, where XX differs between phones) files are packed within kernel (zImage exactly) and ONLY THESE two are provided by Samsung in their opensource release... Interesting, isn't it? For example, I have GH version, which I may add to zImage manually, however adding more of them breaks the size limit for boot partition, so it's impossible to have all these versions together. However, stock kernel somehow has them, don't know how because zImages aren't extractable.
And just to confirm my theory, I've compiled a kernel with mine version of camera firmware, made full wipe, installed sammy rom+my kernel, rebooted, launched camera and voila - it worked
Thus, we has to live with this bug unless Samsung do something about it or someone else proves me that I'm wrong
I say, may good luck be with you accomplishing these features in the kernel :good:
Best of luck with this project Hbohd
Thanks to you, there is some life potential remaining for i9305!
Long life to i9305 and may the (dev) force be with you HboHd!
Thanks for your work!
+1 Nice one.
Hbohd said:
What you say?
Click to expand...
Click to collapse
I say: it's freaking interesting!!!!
Just a supposition , for the future , the MDNIe hijack for more natural colors would be great , i'm waiting the F2FS version to switch to NI3
aaz03 said:
Just a supposition , for the future , the MDNIe hijack for more natural colors would be great , i'm waiting the F2FS version to switch to NI3
Click to expand...
Click to collapse
Hmm.. Isn't 'Screen mode' under Display settings enough? It gives a little bit of difference without need of additional kernel's code modification.
New alpha 0.1
Okay, to keep this project alive, to show off some progress step by step and to satisfy flashoholics - I've decided to release my small achievements in form of alpha kernels
Firstly, let's restart naming convention of the kernel. It will be simple x.x now, starting from available below 0.1 version :cyclops:
Small changelog:
removed debugging in many places
compiled with linaro 4.9
few tweaking commits
Let's say that due to my 'stupidity' or magic ability to forget something, I've spent on it many hours today :silly:
Is Insecure ADB fixed?
Just gave the new version a flash, insecure adb wasn't set. I've fixed it up and attached it.
@Hbohd if you want to patch this in later veresions, make these changes to the /ramdisk/default.prop
- change ro.adb.secure=1 to 0
- change persist.sys.usb.config=mtp to mtp,adb
then just copy the adbd file from my /sbin
This is for old bootloader only?
SE disabled on 0.1?
it says nothing in system anymore below build
you should maybe consider a txt file in the zip and jot into it every time you change something before you forget
v0.2
tweaked this
added that
etc..
@Hbohd tks for your excelent work!!!, one notice, the I9305 didnt charge the battery when is off. Only, starts and boots normally, and there starts charge. Its only a detail, but in my case Important. Tks again for your work!!!!
ShonkUK said:
SE disabled on 0.1?
it says nothing in system anymore below build
you should maybe consider a txt file in the zip and jot into it every time you change something before you forget
v0.2
tweaked this
added that
etc..
Click to expand...
Click to collapse
sham79 said:
This is for old bootloader only?
Click to expand...
Click to collapse
I haven't stated anything different from what is true I mean, if I write that you can you use it with new bootloader or SE is disabled - then it would be true
I think that in next release I will disable it (simply forgotten due to my compiling problems mentioned earlier).
Oh, and I don't need another changelog when everything is written in the git I haven't just suceeded in uploading it to the github yet :/
machotecba said:
@Hbohd tks for your excelent work!!!, one notice, the I9305 didnt charge the battery when is off. Only, starts and boots normally, and there starts charge. Its only a detail, but in my case Important. Tks again for your work!!!!
Click to expand...
Click to collapse
Yeah, someone mentioned it already. I will try to fix it for next version, thanks!
djb77 said:
Just gave the new version a flash, insecure adb wasn't set. I've fixed it up and attached it.
@Hbohd if you want to patch this in later veresions, make these changes to the /ramdisk/default.prop
- change ro.adb.secure=1 to 0
- change persist.sys.usb.config=mtp to mtp,adb
then just copy the adbd file from my /sbin
Click to expand...
Click to collapse
Will be in for the next so-called 'alpha'
Just to be sure, Is "HboKernel alpha v0.1" an update of previous "HboKernel v2" of boeffla thread ? Same source + small changelog you @Hbohd mentionned in post #10 ?
fpriot said:
Just to be sure, Is "HboKernel alpha v0.1" an update of previous "HboKernel v2" of boeffla thread ? Same source + small changelog you @Hbohd mentionned in post #10 ?
Click to expand...
Click to collapse
Yep, you are right
If I may suggest @Hbohd... Could you please start with the power features implementation? Charging rates, ignore unstable power and margin...
Because these are the ones I really miss... My chargers and/or cables are not good and I need these mods to charge properly...
Thanks!
Firsty thanks for all your hard work.
The phone no longer charges from the car dock. This was the same for the stock kernels in 4.1.2 & 4.3 - still withold bootloader. 4.1.2's was fixed with Pegasus kernel and 4.3 was fixed by your Beoffia 5 kernel.

Categories

Resources