yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] droid4lif3:
Will this ROM work on the Verizon Developer Edition? I am already rooted and I have TWRP installed as my recovery.
[Galaxy S 5 Original Android Development] GuyInDogSuit:
It might, won't brick your device if it doesn't. But don't expect to have data connectivity.
[Galaxy S 5 Original Android Development] albinoman887:
hey whats the link to the actuall device tree you are using. PM me as i'm bad at watching threads but i'm getting the s5 in a couple days and can help you out if i knew where your source was
[Galaxy S 5 Original Android Development] Adi Shakthi:
sure add me in hangout

audiogod@live.com
[Galaxy S 5 Original Android Development] stevew84:
Since no one brought it up, there is a new build in the OP.
[Galaxy S 5 Original Android Development] Slicktune:
Theres no changelog .... I checked all provided links and couldn't see the changes... If you can please load me to the change log... Thanks in advance?
[Galaxy S 5 Original Android Development] stevew84:
Same ol' same ol', no haptic feedback. When i realized that I went back to TW unfortunately.
[Galaxy S 5 Original Android Development] Slicktune:
Thanks for the quick response, same here (back to touch jizz), tried the new mokee and calls can't be answered..?

but hey at least their finally working on it..? I'm hoping maybe for the end of this month we have a working rom (one can only dream?)
[Galaxy S 5 Original Android Development] stevew84:
Sucks, but is what it is. I'm using the Project Infinity 5.0 ROM. God how I hate TW, but I'm not willing to use a broken ROM.
[Galaxy S 5 Original Android Development] Adi Shakthi:
Aosp has bugs coz sam sucks never released complete source....raise a potion as per GPL and ask Sammy for full source......
[Galaxy S 5 Original Android Development] xSunny:
Everything but haptic feedback is working?
[Galaxy S 5 Original Android Development] Hero_is_Over:
Wait... what company or devices other than nexus devices release full source? Even on nexus devices all binaries are proprietary, prebuilt, and closed source. .. if you are talking about kernel code well I am pretty sure it is complete and if not they left out something uber simple and not required by GPL. Those sneaky bastards ;)
[Galaxy S 5 Original Android Development] matheus_sc:
I hope all aosp/aokp ROM have good support, Samsung one da y will abandom s5
[Galaxy S 5 Original Android Development] :
Once the Google Play Edition of the S5 comes out, we'll have more AOSP roms than we will know what to do with.
[Galaxy S 5 Original Android Development] Slicktune:
Isn't aosp and google ROM different formats? Isn't google Roms ran by touch wiz framework or something like that? But then again is that why aosp Roms exploded (a lot of development) on htcm8? Because I'd Google rom, can someone clarify?

Thanks in advance! ?
[Galaxy S 5 Original Android Development] djkinetic:
Gpe devices from HTC and Samsung still have some sort of sense and tw frameworks built in to get everything to work properly. As far as what it means for aosp Dev being easier that I don't think is the case....but I could be wrong,
[Galaxy S 5 Original Android Development] Slicktune:
Can someone clarify this? I'm so close to selling my phone, someone offered $500.. But I wanna know before I make this move...
[Galaxy S 5 Original Android Development] klutch:
i was thinking going back to my N5 using PA till this thing gets straight up AOSP i never thought it was going to take that long ton a S5 :eek:
[Galaxy S 5 Original Android Development] Slicktune:
That's EXACTLY WHAT I SAID!! THANK UUUU, someone finally sees it!!!
[Galaxy S 5 Original Android Development] :
I'd imagine that the release of the GPE would at least help get the camera and haptic feedback going. Which are the two main issues with S5 AOSP roms right now.
[Galaxy S 5 Original Android Development] Reynaldinho111:
Really guys?? Have you ever done any development of any sort? Do you have any idea what goes into this sort of stuff and the new difficulties Samsung has created? Please do go back to the N5, nobody has time for your whiney **** :)

