Related
For the last couple of days I've been trying to get Eclair 3D acceleration running on 32A with old radio. I was somehow succesful so I decided to release one Sense based ROM port and one "plain" Eclair. I had succes with other ROMs though (not all of them, but a few). Edit March 2nd - It now seems that it works on 32B/G1 as well, so I've added the porting package for those phones, see below.
This ROM is highly experimental! So bear that in mind. The only testing I've done is here on my own Magic - I am not using any ext3/ext4 partition for app2sd, for example, so I'm not sure how it behaves if you use one.
I've added a few things here and there that are essential to me like Market Enabler, More Locale 2, some ringtone and notification files and mixed in a few files from other Eclair ROMs to get a few things working. I've also changed the default analog clock (the Android widget, not HTC widget) to Pulse clock.
Thanks to:
ahmgsk (obviously), Kingclick, Cyanogen and all the other devs working on his kernel source, Amon_RA, all OpenEclair devs, polyrhytmic, dzo, vilord and many others.
What seems to work:
- 3D acceleration seems to work fine. I can get about 20fps in Neocore benchmark. I've also tested Radiant, Armadillo Roll and iDracula and they all seem to work. 3D Gallery works as well.
- Multitouch works
- Camera works, mostly - no video recording, though. If you take picture, it shows a garbled screen for a moment, but the picture itself is taken just fine.
- GPS and accelerometer work
- LED notifications work, all colors
- Bluetooth MIGHT work, needs testing. But you can enable it.
- Google Sync seems to work just fine
What seems not to work:
- YouTube and video playback in gallery doesn't work at all for now. Sorry.
Known Issues:
- Rather slow on startup. Give it time to start up fully, even after you see the home screen. You may even get a few "App not responding - FC/Wait?" warnings - just click on Wait and give it more time. But after it starts, it seems pretty fast to me. It's no SuperD, but still quite fast, I'd say.
- Live wallpapers are problematic and I'd recommend staying away from them. Some work (not very fast, though), some don't.
- Launcher 2 is problematic. I've kept it in the ROM and it certainly looks nice, but I've had all sorts of problems when I had it enabled, including long phone freezes, terrible lag in applications and other. I'd HIGHLY recommend just using the "normal" launcher (it's "Nexus style" anyway).
Note:
Take this port "as is" 'cause I probably won't support it much. I think of it more as a "proof of concept" that seemed too cool to me not to share it with others, but I don't have enough time to offer full support or work on it much these days. Maybe I'll release another version someday, maybe not. Sorry. I'm just being honest here.
Download:
v1.0 - md5 1d52c09ac080abd6f1620a00afb96d30
Rapidshare mirror
Mediafire mirror
Porting package for 32B - Warning: potentially unstable in many different ways! (see the thread comments first) - md5 506d30b69186059abc2a22804952e7a8 (Flash over the main ROM without rebooting the phone)
Rapidshare mirror
Mediafire mirror
(reserved just in case)
I will check it inmediatly...
but this driver 3d not work on magic 32b??Why not come out yet for the ROM 32b?
It might, as I don't think the solution here is specific to 32A. I'll maybe try to make a 32B kernel soon and let someone test it. Right now, I've yet to hear about this working for someone else on 32A other than me
Im flashing it ATM.
Give me a few minutes
ok when you relase a 32b Kernel,Warn
Well, i flashed it.
You're right, 3D is working
I tried it with SpeedX and Hyper Space, and they both are working. Not as fast as it would on a donut based rom (looks like the frame rate is a little lower) but they are absolutely working.
Launcher2 is still a bit laggy.
Some Live Wallpapers aren't working, they forced the phone to restart.
The gallery is working.
There are some bugs (like pressing the home button while in an app, will sometimes block my phone) that forced me to remove the battery.
This rom is not working enough for a daily use, but you did a great job.
Waiting for a bug fix Imma try the hero port now
Good to know, thanks!
BTW, as I've mentioned in the first post, I don't recommend using Launcher 2, it causes all sorts of weird issues with this ROM. And I also mention that live wallpapers are problematic and you should just stay away from them
Oh, and as for the framerates in 3D - in my experience they're actually slightly higher on average than with my own SuperD port I'm now using as a day-to-day ROM (I miss Sense UI, but 1.5 is starting to lag behind on all the interesting stuff, so...).
Case_ thx for working on this
i could not work becoz my tester was on new radio
i hope u get my hero 2.1 working too
From what I gather, this is a KERNEL modification that makes the HERO drivers work with this "old radio", correct?
Could you please provide the kernel diff (patch)?
ahmgsk: You're welcome. I'm always somehow uneasy as to what the reaction of the original dev would be when I'm using and perhaps modifying someone else's work, so thanks for this
I'll try to follow the progress of most Eclair ROMs but I'm gonna be quite busy for at least the next week or so, so no promises on any other updates or more ports (but I'd LOVE to have a reliable Sense UI ROM with Android 1.6 or higher, I can tell you that - Kinglick's Eclair Hero is close, but still not close enough to rely on it on day-to-day basis). I'm glad I managed to at least steal the weekend for Android for once and got this working, more or less.
lbcoder: Actually, there's really not much to patch. I've spent countless hours trying to port parts of the Kaiser kernel as discussed in one of the G1 forum threads, yet in the end I've ended up using pretty much just the plain vanilla Cyanogen Eclair kernel sources with only the camera code backported from the Donut sources to get the camera working (but I can certainly provide some kind of diff if need be).
Then there's the permission problem with /dev/msm_hw3dc and /dev/msm_hw3dm that on most Eclair ROMs needs fixing (chmod 666 and chmod 660 in init.rc, respectively).
And then it might or might not be an issue with the contents of /system/lib/egl and /system/lib/hw (and perhaps some other libs as well) which, I'm sorry to say, I've yet to fully test. Those from ahmgsk's AME Eclair seem to work, but looks to me like it's not exclusively just those, that it might work with some others as well. I know it's not very professional (but I've said it many times, I'm no dev and certainly no coder, I'm just determined and persistent ), but I honestly didn't have time to test those different libraries fully, sorry. I was just trying to get something as usable as possible and share it with others so they may perhaps investigate further. Though it somehow amazes me that I of all people got it working when there's so many people with coding and Android knowledge WAY beyond my own here (which is not that hard to achieve, anyway)
Case_ said:
ahmgsk: You're welcome. I'm always somehow uneasy as to what the reaction of the original dev would be when I'm using and perhaps modifying someone else's work, so thanks for this
I'll try to follow the progress of most Eclair ROMs but I'm gonna be quite busy for at least the next week or so, so no promises on any other updates or more ports (but I'd LOVE to have a reliable Sense UI ROM with Android 1.6 or higher, I can tell you that - Kinglick's Eclair Hero is close, but still not close enough to rely on it on day-to-day basis). I'm glad I managed to at least steal the weekend for Android for once and got this working, more or less.
Click to expand...
Click to collapse
i hav no problem when u use my rom
its no probs -> but i m glad 32A (old radio) users are getting this. i m working on hero rom i think i can try to get everything working
for now videos and all are working
now some widgets n network is remaining (mostly solved) v2 coming soon
YouTube and video playback in gallery doesn't work at all
Click to expand...
Click to collapse
Why? I remember in the original ahmgsk 's ROM they are working as well...
What has been changed from the old to the new Radio/SPL to break the YouTube/Gallery video playback?
As for the "why?", that's a very good question I'd really like to know the answer to.
As for "what has changed" - the kernel has changed (had to for the ROM to work with the old radio) and with it all the "drivers". I'm not happy that YouTube and video doesn't work, but I don't have much time to investigate further right now. And until now, neither did Eclair 3D acceleration with the old radio, so I guess it's still progress.
I'm sure someone will figure it out eventually.
Added links for 32B/G1 porting package. Yes, 3D really seems to work on those phones as well.
how do I apply the 32B patch?
just replace the files with the once from teh original zip file , repack it, and then apply the new zip?
stefanero313 said:
how do I apply the 32B patch?
just replace the files with the once from teh original zip file , repack it, and then apply the new zip?
Click to expand...
Click to collapse
yeah how do us g1 owners do this thang ...
?????????????????????????????????????????
I guess I figured it out,
download both zip files, apply zip one, then apply the 2nd one other the other.
replacing files wont work because of the files within the "META-INF" folder
Ok,
here is our new release.
Well... Here we are at last! Whole new ROM, whole new thread
For a long time we have been working to build the best possible version of HoneyComb to the Advent Vega. It has been a LONG road, with many hacks and pitfalls along the way. We started with the messiest set of files anyone has ever seen, and we have now progressed to this. Full-fledged, GPU accelerated, NATIVE, Honeycomb 3.2 on the Advent Vega.
There's no going back now. I'm so happy with this ROM that I'm actually going a little crazy with affection. There are still some bugs... Rebooting to CWM causes a stale boot, you have to hold power to turn the tab off, then on next bot you get CWM. Still no camera, bluetooth isn't working. But other than that... Well, I'll let you guys see for yourself.
On the speaker issue, I feel I must put a quick note here... We BELIEVE that the "Overheating speaker" issue is now resolved. Audio levels are now well within the safe limits, and voltages are back at what should be a very safe level. But as always, please be VERY careful, unfortunately we cannot be responsible for any hardware failures resulting from using a custom ROM, but we are very confident that this issue should now be totally resolved.
VegaComb 3.2 Build 9b und 9n Update3 Features:
Update1+2 included
The clock and date issue should now been fixed for all
GPU RAM reduced to 96MB , more RAM for Apps
support for high Wifi channels like 12 + 13
new Honeycomb market
support for the soon coming GPS App included
Downloads, please choose the right Version (original ROM download is at the bottom of this thread!)! (or you Bootloop) :
Update 3 for Build9n: VegaComb_HC3.2_Build9n_update3.zip
Update 3 for Build9b: VegaComb_HC3.2_Build9b_update3.zip
VegaComb 3.2 Build 9b und 9n Update2 Features:
Fix for Bluetooth MAC addressing to hopefully make BT work correctly now.
Above fix should now also make WiFi considerably more stable.
Fix for people who were experiencing issues with the Market not being able to install apps.
Downloads, please choose the right Version (original ROM download is at the bottom of this thread!)! (or you Bootloop) Update 2 can be installed directly over 9n OR 9n-Update1 (it includes all of the Update 1 and Update 2 changes in a single package):
Update 2 for Build9n: VegaComb_HC3.2_Build9n_update2.zip
Update 2 for Build9b: VegaComb_HC3.2_Build9b_update2.zip
VegaComb 3.2 Build 9b und 9n Update1 Features:
Working Deep Standby
Updated camera lib
Re-added App Drivemount
VegaComb 3.2 Build 9b Features:
•Coarse location discovery (based on WiFi connection) is now working correctly.
•Updated camera libraries to the latest version thanks to the development effort by many (including Eduardo and Redscorpion) over at MoDaCo. Google Talk video chat should now be working, as well as the stock Camera app. Other apps have been tested but there is a possibility that not all of them work (please test and let us know!), but we felt that it was more important for Gtalk to work as the camera isn't much use for actually taking pictures
•Added Eduardo's accelerometer patch. This should allow much more responsive accelerometer with no lag.
•Power management for bluetooth/wireless has been fixed. Hopefully this should stop them interfering with eachother when one is disabled.
•Screen calibration functionality built in to the kernel to calibrate on the fly.
•USB on-the-fly host/slave switcher integrated in to the kernel, this should allow switching between USB host/slave on the tablets side USB port without the need to reboot!
•Disabled device suspend when the tablet is connected to an active USB connection, preventing the USB connection from being severed.
•Added a brand new app called: Shuttle Tools which includes the toggles for the above two options. Allowing you to calibrate the screen or switch USB modes from within Android.
• Better language support then 9n, newer Gapps
• No apps are moved to data
• It have a bigger system partition then 9n, so when you have bad nand blocks, this could be work better for you
• When you use the Full Rom Installer you don´t need to flash ModdedstockV2 (Beware when you flash the new full rom it is like the ModdedStockV2 install, you loose all data)
• All future updates after this Full ROM will come as CWM update zip, so that your data are save
VegaComb 3.2 Build 9n Features:
Please be aware that although there was a "version 9" release on some German forums, this update was never integrated into the full build process, and was a side-project by rebel1 to acheive 2 goals. 1) To greatly increase the /system partition size (from 150mb to 200mb) and use that size to add larger apps that have increased language support for non-english speaking users. This build is unrelated to the previous "build 9" and as such has been labelled 9n (new, or newbe5, meaning that it has gone through the usual build and testing processes by myself), an alternate installer based on THIS build will also be provided by rebel1, including the expanded /system partition and enhanced language capability, this alternate build will be labelled 9b (bigger system, alternate build) and will be an nvflash installer rather than a CWM image.
•System image has been shrunk considerably, this should help people who have a lot of random lockups / install issues due to bad NAND blocks. Build 8.1 was using 149.5mb of the allocated 150mb provided by ModdedStockv2, Build 9n is only using 139.8mb allowing much more room to avoid bad blocks if you have them.
•Google Books has been removed entirely. It looks nice, but it's pointless as you can't even access the Store outside of the US. Install this manually if you want it for some reason.
•Google Maps and Street View have been moved in to /data to save space and because they can both be installed/updated from the market, so there is no need for them to be in /system.
•Coarse location discovery (based on WiFi connection) is now working correctly.
•Updated camera libraries to the latest version thanks to the development effort by many (including Eduardo and Redscorpion) over at MoDaCo. Google Talk video chat should now be working, as well as the stock Camera app. Other apps have been tested but there is a possibility that not all of them work (please test and let us know!), but we felt that it was more important for Gtalk to work as the camera isn't much use for actually taking pictures
•Added Eduardo's accelerometer patch. This should allow much more responsive accelerometer with no lag.
•Power management for bluetooth/wireless has been fixed. Hopefully this should stop them interfering with eachother when one is disabled.
•Screen calibration functionality built in to the kernel to calibrate on the fly.
•USB on-the-fly host/slave switcher integrated in to the kernel, this should allow switching between USB host/slave on the tablets side USB port without the need to reboot!
•Disabled device suspend when the tablet is connected to an active USB connection, preventing the USB connection from being severed.
•Added a brand new app called: Shuttle Tools which includes the toggles for the above two options. Allowing you to calibrate the screen or switch USB modes from within Android.
Current issues:
On rebooting to recovery, the tablet will "hang" on a stale boot. Hold down the power button until the screen goes completely off, and then power back on to get to CWM.
More? Probably! You tell us
SO many people have worked on this, and are now part of the team, but everyone who uses and loves VegaComb have the following Droid Soldiers to thank:
Ejtagle
Rebel1 / [email protected]
Corvus
HomerSp
Cass67
a_appleby
BillyBobJoe (Also BillyTheFish I believe?)
stiggy2001
Oh... I might have done some stuff too
Remember, this MUST be flashed over ModdedStock v2 or it will not work!
This is the one and only way to move to our image:
modstock -> data wipe -> vegacomb 3.2.
Dont ask for help if you dont follow this steps.
Download VegaComb_HC3.2_Build9n.zip NOW! This is for all users that comes from an previous build like 8.1 or ModdeStockV2
For users that comes from my Build9 they can download and flash it with CWM recovery Download VegaComb_HC3.2_Build9b.zip HERE!
And the last file:
Download VegaComb HC3.2 9b Installer.zip HERE!
This is a windows installer for the 9b Full ROM, you don´t need to install ModdedStock before, it makes it all for you
We hope you enjoy VegaComb.
If you are feeling very generous and wish to donate to the people who put in a lot of hard work for this ROM, please:
DONATE TO TeamNewCo HERE!
newbe5 and the Team.
Have fun.
rebel1
Great job guys!
I can hardly wait to test this one out!
Very very speed rom..
Thanks
This week, I'm going to receive my Advent Vega. I believe this is the best Honeycomb ROM available (better than Vegacomb 1.7), is it correct?
Thanks!!
wow, loving this as it really does fly, very impressed.
I've just installed it. It really does fly. Just installing my apps now. Will let you know if I come across any problems.
Sent from my GT-I9100 using XDA App
SHWIINNGGGG!!!
Thank you gtablet gods!!!!
I must say i just installed it and its fast!!!
Faster then my gtablet on gtabletcomb 3.3.
OK so you vega gurus. whats the difference between advent vega/viewsonic viewpad 10s and the gtablet.
why can the roms be ingterchanable and whats the difference.
thanks for the roms guys, Now I dont have a reason to sell it.
youtube restarts itself when you rotate the screen.
Apps from market forcloses...
was using opera for a bit with some flash content, went to the home screen and went back to opera and the tablet resetted itself.
what do you mean by "Native App2SD has been added back in (is not present on 3.2 ROMS as standard)."
Does that mean we dont have to get the app2sd app?
I looked for the app2sd in the settings and is unable to find it.
can you please explain..??
I love it, thanks for your hard work.
awesome build
much much better than beta 1.7
thank you so much for that.
just one question, compare to 1.7, all icons look too big.
different resolution or different density?
I don't think we can change the resolution.
Thanks.
Edit: I use LCD density to make the icons smaller, got wifi error, after uninstall lcd density and reboot, no error.
aarrggg... I'm at work and can't get this till I get home.
5pm can't come quick enough now
Been playing with this since yesterday evening.
You can change the screen Res in your build.prop file. I'm on 140dpi at the moment, many people seem happy with 127
USB host mode doesn't work yet, hopefully not too far away
Everything is really fast. No lag at all. There are a few little oddities here and there but nothing too drastic. An amazing release really.
HDMI out is working? My TV didn't recognize it. Pretty fast. I set the density to 140. Looks better now. Thanks.
Sent from my VegaComb 3.2 using XDA Premium App
cant get to recovery, tried everything, holding powerbutton while reboot, nothing helps, it just reboots...
freddje said:
cant get to recovery, tried everything, holding powerbutton while reboot, nothing helps, it just reboots...
Click to expand...
Click to collapse
You need to hold power button until you see the power down menu, select recovery then it'll hang on reboot, hold the power then until the tablet is forced off and when you power back up, it'll boot into cwm recovery
could someone with an official dock please try and see if they can still connect usb peripherals on this rom, I know you can't directly until they fix it, but was wondering if it still worked via the dock. If so i'll buy one
thanks,
malty
Hi there.
I have been running this for a few hours, i have got to say, its fantastic. So quick and smooth. I think i will be running vegacomb from now on.
Just curious about the keyboard, it seems very small. Is that the stock one for 3.2? No major problem just installed hackers keyboard.
Still not sure about the pixel density, but i can easy change that.
Love the first boot screen, should make it more difficult to bang out a vegacomb clone on ebay
Any tips on getting the accelerometer working properly with games?
Many thanks to you and TeamNewCo, this is a fantastic ROM
Legendary. This rom is awesome.
DO NOT POST IN THIS THREAD UNTIL YOU HAVE COMPLETELY READ THIS POST AND THE FAQ.
Since jt1134 is no longer supporting his CM9 releases here on XDA and asking people to go elsewhere for support, I have decided to start building CM9 for the Infuse.
Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working. Even more goes to LinuxBozo - without his CM7 work we would be nowhere.
http://d-h.st/vN1 - 06/20/2012 build
http://d-h.st/ahW - 06/27/2012 build
http://d-h.st/Pfr - 07/28/2012 build
Installation instructions-from a Gingerbread firmware with "red CWM":
Place this release and an ICS gapps release on your SD card.
Flash this ZIP in CWM
Reboot - you will get stuck at the Samsung screen
Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
Go to Mounts and Storage and format: system, data, cache
Flash this ZIP a second time, then flash gapps
Reboot and enjoy
Coming from any AOSP-based firmware with "blue CWM":
Flash this, flash gapps, wipe. That should be all you need.
What is working:
Calls
GPS
Sound
Video playback
What is partially working:
Camera (minor flakiness, but mostly working)
Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
Wifi - It frequently loses connection when the device is asleep. Most likely needs some SDHCI driver tweaks to match the N7000 wifi driver.
Wifi Direct - A little glitchy but mostly working with I777/N7000. Won't talk to a P7510 (Tab 10.1) though.
Bluetooth - A2DP (music) and SCO (call audio) now works. However BT power management (LPM) is currently disabled, so BT may eat your battery when on.
Not working:
TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.
Known issues:
SetCPU seems to be unable to set the minimum frequency to 100 MHz. This is one of the main reasons for holding off on OC - even stock clock code isn't working quite right
Facebook contact sync has been blocked by Google in ICS - this is universal to ICS on all devices I'm aware of. Facebook got what they deserved here.
Building - Use the Source, Luke
Kernel source is at: https://github.com/teamhacksung/android_kernel_samsung_dempsey
Device repo at: https://github.com/teamhacksung/android_device_samsung_infuse4g
To build, first prep your system for a Cyanogenmod build by following the instructions at:
http://wiki.cyanogenmod.com/wiki/Building_from_source
Once you have done the first "repo sync", at the two following lines to .repo/local_manifest.xml
Code:
<project path="device/samsung/infuse4g" name="teamhacksung/android_device_samsung_infuse4g" remote="github"/>
<project path="kernel/samsung/dempsey" name="teamhacksung/android_kernel_samsung_dempsey" remote="github" />
Run "repo sync" again
Sync https://github.com/TheMuppets/proprietary_vendor_samsung/ into vendor/samsung
Drop the contents of the attached tarball into vendor/samsung
(I really need to clean that process up...)
Run:
Code:
. build/envsetup.sh && brunch infuse4g
FAQ
Q: I get weird rainbows in recovery and when my device boots? What gives?
A: This is what happens when a Gingerbread or ICS kernel is booted on a device with Froyo bootloaders. You will need to either live with the rainbows (recovery is at least partially usable with the rainbows now) or flash Gingerbread bootloaders. Stay tuned for more info on bootloader flashing.
Unfortunately, the classic "rainbow fix" we used for Gingerbread is not compatible with how video acceleration is set up in ICS. The rainbowfix will just cause the device to crash immediately on boot. (I think this is why jt was not successful with LinuxBozo's CM7 source.)
Q: I'm getting rainbows, how do I flash Gingerbread bootloaders?
Flash the bootloaders from the file attached to this post using Heimdall as follows:
Code:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
DO NOT do this unless you are experiencing rainbows, and DO NOT do this until you have confirmed you can flash less dangerous stuff (like kernels) with Heimdall. If the flash fails you will hardbrick!
Thanks to LinuxBozo for confirming, way back in the days of UCKJ2, that Heimdall can safely flash bootloaders from leaks. http://forum.xda-developers.com/showthread.php?p=18539754#post18539754 - Be warned, once you do this step there is no going back. For whatever reason the Infuse won't flash dumped bootloaders, so there is no known way to return to Froyo and Rogers Gingerbread bootloaders.
Change Log
7/28/2012:
Removed 1000 MHz cpufreq step - the extra frequency step was causing all sorts of weird derpage.
Fixed 1200 MHz step (it was using the wrong PLL settings)
Moved to open source sensor HAL
7/22/2012:
Major improvements to camera flash functionality - torch is still broken but most other flash functions work
EXIF info (including rotation) is now saved. However I had to disable JPEG thumbnail generation, which slows down viewing of images in gallery
Structural changes to the repos to make things cleaner - Once two patches get merged by CM I plan on submitting Infuse for official nightlies
CPU clock handling for GPU bus frequency was changed from a policy change (min freq bumped to 200 MHz in policy, which would cause some apps to "stick" the min at 200) to a DVFS lock. Min no longer bumps up to 200 - however any time the GPU is active it'll still lock to 200 MHz.
6/27/2012:
Discovered our device has a Broadcom BT chipset - the CG2900 is NOT used for Bluetooth. BT is now fully functional other than possible power management issues
6/20/2012:
Various upstream stuff
Wifi Direct support added - partially glitchy (see OP)
Bluetooth support brought up to CM7 levels (Audio stuff is still broken)
5/27/2012:
New wifi driver from GT-N7000 Update3 source drop: Hopefully will improve wifi for those with issues
New LPM (charging while off) code from I9100
All upstream changes since last build, including lockscreen weather
5/19/2012:
Lots of upstream CM9 changes, including theme engine and customizable lockscreen
Settings->Advanced now works. mDNIE settings (tested) and HSPA+ control (untested)
A small patch that might help wifi driver loading issues, but not guaranteed (gokhanmoral reverted it within a day in his case...)
5/2/2012:
Pulled in a few wifi fixes from gokhanmoral's I9100 SiyahKernel tree. May help those who are having wifi issues.
4/23:
Fixed wifi MAC address getting set randomly on every boot
4/22:
Misc stuff from CM9 upstream
New wifi driver backported from the I9100 update4 sources and pershoot's Tab 10.1 kernel - Fixes wifi tethering!
USB tethering removed until I can make the RNDIS driver play with the new net/wireless code - not even sure if it was working to begin with.
4/19:
No more banding in recovery (thank codeworkx for this one, exact same fix as for I9100)
FFC is no longer cropped to one corner of the sensor. Full resolution support for FFC still not implemented
Various upstream changes
Very nice any idea on how to get mtd to work? Also would that improve speed ? Thx
Sent from my SGH-I997 using xda premium
Thanks for taking this on for all of us here in the xda community.
Sent from my MB865 using xda premium
The_Zodiac said:
Very nice any idea on how to get mtd to work? Also would that improve speed ? Thx
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I believe that was primarily used to eliminate the need for Samsung's proprietary RFS/FSR modules.
It doesn't carry a speed benefit, but it's beneficial in the long run for kernel developers.
Current differences between my build and jt's last:
1) I haven't put AriesParts in yet - half of the features don't work
2) Overclock is not in yet - The overclock code from netarchy/LB is ancient and needs to be reworked. Voltage control is in there though
3) Car dock audio redirection is working, using a built-in CM9 approach instead of a separate dock audio redirector app. I had to make some changes in libaudio of aries-common to fix this. Probably some more work needs to be done here - ringtones when docked are iffy.
Great work... blindly flashing now based on developer name.
Sounds great.. I just got jt1134's build 2 installed and working..
Looking forward to seeing what you put together for us. Always great stuff coming from you!!
Entropy512 said:
Since jt1134 is no longer supporting his CM9 releases here, I have decided to start building CM9 for the Infuse.
Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working.
http://d-h.st/x53 - 4/15/2012 build
Installation instructions-from a Gingerbread firmware with "red CWM":
Place this release and an ICS gapps release on your SD card.
Flash this ZIP in CWM
Reboot - you will get stuck at the Samsung screen
Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
Go to Mounts and Storage and format: system, data, cache
Flash this ZIP a second time, then flash gapps
Reboot and enjoy
What is working:
Calls
GPS
Wifi
Sound
Camera
Video playback
What is partially working:
Camera (front camera is zoomed in excessively)
Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
Not working:
Wifi tethering - We need far more than the HIDDEN_SSID fix CM7 required unfortunately
Bluetooth - Not working at all, not even to CM7 levels
TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.
Click to expand...
Click to collapse
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Thanks for this! Did you fix/attempt to fix the problem with music coming out of the speaker when you get a notification with headphones plugged in? That's the only thing keeping me from loving ICS, since it's preventing me from listening to music at work.
kirin0ichiban said:
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Click to expand...
Click to collapse
I don't know what he's doing... All I know is he released his first build here but refuses to post any subsequent builds here, even though this is where all other Infuse development occurs. It's unreasonable to ask users to go to another forum just for ONE firmware, especially a forum with broken CSS stylesheets and a horrifically immature/irresponsible userbase. jt1134, imnuts, and Ezekeel are the only RW fans I've met that weren't complete douchebags and had technical skills to back up their bravado. Others think it's "kewl" to tell users to flash bootloaders all the time and then laugh at them if they hardbrick.
Frooty said:
Thanks for this! Did you fix/attempt to fix the problem with music coming out of the speaker when you get a notification with headphones plugged in? That's the only thing keeping me from loving ICS, since it's preventing me from listening to music at work.
Click to expand...
Click to collapse
Not yet... I'm just starting to mess with libaudio.
Awesome finally in the Dev section thanks Entropy!
Sent from my SGH-I997 using xda premium
kirin0ichiban said:
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Click to expand...
Click to collapse
1st must you quote the entire op?
Yes and no...yes jt is still building...no he is not posting on XDA...jt prefer the rootzwiki site that's where he is posting....
Check or Hold??
Entropy512 said:
I don't know what he's doing... All I know is he released his first build here but refuses to post any subsequent builds here, even though this is where all other Infuse development occurs. It's unreasonable to ask users to go to another forum just for ONE firmware, especially a forum with broken CSS stylesheets and a horrifically immature/irresponsible userbase. jt1134, imnuts, and Ezekeel are the only RW fans I've met that weren't complete douchebags and had technical skills to back up their bravado. Others think it's "kewl" to tell users to flash bootloaders all the time and then laugh at them if they hardbrick.
Not yet... I'm just starting to mess with libaudio.
Click to expand...
Click to collapse
Alright, well thanks for the quick reply. I didn't/don't know whats going on either. I'll just continue to monitor both threads and eventually things will become clearer on what he's doing. Great work on the ROM by the way! Keep it up.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
bigjoe2675 said:
1st must you quote the entire op?
Yes and no...yes jt is still building...no he is not posting on XDA...jt prefer the rootzwiki site that's where he is posting....
Check or Hold??
Click to expand...
Click to collapse
Obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
He and I clearly also have differing opinions on how to go forward. My opinion - fix what's broke until you hit something insurmountable (like fully working Bluetooth on CM7).
Then add shiny destabilizing features like overclocking...
kirin0ichiban said:
Alright, well thanks for the quick reply. I didn't/don't know whats going on either. I'll just continue to monitor both threads and eventually things will become clearer on what he's doing. Great work on the ROM by the way! Keep it up.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
Obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
Click to expand...
Click to collapse
No need to be rude to mister Joe he was only trying to help!
I'm glad its finally on XDA makes it easier to know when an update is since I only check this site
Sent from my SGH-I997 using xda premium
kirin0ichiban said:
obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
Click to expand...
Click to collapse
Actually you didn't but YW for clearing up your confusions....
Runs beautifully as advertised!
I spoke with Entropy.. I would like everyone to take note:
Your phone is lying to you when it says you are on H+ all the time. That would kill your battery. It will jump to H and 3G all the time. CM9 does not display H+, only H.
I found Alarm Free (HD) does the same thing as Touchwiz Clock (Alarm, Stopwatch, and Countdown). I rely on Touchwiz clock at work for testing devices times and at home for timing punishments and waking up in the morning... I felt this was important to mention.
Q&A for [p6800](18/Nov/2014)CyanogenMod 12.0 (Android 5.0) experimental
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [p6800](18/Nov/2014)CyanogenMod 12.0 (Android 5.0) experimental. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hey Daniel, any solution to fix 3g on p6800 lollipop? Thanks
---------- Post added at 07:55 AM ---------- Previous post was at 07:19 AM ----------
Hey,Daniel,any solution to fix 3g on p6800 lollipop?Thanks
I need 10post to be able to post in Development board
Looking for fawrd to this build,
need at least mobile data, i will try it out...
had been follow since 4.3 till now..
Dear Daniel
Thanks for your developments. Will try it and revert for any comments.
Anthony
Daniel
Why cannot play youtube video in the apps. just only black blank screen, can you please to fix it?
Thanks for your great work
Anthony
HAPPYFATHER said:
Daniel
Why cannot play youtube video in the apps. just only black blank screen, can you please to fix it?
Thanks for your great work
Anthony
Click to expand...
Click to collapse
As far as know it a known problem in cm at the moment it has to do with the hw decoders.
Sent from my Xperia Z1
Method to achieve root
Got ideas how to achieve root? KitKat method or any specified methods?
Amazing work, Daniel. Thanks so much for your effort.
My impressions on this release: battery life is AMAZING, a lot better than official firmware; I am unable to play any kind of video, Youtube included, that´s the only thing that is really bothering me since I use chromecast to watch movies from it; Incredibly fast and responsive; some screen tearing when browsing the web (using Chrome); I don´t know if it is just my imagination but the color scheme seems to be a little "off", contrast is a bit down; some reboots here and there, it doesn´t seem to have a specific reason.
Well, that´s it. Thanks again for all your work!
cm 12
Its super awesome we are seeing lollipop on gt6810 all though there were some fixes need for video decoding and others. I did try it out but all the roms I've tried don't quiet give me the simple stable experience paranoid 3.68 gives me especially with camera flash everytime its opened for new pictures to be taken and browser distortions which is hardly experienced in pa3.68. Looking at the paranoid rom, do you think lollipop could use abit of the old experince of paranoid just incase the new updates coming out of lollipop pose abit too much of difficulty?... I really would love to see this awesome lollipop interface you've given us a chance to experience on a paranoid kind of feel...u know... Also, compared to how light paranoid is, the kitkat and others seem to perform under alot of pressure. My tab practically gets really warm when watching a video on low screen light and a minimized volume. These things are scaring the crap out of me so I've reverted back to paranoid. Would love to have a positive feedback, hopefully... Once again, Thank you for the work you've done so far.. You're aweSome!
---------- Post added at 05:38 PM ---------- Previous post was at 05:32 PM ----------
My laptop got stolen recently.. Really wanted to tinker with this new build. now I have to do that directly from my tab somehow...really depressing and stressful but all goes well, hoping for a better future with cm 12.. :cyclops:
I Need Multi-User Support
Thank you Daniel. I love it!
I hope that the multi-user support will be added in the next build. Your efforts are greatly appreciated.
Happy New Year!
test results for 5/1
very usable but not too stable,random crashes,auto restart,freezing
apps start fast but then lag a little
over all almost can be used as daily drive other than lag and random random crash and reboot
miss xposed and themes engine,lollipop has an annoying green-white theme ,yuck
Some issues with 10th Jan build
Hey Daniel,
Firstly, thanks a ton for your hard work. I check this forum on daily basis to check out new builds if any. I really love your work. I am still using my 3 year old tab just because of you.
I have installed the the 10th Jan build. There is one major issue I want to report. When I leave the tablet on for sometime untouched on charging or anything. I come back and try to use it at the moment the screen never switches on. I have to push the power button and hard restart the device again.
It seems to be dying out after going into deep sleep and need to be restarted to start using again.
If I am missing some solution for this please let me know so i can fix this. Otherwise this new build and new kernel is awesome. Even the speed of device has tremendously improved.
Ravi
reboot into recovery
hi
I installed this cyanogen rom on my P6800 , but in "Rom Manager" app i couldn't Reboot to Recovery.
when i press "Reboot to Recovery" my tab doesn't reboot!!!!!!!
Great Rom
This ROM is by far better than kitkat on many ways...and its much more stable... So far everything works perfectly...the only small thing is, I think lollipop is abit too heavy on the tab 7.7. Cm 12, I'm really enjoying the feel... Thanks Dan.
So how can lollipop feel lighter but with the same features? In terms of its memory management, speed at which it can process one or more things at a time and considering where tab 7.7 is coming from, it doesn't seem all that simple...
Also, you we could tell you if there were any problems.. No distortion or anything but there are minor flickers which kinda scares me..I hope its nothing. The flashlight function don't work. Any gapps higher than the micro version, I get this error "insufficient internal storage-aborting installation'. I use the latest TWRP.
Is it possible to get a camera app with photosphere? I really love that function in a camera..
Everything else works just fine...WiFi works better on da kk versions and much better on da lollipop (cm12). Like I said from the beginning, seems the lollipop weighs the tabs overall performance down a lot.. I couldn't find anything in the root folder that helped so maybe you could teach me a thing or two about that area on android lollipop...
I have a tab gtp6810
Thanks
And o, the previous ROMs that some people complained about the charging running down the battery instead while plugged in and running at least one app like the browser... I did a power supply reset in the terminal... I don't know if worked but I'll give a feedback here if I see any improvements for everyone using any of Dan HK ROMs...
fifth try
Well, I only installed the cm12 without gapp.. I'm going to fix in the apps I want from the gapp... So far, running abit smoother than with gapp install along cm12 together... For the torch, I'm going to take the one from cm11 and try make it a system app.. Also, the camera...the flash only works when every time you open anew and take the first picture or select through the flash settings.. Just like all the previous ROMs from carbon to slimkat... Only PAC and paranoid 4.2.2 are the last that works the way you would want..but graphical interface ain't as good as this..hehe
---------- Post added at 09:10 PM ---------- Previous post was at 08:57 PM ----------
The dalvik heap size allocations...do they work through the system's available storage, ram or some separate caches space separated? I sort of change those area abut..there was abit of change around the graphic performance and processor...couldn't really tell but it felt abit different... Will those sort of changes affect anything negatively as well somewhere in the custom firmware? I want to be careful I'm not doing anything wrong...
runs good
I think it run better without gapp....only difference is, you won't have all the Google service interface eating away your battery and stuffs power related.. Also, recent app button, the apps take abit more time for the close sign to appear... Its basic issues still remain like the missing torch function But in all, it works very good.. U think this new cm 12 could actually become an OS on it own? I've been going round the web seeing as how Aroma installer are popularly used with different cool installer interfaces... Cm12 so far ROCKS!
For those having battery charging problems, get the stock recovery (it worked for me) and flash in the pit file for ur device as well, seems to help somehow...you can try sbl bin but I mean, its just an idea... I lost my laptop so I can't manage going back and forth from friends houses all the time...
few cm12
Bluetooth..pair and connects with some av control. Didn't realize the tab was my PC now. Sending files..-"no bluetooth device found" (while paired or with the extra a/v connection).
Tab turned off, trying to charge under twrp 2.8.2.1, "battery draw jpg cannot load" or sth like that. Not sure what that means but a white one shows charging after the error.
Mobile Odin can't see nor access external SD.
On first install, Google search appears after turning off in launcher settings, open recent apps tab (show up here insteadv big and white), go back and turn on in setting,"heeeyyy, you're here!! Welcome back to my screen..lol".. So its not ICS version I see on the home screen.
Live paper on, turned on Bluetooth first time and device restarts. Surfing over 5 tabs on browser at the same time, restarts. Also, using an app like torrent to download one file while watching a movie (tab get very warm & freezes completely and unresponsive till I keep on power button till it restarts the device)
But I'm only testing all this with a fresh installation and gapp 5 beta 12 nano. I haven't changed any settings at all. Just want to help out with more feedbacks on overall performance.
Most responses to apps opening and closing can be slow in moments where about at least three or four apps have been opened.. So I have to manage an app at a time while clearing my recent apps. And surface a page or two unless with a different browser like UC browser, its okay.
Colors, everything feels cool. Flashed lollipop font and system sounds (don't remember where I got them but I'm sure it was on xda). It sort of felt like I was using the kitkat version that's why I changed them. Runs and feels abit better than my first time install cm12.
I don't know if there are any memory forced to leak but maybe you could hover around to see if something's is abit off about it from what I've said so far.
So between recovery and custom ROM, seems there's some unstable thing going on from within their interactions... I don't know, maybe recovery also needs an update....I guess...?... Well, you're the expert so these are my user experiences so far... Will let you know if anything else comes up
This new lollipop really is different. I can't even tell in the lib files are supposed to be in the apps or lib folder or both when trying out an app like the latest Google camera. I've tried but I only get as far as paranoma and it stops working at photosphere. Sometimes it opens but da circle has no use when the pictures are supposed to be taken. Read from file to file, I must say...I have never been this lost in android...hahahahaha
updating on cm12 issues that could help, hopefully
Lollipop looks light but feels heavy on performance i think cos of how much memory it over-uses.. Maybe its the kernels or sth so I'll wait for what Daniel will help us with to understand more (thank you again Daniel. U're awesome!)
What I noticed today was, when the memories goes to its limits in usage is some areas I think, the tab glitches, slows down abit and restarts if anything else opens... I was only watching a movie series (homeland TV series) from my 32GB SD card, and downloading a ROM from media fire with all my apps closed but the system running. No other recent tabs were opened.. Before I continue, I limited the memory use so between 5mb to 256mb does seem enough unless u r da type that multitasks a lot more (but that should not the case, right?...weird tho). I did this cos when I increased it, with a bit extra apps (about 1 or 2 etrxa apps running), its kept either freezing badly or restarting. So I just had to test this to see if its me or this new OS is going to be hard to work with...
Secondly...I use MX player a lot... Sometimes hardware works but when switched to software decoding and back to hardware, suddenly hardware is not supported unless I close the current video or app itself and start again. But will still fail at hardware decoding and sometimes restarts unexpectedly during software decoding.. Too much info?...haha... Naaah.. Lol
JESUS! The cursor is abit difficult to move around with a huge finger that covers it completely...lol
In case you are wondering,"where did this guy come from"...I assure u, I have been a fan of xda for about a year or two maybe or more cos I remember using my first tab its been almost or over two years. I only recently joined cos android has fascinated me in many ways and by having alot of great customization options and being an open source if I may add... I'm happy old devices get to meet the challenges that people have doubts on.. I'm grateful that I still use some of my old devices with a lot of confidence...
---------- Post added at 01:57 PM ---------- Previous post was at 01:41 PM ----------
saeghe3000 said:
hi
I installed this cyanogen rom on my P6800 , but in "Rom Manager" app i couldn't Reboot to Recovery.
when i press "Reboot to Recovery" my tab doesn't reboot!!!!!!!
Click to expand...
Click to collapse
Really? How did you install it? And did you do a factory reset after install ROM or clearing cache and dalvik cache? Have u tried a long press on the power button to shutdown first?
As for ROM manager, I can't say for sure I can help u with that but I also noticed some things like mobile odin don't fully run all its functions on my tab p6810 with the p6800 kernal I found for mobile Odin to work o my tab.. I can't see the external SD unless i copy da file I want to use to the internal storage... So cm12 is still a working progress I guess.. Refer to the original cm12 post...Daniel said sth about the we probably will have to end up with our own new custom kernel to use I think due some out dated resources...For now, if no options works for u... If u know how to open the tab gently to take out the battery's connection and back in to enable u go into recovery to do a back up just in case... The u can sort out the ROM properly...and only if ur tab doesn't allow u to shut it down manually... At ur own risk..u can watch YouTube videos on how to handle ur tab p6800 with care when opening..
I've used twrp recovery and cwm recovery (which cwm needs to be rooted before flashing ROM), they all worked well for me so far.. A feww issues I've already pointed out but could be sorted eventually..
I searched da web for info and made a few changes to my build prop. Would share with u if interested...but remember, I'm only using the WiFi version of ur tab..
---------- Post added at 02:20 PM ---------- Previous post was at 01:57 PM ----------
I think the last cwm recovery works abit better (if in case u have charging charging issues and don't want to use the original stock recovery).. U flash that and root ur device through the recovery, restart recovery to root or fix root then install cm12 with mini or nano gapps 5.0. Battery draw is missing in ROM but don't worry, it will still charge.
I want to share my super su which I flashed to root the device but I can't get the upload button to pop up any window to find the file on my tab in the system's browser on the cm12. Well, all the same...Good luck!
I wonder if this is what they call a memory leak...
Three words...poor memory management... For an old device, lollipop settings over use tab hardware resources..though its performance is better in terms of gaming.
OK...I said I made a few changes to my build.prop...well, here they are:
#
ro.sf.lcd_density=180
ro.HOME_APP_ADJ=1
#
wifi.supplicant_scan_interval=84
dalvik.vm.heapstartsize=7m
dalvik.vm.heapgrowthlimit=49m
dalvik.vm.heapsize=294m
dalvik.vm.heaptargetutilization=0.72
dalvik.vm.heapminfree=788k
dalvik.vm.heapmaxfree=7m
dalvik.vm.lockprof.threshold=600
These are lines I made changes to (p6810)
******
I'm using nova launcher as system launcher
Flash some L fonts and sound I found on YouTube
And boot animation
Just to try get it to feel like lollipop as much as possible..
I notice a white line that flickers between long minutes like about 45mins during a movie playing on my MX player.. It also happens during charging the device when running twrp I guess...i see that on my lockscreen when on landscape mode...don't really know what that means...but I take out the charger for some time and plug it back and it stops for a long while but I switched to cwm.. Da MX player thing still shows though..
I removed that performance tweak app... Can't risk overheating...sorryyyy...I get scared a lot when I know my device hardware has its limits and way of coding to the responsiveness to whatever android versions out there....and I guess it all depends on the hardware make or build period and its sources..
Well, catch ya'll later... Still waiting for kernel and/or some ideas...
Cm file manager don't do much aside from viewing files and folder or install apps..
I tried material manager pro...that too crashes when I try to select everything at once in a folder...have no clue what that means either but will make time for the apps later.. Right now, cm12 needs a good workout till I feel its stable enough for extra updates from Daniel and others who enjoy helping g out....
PEACE!!
tasty lollipop
arrrghhhh! Wish I had an 'F5' button on my Google keyboard!!!
Just messing around..lol... But seriously though, you use it for abit with different apps running and closed...then remove all recent tabs...restart, you have most apps you opened which a lot are related to Google running as background processes......mmmmm....didn't realize the system takes me abit too seriously...Haha
So now, I have 'ccleaner' and 'the cleaner' installed. Ccleaner runs... 561.6mb ram of 770.97mb used. Okaaaay..........analyze....clean processes, empty folders, cache....no changes to memory.....awkward...lol..
Now, 'the cleaner' app- analyze, 197mb or sth to be recovered...nice! - 'clean'.......384.84mb in use...shows in ccleaner....wow!
This is.....sth......
Ok so, system bootup........Google+ and YouTube are background processes.... Sometimes 'music' pops up....weird....I.....don't think I'm ready to dance just yet... But after a while they get tired and leave, leaving YouTube behind.......maybe it wants me to watch xda videos....... Ok, so Google app pops up when I've l've literary stopped all its functions... I haven't force closed it, no no no...well....not yet but I will....
I once saw Google service and Google play service pop up...are they related?
Also, I would like to make guess or assumption; I think it takes abit longer to load everything compared to previous ROMs... Even when its already booted to home screen..
Ok, so some was last night's observations.. I think this gapp is going to make me saaad.
Will use only cm12 without gapp and run the Google apps manually instead to avoid multiple background processes at once...gms core.....interesting and can be quiet a strain...o well.....laterrrrrrr
Disclaimer (partially borrowed from MIT license) - WARNING:
THIS SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND. If you loose your data, brick your device, any other damage or anything else happens (e.g. your cat eats your dog), it is YOUR PROBLEM and YOUR RESPONSIBILITY. Your device warranty is most probably void after installing this.
To avoid any confusion let me explain my position. I still have a felling that some people don’t understand this. I didn’t create this, I only fixed some problems (mostly closely related to i9305 device) and built it. It is a big difference, similar to buying versus building a house. Buying a house is not a simple thing (at least in my country) and you’d probably need to do some changes and repairs before you can start living in it. But building a house is something completely different and much more difficult. The work I’ve done on these CM builds is more like buying a house. The see the list of people who "built the house" go into Settings on your phone, section About phone and then Contributors. It is a really long list. Thanks to all of them
Also, please, keep in mind, that I am only sharing results of my hobby.
Now, please, proceed to the this post for the build (I’ll probably change this to more traditional OP after the code stabilizes, but now I’d like to keep track of history, instead permanent rewriting the OP.)
Thanks @nels83 for several commits.
Sometimes it takes me a while to publish new build. But there are also other builds from @mad89 - https://drive.google.com/open?id=0B_ohj9exsQJMSU84MGxkbFdnYUk
OK, so here is the first taste (which I know about) of CM 14 (Android 7 Nougat) for Samsung Galaxy S3 LTE - i9305. Before You even think about installing it on your device, please, keep in mind the warning from OP. Consider the build experimental - AFAIK CM 14 has not been even officially released yet. Be prepared to restore your current system. You have been warned and you can download here:
cm-14.0-20160930-UNOFFICIAL-i9305.zip
Please expect bugs.
Basically all hw is working (I didn’t do any thorough testing, I’ve just checked the basic functionality):
- RIL - data (2G, 3G, LTE), in/out calls, I didn’t check SMS
- wifi
- bluetooth
- GPS (with one minor glitch - see notes bellow)
- camera (I can take photos, but there is some problem with video recording) and flash light
- probably all the sensors (accelerometer, magnetic field, orientation, pressure, light, proximity, etc.) I haven’t checked them one by one, but also haven’t noticed any sensor functionality missing
- NFC
Notes, problems, etc.
- mobile data probably won’t work after first boot, reboot fixes it
- as mentioned above, there is one GPS glitch - I can get the fix, no problem with that, but the list of satellites (e.g. in SatStat) contains sometimes SBAS satellites. This is probably some software error (there is quite big change in gps code) or I’ve found hidden hw functionality (I don’t think so, I am not sure if I can even receive signal from these satellites in my area).
- I can’t access developer setting menu
- there was a bug in the camera code, which was also in cm 13. This bug caused crashes when the preview started, I don’t understand how the camera can work in cm13...
- the recovery image is too big to fit into recovery partition
- selinux is permissive
- I’ve finally fixed the annoying bug in kernel, which caused kernel panic (and phone reboot) when there was missing camera firmware. Beside thisi, the firmware is now loaded from system partition
- there are probably many other bugs, the development is still in progress
Code changes:
All the code changes I did to make this work are in attached diff file (code.diff) and this repo. Many of them are quick & dirty fixes (just to make it work). I am planing to do it properly and upload on github. There is also attached roomservice.xml, which I*used and list of commits and some screenshots.
reserved
OMG WHAT RIL WORKS
YOU ARE A LEGEND
i'll help to test in 2 weeks time, exams now. Just ended school and its 9pm whew
(even i9300 hasn't gotten it yet)
btw1: why isnt your thread xda:db yet
btw2: since a kernel takes 6 minutes to build i'm making one right now just for fun to see if it works. will upload later lol. at the same time start backing up stuff slowly.
https://www.androidfilehost.com/?fid=457095661767098439
for those who are already testing this rom to try. I have not tested it myself, please back up system beforehand.
Hey, so good to see you here with such good news about your CM14 alpha. Keep up the good work and thanks a lot to spend your free time with this hobby.
When I'll have free time, be sure I'll test your builds and report.
Awesome. Never expect to keep this phone this long when I bought it 2012 and now 7.0 :laugh:
RIL works before i9300... This must be magic, the least buggy build you can publicly get for the i9300 is a build where nothing works, not even WiFi, but here RIL works too, and WiFi, amazing work :good:
What is this sorcery? How in GOD's name did you achieve this feat? My internet was down for ~30 minutes and this is what I see first thing. HOW? I swear I will have to donate some money to you @p.a.n because reasons. If you can PM me some info as to how i can donate some money, I'll be more than willing to.
Hi everyone,
thanks for the support (@西村大一 thanks for offering the donation, I appreciate it, but I`d like to keep money out of this).
There is no magic involved, Just good old plain debugging and RIL wasn`t the most difficult one. The fix for camera, even if it looks simple, was more difficult. I was overlooking the solution for long time, maybe because the code works in cm13 (this I consider magic).
@limjh16 what do you expect from building the kernel? There some important fixes there, but it doesn`t make much sense without the rest.
Maybe some of my fixes may help i9300 porting. It would make sense (e.g. I suppose the kernel version is at least similar, so finit_module syscall has to be changed back to init_module).
Thanks Pan for your work! I will try it. ?
Sent from my SM-G920F using XDA-Developers mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Hi Pan wich version of Opengaps should I install? The 7.0 android version?
Thanks
Sent from my SM-G920F using XDA-Developers mobile app
p.a.n said:
Hi everyone,
thanks for the support (@西村大一 thanks for offering the donation, I appreciate it, but I`d like to keep money out of this).
There is no magic involved, Just good old plain debugging and RIL wasn`t the most difficult one. The fix for camera, even if it looks simple, was more difficult. I was overlooking the solution for long time, maybe because the code works in cm13 (this I consider magic).
@limjh16 what do you expect from building the kernel? There some important fixes there, but it doesn`t make much sense without the rest.
Maybe some of my fixes may help i9300 porting. It would make sense (e.g. I suppose the kernel version is at least similar, so finit_module syscall has to be changed back to init_module).
Click to expand...
Click to collapse
Okay, I respect your decision. One bug to report is external SD card. It doesn't get mounted in fstab, but it gets detected as dev/block/platforms3c-sdhci.2 (if that is the sdcard) without any problems. I'll look into the fstab and add some mount point for sdcard and see if i can make it to work.
Dev settings menu is multiple tap on build number and works without any issue, WiFi works, RIL works, haven't tested the camera, calls work, everything is fine and dandy. Once the SDcard problem is fixed, it is good for daily driving needs.
The GPS 'Glitch' you talk about is not a glitch per say. It is supposed to help with GPS somehow (see this wikipedia article to feed your brain information). And as a little tip, after the first boot, just reboot once to get 3G/LTE/Whatever if you're not near WiFi. Smooth runner, daily driver candidate.
mop09737 said:
Thanks Pan for your work! I will try it.
Sent from my SM-G920F using XDA-Developers mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Hi Pan wich version of Opengaps should I install? The 7.0 android version?
Thanks
Sent from my SM-G920F using XDA-Developers mobile app
Click to expand...
Click to collapse
7.0 ARM yes, Pico or Nano are recommended
Very nice work p.a.n. It's already mostly working and very smooth.
Yeah i can confirm, external SD card is not avialable in system. I found another one too, com.android.phone process is crashing when entering dialer/settings/ call settings/call barring.
Pardon my nebulous language without logcats but I noticed one thing about that camera crashes. For me, it's often happening when i try to launch app with camera access and there is another one(or more) in recents menu which had accessed camera. Clearing all apps in recents can bring back access to camera but sometimes only reboot can help, hard to reproduce exactly same scenario. Fast opening and switching beetween diffrent apps with access to camera preview (eg cm cam, googlecam, camerazoom, instagram, fb messanger) can quicly cause these crashes too. Maybe there is some kind of dependency/lock / timming or ram management issue which causes that. Thanks again for great work.
I confirm SD card is mor available. SMS is working, GPS also.
Is not possible to setup weather source for clock widget.
Is not possible to change battery icon
Thanks.
Sent from my GT-I9305 using XDA-Developers mobile app
p.a.n said:
@limjh16 what do you expect from building the kernel? There some important fixes there, but it doesn`t make much sense without the rest.
Click to expand...
Click to collapse
Well I was tired from studying and wanted to take a break
Nothing more than just a little experiment.
Sent from my GT-I9305 using XDA Labs
God damnit, hate to be the first one.
Could any one please test the front camera ?
NVM: Crashed once, working now
can i install this rom On gt i9300???
Sent from my GT-I9300 using Tapatalk
FaySAL Majoka said:
can i install this rom On gt i9300???
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
no.
Hi Pan! I just wanna say, "thanks" for all your hard work for this device. I've been using your builds ever since winxuser switched phones. You're doing great work, keep it up!
Cheers,
eages.
FaySAL Majoka said:
can i install this rom On gt i9300???
Click to expand...
Click to collapse
If you want a brick then go ahead. Otherwise get the i9305.