[N910C/H][DEV] AOSP sources - Galaxy Note 4 Original Android Development

*omg, thread updating needed*
Hey guys, as some of you might know, I was donated a Galaxy Note 4 (N910C) and am now working on AOSP for it.
The sources required to build a ROM are hosted at GitHub currently:
device: https://github.com/teameos/device_samsung_treltexx/
kernel: https://github.com/raymanfx/kernel_samsung_trelte/
vendor: https://github.com/raymanfx/vendor_samsung_treltexx/
If you want to give this a shot, you should be familiar with git and repo and be able to sync the TeamEos source yourself.
If anybody feels brave enough, give it a try yourself, all the required bits are posted above
TODO/BROKEN:
Bluetooth headset calls (RX works, TX is broken)
Open source AVC (H.264) Encoder is broken (Videos recorded in portrait are rotated by 90° counter clockwise, and there's artifacts all over the place)
Everything else should be pretty much working.

hopefully watching all your work. congratulations.

hey! any progress on this? I'm really excited!
Sent from my SM-N910C using XDA Free mobile app

+1

Congratulations

First success:
The phone is booting and the adb server is starting.
I'm still missing some sensor blobs from stock which causes the sensor layer not to start and thus prevent various other init tasks (such as display, EGL) to crash.
I'm going to work on getting at least display up this weekend.
No promises though.

This is great news. Thanks for this hard work. Thank you for making our donation future experience CM12.

someone was trying to port CM11 to galaxy alpha.. i guess its a similar kernel..
http://forum.xda-developers.com/note-4/development/exynos-543x-android-development-t2949478
dats d link.. jus posting, if it helps u in anyways..

Good luck!

Superb!!!

Awesome work looking forward to seeing it on my N910U... hopefully

Great :good:

Awesome!

More progress today:
The device partially boots now, boot animation shows but that's where it loops.
Sensors are fully working and storage handling (internal storage, external sdcard and usbdisk) have been fixed.
I'm still missing some camera blobs which I believe keep the device from booting up (because it crashes other init services).
I'll look into that tomorrow probably.
All the latest fixes have been pushed to my github repos, so if anyone in here feels like experimenting a bit, let me know how it goes

RaymanFX said:
More progress today:
The device partially boots now, boot animation shows but that's where it loops.
Sensors are fully working and storage handling (internal storage, external sdcard and usbdisk) have been fixed.
I'm still missing some camera blobs which I believe keep the device from booting up (because it crashes other init services).
I'll look into that tomorrow probably.
All the latest fixes have been pushed to my github repos, so if anyone in here feels like experimenting a bit, let me know how it goes
Click to expand...
Click to collapse
These words cause many joys.

@RaymanFX , great work, update the first post with every progres, and for the other guys this a dev thread, dont spam with greets otherwise im sure a mod is gonna close the thread, keep it dev related or someone can open a thread in the general options for this project

Go go go

Progress?

+1

Well, as stated on the first post, it'd probably make more sense to watch my github for progress instead of asking in this thread.. Just saying.
Big progress has been made in terms of audio, as I finally got around to configuring proper mixer paths for audio devices here: https://github.com/RaymanFX/device_samsung_trelte/commit/c5954750b5c13ce9bf27992f145a18a837099e12.
I had to do lots of research because there is little to no documentation on these mixer_paths.xml configs, so I ended up creating it from scratch based on Samsung's UCM config.
The device still doesn't boot further than the bootanimation, but I still have some interesting lines in the logs to solve, for example it still reports invalid input/output devices in audioflinger, which clearly is an issue.
At least the issues preventing us from booting are no actual display issues, but init services crashing.
Also, it looks like the RIL is starting up after adding Samsung's cbd daemon to early init execution (ramdisk), but I don't expect telephony/mobile data to work just yet.

Related

[BUILD] **Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!

Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>​
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps! We don't make empty promises, we just provide solid and complete builds. No ETA's, no threads without download links or instructions... Enjoy!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for BLAC) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post. Others have said this is a horrible keyboard, and you should just use Swype. I'm a big fan of use what works for you, so you folks make the decision for yourself!
Anything that's broken in Froyo, is probably broken in this build.
Blackstone users - help me flesh out this section! Anything that's not working let me know!
Changelog​ March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Startup.txt that works with frx06 and gbx0a
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off gsensor_axis=-2,-1,3 msmsdcc_nopwrsave rel_path=GBX0A"
boot
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
i suggest using zeam launcher it's faster and lighter than the stock one
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
if you need storage access,use wifi explorers,they proved very good solution for not being able to access sotrage via usb
welard said:
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Click to expand...
Click to collapse
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
farukb said:
not sure if pmem.extra=1 is needed at all and does it perfor better without it,i read somewhere that it does....maybe arrrghhh knows
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
i've attached ts-calibration for blackstone,so if anyone needs it,it is precisely calibrated....additionally if someone wants to do it by himself,he (she) should use 11** kernels (current are 13**),because calibraiton feature was removed from later kernels
Click to expand...
Click to collapse
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
arrrghhh said:
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
farukb said:
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
Click to expand...
Click to collapse
Ah no worries. Let me know if there is something you think I should change, I don't have a Blackstone and I'm always looking to improve the process for you guys!
arrrghhh said:
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yes it shows in window....thanks
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
copied everything to 5th post,so it's all in one place
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
Click to expand...
Click to collapse
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
farukb said:
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
Click to expand...
Click to collapse
What recommendation do you have? I didn't think Swype was free..?
farukb said:
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
Click to expand...
Click to collapse
Probably true, I'll take that part out thanks.
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
Click to expand...
Click to collapse
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
farukb said:
front camera
Click to expand...
Click to collapse
I'll add it, but don't expect it to work anytime soon .
farukb said:
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
Click to expand...
Click to collapse
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
farukb said:
@arrrghhh, i think you should remove the sensor rotation part of the post,because could confuse people...but then again you're the boss,so do as you please
Click to expand...
Click to collapse
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
welard said:
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
Click to expand...
Click to collapse
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
arrrghhh said:
What recommendation do you have? I didn't think Swype was free..?
Probably true, I'll take that part out thanks.
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
I'll add it, but don't expect it to work anytime soon .
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
Click to expand...
Click to collapse
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
@argh
swype is free,you just need to register and you gain access to swype beta
it's called beta because it is made for devices that don't come with if out of the box and therefore are still developing it,but it works great,nevertheless
welard said:
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
Click to expand...
Click to collapse
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
farukb said:
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
Click to expand...
Click to collapse
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
farukb said:
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
Click to expand...
Click to collapse
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
arrrghhh said:
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
Click to expand...
Click to collapse
i have not a device to donate.....but if we all donate for a device that would speed things up much faster...... i think you should start a new thread for donate for a blackstone device......im sure theres lots of blackstone users willing to do this because the end result will pay off for all of us.......
i had a sod and now i can't boot,the animation just keeps looping...hw buttons vibrate then i touch them,but do not work....power button doesn't work either
happened to me once before,but i don't know what i did to solve it...i maybe deleted the data.img
this time i tried to wipe and format the partition,didn't help
i tried with fresh files (except for the data.img) but still nothing...
@arrrghhh: wanna swap with me for your rhodium,if you want it badly?
@werald and others:if we are going to donate a device,it'd be best to donate it do a dev,maybe stinebd,don't know