Sent from my SM-G900T
[Galaxy S 5 Original Android Development] Ave666:
Yup. Sometimes we need to chill down and relax. Lot of effort, time and patience to get something work. Nobody stop you from what the decision that you've made. Do switch the device now and let we know the difference. Mod, please clear the off topic discussion from the development thread. Tq
[Galaxy S 5 Original Android Development] djkinetic:
If I recall much of the libs/drivers that are not working are closed source...if this is the case GPE won't help much to fix these issues as far as in know....again i could be wrong about this...GPE while aosp in appearance if u dig in still uses the TW/Sense frameworks to get everything to play nicely....which is not present in aosp code obviously...I'm sure the Devs will eventually sort it out via code/workarounds but how long till that is though is a question that can't be answered at the moment...
[Galaxy S 5 Original Android Development] klutch:
RELAX!! only thing i said i never seen this take so long i went tru alot of fone shesh!! seams like there people take it personal in this lucky i have patient to wait (just in case i am not talking reckless or something cuz i know people describe things here how people talk with out knowing) again relax not that serious man :laugh:
[Galaxy S 5 Original Android Development] veebomb:
I'd take the money and run. This will be the last Samsung device I purchase. No disrespect to the developers I am just not very happy with the S5. The only reason I upgraded was because I dropped my Note 2 and broke the LCD screen. I'm thinking of shelling out the $150 getting it fixed and selling the S5. Samsung has really underwhelmed me this time around. Not to mention the base TW ROM is absolute junk.

The Devs on XDA are our only hope to save this device.
[Galaxy S 5 Original Android Development] Slicktune:
Lg g3 it is then, I got till 6pm, I'm going back to my s4 and installing aosp ROM right away!

Thanks wait...but...

Just came from the other lg g3 threads and they're saying that root might be impossible for the g3
[Galaxy S 5 Original Android Development] djkinetic:
I wouldnt go running of to the G3 just yet, great looking phone, and they did improve the UI, however if its like the other LG flagships it will have a locked down BL, and again LG doesnt give the user any way to unlock it. The G2 was lucky in that the Loki exploit was not patched at launch, later firmware patched it...If you really need AOSP now get a Nexus or M8.
[Galaxy S 5 Original Android Development] Ramondel:
LOL.
[Galaxy S 5 Original Android Development] Slicktune:
Palomo, Instead of Lol'ing what do you suggest I do?? I kinda of held off because I'm scared about the whole boot loader being impossible to unlock on the G3... So say the threads....
[Galaxy S 5 Original Android Development] albinoman887:
you guys are nuts.

not mnay people (at least devs) have the phone. with the s4 steve had it before release. heptic feedback is fixed on cm. only thing broken is incoming calls and camera. this all seems pretty normal to me. there isnt anything bad about the s5 thats gonna make it hard to dev for. its just a 8974 processor. the s4 was 8960 as was the s3 and countless other phones so it was mostly copy and paste

stop the gloom and doom and actually do some reading before spouting crazy theories
[Galaxy S 5 Original Android Development] Slicktune:
Just out of curiosity, any of you guys gonna hop on the g3?

Thanks in advance!
[Galaxy S 5 Original Android Development] Ave666:
Read the benchmark/review from gsmarena. Try it
[Galaxy S 5 Original Android Development] Hellscythe:
Roms such as Omega and Alliance are based on stock rom and allow for customizations not originally present.

Could the same thing be done to a GPE rom?
[Galaxy S 5 Original Android Development] FlemishDroid:
Sure why not? ;)

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] KillerWays:
Hi guys i want to install that rom but what's the autonomy of the S5 with that rom ? thanks

i have a F (Qualcomm Version)
[Galaxy S 5 Original Android Development] sualpine:
These guys are building off of Garwynn's public Github. Garwynn is doing the bringup and he never intended for these roms to be released yet. No one in these forums is helping to fix the issues, they are only kanging Garwynn. Follow https://plus.google.com/+XdaGarwynn/posts to see the progress on fixing these things.

P.S., Garwynn has a Sprint S5 which is why the current roms only support Sprint calls/data. https://github.com/garwynn/android_device_samsung_klte
[Galaxy S 5 Original Android Development] Kurotsuchi:
PLEASE make one for SM-G900H, there is NO CUSTOM rom for our poor phone. :(, I feel disappointed on buying this phone. but I had no choice, SM-G900F was not available in my city :(
[Galaxy S 5 Original Android Development] byte9:
Whether it's a GS3 or GS5 there have always been issues with AOSP on Samsung devices. AOSP has never been a perfect platform because it's a bunch of hobbyist work to compile(there have been some good examples like task650 AOKP, even then never feature complete) on something that needs to be stable. GS3 had audio issues that Cyanogen and faux provided solutions for. GS4 had camera issues on AOSP. If you own an klte version then you should not be in the Original thread, you should be in the Android Development thread. There are a few roms there that modify TW to the point you can't complain. If you want a rom that's got a ram footprint lower than AOSP, there is something there for you. If you want a rom that has everything and looks prettier than AOSP, there is something there for you.

The point of my post, developers of AOSP roms realize what they are, they're always unfinished and unpolished for more than one reason and this is always going to be the case on most retail devices besides Nexus. If you have a bootloader unlocked phone people, you should take stability and feature completion above all else. Don't get into arguments because your phone random rebooted on your gf 7x because you UV 150mv. Until the GPE editions come around, lay off things that aren't feature complete if that's what you need. (No disrespect to the OP for putting out something that is probably his hobby)
[Galaxy S 5 Original Android Development] xda23:
When will this rom have a working camera just asking. Thanks!!!
[Galaxy S 5 Original Android Development] culson_35:
Maybe when found the correct module to get camera work

CM 11 4.4.4 (SM-G900T)
[Galaxy S 5 Original Android Development] thehacker911:
@OP

Kernel and device Sources? I can not founding on Github.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] adj998:
Latest version of aokp doesn't boot past the Samsung logo, I believe its the 07/12 build. The one from June boots up though.
[Galaxy S 5 Original Android Development] mocsab:
Links in OP Are down - have been for some time -

is there any more support for this ROM? CM 11 has camera working now and most other issues seem to have bene resolved - would love to have AOKP rom on my S5 - are there plans to continue supporting this ROM ?
[Galaxy S 5 Original Android Development] AndroidDeveloperLB:
Hi,

I have a question regarding This rom and other AOSP based roms in general on Galaxy S5.

Does any AOSP rom succeed having any of the next features :

1. screen recording (and do it well)

2. MHL/HDMI (to show on the TV what is seen on the device)

3. calls recording, as done on some stock based roms (you have a button during calls that will simply toggle call recording and it works great).

4. screen casting and DLNA

?
[Galaxy S 5 Original Android Development] dandv:
Why not list it on the official website?

Why isn't this ROM listed at http://aokp.co/devices/ under Samsung?
[Galaxy S 5 Original Android Development] Ave666:
Cause it's not official
[Galaxy S 5 Original Android Development] tiwas:
Does this ROM handle Samsung's flip cover correctly?
[Galaxy S 5 Original Android Development] EVERED78:
Broken link can't download?
[Galaxy S 5 Original Android Development] -rage-:
You're talking about the link on aokp.co?
[Galaxy S 5 Original Android Development] hexer7568:
i found this http://aokp.co/devices/klte
[Galaxy S 5 Original Android Development] Ave666:
It's official support from elelinux[emoji1]

from SM-G900F / SM-N9005
[Galaxy S 5 Original Android Development] darock159:
Will this work on the SM-G900T
[Galaxy S 5 Original Android Development] byte9:
Baking a fresh nandroid right meow, will report back after trying that linked AOKP on my 900T
[Galaxy S 5 Original Android Development] m2geek:
Is AOKP running on the 900i handset?
[Galaxy S 5 Original Android Development] TheMathMan:
How is the camera quality lately? Is it closer to Touch wiz camera yet?
[Galaxy S 5 Original Android Development] xda23:
How did it work for you on your T-Mobile Gs5?
[Galaxy S 5 Original Android Development] byte9:
I wasn't a fan, It booted just fine. There really isn't a need for following the AOKP tree though because it's based on CM and all the tweaks they offer you can get from Gravity Box and be on a fork that is getting nightly builds. That said, I can offer CM has nailed it and it's running stable and wonderfully. :)

http://download.cyanogenmod.org/?device=klte&type=nightly

---------- Post added at 08:01 PM ---------- Previous post was at 07:59 PM ----------

It's good, I'm using CM but the camera is the same. Obviously less granular controls, some focus modes missing but it's fine for average use for me. It is a camera in a phone after all, wasn't that great to start. ;)
[Galaxy S 5 Original Android Development] wackowizzard:
Flashed today this rom and must say I'm verry happy with it! Run verry smooth and superfast! Tnx! [emoji6]
[T-Mobile HTC One (M8)] altimax98:
Here is the OTA for the T-Mobile M8.feel free to rehost if needed. Pulled straight from a live phone.

Flash through stock recovery on an unrooted LOCKED phone. I say locked because some OTAs fail when they cannot access the few apps that were located in the /Data partition that gets wiped after an unlock.

