Thank you! : )
Yeah, when you say it it makes sense. It's gone now though. Together with a lot of other things. That weren't necessary.
[ROM][ICS][UNLOCKED][ALL MDPI] Helium Light / updated 23-july-14
- Thread starter Verbato
- Start date
-
- Tags
- development
Yeah, when you say it it makes sense. It's gone now though. Together with a lot of other things. That weren't necessary.
I am using whatever git clone git://github.com/KaSt/Kappa is giving me.
Thank you!That would really help a lot! : )
But... :-/
From a fresh git clone:
Any idea why it doesn't work? (AKA "What am I doing wrong?" : P )Code:$ git cherry-pick 04516aaab7f7fe0fa248a07f73c051551c68a6e8 error: could not apply 04516aa... I2C Fixes for 100% Battery bug hint: after resolving the conflicts, mark the corrected paths hint: with 'git add <paths>' or 'git rm <paths>' hint: and commit the result with 'git commit'
: )
Will do!
do a
Code:
git status
Code:
git --apply checkand post the output.
Code:
~/Android/build/Kappa$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
It took 2.04 seconds to enumerate untracked files. 'status -uno'
may speed it up, but you have to be careful not to forget to add
new files yourself (see 'git help status').
nothing to commit, working directory clean
Code:
~/Android/build/Kappa$ git --apply check
Unknown option: --apply
usage: git [--version] [--help] [-C <path>] [-c name=value]
[--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
[-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
[--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
<command> [<args>]
$And just in case you are curious : )
Code:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty
Last edited:
I will just look at it next week or so.
There might other patches required before applying this patch.
.
There might other patches required before applying this patch.
.I just got a message from haitran1211, who told me his ST15i's touch screen just got bricked.
Looking in to things it turns out last time I remade the whole thing I some how managed to copy the mini pro device files in to what obviously isn't mini pro. I feel like my heart is in my throat, I feel so bad for this guy. : (
(The other files/devices are ok, I've checked and double checked and checked again - which I should have done in the first place)
And that was, ironically, what I wanted to avoid all along. I know how important the phone is to everyone...
So if anyone has a -working- tip on how to unbrick the touch screen on the ST15i/smultron/mini, please post it or send a message to haitran1211.
Due to time differences, he's vast asleep right now.
Yeah, I'm an idiot! : (
Edit: So, I touch-bricked my own phone (intentionally) with the coconut ROM, installed the mango ROM and all was well again. Crossing my fingers it's as easy for the smultron as well! I'll make a new ROM for smultron and upload it asap.
Uploaded. Also, the reason to why I thought that would work was this post: http://xdaforums.com/showpost.php?p=35481026&postcount=3
And in my case it is that simple. I'm crossing my fingers...
Looking in to things it turns out last time I remade the whole thing I some how managed to copy the mini pro device files in to what obviously isn't mini pro. I feel like my heart is in my throat, I feel so bad for this guy. : (
(The other files/devices are ok, I've checked and double checked and checked again - which I should have done in the first place)
And that was, ironically, what I wanted to avoid all along. I know how important the phone is to everyone...
So if anyone has a -working- tip on how to unbrick the touch screen on the ST15i/smultron/mini, please post it or send a message to haitran1211.
Due to time differences, he's vast asleep right now.
Yeah, I'm an idiot! : (
Edit: So, I touch-bricked my own phone (intentionally) with the coconut ROM, installed the mango ROM and all was well again. Crossing my fingers it's as easy for the smultron as well! I'll make a new ROM for smultron and upload it asap.
Uploaded. Also, the reason to why I thought that would work was this post: http://xdaforums.com/showpost.php?p=35481026&postcount=3
And in my case it is that simple. I'm crossing my fingers...
Last edited:
Thank you!
It's pretty simple really. No services (err... well, as few as possible, I meant to say), as small programs as possible (uses as little RAM as possible) = uses less CPU and thus also less battery. If you undervolt the CPU as well (though this risks the phone being unstable, as in suddenly rebooting) you should be able to go even further.
Thanks for testing and for the feedback!
Do you mind adding a guide on how to flash starting from a fresh official ICS flash? I've tried most roms in here but I don't think I can try this one...
Sent from my Nexus 5 using Tapatalk
EDIT: Managed to install it just fine. Awesome ROM!!!! But my camera is inverted (WT19i) please help!
Sent from my Nexus 5 using Tapatalk
EDIT: Managed to install it just fine. Awesome ROM!!!! But my camera is inverted (WT19i) please help!
Last edited:
@Verbato
Patched Kappa 1.6 with the Battery Bug patch
Check my fork of Kappa
https://github.com/karandpr/Kappa_Doppler
It's just a plain patch.
do a git clone and compile it . It should work fine .
I don't have my phone so I can't test it.
Please report your findings !!
Patched Kappa 1.6 with the Battery Bug patch
Check my fork of Kappa
https://github.com/karandpr/Kappa_Doppler
It's just a plain patch.
do a git clone and compile it
. It should work fine .I don't have my phone so I can't test it.
Please report your findings
!!EDIT: Managed to install it just fine. Awesome ROM!!!! But my camera is inverted (WT19i) please help!
Thanks for letting me know! I'll fix that in an upcoming release. Here's a quick fix though. Just install in CWM.
Let me know if it worked or not.
@Verbato
Patched Kappa 1.6 with the Battery Bug patch
Check my fork of Kappa
https://github.com/karandpr/Kappa_Doppler
It's just a plain patch.
do a git clone and compile it
I don't have my phone so I can't test it.
Please report your findings
Tried it. Weird thing is, upon running ./tools/makedefmango there's no .config anywhere. No worries, I just used my own. Compiled. Installed. Messed up my phone so it didn't want to boot in to android. Did show the boot up logo, but did not boot long enough to go in to CWM. Weird.
So, short story: no luck.
Edit: A quick diff gives me (apart from all the files in arch/arm/configs/*):
diff -rupN Kappa/arch/arm/include/asm/io.h Kappa_Doppler/arch/arm/include/asm/io.h
diff -rupN Kappa/drivers/gpu/msm/adreno_ringbuffer.h Kappa_Doppler/drivers/gpu/msm/adreno_ringbuffer.h
diff -rupN Kappa/drivers/i2c/busses/i2c-msm.c Kappa_Doppler/drivers/i2c/busses/i2c-msm.c
diff -rupN Kappa/drivers/i2c/busses/i2c-qup.c Kappa_Doppler/drivers/i2c/busses/i2c-qup.c
diff -rupN Kappa/drivers/i2c/busses/i2c-ssbi.c Kappa_Doppler/drivers/i2c/busses/i2c-ssbi.c
diff -rupN Kappa/drivers/i2c/chips/akm8975.c Kappa_Doppler/drivers/i2c/chips/akm8975.c
diff -rupN Kappa/drivers/i2c/i2c-core.c Kappa_Doppler/drivers/i2c/i2c-core.c
diff -rupN Kappa/drivers/i2c/i2c-dev.c Kappa_Doppler/drivers/i2c/i2c-dev.c
diff -rupN Kappa/drivers/i2c/Kconfig Kappa_Doppler/drivers/i2c/Kconfig
diff -rupN Kappa/.git/config Kappa_Doppler/.git/config
Binary files Kappa/.git/index and Kappa_Doppler/.git/index differ
diff -rupN Kappa/.git/logs/HEAD Kappa_Doppler/.git/logs/HEAD
diff -rupN Kappa/.git/logs/refs/heads/master Kappa_Doppler/.git/logs/refs/heads/master
diff -rupN Kappa/.git/logs/refs/remotes/origin/HEAD Kappa_Doppler/.git/logs/refs/remotes/origin/HEAD
Binary files Kappa/.git/objects/pack/pack-1fc8d1554a2ba37f65199b55a72dd1207d4e7f1c.idx and Kappa_Doppler/.git/objects/pack/pack-1fc8d1554a2ba37f65199b55a72dd1207d4e7f1c.idx differ
Binary files Kappa/.git/objects/pack/pack-1fc8d1554a2ba37f65199b55a72dd1207d4e7f1c.pack and Kappa_Doppler/.git/objects/pack/pack-1fc8d1554a2ba37f65199b55a72dd1207d4e7f1c.pack differ
Binary files Kappa/.git/objects/pack/pack-bc900b9a3c0d6993757d7597c3c50f7cff91e727.idx and Kappa_Doppler/.git/objects/pack/pack-bc900b9a3c0d6993757d7597c3c50f7cff91e727.idx differ
Binary files Kappa/.git/objects/pack/pack-bc900b9a3c0d6993757d7597c3c50f7cff91e727.pack and Kappa_Doppler/.git/objects/pack/pack-bc900b9a3c0d6993757d7597c3c50f7cff91e727.pack differ
diff -rupN Kappa/.git/packed-refs Kappa_Doppler/.git/packed-refs
diff -rupN Kappa/.git/refs/heads/master Kappa_Doppler/.git/refs/heads/master
diff -rupN Kappa/.gitignore Kappa_Doppler/.gitignore
diff -rupN Kappa/include/linux/i2c.h Kappa_Doppler/include/linux/i2c.h
diff -rupN Kappa/include/linux/utsrelease.h Kappa_Doppler/include/linux/utsrelease.h
I guess it's somewhere in this i-square-c-mess that the battery fix exists?
Last edited:
Yes, it did work. Thanks again for the spectacular ROM.
My girlfriend is overly attached to her current erm.. phone (a Bada Wave 525) which I'm trying to replace with something simple but more modern. Everytime she's seen my LWW, she always said it was too complicated (let's say technology is not her strong point). I guess the bada - android differences together with the do-it-all roms I had installed helped. I've flashed your ROM and removed even more stuff which she would never use, and she gave me the approval to go and start moving her stuff from the wave to the lww.
So as long as the battery holds up more than a day, my life just got easier thanks to you.
@Verbato
Patched Kappa 1.6 with the Battery Bug patch
Check my fork of Kappa
https://github.com/karandpr/Kappa_Doppler
It's just a plain patch.
do a git clone and compile it
I don't have my phone so I can't test it.
Please report your findings
Hi u uploud this kernel with patch?
Tried it. Weird thing is, upon running ./tools/makedefmango there's no .config anywhere. No worries, I just used my own. Compiled. Installed. Messed up my phone so it didn't want to boot in to android. Did show the boot up logo, but did not boot long enough to go in to CWM. Weird.
So, short story: no luck.
I guess it's somewhere in this i-square-c-mess that the battery fix exists?
yes. the readl are replaced by readl_relaxed and a host of other changes in i2c drivers...I hope you have used _180 config
...if you used _0 config then fastboot erase would be required . Else the phone's boot will fail (like you said). What phone are you using ?
I can upload the zImage if you want. check if it works...
I uploaded the source. Basically the patch which existed on 1.7.Beta10 is directly applied to 1.6 ..
Last edited:
Thank you for letting me know! Since I don't have any other phone than my own (Mini Pro/SK17i/mango) I don't know how things affect the other phones. So I'm dependant on feedback from you guys when things go wrong or don't work properly.
Glad she liked it! I've done my best to keep the xperia-experience in there, while at the same time keep the ram- and cpu-usage to a minimum (both makes for a smaller rom and also saves battery).
Mhm. I thought so. But waaay too much for me to get in to.
I used my own .config. (The one I've uploaded earlier) To no avail. I don't even know if it was read. Since, like I said, there was no .config after running makedefmango. Did a find for it. Nothing. No .config. No worries, added my own. Still did not boot.I hope you have used _180 config
Now, the thing is, yes, then the boot will fail. But it should have booted again when I added my standard kernel (180). Nothing. Did not boot. Nor did your first doppler 180 boot. But the files were there (aroma-explorer). So I have no idea as to what happened.
http://xdaforums.com/attachment.php?attachmentid=2820925&d=1403893983
Check this boot.img on your device.
It should boot technically
Compiled for mango with 180 layout
It should boot technically
Compiled for mango with 180 layout
Check this boot.img on your device.
It should boot technically
Compiled for mango with 180 layout
Few minutes ago ,I flashed this kernel and rom from first page on my Mango ... There is only one problem - WiFi doesn't work :/ I have to flash something more?
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
19TOO MUCH TEXT!
Pictures:
READ THIS FIRST - THEN DOWNLOAD BELOW.
UNLOCKED BOOTLOADER ONLY!
REMEMBER TO FASTBOOT ERASE SYSTEM/FASTBOOT ERASE USERDATA AFTER INSTALLING KERNEL! (if this makes no sense to you, read the stuff in blue below)
INSTALL HELIUM ROM FIRST, THEN INSTALL DEVICE FILES - failing to do so will result in a black screen after loading CWM (just nap out the battery, reinsert and enter CWM if you forget, then install device files)
For the daring, here you go:
This ROM is based on Saqib Nazm's wonderful work, Fluorescent Feather ROM. So most of what´s right with this ROM is his work and thanks to him. : )
The ROM is based on Kappa by kast with batteryfixes added by karandpr.
If anyone wants to use this to build something else upon this, feel free to do so!
If you have no idea how to fastboot erase system/userdata, I made this file for you.
Kernel flasher - http://www.mediafire.com/download/hzn3iqh25g5pxij/Kernel_Flasher.zip
Put this where ever you want (more thanks to karandpr! : ).
Put the kernel image in the IMG folder in Kernel_Flasher. Make sure you only have ONE kernel in the IMG folder. Only put the kernel you wish to flash in the IMG folder. Putting more than one kernel in IMG folder will fail.
Right click on and run Kernel_Flashing_Tool.bat as admin. Hook up your phone. Does not matter if it is in a ROM, in CWM or in fastboot mode. The batch file will do it all.
BUT: This only works if you have the drivers in windows installed for your phone (you do if you have used flashtool to flash other kernels before).
This also makes it easy to flash "back to" a standard kernel later.4@Verbato
Nice project here ! I'll do my best to help you with this one ^^
Well, first, i got system crash when I flash devices modules (mango) (at file "language_slv.xml")
I tried with Doppler and your provided kernel, same issue :/ corrupted zip maybe ?
Btw here's a little guide I made to help people with fastboot erase
---------- Post added at 12:57 PM ---------- Previous post was at 12:02 PM ----------
Easy guide to use Fastboot Erase/Flash on Windows 7/8/8.1
============================================
1) Install 15 seconds ADB Installer v1.3
NOTE: If you are on Windows 8/8.1 and you need to install ADB drivers, you might want disable Driver Signature Verification
NOTE 2 : If in the past, you successfully used flashtool to flash a kernel on the system you're running, then the drivers are already installed
2) Press "Windows+R" and type "cmd"
3) Press enter
4) Connect your device in fastboot mode
5) check if your device is connected in fastboot mode by entering in cmd :
Code:fastboot devices
If you are using Windows 8/8.1 and you don't have your device listed here even if your device is connected in fastboot mode (e.g. on mango, notifications led is blue when connected in fastboot mode), please check the note at 1). Windows probably blocked the installation of the drivers when you tried to install them trough the installation of 15 seconds ADB Installer v1.3
6) flash your kernel (in case you want to)
7a) Do an "erase system":
Simply type
Code:fastboot erase system
You'll get something like this :
7b) Do an "erase userdata"
again, simply type
and you should get something like thisCode:fastboot erase userdata
I hope it helps ! And I'm sorry about the screenshots in french, and about my bad english ^^2
So... Do you use Windows or OSX? There are several guides out there on how to install fastboot.
xda explanation
Explanation on how to install fastboot in windows, with pictures and all
The commands you want to run are, simply:
Code:fastboot erase userdataCode:fastboot erase system
And if you have the kernel in the same folder as fastboot you could also install it like this:
Code:fastboot flash boot helium-coconut.img
