Related
http://www.androidpolice.com/2010/1...3-gingerbread-being-pushed-to-aosp-right-now/
go, go, go! )
These are very good news
I already see my Hero running CM 7
:happy face:
Excellent News Lets see who get's their GingerBread ROM out first
Sweet, if the hero really will be supported!
Cooooooooooooooool man very nice go go go go gooooooooooooooogle
Tchuup-tchuup! Hotness train is leaving the stations
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
dkelley said:
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
Click to expand...
Click to collapse
Feeyo...
Good news
Sent from my HTC Hero
C0mpu13rFr34k said:
Feeyo...
Click to expand...
Click to collapse
should be interesting to watch his progress
I wish the technical know-how would be something well documented.
What I mean is, ive seen lox/benocharm (sp?) progress in the last year in terms of Android knowledge, almost from the start. Ive seen one of these two guys post about initial questions about how things work, then edit his own post to do a mini-FAQ on ROM cooking. Now today it would look like they would kick some major ass at doing it if they were still able to give time for this, because they know the Hero hardware by heart; they know the usual glitch when porting (ie: how to make camera/bluetooth work, etc), all the minor details that makes a ROM usable or not for a day-to-day ROM! However, this kind of knowledge seems not so well documented.
What i'm basically saying is if a developer bails out the documentation about how to rebuild a custom ROM does too. It looks like (from a non-cooker point of view) that there is no centralized Wiki or webpage about the usual generic steps or roadblocks when porting from another device or when starting from AOSP to build FOR an Htc Hero (or any device, too).
Personally i know enough about linux in general, ive build a few updates.zip for my own knowledge's sake (nothing fancy though, removed/added apks ), but I have my questions on how to properly make something not built specifically for an Hero work with all the hardware functioning. I'm sure many others are in the same boat (plenty of tech knowledge but lack of Android ROM resources). For example, the question I had in mind were in the form of:
Does specific hardware components (gps, wifi, bt) relies on linux kernel modules? Does it need some kind of special APKS or Jars to make it work along with the framework, or just kernel modules are enough once loaded?
Following up on the point above: would copying modules from another device specific ROM would be sufficient? (I guess not), what about Android release versions (Eclair, Froyo, Gingerbread, etc)? Can modules work regardless of the Android version being run on?
ETC...
Well its pretty much a long rant, but since i'm stuck with a 3 year contract on Telus with an HTC Hero, I wouldnt mind giving a bit of my free time to make a working ROM out of it. However I am/was under the impression that the Hero ROM development scene went to a stop once Cyanogen started supporting Hero (seems to me there are only two *major* roms out there, CM and VillainRom), and due to that ROM cookers stoped caring about the Hero since it was well enough supported as it is (with CM on board).
Thanks for listening, doctor
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
l0st.prophet said:
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
Click to expand...
Click to collapse
Any luck with it? I had the same idea, reading now a lot of information about building a rom.
Maybe we can post some useful links or tutorials about building ROMs in this thread so that we can kind of collaborate?
That would be a great idea, i really like the idea of building my own rom. or at least try to build one.
Here you can find how to setup your own machine to build android roms
http://source.android.com/source/download.html
if you have problems with installing sun-java5-jdk follow the instructions on this page:
http://blog.enea.com/Blog/bid/32050/Ubuntu-9-10-Java-5-and-the-Android-Open-Source-Project
Also checkout Cyanogen's wiki, they really did an excellent job there:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero
I'm progressing... slowly. Downloading Ubuntu 10.10 iso, 200MB of updates, the SDK, Eclipse, the ADT plugin, all the platform updates and GIT is taking a while on < 2Mb connection...
Especially the repo syncing... that just takes ages ;
krispijn_s said:
Especially the repo syncing... that just takes ages ;
Click to expand...
Click to collapse
Gives me time to read I spose! I totally understand how to build off Cyanogen's code, that sounds simple, but I get a little lost when it comes to syncing with AOSP or branching Cyanogen to make changes... but I got hours of dowloading yet so I can read up about it then!
Make sure you download the x64 version of Ubuntu. Since 2.2.1 you need a 64-bit system to compile the Android OS project.
Also don't expect to get it compiling right away, I reckon somekind of cpu-profile is missing (could be named different). Third I heard that the sound and camera (again) systems got changed, could be buggers to get those working.
Just my two cents
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Reserved
Hi Flinny, great job on the AOSP builds they are running perfect. I only had one satback sins build 4. Suddenly my gallery stopt working and dropbox to. Because of the gallery problem my camera won't boot either. I flashed build 5 but I had the same problem. Build 4 was flashed with a full wipe and build 5 was flashed as update that the reason of course why the problem didn't left but sometimes it helps Does this sound familiar? Greetz Munky
I tested it last evening but have many FC message about "aosp keyboard" even with the physical keyboard
I wiped all but still the same message going back to cm10.1
Ok I'm a little rusty on the details at the moment but: AOSP means that you want it to get as close as stock experience as you can get right? (I'm really looking for a G-lite thing but then with ICS/Jelly Bean, sort of Nexus feel but then for our Desire Z)
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Sent from my HTC Vision using xda app-developers app
I know that this is a dumb question and the answer is probably within the other thread, but... Ah heck, now it's just that I'm too lazy to look for the solution LOL...
But I installed AOSP 4.2 v6 last night and so far I'm not experiencing any major problems (except for FCing when I edit a picture and a bit of confusion adjusting to some new features LOL)... But when is this project going to be merged with CM? There are LOTS of creature comforts (e.g. silence during night hours, T9-style contact search, etc.) that I'm used to with the CM-optimized version that I kinda miss and only noticed that it was gone when I flashed it (I was under the impression that those features were all standard?)
Sorry to pester and thanks in advance.
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Eddy130306 said:
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Click to expand...
Click to collapse
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
google ears
EDIT: Sorry wrong thread
BTW: how can I delete my post?
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
zofox said:
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
Click to expand...
Click to collapse
http://andromadus.flinny.org/?q=node/2
This is absolutely the smoothest 4.0+ ROM I have ever used. Might switch to CM10.1 though for more features.
adamz667 said:
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Click to expand...
Click to collapse
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
Oh jeez... Either I had a total brain fart and completely missed the link or it got posted anywhere from the time I posted it to the catching up of 14+ hours of sleep (I only slept 7 hours across 3 days LOL), but I guess CM10.1 is already posted. I'll download it and see what's up. Thanks for not flaming me guys. I would've gotten the N4 but I'm not a big fan of LG (had countless bad hardware experiences) and my phone is somewhat last on my "to upgrade list", so thanks for everybody's help and keep up the good work! There's some top quality Münchner Bier mit your name on it once I get some disposable income
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
No I have not.
Sent from my HTC Vision using xda app-developers app
---------- Post added at 02:11 PM ---------- Previous post was at 02:00 PM ----------
LAMER_CZ
That is strange. Which recovery are you using? Don't use clockworkmod as they're always full of glitches and bugs. Don't use ROM Manager to flash ROMs either as they as well have glitches. I recommend doing everything in recovery. If you do have clockworkmod I recommend flashing 4ext as it has more features and can make your phone a little faster
Sent from my HTC Vision using xda app-developers app
Ok I just went ahead and installed it. This is exactly what I need for a ROM on my Desire Z! Thanks Flinny, and keep up the good work!
Now my experience with this ROM:
- I just fly trough my home screens and menu's, it runs fluently!
- When at stock speeds (so 1Ghz) I sometime run into problems booting up the settings. I just hangs there for 4+ seconds untill it actually shows the settings. Setting clockspeeds to 1,8Ghz fixes this most of the times, but it's something you might want to look into (Or don't, it's your ROM)
- The above also happens with some apps.
I don't run swap or any other optimization, so I don't know if it's my problem or a ROM problem, but if you want me to do some more testing just tell me what I need to do
Boot Loop
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
usc911 said:
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
Click to expand...
Click to collapse
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Authorita said:
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Click to expand...
Click to collapse
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
usc911 said:
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
Click to expand...
Click to collapse
Do you think you could get a log of the reboot? Might help in figuring out why it is rebooting like that.
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Current Build Changelog
Build 16
Rom
Should have fixed the zoom problem with browser some were having with large fingers/thumb presses.
Notification LED should be green again.
Disabled sliding picture animation when taking a picture for now.
Saga, rotation issue should be resolved again.
Everything else synced with CM.
Kernel
Patched to 3.0.66
Saga - S2W should be disabled by default on a clean install
Increased PMEM allocation on both SAGA and VISION as we were having out of PMEM issues sometimes when coming out of standby.
MDDI - sorry still need an updated kernel for you.
Checkout http://andromadus.flinny.org for previous changelogs
Looking forward to this
Flinny said:
Files still uploading...
Click to expand...
Click to collapse
Could you please reply back when you've made the files available? Thanks!
rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
Uploaded
Sent from my Nexus 7 using Tapatalk 2
rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
http://andromadus.codefi.re/ and sort by 'Date'
Wooo! Trying this
Can I flash directly over 4.1.2 build 129?
or would you recommend a clean wipe : ]
or check the link to the new website on the OP
I would suggest doing a wipe as Gapps etc are all different... if you do try an upgrade then I would suggest backing up... flashing rom/new gapps/wipe cache/dalvik at least.. then most likely finding it didn't work and having to wipe anyway
Nick.
Thx so much. I will try it.
Just tried installing directly over 129, rotation broke so I'm going to try from a full wipe. ( everything else is hunky dory really, although took a quite some time for the phone to calm down and get back to it's usual pace)
By the by, I notice the kill all icon from 129 is gone, is there anyway I can add that myself rather than wait for an update? ( as it's super handy!)
Thanks again flinny and Andromadus folks! My phone is even more woosh woosh and fancy than ever before.
Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?
jspina said:
Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?
Click to expand...
Click to collapse
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.
Pantherx12 said:
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.
Click to expand...
Click to collapse
Thanks. I know what the differences between the two are. I was just wondering if thats all that differentiated the two. And after looking at the titles its obvious that they are.
haha took me a few mins to realise this is the new cm 10.1 anyways good work as usual flinny downloading now
Sent from my HTC Vision using xda app-developers app
Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.
Flinny please make name theme more easy. It difficult to distinguish
Sent from my HTC Desire Z using xda app-developers app
rubin110 said:
Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.
Click to expand...
Click to collapse
Its missing in the settings menu for me also. And wifi works but sometimes it doesn't connect, everything else seems to work
Sent from my HTC Vision using xda app-developers app
Go to about phone and tap build number until it tells you that your now a developer....
Sent from my Nexus 7 using Tapatalk 2
Thanks flinny~~
It's so wonderful~
But I can't find the CM's function, like "Performance",
If the CM 10.1 have some function not implement??
Some features have not yet been ported to 10.1 by the CM team yet. But performance and developer are hidden in all 4.2 builds until you do the tap build number thing
Okay everybody, I want to start a WIP on this as it seems that we can get somewhere. The last dev seems to have dropped the project so I picked it up. :good:
***NOTE*** This is meant for development/testing purposes ONLY. It is in NO WAY for the faint of heart and you must follow ALL instructions or it will not boot! You have been warned!
As of 5/7/2013, the following things are working:
Camera (flash works, it takes pictures)
Sound (the only reason I know this works is because the shutter noise goes off in the camera app, there is no other way to test this right now)
The test apps (browser, notepad, gallery, camera, browser, phone, calculator, calendar, clock)
Power button (phone goes to sleep and wakes, hold the power button down to shut off the phone - the shutdown takes a second because it shuts down just like a linux kernel would - plug it in the charger to test this, it will vibrate once it is off)
Not working - just about everything else. Most items are still placeholders and there is a stability issue where the apps all close themselves after a few seconds which I am trying to figure out. There is no data or cellular connectivity of any kind. This may be fixable, however, since I was able to get the camera working by pulling the prebuilts from a different CM version. I'll keep experimenting with this. If you put the device to sleep, it does not wake up to the same brightness (it is dimmed) and you can not adjust the brightness right now (working on this as well, its a permissions issue in the kernel source but I haven't been able to narrow it down yet).
It is VERY finicky about how it is installed. I won't give any support for anything but TWRP 2.5.0.0
To install:
-Download the kernel zip and the latest daily from Ubuntu (I will post links later)
-Backup your current ROM in its entirety using TWRP - check every item on the list or you may have to go to a fresh install of your version you were running previously.
-In TWRP (once again, make sure its 2.5.0.0 because these are 2.5.0.0 specific instructions), factory reset but do an advanced reset, check dalvik, data, system, and cache. ***MAKE SURE THAT YOU DON'T FORMAT YOUR MICROSD***
-Install the kernel zip and do not wipe cache or dalvik
-Install the Ubuntu preinstalled image, once again make sure you do not wipe the cache or the dalvik.
-Do not do anything else, no fixing permissions or anything, just reboot
-Wait about 2 minutes for the lock screen to come up and then you can use it
I will keep working on the kernel - the other functions will not work until Ubuntu implements them.
This is my first time working with actual development - if anyone wants to give me a tutorial to get my project up on GitHub so everyone can work on it, I would be more than happy to do so.
Here are the links:
Kernel built 5/7/2013: http://d-h.st/185
Latest Ubuntu Touch base: http://cdimage.ubuntu.com/ubuntu-to...current/raring-preinstalled-phablet-armhf.zip
Since the source has been moved to Raring Ringtail, there should not be a need to update that link. Please note that the 5/7/2013 build is the one that I tested and be sure to let me know if it gets broken in the future.
Enjoy everyone and once again, if you want to contribute, I'm more than happy to set up a GitHub, I just need some basic help getting it started.
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
TheLastSidekick said:
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am hoping that development will take off. Ubuntu is set to start releasing alpha apps on the 16th so figuring out how to get a working kernel for it was top priority for me and nobody else seemed interested in doing it.
I've literally spent hours, lots of expletives, and other unpleasant things trying to get this built. I think I should have started working with CM BEFORE taking on UT but it paid off
Thank you sir,
Dling now
Sent from my Galaxy Nexus using xda premium
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
ktetreault14 said:
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
EtherealRemnant said:
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
Click to expand...
Click to collapse
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
eggydrums said:
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The kernel is a CM base. Its a massive fork of CM that's kind of a royal pain in the ass to work with since its not been synced since they forked it and they've made major modifications to the code (all traces of Dalvik are gone, for example). You also have to make modifications to the kernel build so it functions more like a linux system, there are process patches that have to be applied to the kernel, etc.
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Cannot wair for Ubuntu to be fully released, I would like to use this as a daily driver
Sent from my SGH-T999 using xda premium
charlieb620 said:
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Click to expand...
Click to collapse
So you had the same issue with your build?
Admittedly, I never tried it because I was determined to build my own and yours was March dated. I had posted in the thread trying to get some assistance from you actually - but yeah, its certainly not usable right now.
Was your kernel a forced M1 or did you somehow find a way to get the nightly source to build? I've built M1 and M2 so far. Since I had the same results with both and UT is based off of M1, I haven't messed with M3.
I wish I could figure out the WiFi and the force close of apps - did you patch the kernel successfully? I added the proc patch as best I could (raw data paste but it didn't throw warnings so it must have worked - I'm not a programmer) and it didn't fix anything, apps still just close after a few seconds.
I was surprised that I got the camera and sound though just by switching CM versions. Maybe the same thing can happen with the WiFi? I noticed that it is being built as a module but I don't know enough about the Android kernel to reconfigure it as a built-in (I don't know if the Ubuntu kernel has the code for detecting all the hardware just yet, I'm guessing it doesn't). I've done lots of Linux kernel tweaking (I have toyed with it since Red Hat 1.0 and its my daily driver in the form of Ubuntu 13.04 right now - usually I use Mint but I wanted to eliminate as many variables as possible) but I don't know much about Android.
Admittedly, I started with UT before I had ever worked with CM even so I've learned a LOT. lol
Thanks for this.
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
biohazard said:
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It should work fine with the latest DP. I haven't bothered to update it because the kernel source hasn't really been worked on. They're still focusing all of their work on Google devices.
There isn't a stable kernel for any S3 variant right now.
Sent from my SGH-T999 using Tapatalk 4 Beta
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
biohazard said:
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Make sure you followed the directions exactly, any deviation will cause it not to boot. Also there is no boot screen. What you can do is plug it in to the charger before you boot it - if it fails to boot the phone will power off and take you to the charging screen. If it doesn't, give it a few minutes to load up especially the first boot.
If it fails again, let me know and I'll see about building a new kernel some time this week. As far as I am aware there is no newer kernel source on the Ubuntu side but I can try to build an RC5 based kernel (this is an M1 kernel).
Its worked for everyone else but I can't test it right now because I'm getting ready to go out and need my phone.
Sent from my SGH-T999 using Tapatalk 4 Beta
Alright I see, thanks for all the help. Could you possibly point me to the correct base download, I have tried multiple phablet bases, and I just can't get it to boot for some reason. Thanks in advance for all the help.
Sent from my SGH-T999 using Tapatalk 4 Beta
The international GS3 has working wi-fi.....i know the hardware is completely different but do you think you might be able to look at how they got it working over there?
http://forum.xda-developers.com/showthread.php?t=2315397
Here's the commit that shows how he got wi-fi working: https://github.com/Androguide/andro...mmit/feac1d9af58c2947e0f3f6b6719553be5811ce6d try applying that to init.qcom.rc i would but my computer won't build anything i'm trying to fix it...
Also for github you really just need to post your manifests file and whatever you've modified from the source code. i'm not really a pro with github but i've worked with it quite a lot. They have an awesome tutorial on their website i'd recommend checking out.
Okay Ubuntu made upstream code changes that broke the kernel. Give me a few days and I'll have an update.
Plays2 - that patch *should* work for us as well since we use Broadcom's WiFi just like the international version does (odd that they didn't use Qualcomm's since it came with the SoC but it works in our favor in this instance). Still takes a lot of configuration to get it running though.
Kinda redundant since adityaxavier just put his build up, but here's what I built last night. I can't test it since I'm still not home (I built over SSH), but I think I fixed some if not all of the problems it was having. If I end up getting working builds as good as adityaxavier's, maybe I'll turn this into an unofficial nightly thread. I'm really hoping crespo4g can be included in CM's official nightlies again!
Alpha 2
This is the first build that I've gotten to boot, so I figured I'd post it here.
It's very very buggy as of yet (like FCs everywhere). I'm working on resolving the issues, but it's source built (not a port) and it boots.
So people might want to mess around with it. Obviously I take no responsibility if you brick your devices.
Download
Code:
Hey all,
This is in the works, if it ends up building and booting out of the box, we'll have working CM11 KitKat for our Nexus S 4G devices.
I'm not really a dev, mainly a hacker/tweaker/modder, but we'll see how this goes.
Here's my GitHub repo, I forked CM's 10.2 crespo4g sources and made some minor changes to update to the CM11 tree.
[url]https://github.com/jc4gavejc/android_device_samsung_crespo4g/tree/cm-11.0[/url]
Check back for goodies soon!
EDIT (10:51PM PST) I made a dumb, dumb, dumb mistake. I was extracting proprietary blobs from a CM10.2 build I had installed on my phone, and all the WiMAX blobs were missing from the manifest.
Just flashed back to stock and retried the process. All blobs synced without a problem. Rookie mistake. Building yet again. Hopeful this time it will work.
NOTE: This does not mean we'll have working WiMAX yet. I anticipate it'll still be broken from 10.2... sorry =[
[QUOTE]============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4
CM_VERSION=11-20131127-UNOFFICIAL-crespo4g
TARGET_PRODUCT=cm_crespo4g
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a8
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.11.0-13-generic-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=KRT16S
OUT_DIR=/home/josh/android/system/out
============================================[/QUOTE]
Dude you're so awesome, thank you so much! I thought our nexus s 4g had met its end. Can't wait until there's a preview. Keep up the good work.
jcruz767 said:
Dude you're so awesome, thank you so much! I thought our nexus s 4g had met its end. Can't wait until there's a preview. Keep up the good work.
Click to expand...
Click to collapse
I think having the blobs from 4.1 did it. Everything is zipped and ready to flash. I'm gonna test it (have to reflash CWM since I went back to stock) and if it works I'll upload it for people to test.
This is awesome to see. My wife has a NS4G that I think would have new life breathed into it with 4.4. She's on 4.2 right now and, unless it's OC'd by a good amount, it chokes on everything.
Migital Warfare said:
This is awesome to see. My wife has a NS4G that I think would have new life breathed into it with 4.4. She's on 4.2 right now and, unless it's OC'd by a good amount, it chokes on everything.
Click to expand...
Click to collapse
I don't know if I'd count on 4.4 being a lifeline to speed. 4.2 runs significantly better than 4.4 on my Nexus One.
That said, I'd limit concurrent processes in your developer settings menu regardless.
I think there's problems with yesterdays CM tree, the ROM I built had so many FCs it was unusable on the crespo4g, so I built for the mako (Nexus 4) from the exact same sources and had the same issues (which I've never had before building CM for the mako).
Trying a build from pure AOSP right now. Will keep you guys posted. PM me if you want the buggy ROM, otherwise I'll toss it.
jc4gavejc said:
I don't know if I'd count on 4.4 being a lifeline to speed. 4.2 runs significantly better than 4.4 on my Nexus One.
That said, I'd limit concurrent processes in your developer settings menu regardless.
I think there's problems with yesterdays CM tree, the ROM I built had so many FCs it was unusable on the crespo4g, so I built for the mako (Nexus 4) from the exact same sources and had the same issues (which I've never had before building CM for the mako).
Trying a build from pure AOSP right now. Will keep you guys posted. PM me if you want the buggy ROM, otherwise I'll toss it.
Click to expand...
Click to collapse
I just want to thank you for your effort regardless of how far you get! I was begining to think the cerspo4g development was dead!
I was thinking about trying to get the crespo CM11 to boot on our devices but I know NOTHING about cooking roms. I just couldn't find the time (too many other projects renovating a FG camper, minecraft server, fixing the car, work, family etc..)
Sooo... THANK YOU! :good:
i'm in to test any build for crespo4g... i won't be able to test data/cell b/c i use this device for listening to music only... would be great to have this on my NS4G though... was looking into making it myself but idk how to do it either lol
Thanks for working on this. I am only using the NS4G as a WiFi device for now, but would love to play around with anything 4.4
Sent from my LG-LS970 using Tapatalk
the1dynasty said:
i'm in to test any build for crespo4g... i won't be able to test data/cell b/c i use this device for listening to music only... would be great to have this on my NS4G though... was looking into making it myself but idk how to do it either lol
Click to expand...
Click to collapse
I'll post it here when I get a working build, right now I'm trying to merge some of cn.fyodor's optimizations from the original Nexus S build. It might end up being pure AOSP as opposed to CM, depends on what I can get to build without errors or other post-build problems. I don't have a ton of time to work on it over the next couple days, but I'll try to do what I can.
jc4gavejc said:
I'll post it here when I get a working build, right now I'm trying to merge some of cn.fyodor's optimizations from the original Nexus S build. It might end up being pure AOSP as opposed to CM, depends on what I can get to build without errors or other post-build problems. I don't have a ton of time to work on it over the next couple days, but I'll try to do what I can.
Click to expand...
Click to collapse
Thanks... Enjoy some turkey today if that's your thing... Personally, I've been using stock for a few months on my N4 and now on my N5 I only rooted to remove some apps and install a custom kernel... I prefer stock to mods now... Mainly because I don't have time to keep up with updating so often... So a stock 4.4 ROM on my NS4G will work for me... I already have the GEL and that runs great for me but I'm still missing the complete 4.4 on it that's why I wanted to flash it lol
Sent from my Nexus 5 using Tapatalk
+1 for full stock
I prefer full stock myself. Google's been giving such sweet goodness lately, it's really the best way to go. Plus if anyone wants to they can customize to their heart's content. I'm very hopefull you'll get this working fully - as stock.
There's really no such thing as stock when it comes to devices outside of Google's support line. Technically if you want stock its a 4.1.1 factory image from Google. AOSP is close to stock but doesn't include any proprietary Google apps by default. You can remove/add any packages you want via adb and create a "stock" ROM, but you can do that coming from any base be it AOSP, CM, or whatever. Personally, I prefer CyanogenMod. That's why I'm working on getting this build working.
Sent from my Nexus 4 using Tapatalk
by "stock" i mean no extra features added...
Right, same here... just not having custom anything - adding gapps is fine, but not custom kernels, themes, etc.
First build up. It's very broken. beware.
I'm just glad you're still working on it, I thought you had given up on 4.4 for the nexus s 4g
---------- Post added at 12:33 PM ---------- Previous post was at 12:00 PM ----------
jc4gavejc said:
First build up. It's very broken. beware.
Click to expand...
Click to collapse
Should we flash any of the stuff from your other 4.4 thread? CMDA fix, or Superuser?
Jfuginay said:
I'm just glad you're still working on it, I thought you had given up on 4.4 for the nexus s 4g
---------- Post added at 12:33 PM ---------- Previous post was at 12:00 PM ----------
Should we flash any of the stuff from your other 4.4 thread? CMDA fix, or Superuser?
Click to expand...
Click to collapse
Nothing except gapps. I'd be impressed if you could get very far with this build though. I made some changes to my source tree, I'll get a new build up tomorrow morning.
I'll give it a go and see what happens on mine. Just got this nexus s 4g from my sister, she had it on Sprint, while visiting her I asked if she had any old Sprint phones she's not using so I can try it out on Ting.
Got two of them now, one for me and one for wife. I have my wife on a stable 4.3 HellyRom, I don't have any problem trying out beta (alpha?) roms on mine though.
I'm going to try it with those two 4.4 tweaks (bionic and dalvik), plus I have a few radios downloaded I can try with it.
I'll let you know how it goes
Edit: So far, it's 'booting', but only to the first set up page asking me to set up a cyanogen account, where I'm constantly bombarded with FC's stating the dialer and systemui have crashed, those happen consistently for a minute or so until the phone reboots and starts the process over again.
I'm going to try flashing a version of Googlephone I saw on another thread after flashing ROM/Gapps, see if that does anything.
I've decided I like this phone enough to start trying some dev work on it. Might take me a while to get back in the loop (last thing I did dev work on was my first android phone, the HTC Hero on Sprint... Looooonngg time ago)
Gonna finish setting up a VM with Ubuntu on it tonight and toy around with some building working with what we've got so far to hep get 4.4 running on the Nexus S 4g
Jfuginay said:
I've decided I like this phone enough to start trying some dev work on it. Might take me a while to get back in the loop (last thing I did dev work on was my first android phone, the HTC Hero on Sprint... Looooonngg time ago)
Gonna finish setting up a VM with Ubuntu on it tonight and toy around with some building working with what we've got so far to hep get 4.4 running on the Nexus S 4g
Click to expand...
Click to collapse
You have my Github repo? I've merged all the necessary changes for the crespo4g in my device tree here:
https://github.com/jc4gavejc/android_device_samsung_crespo4g/tree/cm-11.0
I'm almost done with another build, I actually had openjdk7 installed before, so switched to oraclejdk6 (the one I should have been using).
That might just make the difference in the fcs. There's no other reason why my build shouldn't be working as perfectly as the ones they have for the crespo. Seriously, they're the same device minus the radios.
Hope stuff goes well for you, it'd be fantastic to have another dev working on this.