Fastboot Folder
Hi guys, I am sharing my Fastboot folder to give you ease at understanding on how to flash this kernel
Hi guys, I am sharing my Fastboot folder to give you ease at understanding on how to flash this kernel
[Dual Boot][Kernel][ICS]Doppler 6 Release
- Thread starter karandpr
- Start date
-
- Tags
- development
Hey Saqib thanks for that!
Sent from my Xperia Live with Walkman using XDA Premium 4 mobile app
Nice work 
Are you sure about the Nandroid Restore warning??? I know the CWM code very well since I've had to port it to many new devices for work, and there's nothing that indicates that custom partition sizes can destroy Nandroid function. I did it many times on Play too, worked fine. It's just that Nandroid backups from one sized partition map might not work on another one because they won't physically fit (system will be too big for example).
Are you just worried about the risk or did someone/something actually tell you this?
Are you sure about the Nandroid Restore warning??? I know the CWM code very well since I've had to port it to many new devices for work, and there's nothing that indicates that custom partition sizes can destroy Nandroid function. I did it many times on Play too, worked fine. It's just that Nandroid backups from one sized partition map might not work on another one because they won't physically fit (system will be too big for example).
Are you just worried about the risk or did someone/something actually tell you this?
I think he is referring to the same like you just said...
Nandroid backup made with this kernel can be restored on this kernel alone, becoz other kernels may have different partition layout.
He should explain clearly in his OP, others may get confused, lolz.
Nandroid backup made with this kernel can be restored on this kernel alone, becoz other kernels may have different partition layout.
He should explain clearly in his OP, others may get confused, lolz.
Last edited:
Yess.. The nandroids made with this kernel can be restored on other kernels provided the partitions are of the same size..Nice work
Are you sure about the Nandroid Restore warning??? I know the CWM code very well since I've had to port it to many new devices for work, and there's nothing that indicates that custom partition sizes can destroy Nandroid function. I did it many times on Play too, worked fine. It's just that Nandroid backups from one sized partition map might not work on another one because they won't physically fit (system will be too big for example).
Are you just worried about the risk or did someone/something actually tell you this?
ofcourse you that.. :thumbup:Sent from my Nexus 5 using xda app-developers app
@CosmicDan
It's more of preventive foresight ...
For starters ,I don't approve of nandroid backup as such .
On Mtd-nand devices the backup are pure images as against tarball archives on emmc .
I don't know the restore mechanism on mtd nand ...
If it is a disk image ,restore can be brought about in many ways.
First it can be pure nand and use offsets and size like we define in config_cmdline....that will be proper nand restore....in that case the restore will fail since the partitions were reallocated in recovery...
Second it can use a disk dump starting from offset ...
if by any chance there is no safeguard to prevent (rare case)
Third it can be a simple mount and copy ...if in this case there is no safeguard then data will just be overwritten(I can confirm this scenario)
Then it's pretty stupid to use disk images instead of tarballs but that's another matter..
That's due to part of my ignorance of restore mechanism of nandroid. As such I can't guarantee the consequences nor I want to dwell on it .
Auto nandroid restore doesn't work ...advanced nandroid restore might work ...but the responsibility and consequences is totally upto the end user .
That's one thing...Another thing is ,I can only vouch for the recovery in doppler ...if someone backs up a doppler image and uses it on another kernel which has a recovery compiled differently or someone else then it's beyond my reach and time to support such issues...which I don't intend too ...
The second part is I am skeptic of nandroid backup as such. In my opinion ,nandroid is worst backup ...
I don't use it personally and I won't test it or "try to amend" it or explain how exactly nandroid works...
It's a 1GB waste of space ...
The third thing is there are many pointless discussions held on threads related to nandroid..especially the ones with twrp and cwm ...I want to avoid such discussions as such ...
Keeping these things in mind I felt it was better to declare nandroid as broken permanently..
Than to discuss pointless on a partially broken system which is flawed in my opinion and serves no purpose ..
People who want to use restore can use it at their own risk . I don't support it as such or intend to ...
It's more of preventive foresight ...
For starters ,I don't approve of nandroid backup as such .
On Mtd-nand devices the backup are pure images as against tarball archives on emmc .
I don't know the restore mechanism on mtd nand ...
If it is a disk image ,restore can be brought about in many ways.
First it can be pure nand and use offsets and size like we define in config_cmdline....that will be proper nand restore....in that case the restore will fail since the partitions were reallocated in recovery...
Second it can use a disk dump starting from offset ...
if by any chance there is no safeguard to prevent (rare case)
Third it can be a simple mount and copy ...if in this case there is no safeguard then data will just be overwritten(I can confirm this scenario)
Then it's pretty stupid to use disk images instead of tarballs but that's another matter..
That's due to part of my ignorance of restore mechanism of nandroid. As such I can't guarantee the consequences nor I want to dwell on it .
Auto nandroid restore doesn't work ...advanced nandroid restore might work ...but the responsibility and consequences is totally upto the end user .
That's one thing...Another thing is ,I can only vouch for the recovery in doppler ...if someone backs up a doppler image and uses it on another kernel which has a recovery compiled differently or someone else then it's beyond my reach and time to support such issues...which I don't intend too ...
The second part is I am skeptic of nandroid backup as such. In my opinion ,nandroid is worst backup ...
I don't use it personally and I won't test it or "try to amend" it or explain how exactly nandroid works...
It's a 1GB waste of space ...
The third thing is there are many pointless discussions held on threads related to nandroid..especially the ones with twrp and cwm ...I want to avoid such discussions as such ...
Keeping these things in mind I felt it was better to declare nandroid as broken permanently..
Than to discuss pointless on a partially broken system which is flawed in my opinion and serves no purpose ..
People who want to use restore can use it at their own risk . I don't support it as such or intend to ...
Ah yes you are right, I completely forgot about that. I think it's the yaffs2 filesystem for the reason of them being images instead of tarballs. But yeah restoring those raw image files can indeed be destructive.
plz help
plz help
i flashed kk kernel which is modified using fastboot
i didnt like kk
so i wanna go back to gb so i flashed rage kernel gb through flashtool
but then recovery didnt work
then i flashed rage using fastboot then erase system and data
now i can enter recovery but i tried installing various gb rom including mine pholebulous too
but it stuck at kernel logo
plzzz help
plz help
i flashed kk kernel which is modified using fastboot
i didnt like kk
so i wanna go back to gb so i flashed rage kernel gb through flashtool
but then recovery didnt work
then i flashed rage using fastboot then erase system and data
now i can enter recovery but i tried installing various gb rom including mine pholebulous too
but it stuck at kernel logo
plzzz help
first of all this is not the appropriate thread for that question. anyways, you should flash stock .FTF to resolve your problem...
What @rahimali said ..You need to flash Stock Gingerbread FTF to use Gingerbread ROMs ...
Doppler v2 should be released in a week's time
Tentative Change log :
Based on Lupus Kernel Source to "fix" the battery bug .
The usual ,I/O schedulers,Governors,file systems ,yadda -yadda
OC upto 1.4 Ghz or 1.6 Ghz(Not decided )
Deprecating the E-100 to E-180 Layouts since no one seems using them (Well not many people are using doppler but thats another matter)
Only E-0 and E-60 layouts .
Stuff already available in Lupus ...
Tentative Change log :
Based on Lupus Kernel Source to "fix" the battery bug .
The usual ,I/O schedulers,Governors,file systems ,yadda -yadda
OC upto 1.4 Ghz or 1.6 Ghz(Not decided )
Deprecating the E-100 to E-180 Layouts since no one seems using them (Well not many people are using doppler but thats another matter
)Only E-0 and E-60 layouts .
Stuff already available in Lupus ...
which version of the lupus kernel are you basing on? v5 was just fine except it needed three phone reboots before wifi was available. v6 i never used but i think people had issues so overall v5 would be preferred if you could work around the wifi not being immediately available issue...Doppler v2 should be released in a week's time
Tentative Change log :
Based on Lupus Kernel Source to "fix" the battery bug .
The usual ,I/O schedulers,Governors,file systems ,yadda -yadda
OC upto 1.4 Ghz or 1.6 Ghz(Not decided )
Deprecating the E-100 to E-180 Layouts since no one seems using them (Well not many people are using doppler but thats another matter
Only E-0 and E-60 layouts .
Stuff already available in Lupus ...
could you not base on kappa or MESA instead?
Last edited:
I am not using it on any versions like v5 or v6 ...
Just starting with Lupus base instead of stock base .
Kappa has battery bug . Which is very unusual in my opinion . Until kast uploads the battery bug patch ,I am helpless ..
Working with Mesa is not planned since an0nym0us' changelog is tooooo much and is not suitable as a base to start.
There are lot of stuff which is being modified.
I wont be packing WiFi modules in ramdisk since I don't like them that way ....
They have to be manually flashed via recovery like with older kernels ..
Edit : Checked Lupus changelog and the new doppler is ,lets say near to v1 Lupus
Edit 2 : It's not that I have tried fixing battery bug on Stock ..But the only outcome I am getting is non bootable kernels ....
I believe all the kernel devs like wedgess have put in lot of effort in their kernels .
Using Lupus' source as base is like getting 4.5 km headstart in a 5 km race . Most of bugs are fixed ,less compilation errors and I get to concentrate on modifications rather than fixing bugs which are already fixed by someone else .
Sent from my SK17i using Tapatalk
Just starting with Lupus base instead of stock base .
Kappa has battery bug . Which is very unusual in my opinion . Until kast uploads the battery bug patch ,I am helpless ..
Working with Mesa is not planned since an0nym0us' changelog is tooooo much and is not suitable as a base to start.
There are lot of stuff which is being modified.
I wont be packing WiFi modules in ramdisk since I don't like them that way ....
They have to be manually flashed via recovery like with older kernels ..
Edit : Checked Lupus changelog and the new doppler is ,lets say near to v1 Lupus
Edit 2 : It's not that I have tried fixing battery bug on Stock ..But the only outcome I am getting is non bootable kernels ....
I believe all the kernel devs like wedgess have put in lot of effort in their kernels .
Using Lupus' source as base is like getting 4.5 km headstart in a 5 km race . Most of bugs are fixed ,less compilation errors and I get to concentrate on modifications rather than fixing bugs which are already fixed by someone else .
Sent from my SK17i using Tapatalk
Last edited:
@karandpr funny thing is i got battery bug on lupus v6 as well
phone got frozen on YouTube, only thing i could do was to remove battery and start it again (power+home button didn't work for some reason), when it finished booting up battery was at 100% before force reboot it was ~60% but no worries got it fixed by getting out battery for ~10 minutes.
Well , like I mentioned in CM10 thread ,it might be different bug ... To be frank Only Kappa and Mesa have @kast 's implementation of the battery bug fix since kast used the Mesa Patch to analyze .@karandpr funny thing is i got battery bug on lupus v6 as well
Lupus and Radeon have a fix but it is different from that of Kappa .
Doppler 2
Thanks to @wedgess for Lupus source and @Christopher83 for his prebuilt Linaro toolchains ,
Download:
https://www.mediafire.com/folder/1zl7s8rn0dgfq/Doppler_2
Configs used are E-60 and E-0
Includes builds for Mango ,Smultron and coconut
Smultron and Coconut are not tested
Wifi modules are needed to be flashed via CWM for Wifi to work .
Plausible bug : Two reboots are required for wifi to work .
Thanks to @wedgess for Lupus source and @Christopher83 for his prebuilt Linaro toolchains ,
Download:
https://www.mediafire.com/folder/1zl7s8rn0dgfq/Doppler_2
Configs used are E-60 and E-0
Includes builds for Mango ,Smultron and coconut
Smultron and Coconut are not tested
Wifi modules are needed to be flashed via CWM for Wifi to work .
Plausible bug : Two reboots are required for wifi to work .
Last edited:
yeah ,I forgot to explain ....It contains modules for cifs ,ntfs and usb-otg .... to enable them you need to push them in /system and manually insmod them.Great to see v2 of your kernel @karandpr congratulations!
/system/lib or /system/bin are recommended
I see you're having fun with the battery bug too!
You'll excuse the silly joke I hope, you know I've been struggling with this for months.
Have a look at this "I2C Fixes for 100% Battery bug" Next time send me a msg mate!
Keep up the good work!
Ka.
:victory:I see you're having fun with the battery bug too!
You'll excuse the silly joke I hope, you know I've been struggling with this for months.
Have a look at this "I2C Fixes for 100% Battery bug" Next time send me a msg mate!
Keep up the good work!
Ka.
...I have had it with battery bug :/ I will check those commits later ...My Mini Pro will go into repairs(damaged touchscreen) so no development for 2 months atleast ..
I am keeping an eye on Kappa 1.7 to see how hybrid kernel works with Kappa ...
Cheers !
New posts
-
[APP][4.0+][FREE] MD5 Checker and Hash 3.8 with upto 81 algorithms (17th)- Latest: caovanthanh203
-
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone