Rules of the thread
-This thread is dead
Please access this thread for CM7-related work.
- NO UBUNTOP. Go spam Lokifish here.
Honestly, if it was up to me, I'd kill HDMirroring and wait until ICS to try and enable ICSresizing using the phone to generate a 720p output. Could be five mathematically provable types of awesome.
- DO NOT PM ME FOR HELP. I provide NO support... And I DEFINITELY won't help porting crap skins.
**** MIUI. There, I said it.
- I became a bit more lenient
I'm giving one chance per noob before raining all nine hells on them
- I got my device back
I missed you guys too <3
- I just restarted this (as of April 21st, 2012)
I have no idea what Turl has been up to. Lemme sync with him.
- Cougar is cool
The dev, not the lady outside my office
Hello, this is my personal/pet project of getting CM7 on the Photon. Now you are not risking SJ's second coming by flashing.
Latest build is here.
Not related to mrinehart93's efforts in any way. I'm basing myself on pure CM7 and pure Motorola sources.
The GSM lock has been confirmed as being in the Radio component. Sad.
OH LOOK A GOOGLE+ PAGE
What it is
- Pure CM goodness. No more, no less.
What works [as of the latest build]
- Touchscreen [ 8 points, thanks to mrinehart93's link in his thread here ]
- Video Acceleration [ youtube doesn't work out of Sprint, WTF ]
- UMTS 3G radio works [ AT&T frequencies ] for voice, data and SMS
- GSM [ tested by olegfusion ]
- CDMA [ data seems to be working ] [ Carrier Name seems to be out of whack ]
- Back-Facing Camera [ will have to rework some stuff for buttonpress->snap ]
-- 720p video, woots
- Front-Facing Camera
- Gapps are installable and work [ tested the Talk Videoconference component ]
- GPS
- Wifi
- Bluetooth
--- I derped the kang from the olympus SO HARD. Thanks to Turl, y'all can call from a car now.
- Youtube (on Sprint's 3G network)
- Charging while plugged to a wall.
What derps
- Charging while off using a computer as a battery pack. It will boot CM7
What sucks balls
- HDMI mirroring
- Youtube (fix found but it's ugly and not unified. This will need to be integrated to Settings.)
What doesn't work at all
- WiMAX
- Sending MMS seems to be splode.
Off the list of stuff I want to try
- webtop
Bragging rights
- 4 days :3
Thanks
- mrinehart93 for the touchscreen link [ here ]
- the bros at CM for the olympus overlay
- Turl for MANY things
- Hashcode for the Phone apk fix here: http://goo.gl/eF1GB
- CM
Side-Effects
- TurbulentEddie, dave0812 and cythrawl have reported that this ROM flashes and works on the Electrify.
Contributions
- qbking77, from the Android Creative Syndicate, made a howto! See http://www.youtube.com/watch?v=tCNLbCdMNuI
Todo
- Fix found for Youtube: set the proxies to 0.0.0.0 and the proxy ports to 0 in the build.prop. The specific properties will have to be software-modified down the road. A wifi-events-listener app will need to be programmed for proxy switching on wifi too.
If you REALLY want to donate to thank me for the groundwork I've done: go save boobies instead. They're more precious (to me, at least) than my beer/pizza fund.
Sun. April 29th, 2012 - build - md5sum
- Mainline resync and styling fixes, RIL rewrite to wipe previous overzealous code by me for mainline submission. Hint hint.
Tues. April 24th, 2012 - build - md5sum
- OC issue is fixed
Mon. April 23rd, 2012 - build - md5sum
- 22nd's build, rebuilt
- WARNING: Clockrate hard-set to 1.45ghz. Use Settings -> Cyanogenmod -> Performance -> CPU to set max rate to 1000mHz and set-on-boot.
Sun. April 22nd, 2012 - build - md5sum
- New kernel, resync'd from Atrix.
=============== REPORTED AS NOT WORKING ===============
Sat. April 21st, 2012 - build - md5sum
- CM7 resync
- Patches reintegrated to mainline and resubmitted
Mon. January 23st, 2012 - build - md5sum
- Camera fix
WARNING WARNING WARNING WARNING WARNING WARNING
=========This build is untested by me and IDGAF============
WARNING WARNING WARNING WARNING WARNING WARNING
Sat. January 21st, 2012 - build - md5sum
- I'M IN UR FORUMZ STEALING UR LIMELITEZ
- Resynchronized with mainline and compiled
WARNING WARNING WARNING WARNING WARNING WARNING
=========This build is untested by me and IDGAF============
WARNING WARNING WARNING WARNING WARNING WARNING
Sun. November 20th, 2011 - build - md5sum
- Resync'd to the current code [ CM 7.2.0 ]
- Code cleanup, camera patch reimplemented (extremely simple, a 5-year old human / 10 year-old monkey could have come up with it)
- Resubmitted to the CyanogenMOD code review site.
Tues. November 8th, 2011 - build - md5sum
- sdcards. oops.
Sun. November 6th, 2011 - build - md5sum
- Bluetooth
- Phone.apk code fix from the Droid3 WE [ bug affects some CDMA users ]
- Camera button snaps photos as expected now
Fri. November 4th, 2011 - build - md5sum
- USB behavior modification [ known to make the phone reboot. DO NOT ENABLE SDCARD MODE PLEASE ]
- CDMA [ testing phase - Motorola does weird stuff ]
Mon. October 17th, 2011 - build - md5sum
- Wifi
Sat. October 15th, 2011 - build - md5sum
- Initial public pre-alpha build (no wifi, no cdma, gsm/umts working, 3G over UMTS is tested)
So how'd you get the RIL working? Does CDMA work or no?
It's moto's own, shoved in CM7. I merged the original init.sunfire.rc with the olympus and reworked the permissions to start everything in an OK manner.
No idea if the CDMA will work. I'm running exclusively GSM/UMTS. I'm canadian, eh!
Wow, outta nowhere, Bam! What works? Nice work man!
cybik said:
It's moto's own, shoved in CM7. I merged the original init.sunfire.rc with the olympus and reworked the permissions to start everything in an OK manner.
No idea if the CDMA will work. I'm running exclusively GSM/UMTS. I'm canadian, eh!
Click to expand...
Click to collapse
Wait, so you took the lib_motoril.so and put it directly in your ROM? Or you edited what is compiled? Either way, nice work!
bricky23 said:
Wow, outta nowhere, Bam! What works? Nice work man!
Click to expand...
Click to collapse
edited the original post to answer you.
It's a non-complete mostly-usable build, honestly.
mrinehart93 said:
Wait, so you took the lib_motoril.so and put it directly in your ROM? Or you edited what is compiled? Either way, nice work!
Click to expand...
Click to collapse
Shoved it right in the build's throat. Since the Photon is like if the Atrix had an illegitimate child with Sprint's engineers, I figured the RIL should be initializable the same way. So I kanged parts of the olympus system.prop and ka-f'in-blamo.
congrats on getting me to unlock again.
ps. will be testing cdma sometime in the near future(asap)
I need someones to test the CDMA! I have NO flippin' idea if it works!
ed: thanks jokersax11
cybik said:
I need someones to test the CDMA! I have NO flippin' idea if it works!
ed: thanks jokersax11
Click to expand...
Click to collapse
your welcome, however im in the process of backing up with titanium(477) so yea i say within two hours ill have it tested properly
btw i stopped my 11.10 upgrade for this.
Gonna test this out. have to unlock the ol' bootloader first.
10charedit
just curious what kernel are you using?
jokersax11 said:
just curious what kernel are you using?
Click to expand...
Click to collapse
motorola's own sources
I didn't mod ANYTHING from the sources, I only built everything. I figure that if it's too far from Motorola's patches, it could end up being /expletive/ing with the hardware too much for my personal taste. My actual JOB is to get **** to compile properly. It came in handy
cool, im having issues with dhd.ko myself hence why wifi is busted with my rc2 kernel
alright flashing now and will repost with cdma results
no go on cdma radio working, looking into it now.
f5f5f5f5f5f5f5f5f5
jokersax11 said:
alright flashing now and will repost with cdma results
no go on cdma radio working, looking into it now.
Click to expand...
Click to collapse
probably has to do with the CDMA component not initializing. I'll have to kang into mrinehart93's build to see how he initializes his part and possibly write a RadioSwitch app or something.
any chance you could make a cdma version. obviously you'll have testers
imma try something.
Just flashed only to find the page was updated and cdma isn't working. lol
Related
NAZ Desire based on Modaco Custom Rom Desire a19 and r22.
All the credit should go to Paul OBrien. I just updated, removed and added on.
- 06/06/2010: Took out the TO DO list. I can't see any way to get Arabic or Trackball on Sense. Yes I am giving up for now.
- 05/21/2010: So it looks like I will support 2 versions of this ROM:
Cutting Edge: The name says it all. It will have the latest releases and can be unstable.
Android Tech with Chinese Support: Same as Android Tech but, as name says, with Chinese support.
Add-on:
intersectRaven's Kernel (2.6.33.4 AVS 925mv CFS 20100524_2152)
Google Maps 4.2
Wired Tether 1.2
Wireless Tether 2.01
DeskClock
Gallery3D
Desk Clock
Car Dock
YouTube from EVO
Known Issues:
Cutting Edge: MMS picture resize problem (Work around: Use Handcent)
Cutting Edge: APN configuration at run time not working. (See post 3 for T-Mobile USA APN)
All versions: Call waiting screeching noise
All versions: FM Radio not working
All versions: Bluetooth does not always detect device. (Getting better with every build but still not reliable)
All versions: If you are having problems with capacitive lights, try this.
Instructions:
Fresh install:
Nandroid backup
Wipe
Install
Enjoy
Upgrade:
Nandroid backup
Install
Enjoy
Let me make it clear, I am not a dev in the sense of Cyanogen or Paul OBrien. I am just a ROM cook/chef. I will try my best to keep this updated and fix as many issues as I can.
Thanks and enjoy!
Cutting Edge Beta 13 Final (based on r22)
Download (4Shared)
Mirror (AndroidSpin)
MD5: 681fb69922accaa9ab2bae0db09e909e
Android Tech Beta 2 With Chinese Support Stable (based on r19 formerly Beta 9 and Beta 11)
Download (4Shared)
Mirror (AndroidSpin)
MD5: e0525b1ec2cf3a2f004b8250ec5dc7c9
If you like NAZ Desire ROM donate here.
Change Log
Change log:
Cutting Edge Beta 13
Updated Kernel
Battery Percent (thank you deanesn)
Cutting Edge Beta 12 Final
Updated Kernel
added Youtube from EVO 4G (see settings for "High quality video on mobile")
Tweaked and much more stable and fast.
Android Tech Beta 2
Update kernel
added Youtube from EVO 4G (see settings for "High quality video on mobile")
Aligned with Cutting Edge build
Beta 12 Test 4 (Final Test)
Re-based from Modaco r22
Updated Kernel to 3.6.34 AVS 925mv CFS
Beta 12 Test 3:
Fixed problem with su.
Updated kernel to 3.6.34-rc7 AVS 925mv CFS
Beta 12 Test 2:
Added HTCFacebook sync app
Added Facebook app
Nexus One Boot animation
Lights and sensor lib update
Added A2SD+ (dalvik 2 SD)
Beta 12 Test 1:
Based on updated Desire release (Similar to Modaco r22)
Moved Lib to Data (More room on System)
Beta 11 Stable:
Moved fonts to data
Updated Kernel to 2.6.33.4_AVS-925mV_CFS_20100513_1031 (Stable fast and no music skipping)
Beta 10:
Peeps is back!
Dev Tools
A few minor tweaks
Beta 9:
Added Car Dock
Moved Fonts to Data (space is getting tight on system)
Removed Footprints (need the space and the camera is flipped in the app)
Reverted back to intersectRaven's Kernel 3.6.33.3 AVS 925mv CFS. No more music skipping and more stable.
Other optimizations
Beta 8:
Fixed wifi connection issue
Add HTC_CIME
Trouble Shooting
I don't post any updates that I have not tested on my own device and I am 100% sure is working. So, when you ask for help, please provide a logcat or I will not be much of help otherwise.
No A2SD
1) If you are coming from another ROM, wipe data, cache, Dalvik-cache and SD:EXT
2) Make sure you have an ext3 or 4 partition.
3) Repair SD:ext
Loop Boot
1) Wipe all data, dalvik-cache, cache, and ext
2) re-flash
Most issues can be resolved by wiping and reinstalling.
TMOBILE APN USA
APN: epc.tmobile.com
Proxy: not set
Port: not set
Username: none
Password: ****
Server: *
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: 216.155.165.50
MMS port: 8080
MCC: 310
MNC:260
Authentication Type: Not set
APN Type: not set
it's very good thing to see more cookers . Thanks man
Im willing to try this but might i ask why you use the 800mv, from what i know is it lowers the radio voltage and makes the phone jump from edge to hsdpa networks way to often. I think this is user problem you are going to hear about often.
Please put HTC_CIME in it.
Thank you!
jmotyka said:
Im willing to try this but might i ask why you use the 800mv, from what i know is it lowers the radio voltage and makes the phone jump from edge to hsdpa networks way to often. I think this is user problem you are going to hear about often.
Click to expand...
Click to collapse
I did not experience any problems using 800mV but I can always change it if I see it as an issue.
can you include TrackballWake?
jmotyka said:
Im willing to try this but might i ask why you use the 800mv, from what i know is it lowers the radio voltage and makes the phone jump from edge to hsdpa networks way to often. I think this is user problem you are going to hear about often.
Click to expand...
Click to collapse
+1
I think you should pack in one of Intersect Raven's stable AVS Builds like the 925 from 04/29/10. That seems to be one the best builds. Most of the .34rc6 kernels are still pretty unstable and gives some accelerated battery drain for most. Thanks for the ROM though!!!
Ill have to check it out sometime. A19 is the best one paul came out with. everything after that was downhill...
cchhk said:
Please put HTC_CIME in it.
Thank you!
Click to expand...
Click to collapse
Will add soon ....
Franklees said:
can you include TrackballWake?
Click to expand...
Click to collapse
I will try but the files have been removed from the post because it was added to CM.....
Thanks for sharing this with us.
We are all waiting new cook/chef with Desire rom.
TrackballWake in option cause i don't want it ( don't like when i push the trackball in my pants and my phone wakes up and the battery drain faster with this)
Franklees said:
can you include TrackballWake?
Click to expand...
Click to collapse
+1
It's why I stick with CM tho.
trackball
imfloflo said:
Thanks for sharing this with us.
We are all waiting new cook/chef with Desire rom.
TrackballWake in option cause i don't want it ( don't like when i push the trackball in my pants and my phone wakes up and the battery drain faster with this)
Click to expand...
Click to collapse
I'm not big on the trackball wake. My phone pocket called and I got my ass chewed for two days after they overheard my conversation!
kevinniven said:
I'm not big on the trackball wake. My phone pocket called and I got my ass chewed for two days after they overheard my conversation!
Click to expand...
Click to collapse
Made me laugh... LOL
THATTON said:
+1
I think you should pack in one of Intersect Raven's stable AVS Builds like the 925 from 04/29/10. That seems to be one the best builds. Most of the .34rc6 kernels are still pretty unstable and gives some accelerated battery drain for most. Thanks for the ROM though!!!
Click to expand...
Click to collapse
but .34rc6/rc7 are way more responsive than .33 as my own test.
speed
so far it feels fast!
Tackball wake rox my sox!
kevinniven said:
so far it feels fast!
Click to expand...
Click to collapse
It is fast and stable. I have been running it for almost a month now. That's way it's Beta 7.
Just started this thread for experimental FM support in my latest AVS-X release. This will be merged into my mainline kernel after cleanup and any other issues have been resolved.
*Source posted to GitHub
Credits go to the ff:
Kali- -> initial input of dmesg about Desire kernel path and later the bluetooth address property remapping
Lint_, imfloflo, bewA -> providing logs for analysis from Desire
20100715_1511:
- updated to latest FM source I posted in my GitHub which contains a slight modification which should improve stability
- only bug I found so far is that the radio app will show the wrong frequency BUT still output the correct one
*after trying out different combinations which previously crashed the FM radio, it hasn't crashed once...takes awhile to tune into a station but other than that it seems stable...also, the initial frequency DISPLAY (not output) to 0 bug seems to be not 0 but the frequency the first time the radio is launched...
20100715_0803:
- this should fix the timeout problems with the radio
- causes a weird frequency switch to lowest detected in r23...unsure if r19 is also affected (don't want to wipe so please test and post your results here)
- WiFi on r19 works (found my patch file)
20100713_1658:
- uncommented a line of code which prevents the IO bus from being configured for serial transfer in some cases
*should fix the intermittent problems everyone's been experiencing (including mine when I switched from my test FM branch to my official FM branch which I'm releasing here)
20100713_1011:
- updated to .35-rc5
- cleaned up FM code a bit
20100712_1348:
- reverted WiFi driver to work with Modaco Desire r19
20100712_0832:
- Initial release of .35-rc4 kernel with FM support
- needs a ROM with Desire FM radio (tested in Modaco r19 Desire ROM)
- wifi doesn't work with Desire ROM though
Here're the links:
*Please go to my MediaFire folder for the latest releases
http://www.mediafire.com/intersectRaven
20100715_1511:
CFS:
925mV -> http://www.mediafire.com/?nu2ijzk5d2ym2yz
20100715_0803:
CFS:
925mV -> http://www.mediafire.com/?ewm2kowyoyydonq
20100713_1658:
CFS:
925mV -> http://www.mediafire.com/?n0e0loztl1j
20100713_1011:
CFS:
925mV -> http://www.mediafire.com/?3ny1yozijjj
20100712_1348:
CFS:
925mV -> http://www.mediafire.com/?yyemyimkmmk
20100712_0832:
CFS:
925mV -> http://www.mediafire.com/?dtmmykwmoiy
Nice job intersect, this is a definite score!
jlevy73 said:
Nice job intersect, this is a definite score!
Click to expand...
Click to collapse
Thanks! It's amazing what I can do when I'm bored.
Start working on a non desire version if you're that bored. =P
JCopernicus said:
Start working on a non desire version if you're that bored. =P
Click to expand...
Click to collapse
That I can't do. Even the threat of death can't make me program in Java or a hybrid of that.
so, in detail, this kernel + current Desire ported Room = working FM Radio (inlc. receivable FM signal and working sound) but unable to connect wifi??
chrisvuong said:
so, in detail, this kernel + current Desire ported Room = working FM Radio (inlc. receivable FM signal and working sound) but unable to connect wifi??
Click to expand...
Click to collapse
Yes. For that either I would need to revert to an older WiFi driver version OR someone can update the components necessary to get it up on the Desire ROM.
Will it work on Desire 2.2 ROMs?..
great job , i hope u'll find a right way fixing wifi problem, appriciate your work,mate^^
Eclair~ said:
Will it work on Desire 2.2 ROMs?..
Click to expand...
Click to collapse
Can you post a link to that? I do want to get a ROM with Radio AND wifi and wifi works on FroYo so it should work there if it has a radio app. Haven't tested any other Desire ROM though.
intersectRaven said:
Thanks! It's amazing what I can do when I'm bored.
Click to expand...
Click to collapse
Woohoo for boredom
WOW!
Absolutely brilliant work... I bet all the engineers at Google are jealous right now!!!
*Double post*
intersectRaven said:
Can you post a link to that? I do want to get a ROM with Radio AND wifi and wifi works on FroYo so it should work there if it has a radio app.
Click to expand...
Click to collapse
Yea.. King ported it a few days ago, I don't believe he is posting his newer work here anymore though.
http://kingxklick.com/forum/viewtopic.php?f=3&t=14
This will be good advertising for him, lol.
Eclair~ said:
Yea.. King ported it a few days ago, I don't believe he is posting his newer work here anymore though.
http://kingxklick.com/forum/viewtopic.php?f=3&t=14
This will be good advertising for him, lol.
Click to expand...
Click to collapse
Yep he has been officially kanged lol
chromiumcloud said:
WOW!
Absolutely brilliant work... I bet all the engineers at Google are jealous right now!!!
Click to expand...
Click to collapse
I doubt it. They do work at the big G you know. Although they might get a teensy bit jealous if all those who promised to donate does donate.
I just gave this a go on Kings Alpha 3 Desire Froyo port.
Wifi was working but radio app and the widget would not start, just said "radio turning on" and nothing was happening. I did have headset plugged in also.
joshlusignan said:
I just gave this a go on Kings Alpha 3 Desire Froyo port.
Wifi was working but radio app and the widget would not start, just said "radio turning on" and nothing was happening. I did have headset plugged in also.
Click to expand...
Click to collapse
I see. I don't have time to debug right now since it's already the start of the work week. I'll just try it later.
I don't know how useful it will be, but if you look over at maemo.org you'll see drivers for fm transmit over there (n900), they are linux based, but for a different chipset.
*cough* *wink* *nudge*
=D
intersectRaven said:
Can you post a link to that? I do want to get a ROM with Radio AND wifi and wifi works on FroYo so it should work there if it has a radio app. Haven't tested any other Desire ROM though.
Click to expand...
Click to collapse
This is Kingklick 2.2 Froyo Desire2Nexus pre Beta, still having bugs like graphic and bluetooh, you can try this, i havent flashed it so i dont know he integrated Radio Fm app or not.
http://kingxklick.com/?page_id=28
CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Warning : Not for new users, flash this build only if you know what you are doing !!!
What is CyanogenMod (in less terse form - by mad-murdock)?
since i am a bit idle right now, i try to answer this.
cyanogenmod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information. General Q&A thread is at http://forum.xda-developers.com/showthread.php?t=1176411 and that also contains the Installation instructions.
teamhacksung:
atin - http://twitter.com/atinm
codeworkx - http://twitter.com/codeworkx
coolya - http://twitter.com/dumdidum
guiperpt - http://twitter.com/guiperpt
unhelpful - http://twitter.com/unhelpfulone
Changelog:
Generic Changelog CMSRC Twitter
Device specific Changelog by igor.tonky
Sources:
http://github.com/CyanogenMod - all the CM7 non-kernel source
http://github.com/CyanogenMod/samsung-kernel-c1 - Galaxy S2 international kernel source used in CM7
http://github.com/teamhacksung/samsung-kernel-c1att - AT&T Galaxy S2 kernel source used in CM7
Modems:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Support_Downloads
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
The bug list (as best as I can remember anyway) is on the Q&A thread.
Codeworkx put up a temporary KANG build until build bot comes alive: http://www.multiupload.com/1776L41QDV - no bug reports please, it is a nightly, like all nightlies. Install using the "Harder way" in the OP for a first time install.
Great work AdinM and Team Hacksung. Downloading now
Great job. Looking forward to testing it out, thanks for the nightlies :]
Good job !
Downloading ..
Great work guys !!
Tks for all!
Excellent work to all of you guys at CM. Now let's await the this don't work moans.
Will test out.
Sent from my GT-I9100 using XDA App
Awesome! Downloading, thanks for all this
N1 guys
from my SGSII running MIUI 2.3.3
thanks mate, downloading now
thnx
downloading
Downloading!!! \o/
Looking forward to any videos anyone makes so us lowly SGS users can see the power...
jaju123 said:
Looking forward to any videos anyone makes so us lowly SGS users can see the power...
Click to expand...
Click to collapse
Take a look at http://www.youtube.com/watch?v=c4QN-9b6alQ from Codeworkx.
Only 100 mb ?
The most Stockroms have around 300 !
from my SGSII running MIUI 2.3.3
Wicked.
thanks for the hard work boys. Totally donating all of my organs.
Downloading!
I like!
Just jizzed in my pants
redbull320 said:
Only 100 mb ?
The most Stockroms have around 300 !
from my SGSII running MIUI 2.3.3
Click to expand...
Click to collapse
well this isnt stock rom, is it
The Official MIUI Photon Rom Thread!
IM HOPING TO PUSH OUT A NEW BUILD IN A COUPLE DAYS
NO 4G's - DON'T ASK FOR THEM TO BE WORKING!
Note: Yes we know that Evo now has 4G, but technically that is a modified CM7 and not actually MIUI.
This rom is a port from the Motorola Atrix. Currently it is in Alpha status, so there is a lot of stuff that isn't working correctly. We are dillegently working on getting everything fixed and to a stable build. Once we have a stable version we will work on keeping up with the weekly MIUI releases.
Requirements
Unlocked Bootloader
Wipe/Wipe/Wipe
CWM Recovery (TWRP doesn't fully work yet)
Downloads
Alpha Releases - Box.Net
THIS IS WHERE I WILL BE POSTING BUILDS FOR A WHILE
Updated to include build 7!
Download Mirrors
GSM release - this is from sky24987, we are working on incorporating his work into our build. For now if you need GSM you will have to use his rom.
Working
CDMA Call/Data
Text
Wifi
Camera (front and back)
Torch (some issues with lockscreen)
GPS
Bluetooth
Audio (some issues with games and apps)
Rotation
Bottom LED's (sometimes turn themselves off)
USB
MMS (This is really hit or miss, it works for some people though)
Broken
Auto Backlight
Mute in call
FM
We have also made a few modifications to the apps that are included with MIUI - adding some and removing others.
Removed Apps
MIUI Market
MIUI Stats
MIUI Camera (broken)
Added Apps
Compass
FM
CM7 Camera (for front and rear camera)
Credits
XboxFanJ - Porting From Atrix
Ebbinger_413 - Bug Fixes
DethMetalz69 - Bug Fixes and Testing
sky24987 - Chinese GSM Build
JEbbinger - Testing
Cybik - CM7 Sources and Kernel Used
Miui Atrix Team
Miui Development Team
CM7 Development Team
Motorola and Sprint
Thank our contributers
As this account is a shared account for our contributers thanking this post will not give credit were credit is due. Please thank them individually - I am trying to get links to thank them directly from this post, but I don't know if thats supported by these forums.
Full Changelog
We will be posting and updating the full changelog once we get out of the alpha status.
Download Mirrors
These mirrors are updated in no particular order. If there are any missing or broken links please pm one of us.
Dropbox
Test 1 (12-13-2011)
Test 2 (12-13-2011)
Test 3 (12-14-2011)
Test 4 (12-16-2011)
Test 5 (12-19-2011)
Test 5-2 (12-20-2011)
Test 6 (12-22-2011)
Test 7 (1-19-2012)
Tweaks, Mods, Tips, Ect.
This information will be specific to the Motorola Photon's MIUI, if you are looking for general MIUI tweaks, mods, and tips take a look at the Miui Manual from miui.us
Tips
- Issues with Torch
Sometimes when using the torch at the lockscreen it will simply flash on then flash off. To work around this before holding the home key to activate the torch move the unlock slider slightly - not actually unlocking phone. For whatever reason this will allow the torch to stay turned on.
Click to expand...
Click to collapse
Thank you! this is great. Downloading test 6 now.
Test 6 seems not to flash...after 10 sec or so says complete then hangs at Motorola screen. tried twice just to make sure
dj4enzik said:
Test 6 seems not to flash...after 10 sec or so says complete then hangs at Motorola screen. tried twice just to make sure
Click to expand...
Click to collapse
are you flashing to mopho or electrify? and you did a full wipe and your unlocked?
Test 6 want working for me last night either, sits at the moto unlocked screen
Sent from my MB855 using XDA App
double check the md5 - there is a text document in the box folder with the md5 for each build.
if they match then go back to build 5-2 - dethmetalz put up test 6 so i don't know if he changed anything.
If you give me a second i can re-upload it...
edit: uploading now...
edit2: upload is finished - test 6 should be good now. dethmetalz did upload the incorrect copy - sorry.
dj4enzik said:
Test 6 seems not to flash...after 10 sec or so says complete then hangs at Motorola screen. tried twice just to make sure
Click to expand...
Click to collapse
Can you logcat?
I accidentaly downloaded the old test 6 that wouldnt flash >.< Sorry about that.
I can upload the correct one if youd like?
Also, Are you still interested in switching to the nexus port ebbinger?
the links for the gsm roms are broken, no matter what link you click it starts to download but then stops like at 39 then just cuts off.
Flashing to a photon. I don't think its getting far enough to logcat...I can be of more use once I get home..at the office
---------- Post added at 03:16 PM ---------- Previous post was at 02:56 PM ----------
tried 5-2 as well, will not flash
How is the battery drain on that firmware?
Sent from my Motorola Photon with Electrify flash using xda app
So 6 isnt working?
Its working, I just downloaded and flashed 6.
I started uploading the good test 6 at work - it looks like its finished. So test 6 in the box downloads should be good - just double check the md5 to be safe.
@dethmetalz69
test 6 shoudl be good for now - if more people report issues re-upload it then. And as far as the nexus builds go, yes i will be working towards using that as a base to speed up the time it takes for us to release a new version from when miui.com releases an update.
ebbinger_413 said:
I started uploading the good test 6 at work - it looks like its finished. So test 6 in the box downloads should be good - just double check the md5 to be safe.
Click to expand...
Click to collapse
Test 6 works for me...
ebbinger_413 said:
I started uploading the good test 6 at work - it looks like its finished. So test 6 in the box downloads should be good - just double check the md5 to be safe.
@dethmetalz69
test 6 shoudl be good for now - if more people report issues re-upload it then. And as far as the nexus builds go, yes i will be working towards using that as a base to speed up the time it takes for us to release a new version from when miui.com releases an update.
Click to expand...
Click to collapse
Well if theres anything i can do just gtalk me.
Great work! With you guys our photon will have more and more roms, first we have cm7 and then miui, now we have ics!!
Sent from my MB855 using XDA App
This is for developers only. No builds will be posted in this thread.
https://github.com/CM10DNA
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
I thought I would share an update on how this very experimental code-base is doing.
The code is running again (much of yesterday it was crashing on startup).
I have been running dirty flashing from my CM 10.1 build. It seems like that was safe to do so. I tried doing a clean flash this morning but sadly, my clean flash seems to have broken cell service. No phone or data. Restoring my cm 10.1 backup of data to the same install fixed it. Strange. (This included the change pushed this morning that updates the version of the apns file).
Superuser is now working but may be a little flaky. For example, on my clean install Titanium Backup couldn't acquire root access until after I rebooted.
Camera is still not working. It says "failed to connect to camera". I haven't looked at it at all, but there is a massive commit in the M7 kernel pulling source from the HTC One Google Edition for the camera.
Overall, I'm finding it's either completely broken or working very well. I think that the cellular network issue is going to get resolved upstream. I am afraid that we might be on our own for the camera.
crpalmer said:
I thought I would share an update on how this very experimental code-base is doing.
The code is running again (much of yesterday it was crashing on startup).
I have been running dirty flashing from my CM 10.1 build. It seems like that was safe to do so. I tried doing a clean flash this morning but sadly, my clean flash seems to have broken cell service. No phone or data. Restoring my cm 10.1 backup of data to the same install fixed it. Strange. (This included the change pushed this morning that updates the version of the apns file).
Superuser is now working but may be a little flaky. For example, on my clean install Titanium Backup couldn't acquire root access until after I rebooted.
Camera is still not working. It says "failed to connect to camera". I haven't looked at it at all, but there is a massive commit in the M7 kernel pulling source from the HTC One Google Edition for the camera.
Overall, I'm finding it's either completely broken or working very well. I think that the cellular network issue is going to get resolved upstream. I am afraid that we might be on our own for the camera.
Click to expand...
Click to collapse
https://github.com/CyanogenMod/andr...mmit/ec27077d6497c66f52488126ef6b181ef3fbed0d
seems cm has stopped camera building throughout probably prepping for the focal merge
edit: idk if m7 has cam working but it hasn't been detected as a bug
"Current bugs (they are known):
SMS sending will not work (receiving works)
Dialer sub-submenu FC's the dialer
Keyboard FC's when gesture swiping"
Not sure how much this helps. But the m7 kernel recently got its camera code updated with the Google edition. http://review.cyanogenmod.org/#/c/46164/
With that so. They are able to use the 4.2 libs http://review.cyanogenmod.org/#/c/46299/
Flyhalf205 said:
Not sure how much this helps. But the m7 kernel recently got its camera code updated with the Google edition. http://review.cyanogenmod.org/#/c/46164/
With that so. They are able to use the 4.2 libs http://review.cyanogenmod.org/#/c/46299/
Click to expand...
Click to collapse
we'd probably have to merge their whole drivers/media/video/msm and use their camera binaries at least that's how it works with sense if you want to use their 4.2.2 cam libs
JoelZ9614 said:
we'd probably have to merge their whole drivers/media/video/msm and use their camera binaries at least that's how it works with sense if you want to use their 4.2.2 cam libs
Click to expand...
Click to collapse
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
crpalmer said:
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
Click to expand...
Click to collapse
What about the commit introducing the HTCCDMAQualcommRIL?
Sent from my HTC6435LVW using xda app-developers app
times_infinity said:
What about the commit introducing the HTCCDMAQualcommRIL?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Which commit?
crpalmer said:
Which commit?
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/45607/
Hope it helps.
Sent from my HTC6435LVW using xda app-developers app
I'll take a look at the radio stuff tomorrow. I have a couple ideas.
Deck got data working on the m7 (Sprint), check the commits or wait until tomorrow if he hasn't pushed them yet
Sent from my buttered S3
chad0989 said:
I'll take a look at the radio stuff tomorrow. I have a couple ideas.
Click to expand...
Click to collapse
To be clear, it is working fine for me if I dirty flash. I have been running 10.2 builds for 48 hours everywhere from strong wifi to bad 3G in the middle of a forest.
It's only breaking if I do a factory reset before flashing a build. That's why my guess was that it was related to this event being missing:
cyanogenmod.org/#/c/46280/1/libril/ril.cpp
(around line 2240) and that a similar change was going to be required to our libril. My inclination would be to wait and see what happens with the M7 builds (which it sounds are coming along) and see if it just magically fixes itself for us....
Edited to add: sending of text messages wasn't working but looks like they were supposed fixed last night (I haven't built it to test it yet)
crpalmer said:
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
Click to expand...
Click to collapse
mm actually now that i look at it drivers/media/video/msm has been left basically untouched in our source updating to what the m7 has shouldn't be too much of a problem
JoelZ9614 said:
mm actually now that i look at it drivers/media/video/msm has been left basically untouched in our source updating to what the m7 has shouldn't be too much of a problem
Click to expand...
Click to collapse
I tried a cherry-pick before and it looked very bad. But, actually, a lot of it looks like it could be related to the comments that HTC strips from the source when the release that I added back (because it makes it easier to patch from all non-HTC sources).
If you want to take a crack at this, try doing this before cherry-picking their commit:
git show c81741a8337c2342d856ffeac0cc087452729290 drivers/media/video/msm include/media/msm_camera.h | patch -p1 -R
That will strip all the comments back out again and get rid of all those conflicts. The conflicts then look very simple (outside of arch/arm/mach-msm, which is where it gets much harder).
crpalmer said:
I tried a cherry-pick before and it looked very bad. But, actually, a lot of it looks like it could be related to the comments that HTC strips from the source when the release that I added back (because it makes it easier to patch from all non-HTC sources).
If you want to take a crack at this, try doing this before cherry-picking their commit:
git show c81741a8337c2342d856ffeac0cc087452729290 drivers/media/video/msm include/media/msm_camera.h | patch -p1 -R
That will strip all the comments back out again and get rid of all those conflicts. The conflicts then look very simple (outside of arch/arm/mach-msm, which is where it gets much harder).
Click to expand...
Click to collapse
the board-monarudo-camera.c doesn't need to be updated, at least i didn't update it in my m7 kernel port
but i can't seem to get the kernel to build
drivers/gpu/msm/adreno_snapshot.c: In function 'snapshot_rb':
drivers/gpu/msm/adreno_snapshot.c:628: sorry, unimplemented: inlining failed in call to 'parse_ib': recursive inlining
drivers/gpu/msm/adreno_snapshot.c:588: sorry, unimplemented: called from here
make[3]: *** [drivers/gpu/msm/adreno_snapshot.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
i don't believe it's related to any edits i made tho heres my commit https://github.com/Joelz9614/android_kernel_htc_dlx/commit/daa90f2bf8e64a8ad6f4f497ca412bc0a77ab7ef
JoelZ9614 said:
the board-monarudo-camera.c doesn't need to be updated, at least i didn't update it in my m7 kernel port
but i can't seem to get the kernel to build
drivers/gpu/msm/adreno_snapshot.c: In function 'snapshot_rb':
drivers/gpu/msm/adreno_snapshot.c:628: sorry, unimplemented: inlining failed in call to 'parse_ib': recursive inlining
drivers/gpu/msm/adreno_snapshot.c:588: sorry, unimplemented: called from here
make[3]: *** [drivers/gpu/msm/adreno_snapshot.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
i don't believe it's related to any edits i made tho heres my commit https://github.com/Joelz9614/android_kernel_htc_dlx/commit/daa90f2bf8e64a8ad6f4f497ca412bc0a77ab7ef
Click to expand...
Click to collapse
Searching in the browser doesn't have any matches for adreno_snapshot...
Maybe try git checkout -b tmp HEAD~1 and make sure that builds?
Looks like CM just merged an updated audio HAL along with the legacy HAL, both of which incorrectly detect our device for now. Building with a fix now and if all is well I'll submit upstream.
Edit: It's going to cause a bunch of routing issues again also until some other stuff gets merged in. Best to just revert their change for now for builds.
chad0989 said:
Looks like CM just merged an updated audio HAL along with the legacy HAL, both of which incorrectly detect our device for now. Building with a fix now and if all is well I'll submit upstream.
Edit: It's going to cause a bunch of routing issues again also until some other stuff gets merged in. Best to just revert their change for now for builds.
Click to expand...
Click to collapse
Aside from the routing issues, this may already be fixed for us thanks to the m7:
http://review.cyanogenmod.org/#/c/46473/
@chad0989, FYI, I reverted the commit to use legacy alsa early this morning and haven't noticed any problems (play music on Bluetooth, voice calls with and without wired headset) using that build.
You may want to give it a try and see if you're ready to revert it.
Edit: actually, I just noticed that they had also enabled legacy audio in msm8960-common but since reverted that. So, I guess I was still running the legacy mode...
crpalmer said:
@chad0989, FYI, I reverted the commit to use legacy alsa early this morning and haven't noticed any problems (play music on Bluetooth, voice calls with and without wired headset) using that build.
You may want to give it a try and see if you're ready to revert it.
Edit: actually, I just noticed that they had also enabled legacy audio in msm8960-common but since reverted that. So, I guess I was still running the legacy mode...
Click to expand...
Click to collapse
They aren't allowing new HAL to build yet (see https://github.com/CyanogenMod/android_hardware_qcom_audio-caf/blob/cm-10.2/Android.mk) But we will need that flag when they allow the new HAL to build. I added it preemptively to hopefully avoid breakage. The issue was that the legacy HAL they pushed hadn't included some changes for our CSD client and platform detection. Looking at what was committed last night/today it should work now though.