I am not responsible for anything that could (but probably won't) happen to your phone after flashing this

https://mega.co.nz/#!nRlGSZzD!txRPJjAmB8B_B0B43FjaRbopfYprzZntjOuDxMO9CGA

Unedited unaltered non-rooted goodness... Enjoy!
[T-Mobile HTC One (M8)] FreydNot:
Is there a changelog? What was added? I'm trying to figure out if it is worth going back to stock to install it.
[T-Mobile HTC One (M8)] blesstheattack:
From what I've gathered just battery enhancements,WiFi enhancements, and extreme battery saver mode.

Sent from my InFamous HTC One_M8
[T-Mobile HTC One (M8)] BlueCrystal:
I just attempted to flash the rom on a rooted, busyboxed, S-OFF'd phone, and I can guarantee it doesn't install. Guess i'll be reverting and then installing.

:effort:
[T-Mobile HTC One (M8)] jcaicedo82:
Download stock recovery img ad flash it using the htc m8 toolkit.
[T-Mobile HTC One (M8)] morganpants:
i need the system/app/KidMode.google.apk and KidMode.google.odex so i can OTA, i deleted them while debloating, i need the version before OTA, please and thank you!
[T-Mobile HTC One (M8)] epsix:
Yeah...I flash HTC stock recovery. Then it update everything fine, but you need to reflash custom recovery and re rooted again.
[T-Mobile HTC One (M8)] jesses_girl:
Where can I get the stock recovery from
[T-Mobile HTC One (M8)] epsix:
Flash the first firmware from [MENTION=4174733]Behold_this[/MENTION] thread it will have stock recovery.

http://xdaforums.com/showthread.php?t=2754063
[T-Mobile HTC One (M8)] Optimal Carnage:
I was able to flash the stock recovery with no problems but halfway through installing the ota it fails and I get the red exclamation error and I have to force reboot. I'm s-off, unlocked bootloader and rooted...any idea what I'm doing wrong by chance?
[T-Mobile HTC One (M8)] treIII:
You've got something altered. Apps missing out of system or something

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2
[T-Mobile HTC One (M8)] Optimal Carnage:
That's what I would have said any other time but so far I haven't removed anything or had a need to debloat. Phone is still 100% stock with the exception of unlocked, rooted, and s-ff. I even installed the apps that are removed when unlocking. Its strange to me for sure...I guess I will have to wait for a rooted, flashable update to be posted :/
[T-Mobile HTC One (M8)] Jhoopes517:
I keep getting the same issue as the guy above. I flashed the RUU from Behold_This this morning and then when I went in to recovery it wouldn't let me do anything so I flashed Philz CWM and then tried flashing to have it fail.
[T-Mobile HTC One (M8)] treIII:
Relock

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2

---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------

It's not an ruu. You can't have a custom recovery. You must be 100% stock

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2
[T-Mobile HTC One (M8)] Fenny:
I just patched all of the original files on my dev box, would you like me to post an updated stock (odexed) image that you can flash from recovery?
[T-Mobile HTC One (M8)] Jhoopes517:
That would be excellent, Fenny. Thank you.

I think a lot of us would like that. I want to go back to the stock feel of things, I only rooted cause of battery issues but they've seemed to have solved themselves and I am much happier with the performance of the device
[T-Mobile HTC One (M8)] Fenny:
The image I have is currently pre-rooted. Do you want me to remove the root files, or just post it as-is?
[T-Mobile HTC One (M8)] Jhoopes517:
Root is fine. Currently using your other deodexed stock rom.
[T-Mobile HTC One (M8)] jesses_girl:
As is please
[T-Mobile HTC One (M8)] treIII:
Are you speaking about the stock Rom before the ota or a stock Rom with the 1.57 ota? Or a stock odexed do that we can accept the ota. If it is to accept the ota it would be best for it Not to be rooted. Thanks.

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2
[T-Mobile HTC One (M8)] Fenny:
Will do, I'm just testing it now to make sure the package won't do anything silly like brick devices. :D

I took the original ship firmware, and applied the OTA manually to the files. This will have the OTA already applied on it, as well as preload data restored. I am testing it now with the original ship stock kernel and hboot vs the new stock kernel and hboot to see if it is worth adding a firmware update package to the updater script.

Right now I am thinking I will just make a second package to apply the firmware package if people want it. (bootloaders, recovery, radio, kernel, etc...)
[T-Mobile HTC One (M8)] treIII:
Ok. So you are doing this so it can be flashed through custom recovery?

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2
[T-Mobile HTC One (M8)] Jhoopes517:
Want a test dummy? I have the insurance so... Brick thee device! :P

Yeah, It will be flashable in custom recovery based off what was said earlier I believe.
[T-Mobile HTC One (M8)] Behold_this:
Already posted mate

http://xdaforums.com/showthread.php?t=2754063
[T-Mobile HTC One (M8)] treIII:
I've already flashed the custom firmware. Has anyone made a flashable zip for the new kernel? That's what I would like. The h boot was the same as explained earlier. I'd like to have everything except the recovery as I use my phone as stock with root. If I want mods which are few I just use xposed. With sense 6 tools. Does the trick for me. But I like my firmware and kernel to match as HTC intended. Do you think I can pull the boot.img out of the full package and just flash it through fastboot? Fastboot flash img boot img? Is that right? I feel like the new kernel should be included in the Rom you are preparing for us as was intended. Some of the fixes come through the kernel operating with the firmware. If we don't like the kernel we can always flash the older one. But I'm one of many. Kernels are designed to work with certain firmware. Such as scanning for lte is now done on the kernel side if I read correctly. Thanks. It's great that you are taking your time to do this.

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2
[T-Mobile HTC One (M8)] Behold_this:
Kernels are packaged in the boot.img, if you want the stock one, simply take it from the official firmware zip in my thread. Keep in mind, however, it should only be used on 1.57 based ROMs.
[T-Mobile HTC One (M8)] Fenny:
I believe I have worked out how to flash it from recovery as well as fastboot. We'll have to see if it works or not. :D
[T-Mobile HTC One (M8)] Behold_this:
Let me save you some trouble bro, I've been nodding HTC since the myTouch line and I can tell you most partitions are not accessible via recovery. Some are, most aren't.
[T-Mobile HTC One (M8)] Fenny:
I noticed that the original OTA hooks into a function that does the same thing as fastboot. I believe that I can get it to work from a custom recovery as well, but again, we'll see. :D
[T-Mobile HTC One (M8)] treIII:
Yeah I flashed the custom firmware earlier but it doesn't contain the kernel.

My apologies. I did not see your post above this one. And when u say able to flash from recovery are you specifically speaking about the kernel? Thanks

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2
[T-Mobile HTC One (M8)] Behold_this:
[emoji106]. I hope you can get it done, I do, but it would be a first on a sense based rom. That doesn't mean it can't be done, it just means it hasn't been yet. That being said, in my years of experience some partitions are locked down and you will not be able to write to them through recovery. AOSP is different and CM, as they often use temporary firmware.
[T-Mobile HTC One (M8)] treIII:
I'm no dev whatsoever. But aren't the kernel possible to flash while flashing a Rom through custom recovery?

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2
[T-Mobile HTC One (M8)] Behold_this:
Yes of course...you always flash the boot image that matches your rom, that's Android 101. If you reread my post you'll see that I said some partitions are locked down, not all.
[T-Mobile HTC One (M8)] Fenny:
Yes, the kernel should be, but there are certain partitions that the device normally refuses to update from recovery.
[T-Mobile HTC One (M8)] treIII:
Seems to me the easiest way would be to include the boot .img in the custom firmware so that can be upgraded along with radio etc and then the Rom you are creating can be flashed through custom recovery and we will have the entire package minus stock recovery from the its. Thanks. This is awesome.

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2
[T-Mobile HTC One (M8)] Behold_this:
I suppose you can DD some partitions or attempts to utilize the write_raw_image function, so in that respect you COULD put them in your rom zip for s-off users, but some partitions are inaccessible for s-on. for example the touch panel drivers cannot be flashed by recovery and some others.

Generally speaking it's not recommended to package firmware with your roms, but I'm certainly not going to tell you what to do with your own releases I can simply tell you there's a reason why the accessible partitions are not included by every developer in the HTC community.

---------- Post added at 02:50 PM ---------- Previous post was at 02:43 PM ----------

I won't do that and here's why, if you are running a rom like ViperOne, for example, and want to update your firmware but you update the boot.img as well, Viper will no longer boot. Then you will come to my thread and tell me how I broke your phone.
[T-Mobile HTC One (M8)] treIII:
Ok. So we need the kernel separate from the boot.img? I think. Lol. Is the tmz in the firmware for the touch panel / touch sensitivity? I remember upgrading firmware before and then all the sudden twrp wouldn't recognize touch so we had to downgrade recovery.

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2

---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------

Ok so is it not possible to downgrade firmware? If that's the case I don't know what to say.

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2