[ROM][DEVTEAM][GSM][17/04/12]GSM GalaxyTab Honeycomb team--HoneyComb RC1 REUPLOADED!!

Hi guys!
After going through some beta stages,we finally got Honeycomb RC1,with all the Major bugs IRONED OUT. Now it's only a matter of solving the minor resolution problems
UPDATE: Application requests for the team are temporary CLOSED.
Our team is made up of :
Devs:
- Me
-cdesal
-Frussou
-diagdave
Testers:
-stevensheaven
-Nezorflame
-slimdizzy
-captain134
-Wackymix
-Phelapkell
-ani55
Stay in touch with the team! Visit our (temporary) forums at http://honeycombsgt.freebb3.com/index.php
IRC Channel for team members only: #honeycombsgt @ freenode It will be opened to the public only in release days!! Requests for help and n00b questions wil be IGNORED in developing days,remember we can ban people from the channel!
HONEYCOMB RC1 20 OCTOBER 2011
DOWNLOAD---> http://www.mediafire.com/?mv5xavv0t1bkl57
Changelog
SD automount fixed with MUSIC and GALLERY working --- thanks diagdave
3G AND GSM FIXED!! --- thanks diagdave
New RIL from Samsung sources
Setup Wizard has been re-enabled because it works
WARNING--- THIS BUILD WILL PROBABLY WIPE INTERNAL SDCARD !!
INSTALLATION GUIDE! ---> http://forum.xda-developers.com/showthread.php?t=1296330
Additional notes:
- You may occur in strange issues like red borders in windows but they are known HC sdk issues, easy to overcome, just search on google or take a look in this forum
DEVELOPEMENT STATUS: Active
Things we're working at:
New kernel,built from new sources
Smoothness increase
Better screen resolution
Minor bugs fixing
I received some requests of guides on how to make a ROM. Well,there aren't specific guides for that,but our dev mssmison wrote a porting guide recently: it's a good start for beginners Take a look at it here: http://forum.xda-developers.com/showthread.php?t=1242216
Updates soon
Dario
Credits:
Spacemoose-- without him none of this could be possible
cdesai-- our kernel guru
diagdave-- for the SD auto mount and 3G fix
All the testers team
The entire XDA community
You have at least one more tester now count me in!
I'll be a tester if you want.
Sent from my ST15i using XDA App
I could be a tester. I have another account on the forum but I must get it back, LOL. So, reply to janne.paasimaa(at)gmail.com if you have something. I will follow that topic and I will tell ya my another account later.
@ OP
Hope this catches some devs eyes. I really hope some help out with a GSM port or possibly a CM8 based on ICS when its out
PS. Its better to put the date tag at begining of topic title in short format, ie [4.10.11]
You might want to have some pre-requisites for testers otherwise the vast majority of posts to this thread will be "Me too!!!11!" posts.
The primary difference between CDMA/GSM ports is at kernel level. The only real hardware difference is in the radio, touchscreen, processor, sound etc. are all the same.
I'ld like to help with it as much as I can, I do dev on my galaxy 3 now
If really the prime comes this month and we get ics sources we can forget honeycomb(although Google will need ta keep it sumwhere else, R.I.P. android.git.kernel.org)
I will defenitly be a tester, no matter what ...
I would gladly help if you show me where I could find tutorials for developing for android so I could help out. I must add I have some good experience with C/C++ and some with C#. If you would be so kind to send me a PM with some tutorials I would gladly help
i would love to be a beta tester but i cant make a nandroid backup on kratos.. any ideas?
can't wait. I am so anxious.
thanks DEV's for all the hard work in advance!!!
I very much doubt any real devs are going to bother with HC now. Spacemoose abandoned it without notice or explanation which is a real shame as he seemed really dedicated to the cuase, and oldmacnut looks like he has given up on challenge aswell.
IMO this is now just wishful thinking. Our best bet is to wait for ICS source to drop.
I have an early port of oldmancut's latest HC release I'm uploading right now,but this evening I can't test so I'm posting it here for the braves who can test
It's based upon old kernel sources and MAY wipe internal SD as old builds. ETA: 50 minutes!
smali26 said:
can't wait. I am so anxious.
thanks DEV's for all the hard work in advance!!!
Click to expand...
Click to collapse
+1
Sent from my GT-P1000 using Tapatalk
First port attempt: http://www.multiupload.com/HMD5JTNJ8X
It could not boot,and there are possibilities it will wipe internal SD. Only for the braves
TheATHEiST said:
I very much doubt any real devs are going to bother with HC now. Spacemoose abandoned it without notice or explanation which is a real shame as he seemed really dedicated to the cuase, and oldmacnut looks like he has given up on challenge aswell.
IMO this is now just wishful thinking. Our best bet is to wait for ICS source to drop.
Click to expand...
Click to collapse
spacemoose1 he doesn't need to explain why he abandoned the project
you must know , everyone here have another life outside the XDA forum
if he got the time , we should has it along time ago , but he doesn't have the time
cheer up ,
anyways , trust me , HC is not that good , GB is away better
HC is so damn bugy lagy crap , i use gtab10.1 and i can't tell you how many lags i get per second , so how about a ported hc ? how it will be you think ?
Lets stop banging our head on closed source HC . ICS is most probably coming on 11 october in samsung unpacked google episode.
ok i did flash it..
these errors come's up afhter boot.
Gmail (proces.com.google.android.gm) stopt
moon phase pro (proces.com.daylightmap.moon.pro.android)
gun bros (proces.com.glu.android.gunbros_free)
messages (proces.com.android.mms)
after close all errors it goes to the honescreen.
menu button not working.
home and back working.
auto turn screen not working.
keyboard don't show when trying to connect with wifi.
when i push the power button ones it reboots.(normali it put off the screen only.
btw boots in 35 sec..so pretty fast
all software still working.so it did not wip anything.
i will come back with more in a while..
hope it helps a bit so far.
regards stef
Downloading, will report asap...
Edit:
Booted in a minute or so, it gave me a Welcome screen with the list of languages and the Start button, I can choose language but nothing happens when I press the button so can't move further...
Wiped again and reflashed - same result. Stuck for now...=\
Btw, when the screen goes to sleep, it sends the device into reboot after a few seconds.
2sevensheaven, how did you pass through the Welcome screen?..
i just pushed the next button en cancel..
and like u say..when the screen goes out..it reboots.
i will now try a factory reset and see what happens.

Letting this die. New dev and user threads created.

LAST UPDATED: 4/2/2012
WHERE ARE WE NOW? IS IT BOOTING? CAN I GET A NEW ROM W/ AN ICS KERNEL?
Is it booting? Yes.
Is there a new ROM for the kernel? Yes. It's still a work in progress and likely to continue changing as the kernel gets more developed.
Can I test the new ROM? Right now, there's no reason to run this ROM unless you're working on the kernel and/or bug testing. It is booting into the OS now and as soon as I fix up the Wifi and SD MMC mount, I'll probably put up a test link for testers -- lots to bugfix, this isn't "usable" yet. Especially since we don't have the Ducati loading for hw codecs.
How long will it take to fix? There is no way to know. I work on the kernel about 4-5 nights a week, and when I fix something, there's always something behind it which needs fixing as well. I am making good progress (in my opinion), but that may still mean weeks of development.
I'm going to keep a page updated on my blog so that at any point in time if you're curious what the output of the boot up looks like you can go take a look (this will be mostly technical output and don't worry if it much of it doesn't make sense):
http://blog.hash-of-codes.com/kindle-fire-ics/
[NOTE: I've now highlighted items in green which are good and some red items still to be fixed.]
2nd post has the current status in more detail
UPDATED 4/7
WORKING -- WILL NEED TESTING:
EXT4 MMC Filesystem Access
USB Android Gadget with modes like ADB and MTP (Do we want mass storage also?)
Battery / Charger Driver
Display driver / SGX / ION now plays nice w/ 512M memory (originally the 3.0 kernel was hard coded for 1G of memory)
Touchscreen is working
Sensors are working to detect tilt / movement
Power button working (no colored leds yet)
New Audio driver from TI is working (thanks nook_lover!)
Headset output / recording
Internal media partition mount
Ducati binary is being loading by the system now and the OMX server is starting -- NEEDS TESTING -- probably still won't work -- but its progress towards hardware codecs
PARTIALLY WORKING:
New Backlight Driver is now partially working. Won't adjust brightness yet, but it's coming.
:| Wireless device and driver is being recognized. Still troubleshooting.
STILL BROKEN:
:/ Color Changing Power Button Leds - Old Driver needs to be updated
FUTURE CHANGES IF NECESSARY:
- Touchscreen Driver has a newer straight Linux driver available which would need minor Android customization (current driver seems ok for now)
- Charger Driver has a newer straight Linux driver available which could be customized for Android (will probably do this one eventually. The current charger driver is very messy)
- Battery Gauge has a generic 3.0 android driver available. It would need minor customization (may or may not rewrite this one eventually)
Glad to hear it's coming along well. Keep up the good work!
Great news. Waiting for the kernel
Sent from my Kindle Fire using xda premium
STOKED!
Thanks Mr. Hash!
I have absolutely know idea what your talking about.
Thank You for being so smart.
kdkinc said:
I have absolutely know idea what your talking about.
Thank You for being so smart.
Click to expand...
Click to collapse
It'll make Netflix work on the Kindle. And stuff... like that. And some games too.
Hashcode said:
It'll make Netflix work on the Kindle. And stuff... like that. And some games too.
Click to expand...
Click to collapse
Love the layman's speak.
kdkinc said:
I have absolutely know idea what your talking about.
Thank You for being so smart.
Click to expand...
Click to collapse
In other words, all your porn will work....
kidding...
THANKS for the update Hash.....GOOD LUCK!!
You are doing the Lord's work here, man. I may not post very much, but I'm monitoring and your hard work is appreciated and my guess is you will get many accolades and hopefully a good shot of donations for this
Oh my god i love u !
Posrting just to show my support, if there is anything that a noob can make to help, i am more than glad to help
I volunteer as a crash test dummy...errr, Tester. Just say the word.
CM7 Infuse - XDA Premium
CM7 Infuse - XDA Premium
This is really good news. I have been waiting for it. Thank you for massive contribution for the community
Sent from my Amazon Kindle Fire using xda premium
Hardware acceleration! Yay Thanks Hashcode
HW Acceleration is a good news Thank you
I also volunteer to test this
Count me in too for testing! Would sure love to give this a flash when the time comes!
Sent from my Amazon Kindle Fire using xda premium
Im also Available for testing.
you are awesome, thanks for your work

[OFFICIAL][WIP] Vanir Apache 4.3.1

How many people are tired of not seeing any love for this awesome little device? Well I made sure to change that
Yes, you read that right. The Rugby Smart is officially supported by VanirAOSP.
Now, on to the boring part:
DO NOT FLASH TO THE GALAXY W OR GALAXY S +
Now that that's taken care of, on with the post.
What's working:
- Data
- MMS
- Calling
- Bluetooth
- Updater
- WiFi
- Vsync
- init.d
(more as I remember/fix stuff)
;
What's broken:
- Internal SD (Unfortunately this is a major grievance and is not isolated to the apache. This is a WIP fix)
- Camera (The setup on this is a b!%ch, I'm still working on it)
- USB tethering (Not sure why this one has to be difficult)
- Screenshots (Tied to SD bug)
And since this is official, We don't need a ROM changelog
Credits
Team VanirAOSP for providing the opportunity for officiated support
arco68 for providing the base code needed for source. building
NuclearMistake and DHOMD for hosting nightlies
grumpyspud for his thirst for more. Thanks for testing unofficially
Links:
Google +: VanirAOSP
Official Webpage: Vaniir
Nightlies:Apache NIGHTLIES
Thirst for more?
I got props omg.
You went out of your way to get the nightlies, so yes .
How are you liking it so far?
I goofed with the 1017 nightly for a little on my break.
Titanium backup actually loaded and kept my location of my folder in the physical SD card. It's never done that till this nightly.
Its way more smoother. What on the changelog (on nuke) made it smoother?
The display drivers from arco didn't agree with their sources so we're using the OpenSEMC one
[/COLOR]Good deal. The gallery, screen print, andcamera issue keep this one from being a Daily driver.
I make a backup of Kemo's cm 9 when I load ur nightlies. If you need me to test things let me know.
I am a decent blackbox tester not a coder.
once the sd issue is fixed the gallery and screenshots should come back to normal. The camera is mainly isolated around the kernel though.
Motorhead1991 said:
once the sd issue is fixed the gallery and screenshots should come back to normal. The camera is mainly isolated around the kernel though.
Click to expand...
Click to collapse
changelogs... until i see control f motorhead. No broken things are getting fixed right?
Just wondering how to read what is being changed.
Wow so good. How is offical? And pic is not galaxy wonder
Galaksi Wonder Candır.
grumpyspud said:
changelogs... until i see control f motorhead. No broken things are getting fixed right?
Just wondering how to read what is being changed.
Click to expand...
Click to collapse
The way their changelogs are set up makes reading them difficult, but all the changes that are specific to the apache I test on local builds before pushing to the main stream.
Heroata said:
Wow so good. How is offical? And pic is not galaxy wonder
Galaksi Wonder Candır.
Click to expand...
Click to collapse
That's because it's not a Wonder, it is a very close relative of it. It's been on these boards longer than you've been a member here .
And?
Camera's still broken, from what I can see so is SD. They're still digging for the SD thing.
Heroata said:
Wow so good. How is offical? And pic is not galaxy wonder
Galaksi Wonder Candır.
Click to expand...
Click to collapse
Its of galaxy rugby smart, a variant of galaxy w (AT & T)
Any news. The thread has been silent for well over a month.
I'm still fixing stuff and nightlies should still be coming out.
So, i guess we should forget about getting a fully working ROM for our beloved device?
Yea the last nightly was in November 2013. I think its a dead phone.
Sent from my SGH-I337 using Tapatalk
It's not dead, just on hold. Moving to CAF drivers requires major kernel updates that I haven't done yet
The download links for the ROM seem to be dead. They are leading me to a 404 error fire truck...
Sent from my SGH-I847 using XDA Free mobile app

[QCOM][DEV][WIP] OSS Camera HAL for S3 Neo (4.4.4 - 8.1+)

Hi guys im back with a new thread.
This is all for my journey to make oreo stable and this is one step further tho it still needs a lot of work to be done...
So for those who are familiar with the Camera u will know that the HAL is responsible for communicating with the qcom server back end who does all the dirty work for ya
It a entry point where u can define stuff like preview sizes, we actually have a 4k preview but sammy deleted that btw , picture or video Sizes, exposure etc.... Its the goto place when u want to either mod your camera a bit or make it more compatible.
For a look about how this works check out some source code from QCOM here: https://github.com/SnowCat6/vendor-qcom-proprietary-mm-camera
I don't aim towards modding this in any way to get like 4k video or stuff like that i aim for stability. I'm still searching for the root cause behind the battery drain on Oreo and the camera HAL was one of my thoughts. Now that its confirmed it isn't the problem i have to look elsewhere but thought it would be cool to share this here anyways.
BTW NO ONE EVER DID THIS FOR SAMSUNG PHONES SO THIS IS THE FIRST IN THE WORLD OF ITS KIND!!!! (Someone submit that to xda portal rlly quick we could help more phones like S5 or S4 :angel
Attached are the files u need to place in /system/lib/
Its NOT fully functional but one can take pictures and videos on both cams from 4.4.4 to 7.1.2 with no issues. Oreo is a different story, for that ill still have to edit more stuff to make it work. Unlike before i have the source code now so it should be easier :good:
Source code is here: https://github.com/S3NEO/vendor_qcom_camera/tree/samsung
Reserved 1
Great Work and Great News !!??

Categories

Resources