Hey guys, this is just a version of @franciscofranco's kernel built with DoubleTap2Wake and Sweep2Wake from Bricked Kernel merged in.
(By downloading and installing the kernel you assume all responsibility for any damage to your device, but I don't post images with the intention of this occurrence and test them to the best of my abilities.)
Download:
r57
boot image - https://sundergaming.com/downloads/hammerhead/franco.Kernel/boot-franco.Kernel-r57-dt2w.img
md5 - 9ba11b4c3f5cd963c69d54bbfd919fe1
zip - https://sundergaming.com/downloads/hammerhead/franco.Kernel/zips/boot-franco.Kernel-r57-dt2w.zip
*Color tweak is integrated since r30, check 2nd post for information on how to enable.
Want a dedicated build for color tweaks because your boot animation isn't pretty enough? Build it yourself. Sources below.
**Test builds posted throughout the thread.
Kernel is for 4.4.1/2 since r19
Installation:
fastboot flash boot boot_name_img
or
flash the .zip in recovery
Sources
Kernel - https://github.com/PhantomGamers/hammerhead
Ramdisk - https://github.com/PhantomGamers/ramdisk_hammerhead
Credits
@franciscofranco for his kernel - http://forum.xda-developers.com/showthread.php?t=2508284
@show-p1984 for the dt2w and s2w additions - http://forum.xda-developers.com/showthread.php?t=2524557
@flar2 for his on-the-fly color tweak, power key touch to wake suspend, and other general dt2w improvements. - http://forum.xda-developers.com/showthread.php?t=2519607
I do accept and appreciate any donations but I urge you to first donate to the amazing developers listed above for their work because my contributions are minimal and without them this kernel variant would not exist.
Franco's original thread for reference only:
franciscofranco said:
Hi all.
Currently does not work with recent CyanogenMod nightlies or any rom has uses CM sources as a base because they made underlying changes that are now incompatible with Kernels that don't follow their path.
Installation:
fastboot flash boot boot_name_img
or
flash the .zip in the recovery
Changelog:
http://kernels.franco-lnx.net/Nexus5/4.4/appfiles/changelog.xml
franco.Kernel updater Free apk: http://forum.xda-developers.com/showthread.php?t=1867127
Nexus Display Control Free apk: http://forum.xda-developers.com/showthread.php?t=2424467
Got any questions that you couldn't find after searching?
FAQ: http://forum.xda-developers.com/showthread.php?t=2532422
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
Click to expand...
Click to collapse
XDA:DevDB Information
franco.Kernel+DT2W/S2W, a Kernel for the Google Nexus 5
Contributors
PhantomGamers, franciscofranco, show-p1984, flar2
Kernel Special Features:
Version Information
Status: Stable
Created 2014-02-06
Last Updated 2014-02-06
Kernel Settings
Disabled by default. To enable execute the code next to terminal in adb shell or terminal emulator as root.
If you wish for it to be automatically enabled on boot you can create the file named in the boot section.
After creating this file you can still execute the terminal code to enable it immediately or you can just reboot and have the kernel enable it for you.
[DT2W/S2W]
S2W
terminal -
Code:
echo 1 > /sys/android_touch/sweep2wake
boot - Create /sdcard/fkSettings/fks2w
DT2W
terminal -
Code:
echo 1 > /sys/android_touch/doubletap2wake
boot - Create /sdcard/fkSettings/fkdt2w
Bottom Half Screen DT2W (Only allows you to double tap bottom half to turn screen on, instead of above.)
terminal -
Code:
echo 2 > /sys/android_touch/doubletap2wake
boot - Create /sdcard/fkSettings/fkdt2wps
S2Sleep
terminal -
Code:
echo 1 > /sys/android_touch/s2w_s2s
boot - Create /sdcard/fkSettings/fks2s
PWRKEY_SUSPEND (Turns off touch to wake when display is turned off with power button, reenables when turned on, useful for long idle periods, unaffected by sweep to sleep)
terminal -
Code:
echo 1 > /sys/module/qpnp_power_on/parameters/pwrkey_suspend
boot - Create /sdcard/fkSettings/fkpwrks
Touch Wake Timeout
terminal -
Code:
echo 15 > /sys/android_touch/wake_timeout
(15 is an example, include the number of minutes you prefer)
boot - Create /sdcard/fkSettings/fkwt with number of minutes to delay timeout (IE: text file with "15" inside)
[COLOR]
*This tweak is experimental and you use it at your own risk.
**Breaks gamma calibration apps.
terminal -
Code:
echo 1 > /sys/module/mdss_dsi/parameters/color_preset
boot - Create /sdcard/fkSettings/fkcolor
[WIDGETS]
*Thanks to @JsChiSurf
http://forum.xda-developers.com/showthread.php?t=2626476
[App]
*Thanks to @casperpas
http://forum.xda-developers.com/showpost.php?p=51682981&postcount=839
just giving my 2 cents, franco's kernel intention is to deliver a stable, optimized and battery efficient kernel for the n5, by baking in these S2W/DT2W features into the kernel, aren't you defeating the purpose? If I would want those features built in, I could have flashed Elementalx, Bricked etc. No offense but that's what occur to me, to others, it may be godsend. :good:
kashix said:
just giving my 2 cents, franco's kernel intention is to deliver a stable, optimized and battery efficient kernel for the n5, by baking in these S2W/DT2W features into the kernel, aren't you defeating the purpose? If I would want those features built in, I could have flashed Elementalx, Bricked etc. No offense but that's what occur to me, to others, it may be godsend. :good:
Click to expand...
Click to collapse
Elementalx and Bricked don't have Franco's custom hotplug driver, personally that's the main selling point of his kernel to me.
I don't particularly care for these features anyway though and just used this as a learning experience to build kernels.
(I am currently running this build though to play around with it, haven't noticed a huge difference in battery life myself)
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
This is very tempting to try out.
Thank you!
---------- Post added at 07:57 PM ---------- Previous post was at 07:57 PM ----------
durhamite said:
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
Click to expand...
Click to collapse
Flashify seems like it'd do the trick, if original Franco kernels are any indication.
Well, I tried it, and it works!
Thanks OP!
Tip: if u have FKU, put the img in the franco.kernel_updater bkp folder and restore if it were bkp. Most easy!
Sent from N5
durhamite said:
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
Click to expand...
Click to collapse
Yeah Flashify seems like your best bet if you're rooted.
I might try and include zip releases in the future, sorry for the inconvenience.
grumphy said:
Well, I tried it, and it works!
Thanks OP!
Tip: if u have FKU, put the img in the franco.kernel_updater bkp folder and restore if it were bkp. Most easy!
Sent from N5
Click to expand...
Click to collapse
Thanks for the confirmation!
Thanks for doing this. Will you be updateing this to keep up with Franco's releases, or was this a one time experiment?
Nastybutler said:
Thanks for doing this. Will you be updateing this to keep up with Franco's releases, or was this a one time experiment?
Click to expand...
Click to collapse
Yeah that's my plan, I'll most likely keep this going until franco includes his own DT2W feature or unless I run into some technically difficulty.
Welp. I'm having trouble getting the dt2w working. Here's what I'm entering in terminal emulator (after "su" of course) without the quotation marks: "echo 1> /sys/android_touch/doubletap2wake"
Nothing happens in the terminal after I hit enter, it just goes to a new command line, and if I turn the screen off it won't wake back up with a double tap. Did I enter the command in wrong?
Nastybutler said:
Welp. I'm having trouble getting the dt2w working. Here's what I'm entering in terminal emulator (after "su" of course) without the quotation marks: "echo 1> /sys/android_touch/doubletap2wake"
Nothing happens in the terminal after I hit enter, it just goes to a new command line, and if I turn the screen off it won't wake back up with a double tap. Did I enter the command in wrong?
Click to expand...
Click to collapse
The space between the 1 and the > is essential.
PhantomGamers said:
The space between the 1 and the > is essential.
Click to expand...
Click to collapse
Eureka! That was my problem. Thanks! Works a treat.
Gonna give this a whirl
edit: works great thanks so much! for subsequent kernels you release, will one have to put in that command every time?
Also so glad you carried over francos screen calibration too! you rule! And so glad you'll be supporting until (if) franco implements it.
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
tyrellcorpnexus said:
edit: works great thanks so much! for subsequent kernels you release, will one have to put in that command every time?
Click to expand...
Click to collapse
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
tyrellcorpnexus said:
Also so glad you carried over francos screen calibration too! you rule!
Click to expand...
Click to collapse
Yeah it's essentially a straight franco build so anything he implements will be included as long as he pushes it to github
tyrellcorpnexus said:
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
Click to expand...
Click to collapse
This isn't currently a feature of the kernel but I do agree that doubletap2screenoff and sweep2screenoff would be really neat.
I'm going to TRY to implement this myself but I wouldn't hold my breath because I'm not really experienced with this level of coding.
PhantomGamers said:
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
Yeah it's essentially a straight franco build so anything he implements will be included as long as he pushes it to github
This isn't currently a feature of the kernel but I do agree that doubletap2screenoff and sweep2screenoff would be really neat.
I'm going to TRY to implement this myself but I wouldn't hold my breath because I'm not really experienced with this level of coding.
Click to expand...
Click to collapse
I see I see. Thanks again! Hitting that button one time to go to sleep is better than waking every time as well that is for sure!
I'm used to putting my device to sleep with a gesture on Activator with my JB'en iPhone 5. But I still have to wake it using home or lock button so I guess its still needed on that as well..
I don't think double tap to sleep would be the best, what about when getting text to fit the screen on Chrome and such? Double tap is a relatively common gesture once the device is awake.
Also, any way you can walk me through how to make sure it automatically kicks in on a reboot?
This is too good
tyrellcorpnexus said:
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
Click to expand...
Click to collapse
I have the LMT Pie controls and one of buttons on my second row is a key that turns the screen off. So now, in theory, I'll hardly ever have to use the power button. :good:
---------- Post added at 11:47 AM ---------- Previous post was at 11:40 AM ----------
PhantomGamers said:
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
Click to expand...
Click to collapse
Would you be kind enough to walk noobs like me through how to set up that file? Right now I've got a note saved with the command that I copy & paste into the terminal each time now, but I can tell that's going to get old pretty quick.
Nastybutler said:
I have the LMT Pie controls and one of buttons on my second row is a key that turns the screen off. So now, in theory, I'll hardly ever have to use the power button. :good:
Click to expand...
Click to collapse
Do you have a link to the APK and maybe a screenshot of what it looks like? I'd only be interested in this toggle.
tyrellcorpnexus said:
I don't think double tap to sleep would be the best, what about when getting text to fit the screen on Chrome and such? Double tap is a relatively common gesture once the device is awake.
Click to expand...
Click to collapse
I meant like the G2 does it, where it's only when you double tap on the notification or nav bar in certain apps etc
tyrellcorpnexus said:
Also, any way you can walk me through how to make sure it automatically kicks in on a reboot?
Click to expand...
Click to collapse
Nastybutler said:
Would you be kind enough to walk noobs like me through how to set up that file? Right now I've got a note saved with the command that I copy & paste into the terminal each time now, but I can tell that's going to get old pretty quick.
Click to expand...
Click to collapse
Trying to figure this out now, it would appear that the kernel doesn't actually have init.d support as my script isn't working... maybe I'm doing something wrong here.
PhantomGamers said:
I meant like the G2 does it, where it's only when you double tap on the notification or nav bar in certain apps etc
Trying to figure this out now, it would appear that the kernel doesn't actually have init.d support as my script isn't working... maybe I'm doing something wrong here.
Click to expand...
Click to collapse
Ah, in that case, that'd be awesome!
No worries, appreciate your work thus far.
This is so great :highfive:
Related
What this kernel does is provide slightly less voltage to the processor. This should not be dangerous for anyone to try, however it may be unstable or just result in general weirdness on a few phones. If it does, all you have to do is revert back to the kernel you had before.
The upsides to less voltage are less heat as well as less power consumption. That means battery life
Remember, this one is running at stock speeds.
Get it on Koush's RomManager (download RomManager from the market) I'll post changelogs in this thread from now on, but keep the kernel on RomManager.
Changelog 8/29:
Lots of stuff.. I dunno.. Look at the CM6 kernel changelog (I've been working on that).
Biggest thing IMO is the usleep stuff which lowers CPU usage and therefore increases battery life.
Note: only tested on CM6. Let me know if you try it on any other roms.
Link: http://kanged.net/up/files/5/kernels/signed-August26-UV950.zip
Changelog 6/20:
Ermm.. I've been releasing my kernels on twitter.. but I'm finally happy with this one.
-Latest Cyan commits
-Minor voltage tweaking
-erm... yeah I dunno.
Get it here http://kanged.net/kmobs/signed-619UV-34.zip or from RomManager.
Changelog 5/14:
-Reinstated those commits reverted earlier.
-Updated to .33.4
-Only doing a 925mV kernel due to the results from the blind study
Changelog 5/1:
-Reverted the following commits thanks to intersectRaven. I think they were the reason for the excessive battery drain.
27dd25f80402a13f9d5c381eda07b560e5545fcc
1490683fb851b992722cbd175d3df087df833656
f2513498e961966d3209aacfffc43de4f41f2ece
-Updated to latest CM source (minus those commits)
Changelog 4/21:
Fixed the board-mahimahi.c in the 850mV kernel.
OLD updates and changelog:
http://iq0.org/story/yet-another-nexus-one-kernel-now-battery-saving
Note: Now offering a universal update.zip method for flashing the kernel (big thanks to Koush for this one)
Thank you www.tdrevolution.com for hosting my work.
Does it still have the highmem?
GEtting an access denied message, Seems the post doesnt exist
Great job. Will get you a logcat if I get any random weirdness.
Maybe now my battery can last longer then my G1 battery did when I am at work.
Anyone care to make an update.zip for those of us without computers nearby to check this out?
Tested and functional with Enomther 1.61. Thanks a lot
What is the CPU voltage and is the some app that can show it?
Running this new kernel at 576/245 mHz, wifi off, 3G connection, brightness set to automatic. will report back with battery life as soon as it runs out. lol
Off of charger: 11:34AM , Wednesday, February 17, 2010
Battery completely drained: TBA
DocRambone said:
Tested and functional with Enomther 1.61. Thanks a lot
What is the CPU voltage and is the some app that can show it?
Click to expand...
Click to collapse
Hey do report if there is any improvements... meanwhile can someone make it into to an update.zip for us?
mgear356 said:
Hey do report if there is any improvements... meanwhile can someone make it into to an update.zip for us?
Click to expand...
Click to collapse
I will, phone seem ok so far, BenchmarkPi at 2670
No slowdowns or reboots during benchmarks or gameplay. Phone feel cooler tho
I'll give this a shot.
Mi|enko said:
Does it still have the highmem?
Click to expand...
Click to collapse
just flashed it. yes it does. my phone hasnt exploded yet either...
Mi|enko said:
Does it still have the highmem?
Click to expand...
Click to collapse
Yes
To those asking for an update.zip: I don't to package this into something that will be easily flashable by all, including those that may not understand the risks (I don't think there are any with this kernel, but can't be sure). I want there to be some rudimentary knowledge of android before someone goes and flashes this and potentially messes up their phone.
Does that make sense? I feel that there should be a barrier to entry on kernels that OC and the like.
What voltages is it for different MHz?
great job, really need something like this... im trying it out! thanks
DocRambone said:
What voltages is it for different MHz?
Click to expand...
Click to collapse
Its not across the board, and I'm not home right now to tell you, but 245 is at 1.0 vs 1.05 and 998 is at 1.250 instead of 1.275
persiansown said:
Yes
To those asking for an update.zip: I don't to package this into something that will be easily flashable by all, including those that may not understand the risks (I don't think there are any with this kernel, but can't be sure). I want there to be some rudimentary knowledge of android before someone goes and flashes this and potentially messes up their phone.
Does that make sense? I feel that there should be a barrier to entry on kernels that OC and the like.
Click to expand...
Click to collapse
I do understand what your saying, I don't think its that much of a barrier though. There are many instructions throughout these boards that will let anyone who is even remotely interested flash a new kernel and push a .ko to their phone... The only reason why I want an update.zip is so that I can flash this on my phone to test it while I'm at work, it would also be nice to be able to switch quickly between kernels and whatnot. I don't have a computer that I can connect to via USB to run fastboot/adb so the only way I can get these on my phone is via a zip.
I don't think that a developer/hacker can be held responsible for others not knowing what issues can be caused by a voltage/clock tweak - especially with disclaimers up everywhere.
FettsVett said:
I do understand what your saying, I don't think its that much of a barrier though. There are many instructions throughout these boards that will let anyone who is even remotely interested flash a new kernel and push a .ko to their phone... The only reason why I want an update.zip is so that I can flash this on my phone to test it while I'm at work, it would also be nice to be able to switch quickly between kernels and whatnot. I don't have a computer that I can connect to via USB to run fastboot/adb so the only way I can get these on my phone is via a zip.
I don't think that a developer/hacker can be held responsible for others not knowing what issues can be caused by a voltage/clock tweak - especially with disclaimers up everywhere.
Click to expand...
Click to collapse
Oh I understand where you're coming from, and I would make you a private one, but I'm not home at the moment. However, for the general user, if they can't use fastboot, I don't want them anywhere near this. I hope someone makes you an update.zip!
I await the PM's!
Dear lord what am I going to do with this should I get my 2800mah battery? my phone will never die! lol
-Charlie
FettsVett said:
I await the PM's!
Click to expand...
Click to collapse
you can make one yourself.
grab boot.img from cyanogen's rom.
grab split_bootimg.pl from http://android-dls.com/files/linux/split_bootimg.zip
grab persiansown's zImage.
(in linux)
put all three in a folder. let's call it kernel.
while in the kernel folder:
./split_bootimg.pl boot.img
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel zImage-persiansown --ramdisk boot.img-ramdisk.gz -o boot-persiansown.img
(in windows)
download this: http://www.sendspace.com/file/kj2wi7
use winrar to open up that up, remove the boot.img in there and replace it with boot-persiansown.img (make sure it is named boot.img)
open up the update-script in META-INF folder (some levels down in there), and remove the format BOOT line (you'll be left with write_raw_image ... line), and save it.
grab this: http://www.relentlessaddictions.com/Androidstuff/signing.zip
unpack to your tools folder in your android-sdk folder distribution, and run autosign.bat. follow the prompts. once setup, you can right click on the .zip file with the boot.img in it to sign it, or you can execute from a cmd prompt: java testsign BOOT-IMG.zip
flash via custom recovery (which can flash .zip's signed with test keys).
you should be all set.
edit: mkbootimg can be found in prebuilt within AOSP distribution, or you can grab this precompiled one: http://forum.xda-developers.com/attachment.php?attachmentid=229872&d=1253485580
avlock[10] is a (the first?) real, *system-level* lock screen replacement for Android (CM 5.0.6).
it replaces the standard "connect the dots" behavior with pin-like mechanism. patterns can be arbitrarily large, and nodes can be repeated. also, there are no numbers -- just circles. definitely not for everyone, but i think some people may like it.
here's how it works:
http://files.clangen.org/avlock/avlock.m4v
if you want to try it you must have CM 5.0.6 installed, then:
1. reboot to bootloader
2. nandroid backup <-- do it. seriously. just in case.
3. flash avlock[x].zip
4. reboot
5. if you don't have a lock pattern already, set one: Home > Menu > Settings > Location and Security > Set Unlock Pattern
faq:
q: what happens if something goes really wrong and i can't log in?
a: i've been tweaking this mod for a long time and you shouldn't have any problems. BUT IF YOU DO:
* restore from nandroid backup made in step 2 above
OR
* if you know how to use adb, just delete the file pattern file and reboot:
adb remount
adb shell rm /data/system/gesture.key
adb shell reboot
q: what files are replaced by the patch?
a: framework.jar, framework-res.apk, android.policy.jar, Settings.apk
q: why not just distribute this as a simple .apk file?
a: this is a system-level mod because it replaces system-level components. it cannot be distributed as an .apk.
changelog:
avlock[8]:
* initial release
avlock[9]:
* added tactile feedback
* reduced login delay
avlock[10]:
* disabling "Use visible pattern" works now
* better integration with system and Settings.
* re-added drag lock option.
avlock[11]:
* added the ability to specify a pattern timeout
use at your own risk. i am not responsible for any damages caused by this software. MAKE A NANDROID BACKUP FIRST!
caution: if you update your rom, install a theme, or flash another mod that replaces framework.jar, framework-res.apk, or android.framework.jar, you may not be able to log in upon reboot (or even spin into a boot loop). either (1) make sure you disable your lock screen before flashing or (2) rm gesture.key as described in the faq!
download:
avlock[11]: http://droidbasement.com/db-blog/?p=202 (thanks, pershoot)
sources:
http://github.com/avatar5d
wow, nifty and works well enough
It'd be really nice if it was faster, there is close to a 2 second lag between entering and unlocking
Cool Thanks
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Good work.
Thanks
imfloflo said:
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Good work.
Thanks
Click to expand...
Click to collapse
You could always unzip the zip and push the files manually
adb shell stop
adb push these files to their respective places framework.jar, android.policy.jar, Settings.apk
adb shell start
If you forget the pattern, you can get it emailed to you right?
Looks awesome in the video, nice idea, better executed!
NICE MOD!
Nice work!!!
prettyboy85712 said:
Nice work!!!
Click to expand...
Click to collapse
+1 Nice ...
Good Job !
This looks awesome! Nice work
@ _avatar
Any chance to make this work with Enom's ROM ?
Nice work!
imfloflo said:
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Click to expand...
Click to collapse
Unfortunately, because this is a system-level mod it cannot be installed as a simple .apk.
bobtentpeg said:
It'd be really nice if it was faster, there is close to a 2 second lag between entering and unlocking
Click to expand...
Click to collapse
The delay is there on purpose. Once you stop touching the circles for 2 seconds, the combination is verified. Without this delay, there would need to be some sort of "OK" button, which I think is undesirable. However, I'll look into making the delay shorter (1 second?) for future builds. The value needs to be long enough so people can still enter their combination relatively slowly, but fast enough so it's not annoying.
pvillasuso said:
Any chance to make this work with Enom's ROM ?
Click to expand...
Click to collapse
Possibly. Is Enom's source available, and easily buildable like Cyanogen's? I'm not super familiar with his project.
This is hot, installing now. My main complaint with the stock lock pattern was the inability to re-use points. just gotta set a good lock pattern and see how this works.
Thanks.
Wow.. this is pretty damned cool! Good job.
One thing, tactile feedback is not working with this, any way to restore that?
daveid said:
One thing, tactile feedback is not working with this, any way to restore that?
Click to expand...
Click to collapse
It's on my TODO list
EDIT: added to avlk[9] build. see original post!
Can you make a them of some sort and replace the dots with numbers?
Can it run on 1.8.1 rom
Re: [MOD] avlk[9], a real, system-level lock screen replacement
anyway to incorporate trackball wake-up in this for us desire port guys ;-)
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
_avatar said:
Possibly. Is Enom's source available, and easily buildable like Cyanogen's? I'm not super familiar with his project.
Click to expand...
Click to collapse
http://android.git.kernel.org/
You'll want to ask him which actual tag he's building for current versions. Also, since I'm not up on framework patching, it might be more complicated if you don't want to break the trackball-wake and/or notification features. Best to contact him @enomther or for someone to raise the suggestion in his thread.
This is not a thread to say ‘thanks’ to developers. Only post here if you have some input in this development progress, by either fixing bugs, or coming up with ideas (and ideally, try your idea and report what happens).
Having that said, let’s move on to where we are at the moment. Currently, we have a build which is based upon Ice Cold Sandwich 6.2 Test Edition for the HTC Desire HD. This build boots up by flashing my custom kernel on it, based on Flyer HC Original Kernel Source, with some patches:
-Quota2 Support
-Genlock Support
-Updated KGSL driver by applying Lord Clockans patches from his kernel
The ZIP we are working on now, can be downloaded here:http://w728685.open.ge.tt/1/files/9iI3CbF/0/blob?download
This ZIP contains a build which is mainly Lord Clockans ICS, with essential changes in the ROM to get it booting (we used LeeDroid’s Flyer HC as the donor ROM). This ROM is made for a HoneyComb HBOOT!
After you have flashed that ZIP, this is the kernel you need: http://ge.tt/9iI3CbF/v/1
You MUST flash this kernel to get it up and running, or it’ll just loop in the logcat complaining about unsupported stuff.
This set should do the following:
-Boot up (bootanimation resets after some time, it’s ok, it will boot within 5 minutes).
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!) Also, the ntrig.c file in /drivers/input/touchscreen/ is modified in the kernel, don’t know if it helped though.
-Full Hardware Accceleration
-Screen is bugged at certain moments (seems to happen especially during things concering wallpapers. Rendering a wallpaper, showing a heavy LWP, etc.). The build.prop file contains some lines such as:
ro.fb.mode=1
debug.composition.type=gpu/mdp
debug.fb.rgb565=0
Perhaps we have to change these lines to get it running without issues (strange thing is, logcat doesn’t seem to make an issue about this). We can also try a recompile of the kernel using the entire driver folder from Lord Clockans kernel (it’s in /drivers/gpu/msm/ in his kernel, and /drivers/video/msm/gpu/kgsl_adreno205_hc in ours, moving the folder to where it should be causes issues, so we keep it like this for the time being).
-Sound is working
-Backcamera seems to be working fine, haven’t tested frontcamera.
-Hardware buttons under the screen aren’t working, and this should be a low
priority for now. It isn’t ideal to use them in ICS anyway (different button functions in comparison with the softbuttons), and I think we shouldn’t focus on this for now.
-GPS switch can be enabled, haven’t tested whether it works.
-Bluetooth switch can be enabled, but turns off automatically after about ten seconds.
-WiFi switch can’t be changed, logcat tells us that it can’t connect with /dev/rfkill, applying this patch in the ramdisk could fix it:
https://github.com/OpenSensation/an...mmit/da09360d70888a7e126871ab2ae5b218514cad18
-Power button and Volume buttons work fine.
-Pen works after we send the event_google command mentioned before.
If the ROM immediately reboots within 10 seconds and it seems like it’s looping, and you can’t even logcat, hold down Power and Volume Down until you get to HBOOT, select FASTBOOT, and enter ‘fastboot erase cache’ in the CMD/Terminal, and reboot, and it should work.
And that’s about it for the current things we know I think. If you manage to fix something, please write down and report what you did to fix it, so we can keep a list. I will work on a vendor folder using the known information, so we can compile a ROM from source, made for our device.
And last, but not least: don’t post here asking for release dates. We will do our utmost best to bring ICS experience to the Flyer, but do not bug us. Thanks.
Now let’s get this up and running guys! I will keep a log of what is fixed and what is not, so we can keep the thread organized. Else we’ll have 50 ZIPs around, not knowing which one is the right one et cetera.
Source code of kernel: http://github.com/Chaosz-X
Ramdisk will be uploaded tomorrow.
Donations are much appreciated, as I'm developing and building atm on a 1.67GHz Dual core...
Donations can me made to [email protected] using Paypal.
i suggest creating two repos... one for ROM and one for kernel... that way single file changes can be tracked even on ROM front, not just kernel...
willing devs can fork those repo and send pull requests to main repo when they get stuff working
I'm not a developer, and I have nothing but love for all the great devs that worked so hard to bring ICS to the Flyer.
Might I suggest, however, that instead of pursuing CM9 builds, the next effort be centered around porting the Android Open Kang Project (AOKP) ROM? In terms of features and customizations, it's considerably ahead of CM9, with numerous supported devices to boot.
I think this ROM, versus CM9, would give users the most flexible and dynamic ICS experience for their Flyer.
Chaosz-X said:
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!)
Click to expand...
Click to collapse
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
nickiberli said:
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
Click to expand...
Click to collapse
yes that should work correctly
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Chaosz-X said:
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Click to expand...
Click to collapse
u want me to add stuff to that ramdisk?
start a github repo for the ramdisk and ROM too... trust me... its VERY helpful...
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Chaosz-X said:
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Click to expand...
Click to collapse
thats great... it should make keeping track of changes much easier and other interested devs can contribute if they want...
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Thracks said:
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Click to expand...
Click to collapse
I can confirm this happened to me also. The only difference is that I was using the kernel for a port of mine, and it did the same thing.
Yes, it is known that for some reason, Go Back already reboots the device. It's no problem though, it works fine anyway. If it is really looping the bootanimation every ten seconds, keep Vol Down and Power pressed, until you get to HBOOT. Select FASTBOOT, and enter 'fastboot erase cache' in the terminal. Then reboot on the device, and it should boot up fine.
Also, kernel won't work on Honeycomb, haven't checked why it doesn't though (and I won't btw, our goal is not to make a new kernel for Honeycomb, but for ICS, where it does its job fine).
Kernel source is uploaded to my Github: http://github.com/Chaosz-X
Edit the CROSS_COMPILE for your toolchain, and it should compile fine (it does here).
Will add the link to the OP within 5 minutes, ramdisk will be uploaded tomorrow.
If chaos has a device tree set up for the Flyer/View, no build prop editing should be necessary, can just submit requests - but I don't notice it on the git.
Thanks for uploading, I'll have a look and see what has changed so far. It's a little difficult to keep track of the changes since there are no commits that document the patches applied over time, but I'll try to make do with what you've got.
Is this straight from flyer HC kernel source?
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Cimer said:
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Click to expand...
Click to collapse
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
lawguy said:
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
Click to expand...
Click to collapse
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Cimer said:
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Click to expand...
Click to collapse
Hang tight for now. Wifi Does not work and the screen freaks out. I'm sure that these things will be fixed soon.
Going to upload ramdisk source within an hour, and try to apply a fix for WiFi, and try to fix the touchscreen by using the command in init.rc mentioned here earlier.
The new modem arrived, I have Internet again, so we have remote access to our Linux machine and can start compiling etc again
Indeed, we're grabbing AOKP source code now. Within about 2 hours we think, we'll start compiling the ROM for the HTC Flyer. Don't know if it will work out, but we have to start somewhere
Beware of googleys
FRANK
Layers
Day/Night theme switcher from first M preview
Init.d support
Advanced reboot
SuperSu 2.52 flashed with the rom
Volume rocker wake
Volume rocker cursor control
Long press quick settings control
Stock Like feel, please don't ask for features
Installation
Roms can change from update to update that sometimes you can dirty flash but if you have errors that other users don't then you will have to clean flash
First Time Installation:
Download the ROM and Other Optional files below.
Connect your Nexus 5 to the PC and transfer all the zips to the root of your device’s storage.
Reboot into recovery mode (Shut down, press VolDown + Power buttons. In bootloader mode, select Recovery mode)
Wipe the following partitions: System, Data and Cache
Install the ROM zip file
Let it boot. Setup now and wait for the ROM to settle.
Reboot into Recovery again and Install the remaining zip files.
Updating from previous version:
1.Download the ROM and Other Optional files below.
2.Connect your Nexus 5 to the PC and transfer all the zips to the root of your device’s storage.
3.Reboot into recovery mode (Shut down, press VolDown + Power buttons. In bootloader mode, select Recovery mode)
4.Wipe the following partitions: Dalvik-cache and Cache
5.Install the ROM zip file
6.Reboot now
7.Let it boot. Setup now and wait for the ROM to settle.
8.Reboot into Recovery again and Install the remaining zip files.
9.If have issues with dirty flash, reboot and redo steps wiping DATA also
Sources
Hammerhead GPL Kernel Source: prebuilt aosp marshmallow n5 kernel in aosp source
Rom Source: Click here
Changelog
Code:
10-19
Minor update
enable systemui tuner by default
add scanning menu into location
speed up recent app back
sprint fix included
Copy pasta from mako changelog
10-15-15
Minor update
added aldy's kernel in and turned back on usb-otg in fstab (n4)
added minkin text layout engine in thanks to @ckret for pointing it out (hammerhead had this already)
10-14-15
bug fixes!!!
some changes on the device tree so anyone using it should update
can build with clang now thanks to @ckret for pointing out the fixes (we are still gcc compiled)
Fixed downloads dark theme thanks to Branden M
Fixed supersu and layers icons being off on the dark theme, thanks Branden again
ambient display color layers inversion fix up ported from lollipop
Fix annoying usb mounting to computer (Thanks to snak3ater pointing this out to zephik)
10-13-15 update-1
added volume rocker wake (in settings/display to turn on)
add volume rocker cursor control
added animation transition animations of .25 and .75
set default animation speeds to .75
added long press recent button switches to the last app
removed the spinner from optimizing apps dialogue so it is quicker at dexopting
added long press on quick settings tile takes you to their settings menu
minor sepolicy fixes
disabled the after flash image verification (was breaking multirom flashing)
10-13 build
Fixed mac address bug thanks to this pull request
https://github.com/marshmako/device_lge_mako/commit/49b11281e25e434d7f56c4677e663e8dff87ccad
Fix a bad copy pasta of the init usb midi support
12-12
Added ambient display and full rotation
removed some debugging code
sped up a few things
Frank 10-12-15 with theme switcher, update 1
added google exchange services included in the build, it replaces exchange2
should be able to remove the layers manager icon from the launcher now
removed cell broadcast receiver
added the locked update receiver commit
beanstown found a line to set doze power saving mode that was set to off in aosp so turn it on
https://www.androidfilehost.com/?fid=24052804347836304
10-12 theme switcher update
added day/night theme switcher back to dev settings like what was in M dev preview 1 (only does settings, bluetooth and package installer so we will have to expand on this for layers), will prob move the switch out to the dashboard below layers or some place later.
added https://github.com/BenzoRom/framewor...54a3aa73367bde which should give core google apps default permissions out the box (you might still have setup wizard bug though)
Your current layers themes will only work properly in light mode
new in 10-11-2015
Removed art optimize everything till we have fully deodexed gapps
advanced reboot
init.d support
supersu and layer manager embedded in setting (you need layers manager of course) (forgot to add the hide icon part )
too tired for the rest so just read the commit history if you wanna know more https://github.com/marshmako/platfor...b5b1c3bc4419da https://github.com/marshmako/platfor...6896b4d256a871 pretty much just kanged a bunch of commits from zephik there.
new in update 1.
fixed init.d, removed aosp clock and aosp mms apps. Use updated and better google versions
added missing files for miracast
Downloads
Current Build = https://www.androidfilehost.com/?fid=24052804347841653 10-19-15
Gapps = https://www.androidfilehost.com/?fid=24052804347841244 Txuki
or
Gapps = https://www.androidfilehost.com/?fid=24052804347841070 banks
Backup Gapps down below if those don't work
gapps without setup wizard if you get wizard fc upon boot thanks to barome (modifed version without setup wizard of above)
just access play store to be able to log in with your google account
http://renderserver.net/?dl=6455ad109b871809d8f34b25a92f6904
For those interested in the commits for the theme switcher
https://github.com/marshmako/platfo...mmit/da669b1ebda7ee8ac7a39d181eb944290ce9ea72
https://github.com/marshmako/platfo...mmit/00b529c60d31e554b9c090c03f02ce06a652135a
https://github.com/marshmako/platfo...mmit/3c683a0124129bda309615a281fc3feb3ec58fde
https://github.com/marshmako/platfo...mmit/22c13d6bfd5dee4843a6fdca953350d7f56b7066
https://github.com/marshmako/platfo...mmit/4f298e8f8ab2c08f0e8c4ae92da72b01e0db6b5d
https://github.com/marshmako/platfo...mmit/4136e2ff29a84be80f8bf7f83a357fb0342e6718
Click to expand...
Click to collapse
Current layers themes will only work on light themes until adapted
OT talk is welcomed in my threads and development is done in the open. I encourage involvement in the project in any way.
Please do not complain about OT, it encourages a fun and relaxed environment
Like the work I did, consider donating. I'm currently not working so it helps feed me
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=BPFLE54YPRV92
Yes, my PayPal account is thatguy32404, I like to keep my banking stuff separated from my social account
XDA:DevDB Information
[L][5.0] Frank N5 - Aosp builds in testing [1-11-2015], ROM for the Google Nexus 5
Contributors
sykopompos, bgill55
Source Code: https://github.com/marshmako
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Stable
Created 2015-02-27
Last Updated 2015-10-19
Reserved
[/HIDE]
nexus devices threads
Mako
http://forum.xda-developers.com/nexus-4/development/lpv-79-mako-port-beta-t2807446
deb
http://forum.xda-developers.com/nex...e/l-android-lpv-dev-deb-t2856915#post55016443+
flo
http://forum.xda-developers.com/nex...id-lpv-dev-flo-enhanced-t2856920#post55016534
hammerhead
http://forum.xda-developers.com/google-nexus-5/development/l-android-lpv-dev-n5-enhanced-t2856934
Look @vomer 's op for a general FAQ for L preview as those apply here along with other downloads for radio, bootloader, etc (maybe looking for my permissive boot.img or art tweaks, they are there)
http://forum.xda-developers.com/google-nexus-5/development/rom-n5-l-developer-preview-t2796003
good morning.. i will try in multirom.. thx a lot!
Best regards
Craxx
Send from my Nexus 5 with Tapatalk
Woot woot! Glad it is stable now. Kudos and great job!
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
Question. Can we now straight flash L kernels without you modifying the ramdisk? Like code blue, arkenstone etc etc?
eluspo said:
Woot woot! Glad it is stable now. Kudos and great job!
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
Question. Can we now straight flash L kernels without you modifying the ramdisk? Like code blue, arkenstone etc etc?
Click to expand...
Click to collapse
Nope. Still need the any kernel version because of how heavy of ramdisk edits that there is.
The whole ramdisk is aosp and modified for permissive selinux so flashing a boot image will crash out the whole system.
@ramjet73 is working on a ramdisk injector to replace the ramdisk in kernels that do a complete boot.IMG
WOw.... downloading .... :laugh:
sykopompos said:
Nope. Still need the any kernel version because of how heavy of ramdisk edits that there is.
The whole ramdisk is aosp and modified for permissive selinux so flashing a boot image will crash out the whole system.
@ramjet73 is working on a ramdisk injector to replace the ramdisk in kernels that do a complete boot.IMG
Click to expand...
Click to collapse
I think im going to use your modified code blue kernel for now. Thanks a lot for bringing this smoothness to n5 L.
I forgot to add in the op and will. If you are coming from the official L preview, you might experience a bunch of force closes on first boot. Just reboot about twice and it will settle down.
This is some funkiness involving selinux getting switched over to permissive.
eluspo said:
I think im going to use your modified code blue kernel for now. Thanks a lot for bringing this smoothness to n5 L.
Click to expand...
Click to collapse
shhhhh there isn't supposed to be any modified versions of his kernel distributed outside his thread, u saw how grumpy he got that we even did a test one
Will I loose my SD card by flashing this
Sent from my Nexus 5 using xda premium
sykopompos said:
shhhhh there isn't supposed to be any modified versions of his kernel distributed outside his thread, u saw how grumpy he got that we even did a test one
Click to expand...
Click to collapse
Okay haha i will be discreet about it. We dont him attacking this thread ??
stewartk said:
Will I loose my SD card by flashing this
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
It will behave exactly like the preview would when it comes to the sdcard so no you shouldn't. I don't have a n5 so o don't know if that behavior is in the preview or not.
I haven't heard anyone say anything about it on mako coming from kit kat
eluspo said:
Okay haha i will be discreet about it. We dont him attacking this thread ??
Click to expand...
Click to collapse
Yes please. He made his wishes clear. Ramjet is working in the injector which will do a reverse anykernel basically and replace the ramdisk like I did in the test.
This could be solved if the L kernel guys made a anykernel version instead of a full boot image so it wouldn't touch my ramdisk.
A lot of the magic that makes it so smooth is in the ramdisk.
sykopompos said:
Yes please. He made his wishes clear. Ramjet is working in the injector which will do a reverse anykernel basically and replace the ramdisk like I did in the test.
This could be solved if the L kernel guys made a anykernel version instead of a full boot image so it wouldn't touch my ramdisk.
A lot of the magic that makes it so smooth is in the ramdisk.
Click to expand...
Click to collapse
Okay okay haha. I can definitely feel that magic in this rom.
eluspo said:
Okay okay haha. I can definitely feel that magic in this rom.
Click to expand...
Click to collapse
Well I believe you were on the left over bunny stew so you could see the difference between the ramdisk difference and the the rest so you should be able to tell how much just the ramdisk does and then the evolution to what it is now and what makes it the complete picture.
Bet you love those 20 second boot times though
Anyways, time to get some sleep. It has been a long night and I'm hitting the caf stuff at every turn in the 1+1 L port and it is giving me a headache just thinking about it.
I'm gonna hang out with my son all day tomorrow so I won't really be on
sykopompos said:
Well I believe you were on the left over bunny stew so you could see the difference between the ramdisk difference and the the rest so you should be able to tell how much just the ramdisk does and then the evolution to what it is now and what makes it the complete picture.
Bet you love those 20 second boot times though
Anyways, time to get some sleep. It has been a long night and I'm hitting the caf stuff at every turn in the 1+1 L port and it is giving me a headache just thinking about it.
I'm gonna hang out with my son all day tomorrow so I won't really be on
Click to expand...
Click to collapse
Thanks man! Get some sleep. Have fun with your son.
Just flashed, works flawlessly, thanks for this great build!
BTW guys, you can use SuperSU, I just haven't gotten around to merging it in to replace koush's before SuperSU worked properly when fully permissive. Just make sure you use 2.02 or higher
Just an FYI, permissive just logs and doesn't actually deny anything so you will see the avc denied in logcats but it does go through.
I gotta tune the policy for hammerhead as I just did a basic aosp one for it
How would I get the home button to work. Its there just doesn't work
Sent from my Nexus 5 using xda premium
Mysterious Magic (G Watch)
The First Custom G Watch ROM Based on the Android 5.1.1 (LDZ22D) OTA
Prerequisites:
Unlocked Bootloader (fastboot oem unlock)
ADB Debugging Enabled (Settings > About > Tap on build number 7 times > Swipe back > Developer Options > Enable ADB Debugging)
Drivers Installed (Windows)
Features:
Rooted out-of-the-gate (su, busybox)
Init.d support built in (/system/etc/init.d)
Improved transitions
Improved speed (slight overclock)
Improved battery life
Increased vibration
Forced GPU rendering
Easy to use installer (Windows, Linux, OSX)
Hotplugging of all 4 cores, as needed
Special Thanks:
invisiblek - For his wonderful custom kernel work!
okibi, arter97, Tomsgt, nagasgura, PlayfulGod, WindyCityRockr, and all other community developers - For their time, effort, and inspiration, in making this watch run faster, better, and even smoother!
All of the community members, watch owners, and rom flashers - Without my amazing users, and the help of this community, none of this would be possible, or even exist!
Donations:
If you happen to like my ROM and find yourself wishing to donate, you can do so by pressing the "Donate to Me" button below my username on the left side of the screen. I spend my free time developing my contributions to the community, and every penny is greatly appreciated!
Changelog:
Version 1.0 r2 (7/12/2015) :
- Removed vibration intensity from the tweaks and added it to it's own seperate file, for end user configuration.
- Removed governor and frequency settings from tweaks and added it to it's own seperate file, for end user configuration.
- Changed the default governor from ondemand to smartmax, to accomodate the kernel included with this rom.
For the best results, refrain from changing the default governor, unless you plan on pairing this rom with a different kernel other than invisiblek's (included).
- Added the ability to change dpi settings.
- Added the ability to enable a specific number of cores (when not using the included kernel).
- Fixed adb, fastboot issues some users were having.
- Major revisions to the installer!
Version 1.0 (7/5/2015) :
- Initial release.
Downloads:
Version 1.0 r2 (md5: 1c2652a3607a53d889c664eec72a37f2)
Mirror 1
Mirror 2
F.A.Q
How do i use the installer?
Extract the archive.
Enter the "Installer" folder.
Enter the folder of the platform you're using (Windows, Linux, or OSX).
Run the installer and follow the on-screen instructions.
Linux and OSX scripts may need the proper permissions in order to run.
Please note: First boot will take some time, and you'll need to re-pair your watch and phone.
How do I edit and install custom settings?
Enter the "Settings" folder.
Open the settings file with the text editor of your choosing.
Make changes to the settings file.
Save the settings file.
Run the installer, select Install Settings, and follow the on-screen instructions.
Questions? Comments? Concerns?
Leave all questions, comments, and concerns below, and I'll be sure to reply as fast as possible!
installer doesnt work
ker2gsr said:
installer doesnt work
Click to expand...
Click to collapse
Which version? Can you screenshot the specific errors?
Sent from my SM-G925P using XDA Free mobile app
MysteriousSparrow said:
Which version? Can you screenshot the specific errors?
Sent from my SM-G925P using XDA Free mobile app
Click to expand...
Click to collapse
that info might help lol yes i was using the wimdows installer im using windows 8 x64 the installer detected my device but when i went to do a reboot it said command anniciated but device didnt reboot into fastboot it went through all format steps and said succesfully flashed rom but device never rebooted to format on flashboot sorry no screen shot i flashed manually
ker2gsr said:
that info might help lol yes i was using the wimdows installer im using windows 8 x64 the installer detected my device but when i went to do a reboot it said command anniciated but device didnt reboot into fastboot it went through all format steps and said succesfully flashed rom but device never rebooted to format on flashboot sorry no screen shot i flashed manually
Click to expand...
Click to collapse
After looking into it, it seems I added an extra unneeded character to the script. I'm reuploading the correct version now, and I'll replace the download link accordingly! Sorry about that!
The fixed version is now uploaded. Give that a try and let me know!
Just installed with windows 10 and installer worked with no problems. Will boot into mint and try installer and report back.
dude1981 said:
Just installed with windows 10 and installer worked with no problems. Will boot into mint and try installer and report back.
Click to expand...
Click to collapse
Thanks! Let me know!
MysteriousSparrow said:
Thanks! Let me know!
Click to expand...
Click to collapse
Installer worked fine on Linux Mint. Will test on watch for a couple days and report back. What kernel is it running?
installed on windows 8 no issues...waiting for sync to test this bad boy out
thanks dev
dude1981 said:
Just installed with windows 10 and installer worked with no problems. Will boot into mint and try installer and report back.
Click to expand...
Click to collapse
dude1981 said:
Installer worked fine on Linux Mint. Will test on watch for a couple days and report back. What kernel is it running?
Click to expand...
Click to collapse
invisiblek's dory kernel
Thanks for the feedback, good to hear the installers are in working order now.
Will download when I get home. Can't wait to try this out...
goast said:
installed on windows 8 no issues...waiting for sync to test this bad boy out
thanks dev
Click to expand...
Click to collapse
Good to hear! Thanks for the feedback!
Report back and let me know what you think!
Ralphyralph said:
Will download when I get home. Can't wait to try this out...
Click to expand...
Click to collapse
Can't wait to hear what you think!
rom working great so far i had already installed manually so i didnt test again for you but others seem to have no issue now great work watch feels more snappier and responsive
ker2gsr said:
rom working great so far i had already installed manually so i didnt test again for you but others seem to have no issue now great work watch feels more snappier and responsive
Click to expand...
Click to collapse
Good to hear! Let me know if you have any concerns or questions in the future, regarding the rom.
Sent from my SM-G925P using XDA Free mobile app
upload
View attachment 3392477 Ok what am I doing wrong?