Related
This Will be the Site for the CM7 Releases and Updates
CM Ba2tF Build Released
As Always We will not be held responsible for ANYTHING involving your phone, by flashing this rom you accept the fact that no mater what catastrophic accident occurs, no matter how many kittens die, if natural disasters wreak havoc on your home land, EVEN IF THE "Dalai Lama" HIMSELF blames us for the mishap, we will not be held liable in any manner what so ever. You accept all risks associated with this rom by choosing to download the file end of story.What Is CyanogenMod:
CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.Warning: Not for new users, flash this build only if you know what you are doing !!!Atrix Dev Team:
(Click for twitter names)
Brandon15811
Edgan
Epsylon3
Eval-
Faux123
Ibproud
Joe_Ferreira
SamCripp
T0dbld
Turl
WesJust The Stats:What Works:
Dock Audio
2G/3G/H+
Calls and SMS
Mute on calls
SIM PINs
RIL FastDormancy Support
WiFi now with faster scan/connect times
Audio
USB
GPS with accuracy reporting
Bluetooth
Camera (many thanks defer!)
Video recorder
(Partial) Dock support
Torch
Display
Touchscreen
Battery Stats
Accurate power usage reporting
Proximity Sensor
Screen orientation
Accelerometer, compass and other sensors.
Internal Storage and External SDCard
SDCard formatting
Ability to swap sdcard and emmc mountpoints
Multimedia Playback (videos, music)
USB Tethering
USB Notifications
USB Mode switching
All Market apps show now
Updated Unified Kernel: one kernel to rule them all!
Battery jump fix by @Jug6ernaut
ext4 filesystem
WiFi Hotspot
5-touch multitouch
Power button doesn't end calls
CrystalTalk support for calls
SMS Delivery Reports
What Doesn’t Work:
Fingerprint sensor - Work in progress (not native to CM)
Webtop - Work in progress (not native to CM)
Changelog:
Atrix CM Ba2tF Release
Dock Audio
Bug Fixes
Download: Atrix CM Ba2tF build
Latest version: Ba2tF
Click to expand...
Click to collapse
Installation Instructions:
Pre-Work:Before powering off the phone download the CM7 package and copy to internal SD CardNote: It is standard CyanogenMod practice to make the external SD Card the primary SD Card on the device. This means after 1st boot all your app folders and personal files will be stored on in the “emmc” folder and all files from your external memory card will now be in the “sdcard” folder.
You can switch this around by going into
Settings>CyanogenMod Settings>Application>Use Internal StorageFlashing Recovery:
Download recovery from ROM Manager (Found in Market)
Flash Clockwork Recovery
Done
Personal Data Backup:
Make sure device is rooted
Download “Titanium Backup” from the Android Market (Consider purchasing Pro version for more automated options)
Open Titanium Backup, press menu key and go to “Batch”
Go to Backup section and select “Backup all user apps”
Allow process to finish
Current ROM Backup:
Reboot phone into CWM recovery (Power Button + Vol Down), press Vol Down until you see "Android Recovery" then press Vol Up to enter.
Go to Backup & Restore and create a backup (this may take some time)
Install CM7 Ba2tF:
While in Recovery install CM7 from internal storage
After installation select Data Wipe/Factory Reset
Then Wipe Cache Partition
Reboot system now
Watch awesome boot animation.
Upgrading from earlier CM7:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Backup to be safe!
Install the ROM zip from sdcard (your Google apps will be backed up automatically).
Personal Data Restore on CM7:
Download “Titanium Backup” from the Android Market (Consider purchasing Pro version for more automated options)
Open Titanium Backup, press menu key and go to “Batch”
Go to Restore section and select “Restore missing apps with data” (note: under no circumstances should you restore system apps, this is the fastest way to get a soft-brick)
If you only downloaded the free version you will have to click “Install” for each app as it restores
Allow process to finish.
Get Google Apps:
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for Motorola Atrix, choose Download ROMs, and pick Google Apps.
Or download and push the gapps zip for CM7 from http://wiki.cyanogenmod.com/wiki/Gapps#Google_Apps to the sdcard and flash it via ClockworkMod recovery.Radio Images:
Flash via Recovery
http://www.multiupload.com/N25DIPNAU6 (AT&T .91)
http://www.multiupload.com/0ZECKA3QZ1 (Bell)Going Back To Your Old ROM From CM7:
Reboot phone into recovery (Power + Vol Up button)
Once in recovery go to Backup & Restore
Select Restore, then select the restore that is dated before you moved to CM7
Allow time for restore, once complete reboot phone.
Click to expand...
Click to collapse
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
Donations
Click to expand...
Click to collapse
If you like our work consider donating to the team, all donations will go towards continued CM7 development and buying LapDocks for the teams to develop for.
PayPal Button
Rules of thread
Read The OP ^
If you wish to thank us do so with the provided "Thanks Button" or Feel free to click the "Donate Button" and donate
Before Asking A question make sure you have followed step one, searched the forums for your question, Use our bug tracker and instructions provided in the OP
If you wish to comment, or reply to another persons post that was not following the rules , DON'T just leave it I will handle it with reporting it
Submit problems or bugs on the Teams page on the bug tracker with EVERYTHING filled out Including a log(link provided in OP)
Take all comment or general discussion to a seperate thread in "General Section"
This is the tone I wish to keep for this thread, currently it is friendly and the questions that are being asked are polite and reasonable. My self and the other team member's will do our best to respond to any reasonable questions like those posted so far. How ever My self and others will not hesitate to report comments and or close the thread if it can not be kept like this!! What is going on so far here is pleasant and I appreciate it so please keep it UP!! If its just a thank you or a cheer on hit the thanks button or the donate button because while I own a beer store it still is neither free nor cost effective to ship the other gentleman on the team beer. Besides those options will keep the thread clean for important questions and updates, thanks again guys and if you want to talk smack open a new thread in general we might not like it but im sure well read it just the same
FAQ
Having Issues or Problems?
Thad take a look here at our FAQ site.
FAQ For Atrix CM 7
Thanks. What does "additional feature" mean for the fingerprint scanner? It will be available but not included or it wont be available for CM?
Many thanks for all the hard work contributed by all the devs working on this project. I look forward to the official Beta release.
WiredPirate said:
Thanks. What does "additional feature" mean for the fingerprint scanner? It will be available but not included or it wont be available for CM?
Click to expand...
Click to collapse
Means that it is additional feature not supported by CM7... yet.
Sent from my MB860 using xda premium
YES!!
Sent from my CHERRYπ-ed Atrix 3G v.06
Swiftks said:
Means that it is additional feature not supported by CM7... yet.
Click to expand...
Click to collapse
Right that is what the OP says, I was hoping for a slight elaboration.. I know the SDK for the fp scanner was released so I was hoping at some point it would be included, its a deal breaker for me. I will be sending a donation if and when it is included. Thanks again.
WiredPirate said:
Thanks. What does "additional feature" mean for the fingerprint scanner? It will be available but not included or it wont be available for CM?
Click to expand...
Click to collapse
It means its uncharted territory, It is not android. These are features that are not opensource. What does it mean for the future, well its tuff to say we have been working hard to get these features we believe we will obtain them, we are just not going to hold back the release of the rest of the work for them. Once they are in fact accomplished they will be included, how ever as always there is no time frame or expected completion date. If they are requirements or "deal breakers" for you than you will have to go else where for the time being. Webtop was honestly a shotty hack job by Moto IOHO, and the fingerprint was done by Authentic and than "AdLibed" so to speak by Motorola and is just proving to be some what difficult. At this point if one was to copy there fingerprint data manually from a stock rom, datadeffender could be used and will work, the lockscreen is getting close , but that still leave the enrollment wizard ... anyhow as you can see all of this is a lot of work and as of late a lot of us have had limited time to work on them due to more pressing engagements (aka real life) once again rest assured they are being worked on , but we can not offer any promises beyond that !!
Very Nice !
WiredPirate said:
Right that is what the OP says, I was hoping for a slight elaboration.. I know the SDK for the fp scanner was released so I was hoping at some point it would be included, its a deal breaker for me. I will be sending a donation if and when it is included. Thanks again.
Click to expand...
Click to collapse
the SDK, is used to create apps that will use what is already on your phone (aka a working fingerprint reader, or at least that is what is expected) It did offer some incite to how things are being done, how ever it did not give us all the keys so to speak, anyhow we have obtained some help, and are getting closer. Depending on what you need from the fingerprint reader than it is still " possible" to use data defender with CM7 it it just would require manually copying data etc. We understand that this is a feature we all want, I mean its part of the reason a lot of us got the phone, hang tight once I have enough time to put into it im sure this is accomplish-able
t0dbld said:
It means its uncharted territory, It is not android. These are features that are not opensource. What does it mean for the future, well its tuff to say we have been working hard to get these features we believe we will obtain them, we are just not going to hold back the release of the rest of the work for them. Once they are in fact accomplished they will be included, how ever as always there is no time frame or expected completion date. If they are requirements or "deal breakers" for you than you will have to go else where for the time being. Webtop was honestly a shotty hack job by Moto IOHO, and the fingerprint was done by Authentic and than "AdLibed" so to speak by Motorola and is just proving to be some what difficult. At this point if one was to copy there fingerprint data manually from a stock rom, datadeffender could be used and will work, the lockscreen is getting close , but that still leave the enrollment wizard ... anyhow as you can see all of this is a lot of work and as of late a lot of us have had limited time to work on them due to more pressing engagements (aka real life) once again rest assured they are being worked on , but we can not offer any promises beyond that !!
Click to expand...
Click to collapse
love the work you guys are doing, love CM7. pretty much everything about it is pure win for me.
the only question i have, and i don't mean to sound like i'm pestering you here, is about the HDMI mirroring. any thoughts on why we're stuck in portrait mode? i know some people have gotten it to work by flashing a photon alien rom, but i'd love this feature on CM7.
Alcapone263 said:
love the work you guys are doing, love CM7. pretty much everything about it is pure win for me.
the only question i have, and i don't mean to sound like i'm pestering you here, is about the HDMI mirroring. any thoughts on why we're stuck in portrait mode? i know some people have gotten it to work by flashing a photon alien rom, but i'd love this feature on CM7.
Click to expand...
Click to collapse
Obviously this is another issue that we are aware of, it is also not limited to our work, but even stock with enabled mirroring has issues. Once again we are at work with this, and i can say that at this point almost daily something is "tried" however as evident by the existence of the problem it has not yet been resolved. We are only at this time announcing a soon to be released BETA so there are issues and currently this is one, how ever for the most part we are very stable, all of us have been using it as our daily for months, pretty much everything works as expected this is why we are looking to move forward into BETA, but why it is BETA and not a full release or RC. thanks for the support and these issues will get ironed out just as soon as we can get them done
t0dbld said:
the SDK, is used to create apps that will use what is already on your phone (aka a working fingerprint reader, or at least that is what is expected) It did offer some incite to how things are being done, how ever it did not give us all the keys so to speak, anyhow we have obtained some help, and are getting closer. Depending on what you need from the fingerprint reader than it is still " possible" to use data defender with CM7 it it just would require manually copying data etc. We understand that this is a feature we all want, I mean its part of the reason a lot of us got the phone, hang tight once I have enough time to put into it im sure this is accomplish-able
Click to expand...
Click to collapse
Thank you for elaborating on this for me! I appreciate the hard work put in by all and look forward to this release. Great job everybody involved!
t0dbld said:
Obviously this is another issue that we are aware of, it is also not limited to our work, but even stock with enabled mirroring has issues. Once again we are at work with this, and i can say that at this point almost daily something is "tried" however as evident by the existence of the problem it has not yet been resolved. We are only at this time announcing a soon to be released BETA so there are issues and currently this is one, how ever for the most part we are very stable, all of us have been using it as our daily for months, pretty much everything works as expected this is why we are looking to move forward into BETA, but why it is BETA and not a full release or RC. thanks for the support and these issues will get ironed out just as soon as we can get them done
Click to expand...
Click to collapse
thanks for the quick reply, glad to see everything is moving forward smoothly. can't wait for this feature to be fixed though, i'd sacrifice webtop/fingerprint scanner permanently if i could just get working HDMI mirroring
once again, thanks for all of your efforts in porting this awesome ROM! you guys are awesome!
Alcapone263 said:
thanks for the quick reply, glad to see everything is moving forward smoothly. can't wait for this feature to be fixed though, i'd sacrifice webtop/fingerprint scanner permanently if i could just get working HDMI mirroring
once again, thanks for all of your efforts in porting this awesome ROM! you guys are awesome!
Click to expand...
Click to collapse
Well if i was a betting man than id bet on the HDMI mirroring being done before those other 2 , but you never know, at this point Fingerprint is really held back by my limited time, i personally took on this part of the equation and I have been the one slacking as this is the busiest time of the year for my RL. anyhow like I said enjoy it, try it, test it, or hate on it either way its going to be made available and will continue to be improved... now im going to bed so you guys have a good night.
**** Side note***
This is the tone I wish to keep for this thread, currently it is friendly and the questions that are being asked are polite and reasonable. My self and the other team member's will do our best to respond to any reasonable questions like those posted so far. How ever My self and others will not hesitate to report comments and or close the thread if it can not be kept like this!! What is going on so far here is pleasant and I appreciate it so please keep it UP!! If its just a thank you or a cheer on hit the thanks button or the donate button because while I own a beer store it still is neither free nor cost effective to ship the other gentleman on the team beer. Besides those options will keep the thread clean for important questions and updates, thanks again guys and if you want to talk smack open a new thread in general we might not like it but im sure well read it just the same
t0dbld said:
Well if i was a betting man than id bet on the HDMI mirroring being done before those other 2 , but you never know, at this point Fingerprint is really held back by my limited time, i personally took on this part of the equation and I have been the one slacking as this is the busiest time of the year for my RL. anyhow like I said enjoy it, try it, test it, or hate on it either way its going to be made available and will continue to be improved... now im going to bed so you guys have a good night.
**** Side note***
This is the tone I wish to keep for this thread, currently it is friendly and questions are being asked and my self and the other team member's will do our best to respond to any reasonable questions like those posted so far. How ever My self and others will not hesitate to report comments and or close the thread if it can not be kept like this!! What is going on so far here is pleasant and I appreciate it so please keep it UP!!
Click to expand...
Click to collapse
seriously, if i can just get my HDMI mirroring this phone with CM7 will last me forever. all i need is my emulators on my big screen in the landscape mode.
do you personally know if there is anything in the photon files that leads us in the right direction? or is it just a fluke that flashing the alien ROM on our phones worked?
every little bit helps how ever if it was narrowed down that far..... well we would more than likely have it working
t0dbld said:
every little bit helps how ever if it was narrowed down that far..... well we would more than likely have it working
Click to expand...
Click to collapse
well, thanks for taking the time to answer my questions, i really appreciate it. easier to wait now that i know top men are working on it.
t0dbld said:
every little bit helps how ever if it was narrowed down that far..... well we would more than likely have it working
Click to expand...
Click to collapse
Sms delivery reports doesn't work yet
Sent from my MB860 using xda premium
help
to flash cm7 beta4 xong thi gap loi voi 4 phim co ban.ban nao biet cach khac phuc lam on chi cho toi.
thank all.
It's jelly time. Made by a TPT user for TPT users.
Notice
Developed on a WE/16Gb 3G TPT. US, UK and ROW Tablets (any size) are confirmed to work, too
Density set to 160 dpi to keep market compatibility. Don't like to do this but the market problems are just annoying. Change it with a appropriate app if you don't like it (btw. our native density is approximate 150 dpi).
Flash on your own risk! Might turn your TPT into a expensive chopping board.
Requirements
This build uses the Lenovo ICS kernel, you need to upgrade to stock ICS first (Make sure you keep root!)
A ICS ClockworkMod version like this one.
Screenshots
here (Thanks obscure.detour)
Installation
Download ROM zipfile (and 3G patch if you want to) and put it on a sd-card
Boot into CWM (Reboot and press Vol+)
Make a nandroid backup in CWM!
Make sure the backup worked!
Full Wipe (May not be needed if you come from an earlier CM10 version)
Flash zip in CWM
Optional: Flash 3G patch in CWM
reboot
Restore Stock ICS
Boot into CWM (Reboot and press Vol+)
Restore old nandroid backup
Additional Steps
If you have problems with random reboots or sleep of death try to change wifi to "always on". You can find it in: settings->wifi->"click the 3 dots in the upper right"->advanced->keep wifi on during sleep
If you want to use NotesMobile you want to look here: http://forum.xda-developers.com/showthread.php?p=34649207#post34649207
If you have problems with wiping (just doesn't work) and want to reformat the data partition, use this zip in CWM: http://ubuntuone.com/4zKT1jqeqhR8qdGh2y4TaM (WARNING: THIS WILL REFORMAT DATA, THAT INCLUDES YOUR INTERNAL SDCARD!)
Working:
Wifi
Touchscreen + Stylus
Bluetooth
HW Graphic Acceleration
Sound (Including Mic)
Cameras Front/Back
Compass (but needs calibration)
HW Video encoding/decoding (i.e. for Youtube HQ)
Mount as USB/MTP for filetransfer (in windows)
GPS (Well "working" like always nearly unusable but its working theoretically)
Lightsensor and other sensors
3G (Ericsson card)
3G (Gobi card)
HDMI
Stylus
Buttons
Not Working
Nothing here anymore. Everything is working somehow but some parts still contain bugs (see buglist)
Known Bugs
Google maps crashes sometimes
3G issues:
- On some devices the carrier is not shown and 3G needs more time to connect
Wifi tethering not working
Stylus only mod not changeable in lockscreen
Some other bugs that occur only on few devices
Things maybe added in future releases
A density of 150dpi (a soon as i find a good hacked market or something else)
Getting everything to work and stable
Thanks
The Cyanogenmod team
Everyone releasing their source codes for other builds
Everyone trying to find and report bugs
pwstein for lending me his gobi card
If you like this ROM press the donate button and smash your hand on the NumPad :fingers-crossed:
Download
see this post -> http://forum.xda-developers.com/showpost.php?p=53241085&postcount=788
Sourcecodes
Device Tree
Framework patches
Kernel
Changelog
Code:
[B]Version 0.9.2 [/B]
- Same as 0.9.1 but with older wifi drivers
[B]Version 0.9.1 [/B]
- Fixed stylus only mode again
- Fixed touchinput for some games/apps
[B]Version 0.9[/B]
- Switched to CM10 Stable Branch
- Newer WIFI driver
- Other things I might have forgoten
[B]Version 0.8.1 (3G Patch)[/B]
- Combined ericssion and gobi patch
- Bluetooth tethering
[B]Version 0.8.1[/B]
- Android 4.1.2
- Stock kernel again for the time beeing
- New Stylus only mode (again use the browser button)
- Confirmed working bluetooth pan (tested with internet connection of galaxy nexus)
[B]Version 0.8 (Experimental)[/B]
- Fixed Camera + Picasa
- Added Stylus only mode (oops: Right now its a no input mode, needs to be fixed)
- Added recovery to reboot options (Upgrade to CWM 6 first, if you want to use this!)
- Changed Kernel:
Additional Filesystem support (NTFS, CIFS)
Overclocking up to 1.7GHz (disabled by default)
[B]Version 0.7.1 (3G Patches)[/B]
- Added missing apn.conf
[B]Version 0.7[/B]
- Reverted some changes to dalvik cache that seem to make trouble
- Added experimental support for Gobi 3G card
- Checked hdmi (seems to work fine here)
[B]Version 0.6[/B]
- Fixed front cam
- Autorotation button official working (and all other buttons)
- Switched Gallery app for picasa sync
- Some minor bugfixes
[B]Version 0.5 (3G Ericsson)[/B]
- Added 3G patch for wifi-only rom
- Read new installation instructions!
[B]Version 0.5 (wifi-only)[/B]
- A wifi-only version (without sms app or cell indicator)
[B]Version 0.4[/B]
- Fixed 2G/3G Problem -> Ericsson card is working now
[B]Version 0.3[/B]
- Fixed GPS
- Fixed Lightsensor
- Some minor bugfixes
- Added experimental(!!!) support for Ericsson 3G (i.e. WE devices)
[B]Version 0.2[/B]
- HW Video decoding fixed -> i.e. youtube HQ
- HW Video encoding fixed -> taking videos with the cam
[B]Version 0.1[/B]
- First release
Amazing! I cannot thank you enough for your continued work Koshu.
Doing a nandroid and testing now. No reason it should not work on a US-based tablet, correct?
Also, any chance we could get an MD5 checksum? Sorry, I'm kind of crazy
obscure.detour said:
Amazing! I cannot thank you enough for your continued work Koshu.
Doing a nandroid and testing now. No reason it should not work on a US-based tablet, correct?
Also, any chance we could get an MD5 checksum? Sorry, I'm kind of crazy
Click to expand...
Click to collapse
Should work. WE, US and UK are pretty much the same devices except the 3G card. I'm just curious if this ROM works also on ROW.
Will test in the morning long day of college and work, need to sober up before I tackle this. Thanks for the Jelly Bean up date.
This ROM is running amazingly well. Everything I do, it does it fast and smoothly. Project Butter truly stands out here. Never has this tablet felt so buttery smooth.
I even installed Major Mayhem to try a game out and I feel like it ran better than the official ICS build (OTA3).
Google Now works. USB drive and mouse worked fine. Pen works fine in Lecture Notes and Quill. The pen button does not work in Quill though, pretty sure it has something to do with the way Quill detects the active pen. Sound works, video works as long as it is SD.
Other than that I'll leave you all with these screenshots.
Great job Koshu and thank you!
obscure.detour said:
This ROM is running amazingly well. Everything I do, it does it fast and smoothly. Project Butter truly stands out here. Never has this tablet felt so buttery smooth.
I even installed Major Mayhem to try a game out and I feel like it ran better than the official ICS build (OTA3).
Google Now works. USB drive and mouse worked fine. Pen works fine in Lecture Notes and Quill. The pen button does not work in Quill though, pretty sure it has something to do with the way Quill detects the active pen. Sound works, video works as long as it is SD.
Other than that I'll leave you all with these screenshots.
Great job Koshu and thank you!
Click to expand...
Click to collapse
You have really nice hand writing on the last screenshot.
This is awesome, and just in time as school is approaching . Can't wait to try it out .
Koshu keep up the good work, this is amazing. expect a donation once I get this loaded.
If someone get's it up on a ROW Tablet, please advise!
DiJu519 said:
You have really nice hand writing on the last screenshot.
This is awesome, and just in time as school is approaching . Can't wait to try it out .
Koshu keep up the good work, this is amazing. expect a donation once I get this loaded.
If someone get's it up on a ROW Tablet, please advise!
Click to expand...
Click to collapse
You have a ROW tablet? Please let me know if this works and if it doesn't (i assume it won't even boot in this case) send me a copy of your boot.img. As i didn't need to modify the kernel itself (compared to ICS with the HC kernel) we could just try to switch the kernels and see what happens.
obscure.detour said:
This ROM is running amazingly well. Everything I do, it does it fast and smoothly. Project Butter truly stands out here. Never has this tablet felt so buttery smooth.
I even installed Major Mayhem to try a game out and I feel like it ran better than the official ICS build (OTA3).
Google Now works. USB drive and mouse worked fine. Pen works fine in Lecture Notes and Quill. The pen button does not work in Quill though, pretty sure it has something to do with the way Quill detects the active pen. Sound works, video works as long as it is SD.
Other than that I'll leave you all with these screenshots.
Great job Koshu and thank you!
Click to expand...
Click to collapse
Project butter is one pf the main reasons i want to get JB on the TPT^^ it's really awesome. Thanks for the screenshots, If you don't mind i would like to post a link to your post in the OP in case someone wants some.
Nice Job Koshu!!:good: will give it a try when i get clockwork up and running.. :fingers-crossed:
US TPT 16GB 3G with 32GB sd card
Very nice work, Maybe I should give it a try .
Koshu said:
Project butter is one pf the main reasons i want to get JB on the TPT^^ it's really awesome. Thanks for the screenshots, If you don't mind i would like to post a link to your post in the OP in case someone wants some.
Click to expand...
Click to collapse
Absolutely, feel free to share the pics. It is running super smooth I am absolutely loving it so far. Now I've got JB CM10 on both of my devices!
Also, I have noticed Chrome runs really great. About a thousand times better than ICS (OTA3). Gets a little slow sometimes with 15-20+ tabs but that is to be expected with our aged hardware.
Another note: I use CSipSimple, it allows me to use SIP in combination with a PBX server (Pbxes.org) for WiFi calling on my phone. I have never been able to get it to work with any Lenovo ROMs. Well it works on this ROM! I can now make/receive calls with my tablet using WiFi. I know many don't know or even care what this is, but just wanted to share my excitement.
Working well here too. Although I get cell phone indicator in my tray
mandrsn1 said:
Working well here too. Although I get cell phone indicator in my tray
Click to expand...
Click to collapse
Yeah I forgot to mention that. You need to enable Airplane mode and then enable WiFi. Although, because I use it on my phone as well, I've been using an app called AutoAP. It automatically enables airplane mode when using a saved WiFi network. For some reason it says it isn't compatible with our tablet in the Play Store. It is literally the only app I could find that wasn't "compatible". It works fine if you sideload it. Download here.
Since this and the few other issues being the GPS(it never worked anyway), HW acceleration for HD playback, and the light sensor I haven't found any reason for it to not be my daily driver.
Cheers.
Omg wow! I need to dig out my TPT!!
US 32GB TPT and loving Jelly Bean can't wait to see were this goes from here. Thanks for all the hard work with JB and CWM.
New version released
Koshu said:
New version released
Click to expand...
Click to collapse
Awesome! HQ video decoding and recording! You are truly a gentleman. Cannot wait to try it out. When my school expenses subsides I'll be donating to you.
Also, you may link directly to the images using the imgur link if you want instead of linking to my post. http://imgur.com/a/r0Iq2 I could also embed them in the 2nd post if you would like.
EDIT: Build v0.2 seems to be fine. HQ videos do indeed work in YouTube. I was even able to get a 720p (mkv) encoded video streaming over WiFi. Works flawlessly (24fps).
Koshu, is there a foreseeable future for 3G in your CM10 builds for TPT?
I'm just curious if it's a hurdle you have hopes in clearing. I'm running a GOBI3000 and paying for a data plan that I'm trying to get the most out of.
BTW, I've got my TPT heading back for service and I'm crossing my fingers for an OTA 2.5 system upon return. Get my root back...
Koshu said:
You have a ROW tablet? Please let me know if this works and if it doesn't (i assume it won't even boot in this case) send me a copy of your boot.img. As i didn't need to modify the kernel itself (compared to ICS with the HC kernel) we could just try to switch the kernels and see what happens.
Click to expand...
Click to collapse
It works also on a ROW tablet!
Good work, thanks! Keep it up!
obscure.detour said:
Awesome! HQ video decoding and recording! You are truly a gentleman. Cannot wait to try it out. When my school expenses subsides I'll be donating to you.
Also, you may link directly to the images using the imgur link if you want instead of linking to my post. http://imgur.com/a/r0Iq2 I could also embed them in the 2nd post if you would like.
EDIT: Build v0.2 seems to be fine. HQ videos do indeed work in YouTube. I was even able to get a 720p (mkv) encoded video streaming over WiFi. Works flawlessly (24fps).
Click to expand...
Click to collapse
Changed the link.
pwstein said:
Koshu, is there a foreseeable future for 3G in your CM10 builds for TPT?
I'm just curious if it's a hurdle you have hopes in clearing. I'm running a GOBI3000 and paying for a data plan that I'm trying to get the most out of.
BTW, I've got my TPT heading back for service and I'm crossing my fingers for an OTA 2.5 system upon return. Get my root back...
Click to expand...
Click to collapse
I think i try fixing 3G next as the other parts are more or less minor problems (gps more, lightsensor less). But i don't have a gobi card but an ericsson, so i will start with the ericsson card to get a grip on this and after the ericsson card is working we could give gobi gobi a try. But this includes a lot of testing and i will need someone with a gobi device to help me out.
mari8b said:
It works also on a ROW tablet!
Good work, thanks! Keep it up!
Click to expand...
Click to collapse
Ah great, then lenovo finally uses a similar kernel for both devices, meaning i can play around with the kernel a bit (would like to add cifs and nfs support, maybe even overclocking some day).
http://www.androidpolice.com/2012/11/13/breaking-android-4-2-being-released-to-aosp/
I know, it's just out so we can't be sure of anything. But I was wondering if CM11 was planned for the 10.1v if it doesn't ask for too much efforts. It's a 4.x update so I would guess it won't break a lot of things. But who knows. The CM10 are still considered experimental after all although they are quite stable, so it might not happen officially ?
So many questions, so much patience to have that I don't...:laugh:
DannyBiker said:
http://www.androidpolice.com/2012/11/13/breaking-android-4-2-being-released-to-aosp/
I know, it's just out so we can't be sure of anything. But I was wondering if CM11 was planned for the 10.1v if it doesn't ask for too much efforts. It's a 4.x update so I would guess it won't break a lot of things. But who knows. The CM10 are still considered experimental after all although they are quite stable, so it might not happen officially ?
So many questions, so much patience to have that I don't...:laugh:
Click to expand...
Click to collapse
I dont think that 4.2 is going to be CM11. Its still Jelly bean after all. I think that our only hope is that its as simple as updating the sources used to compile CM10. Then theoretically it should just slot right in there, the way that 4.1.2 did (although I dont know the actual required work in getting our device from 4.1.1 to 4.1.2), and then hopefully Pershoot could just run a new experimental build for us. Im loving his last CM10 experimental by the way. I dont seem to be having any of the previously mentioned issues.
However, with the age of our device getting closer to two years, Pershoot has been a godsend (along with isimobile and also Seo's coding work previously), but I couldnt ask him to move onto the hassles of a whole new version for us, especially if its not a simple change.
Yeah, if updating to 4.2 would ask too much work, at least to get a stable release, I wouldn't mind that all the effort are focused on bringing a final 4.1 rom for the tab and end development for it. If 4.2 is possible, that'd be great but I guess it would be the last version for us.
All in all, we won't ever be grateful enough for what you do for us pershoot. I know you don't want donations, so I'll just donate to CM instead...
4.2 has changes in Surface Flinger to support multiple screens. I made quick build for P3 and out of the box 4.2 is not compatible with current Nvidia binaries, surface flinger hangs at "create window surface". So unless we can mend 4.2 surface flinger to work with ICS nvidia binaries, this could be end of the road for Tegra 2 devices. Since Google ditched Xoom, hope is even smaller... Other option would be port 4.1.2 Surface Flinger to 4.2....could be useful for other devices though...
Well I just hope then we'll be able to implement some content of 4.2 like the lockscreen, the timer app or the multi-account feature...:good:
with some hacks in Surface Flinger, I actually managed to get surfaces flinger initialized, and now boot animation is working so there might be still chance .... it crashed later on in multimedia though, so still plenty of work.
But yeah, would be nice to back port some 4.2 things, though it might be easier to move 4.1 surface flinger to 4.2, at least if graphic drivers proof to be main issue for upgrade...
Any idea on how simple users like me can help beside beta-testing when the time will come ? Are there devices that we might need to check out as they may help us with this port ?
Thanks !
EDIT : also, I imagine that after some point, you'll share your work with pershoot.
OndraOrg said:
with some hacks in Surface Flinger, I actually managed to get surfaces flinger initialized, and now boot animation is working so there might be still chance
Click to expand...
Click to collapse
Can you tell me what you've changed?
But yeah, would be nice to back port some 4.2 things, though it might be easier to move 4.1 surface flinger to 4.2, at least if graphic drivers proof to be main issue for upgrade...
Click to expand...
Click to collapse
I don't think that this will be easy. There are so much changes in surfaceflinger 4.2, especially the interface has changed. You would have to port the hwcomposer interface from 4.1, but leave the rest of the interface unchanged. Otherwise the rest frameworks/native breaks.
C-o-M said:
Can you tell me what you've changed?
New surface flinger was not loading grallock component at all. So I added in display device call to load grallock, then attempt to create main window surface succeeds. I also tweak api version bit, to accept current version, though I don't think that was the issue, grallock was the main problem. But I can't really confirm if this is enough, since there are more crashes along the line in other components, so all I can see is android boot animation. But surface flinger composition must be working to some degree. And there are no more obvious errors from Surface Flinger.
Now problem is in Audio flinger, which is another component quite modified, it makes some calls to audio_policy.tegra.so with ilegal parameters. So similar issue as with graphics. I commented out this call, but then Dalvik VM crashed with some weird error. Let's see when I have more time.
I don't think that this will be easy. There are so much changes in surfaceflinger 4.2, especially the interface has changed. You would have to port the hwcomposer interface from 4.1, but leave the rest of the interface unchanged. Otherwise the rest frameworks/native breaks.
Click to expand...
Click to collapse
Agree here. My motivation for surface flinger port was a) this effort could be useful also for other devices which were left behind for 4.2 upgrade. b) while new Surface Flinger has many changes, lot of them are related to new multi screen functionality. That could be stubbed on api level (binder interface doesn't actually have that many changes). I bet many ppl would prefer to have 4.2 functionality, and loose HDMI functionality.
Problem I can see is that we don't know how many components we would need to port like this. Seeing now crashes in Audio Flinger, this can be lot bigger issues. There is new bluetooth stack in 4.2, replacing Bluez. If those close code binaries are using Bluez and same api does not exist in 4.2, we're in trouble.
OndraOrg said:
New surface flinger was not loading grallock component at all. So I added in display device call to load grallock, then attempt to create main window surface succeeds. I also tweak api version bit, to accept current version, though I don't think that was the issue, grallock was the main problem. But I can't really confirm if this is enough, since there are more crashes along the line in other components, so all I can see is android boot animation. But surface flinger composition must be working to some degree. And there are no more obvious errors from Surface Flinger.
Click to expand...
Click to collapse
Thanks. I'll try do redo that.
C-o-M said:
Thanks. I'll try do redo that.
Click to expand...
Click to collapse
Let me know if it works for you, or I can share code...
C-o-M said:
Thanks. I'll try do redo that.
Click to expand...
Click to collapse
Actually it is working! Sorry I have just hour a day to play with this, that's why sporadic progress. Anyway after stubbing audio flinger and one call in dalvik, I managed to boot it. It's not usable since, since phone app crash report is all the time in the front. But UI is there. So that hack from surface flinger seems to be work after all
OndraOrg said:
Actually it is working! Sorry I have just hour a day to play with this, that's why sporadic progress. Anyway after stubbing audio flinger and one call in dalvik, I managed to boot it. It's not usable since, since phone app crash report is all the time in the front. But UI is there. So that hack from surface flinger seems to be work after all
Click to expand...
Click to collapse
That's awesome. Do you have a diff for me? Or even a git?
Slightly edited the title as you started messing around with it, although we all know it's just "to see where's it going" for now...
C-o-M said:
That's awesome. Do you have a diff for me? Or even a git?
Click to expand...
Click to collapse
Need to still sort one thing about status bar, whole UI is in phone mode (status bar with soft keys in the middle, and notification bar at the top) and then I can share install package. Ui and wifi works fine, bluetooth and audio does not work. And I still have some issue with storage mapping. This has now new layout thanks to multiuser support.
OndraOrg, I think you need to read a bit about 4.2 : Tablet UI is gone, Phone UI has been pushed to all Android devices.
See this : http://www.androidpolice.com/2012/1...just-like-a-giant-phones-and-thats-fantastic/
OndraOrg said:
Need to still sort one thing about status bar, whole UI is in phone mode (status bar with soft keys in the middle, and notification bar at the top) and then I can share install package. Ui and wifi works fine, bluetooth and audio does not work. And I still have some issue with storage mapping. This has now new layout thanks to multiuser support.
Click to expand...
Click to collapse
I'm not interested in the install package. I'd like to get the source code to experiment on my tab 8.9.
C-o-M said:
I'm not interested in the install package. I'd like to get the source code to experiment on my tab 8.9.
Click to expand...
Click to collapse
OK I will clean code and get you diffs.
C-o-M said:
I'm not interested in the install package. I'd like to get the source code to experiment on my tab 8.9.
Click to expand...
Click to collapse
Here are my patches.
Dalvik patch will get you around storage issue in vm. You can remove it once you fix your boot image
framework-av will patch you crash with audio, though it will make audio not to work. Not sure if you will need this for your 8.9 tab
framework-native will patch you surface flinger, so it works with old binaries
OndraOrg said:
Here are my patches.
Dalvik patch will get you around storage issue in vm. You can remove it once you fix your boot image
framework-av will patch you crash with audio, though it will make audio not to work. Not sure if you will need this for your 8.9 tab
framework-native will patch you surface flinger, so it works with old binaries
Click to expand...
Click to collapse
Nice. Thought it was more to change.
PCM 10.1
CyanogenMod 10.1 & PDroid 2.0
What is this?
It's very easy to answer that. PCM is a new initiative I want to begin that brings to the masses the privacy and protection of PDroid. Instead of reaching only a very little user base, PCM will serve completely unmodified CyanogenMod builds with the PDroid framework applied. There will be no need for the end user to patch sources or go through the hassle of compiling CyanogenMod. And by the way, building ROMs is bad for the environment!
Starting with my own device, the Sony Xperia Z, I will publish the ROMs I build for myself on an unregular basis. Most likely when there are new RC or M builds of CyanogenMod or when there is a new version of PDroid. I actively use them myself, so I'll know when, however unlikely, a bug apart from the CM bugs has made it into PCM.
This is not limited to PDroid 2.0. Some of you users may be aware of the ongoing merge of PDroid 2.0 into OpenPDroid. When I feel like the time is right, PCM will switch to OpenPDroid. Looks like it's not going to happen.
A later goal of PCM is to have a completely automatic buildbot that builds weekly, RC, M and stable versions for a variety of CyanogenMod 10.1+ supported devices.
How do I download?
All downloads will be served through BitTorrent by me. I strongly believe that BitTorrent is the best distribution method for a community driven project and I will not serve direct downloads. It has error correction, is resumable and can serve people with slow and unstable connections as well as people with fast and stable connections (which should stay to seed).
You can download the latest version here: cm-10.1-20130527-PDroid2.0-1.57-yuga.
All torrents are attachments of this post, so you can always grab an older version from the archive.
Don't forget to grab the PDroid 2.0 manager application: PDroid 2.0 Manager.
It will also be available in the Play Store very soon.
How is it named?
The naming scheme is almost the same as for CyanogenMod. The difference is that the string UNOFFICIAL ist replaced by <pdroid_framework>-<version>, e.g. PDroid2.0-1.57 or maybe in a future version OpenPDroid-1.0.1.
Now you can safely install that game from the Play Store you always wanted to try, but didn't because the developers want to spy on you.
Subscribe to this thread and to the PDroid 2.0 thread and stay up to date.
Enjoy!
Changelog:
2013-05-27:
No changes regarding PDroid 2.0.
Compiled with latest CyanogenMod 10.1. For CM 10.1 changes see CM 10.1 changelog.
Reserved.
xelra said:
PCM 10.1
CyanogenMod 10.1 & PDroid 2.0
What is this?
It's very easy to answer that. PCM is a new initiative I want to begin that brings to the masses the privacy and protection of PDroid. Instead of reaching only a very little user base, PCM will serve completely unmodified CyanogenMod builds with a PDroid framework applied. There will be no need for the end user to patch sources or go through the hassle of compiling CyanogenMod. And by the way, building ROMs is bad for the environment!
Starting with my own device, the Sony Xperia Z, I will publish the ROMs I build for myself on an unregular basis. Most likely when there are new RC or M builds of CyanogenMod or when there is a new version of PDroid. I actively use them myself, so I'll know when, however unlikely, a bug apart from the CM bugs has made it into PCM.
This is not limited to PDroid 2.0. Some of you users may be aware of the ongoing merge of PDroid 2.0 into OpenPDroid. When I feel like the time is right, PCM will switch to OpenPDroid.
A later goal of PCM is to have a completely automatic buildbot that builds weekly, RC, M and stable versions for a variety of CyanogenMod 10.1+ supported devices.
How do I download?
All downloads will be served through BitTorrent by me. I strongly believe that BitTorrent is the best distribution method for a community driven project and I will not serve direct downloads. It has error correction, is resumable and can serve people with slow and unstable connections as well as people with fast and stable connections (which should stay to seed).
You can download the latest version here: cm-10.1-20130520-PDroid2.0-1.57-yuga.
All torrents are attachments of this post, so you can always grab an older version from the archive.
Don't forget to grab the PDroid 2.0 manager application: PDroid 2.0 Manager.
How is it named?
The naming scheme is almost the same as for CyanogenMod. The difference is that the string UNOFFICIAL ist replaced by <pdroid_framework>-<version>, e.g. PDroid2.0-1.57 or maybe in a future version OpenPDroid-1.0.1.
Now you can safely install that game from the Play Store you always wanted to try, but didn't because the developers want to spy on you.
Subscribe to this thread and to the PDroid 2.0 thread and stay up to date.
Enjoy!
Click to expand...
Click to collapse
This looks good ! I want to wait until we get a stable release though. I see RC was a few days ago so Stable won't be far behind hopefully :fingers-crossed:
defsix said:
This looks good ! I want to wait until we get a stable release though. I see RC was a few days ago so Stable won't be far behind hopefully :fingers-crossed:
Click to expand...
Click to collapse
Well, it works almost perfectly. There are a few bugs. For example, when you press the loadspeaker button during a call, it won't do anything but disable your internal speaker. So don't press it.
I haven't noticed any other bugs.
What annoys me is that the delay for waking the device up is quite long.
Idle battery life is amazing. I had it lying here idly while I was compiling the ROM and I've lost about 5% / day. That's 20 days standby. The screen drains the battery very fast though. Much faster than it does on stock ROMs. So there's room for improvement there.
Thank you for your feedback.
xelra said:
Well, it works almost perfectly. There are a few bugs. For example, when you press the loadspeaker button during a call, it won't do anything but disable your internal speaker. So don't press it.
I haven't noticed any other bugs.
What annoys me is that the delay for waking the device up is quite long.
Idle battery life is amazing. I had it lying here idly while I was compiling the ROM and I've lost about 5% / day. That's 20 days standby. The screen drains the battery very fast though. Much faster than it does on stock ROMs. So there's room for improvement there.
Thank you for your feedback.
Click to expand...
Click to collapse
I have a stable release on my Xperia Neo - It's an unbelievable upgrade from what I had on it before (stock ICS from NeoV) . I can't get over the battery life. 2 days standby and only 4% battery used !!
New version, OP updated!
2013-05-27:
No changes regarding PDroid 2.0.
Compiled with latest CyanogenMod 10.1. For CM 10.1 changes see CM 10.1 changelog.
There are lots of kernel related updates.
Enjoy!
Still Nightlies though? I checked for a Stable release and didn't see it today.
And still the speaker phone bug too?
Sent from my Brain via my Keyboard on my Xperia Z
defsix said:
Still Nightlies though? I checked for a Stable release and didn't see it today.
And still the speaker phone bug too?
Sent from my Brain via my Keyboard on my Xperia Z
Click to expand...
Click to collapse
I haven't had a chance to test for the speakerphone bug, yet. It's very stable though. I use it as my daily driver and I really use it a lot for work. Didn't have a single problem, yet. Apart from the speakerphone bug that is.
But I am aware of 1 other bug that seems to be introduced by PDroid. In the mobile data screen, the button to limit data usage disappears.
xelra said:
I haven't had a chance to test for the speakerphone bug, yet. It's very stable though. I use it as my daily driver and I really use it a lot for work. Didn't have a single problem, yet. Apart from the speakerphone bug that is.
But I am aware of 1 other bug that seems to be introduced by PDroid. In the mobile data screen, the button to limit data usage disappears.
Click to expand...
Click to collapse
Thanks, I'm still thinking about it. I'm not sure I'll live without the Sony apps
Sent from my Brain via my Keyboard on my Xperia Z
Code:
[B][I][U][COLOR="Red"]WARNING![/COLOR][/U][/I][/B]
This is an ALPHA build. Everything is being worked up to come up to speed as
quickly as possible to be with its CM brother. Just be patient and all will
come in due time. But hey, at least is boots up into the system ... LOL
This is an UNOFFICIAL build of SlimKat (although built from offical SlimRom source) and by NO means is this my ROM. I am just compiling from SlimRom Source and credits go to elelinux, xda-garwyn, albinoman and all other coders who contributed to CyanogenMod device tree.
Code:
For which devices. The ROM should work with all klte versions that are qualcomm
chipsets.
Included in the build are:
kltexx,kltelra,kltetmo,kltecan,klteatt,kltedv,klteub,klteacg,kltedcm,klte
(UNOFFICIALLY SUPPORTED): kltespr,kltevzw,klteusc
Code:
IMPORTANT
* DO NOT expect daily builds. I'll build when I'm free.
* DO ask for support in this thread.
* DO NOT use this unofficial build and ask for support at the official threads.
* DO NOT be rude.
* RESPECT all users
* If u see a NOOB question and u don't feel like replying, DON'T, just ignore
that post. If u do reply, good for u.....and be nice in your reply.
Code:
[B][U]WORKING[/U][/B]
Audio
WiFi
Google Now
Bluetooth
GPS
Video playback
Audio playback
Code:
[B][U]NOT WORKING[/U][/B]
Service
Data
Calls
MMS
Hard keys
Camera
Internal/External SDcard mounting
Code:
[B][U]INSTALLATION[/U][/B]
Do NOT use superwipes
Wipe data, cache, and dalvik cache
* ((do not report bugs if you didn't full wipe))
Flash ROM
Flash GAPPS
Reboot
Report anything that is an issue
As of right now I have no way of testing NFC or IR Blaster, so I do not know if they are working on this build or not. Also on this build there is the infamous red box that appears when moving from screen to screen or app. I am going to fix that either today or tomorrow and then post the new build. The reason there is no data or cell reception is due to the APN list which will also be fixed in the next build.
I tested this on my T-Mobile G900T, so if others can please report back on their experience with this ROM on other devices that would be greatly appreciated and I will get those issues resolved as soon as possible. Thank you.
Code:
[B][U]DOWNLOADS[/U][/B]
ROM: [URL="http://d-h.st/2e0"]SlimKat 4.4.4 (QComm)(ALPHA 1)[/URL]
GAPPS: [URL="http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4"]Click me to pick your poison[/URL]
Great I'll try it out. I've 900F BTW
Thank you. Just remember what is working and what is not working please.
lunerceli said:
Thank you. Just remember what is working and what is not working please.
Click to expand...
Click to collapse
BTW, what the thing that you want me to report?
Just if it boots and the working list is working on your version please.
lunerceli said:
Just if it boots and the working list is working on your version please.
Click to expand...
Click to collapse
Slim minimal gapps.
1st edit: It's booting.
2nd edit: back key, home button and recent/menu key not working? Get NavBar. I like this!
3rd edit: Setting slow to response
4th edit: Stock camera has stopped. Google camera work but need to insert USB storage.
5th edit: Stock Music player not playing
6th edit: USB storage not mounted so can't test out audio/video but ringtone ringing at audio setting.
That's the issues at the moment besides of known issues. I guess i've to restore my backup now. Waiting for your new build thank you.
Ok. Thank you. I will get all of the issues fixed asap.
I'll try it tomorrow but I am also using a sm-g900t so I won't shed much light on the issues/bugs list cause its most likely to be the same as @lunerceli. Still going to flash thou, lol
Thanks for sharing your build with us.
Sent from my SM-G900T
I read your other post in the SlimRoms thread and I'd like to help a bit if I could. I'm going to flash this in the next hour after backing up my memory cards and then I'll grab you some logcats of crashing apps to save you some looking. I know enough to help, but not enough to debug so you aim me at the logs that help you and I'll get you as much as I can.
I run a SM-G900T as well so we will have similar errors. Thank you for taking the time to do this, I really like all the slim roms.
Working: (Mini Gapps)
- Booted and completed setup (hung on "Welcome..." for a bit, it got through)
- Wi-Fi
- Bluetooth/Stereo Bluetooth
- GPS (Took a minute, but did lock with "Device Only" setting chosen)
- Customization Options working (battery color, statusbar transparency, quick tile settings)
- Statusbar brightness slider
- Volume and power buttons
- Real Dark Slim (hangs for a few seconds, but it succeeds)
- Camera works with third party app (Camera ZoomFX) but crashes when taking photo since it can't save to storage (16MP!)
- Headphones (Music stops when unplugged; nice!)
- Music
- Keyboard
- Navigation Bar/Pie Controls
- Dialer
- Root Permissions (had to enable prompt in settings, but it works)
- Secure Lockscreen (Pin Number)
- Normal Apps (Browser, Calc, clock, Dialer, Hangouts, etc.)
Not Working:
- Hardware buttons (Back, Home, Menu/Recents) Tried to run a logcat here, but Android doesn't even see these other than vibration
- No Signal
- Storage (Internal and external can't be accessed) Startup Media Scan Pastebin
- Auto-brightness (Cannot be enabled) Auto-Brightness Log Pastebin
- Occasional Red Rectangle
-NFC (This, once turned on, cannot be turned off and the logcat feedback is about NFC every 7-10 seconds) NFC Feedback Pastebin
Not going to lie, this isn't far from being not only usable, but a daily driver. I'm going to see if I can pull a log later on for Auto-brightness failing and also for startup and maybe see why storage isn't being recognized and mounted. The file system sees both storage cards, /storage/sdcard0 and sdcard1 are both in the root explorer of android tuner, I just get permission denied when I try to access them.
Edit: Ran fix permissions scripts to see if it would mount the memory for me, and it did not. Also, adjusted media scan to prompt and it still didn't find anything. I'm going to try to pastebin you a log for each of the above failing. Got to work on a school assignment first though
Thank you for your feed back bro. I was on 24 hour duty last night and just spent like an hour to bring everything up and build it. I am going to work on it Friday night when I get off of work and hopefully by the end of the weekend it will be daily driveable and I can move to the next project.
lunerceli said:
Thank you for your feed back bro. I was on 24 hour duty last night and just spent like an hour to bring everything up and build it. I am going to work on it Friday night when I get off of work and hopefully by the end of the weekend it will be daily driveable and I can move to the next project.
Click to expand...
Click to collapse
There is no rush, I just wanted to get you some feedback putting things through its paces. I still intend to get you those log files if you find them helpful.
Get some sleep, this project will being be there tomorrow and thanks for tackling this for everyone in the community.
Edit: I put the logs I could get from my device in the last post next to the items in the list. Some things I couldn't pull, but you may know how. Also, and as I mentioned in the post, watching the Logcat scroll every 7-10 seconds I see the NFC log I pasted for you there. Not sure what is causing it, but NFC is toggling itself on and off.
Like I said, no rush on this I just wanted you to have it when you got around to working on it. Now it's my turn to get some sleep and if you need me to pull a log under a certain condition just quote me here and I'll get whatever you need. I'm looking forward to the next test build
Thank you for all of the info bro. I should have the next build up some time Saturday afternoon and almost everything should be fixed. Its been a while since I have done this so I am a little rusty. It is almost like riding a bike. Lol.
Build two is being compiled right now as we speak. I fixed a few things in the code so hopefully everything will work like it should. HAHAHAHA
Okay, so build two keeps stopping and ending in a segmentation fault for the framework.apk... I think I may have fixed it, but really don´t know .. LOL .. keeping the fingers crossed.
lunerceli said:
Okay, so build two keeps stopping and ending in a segmentation fault for the framework.apk... I think I may have fixed it, but really don´t know .. LOL .. keeping the fingers crossed.
Click to expand...
Click to collapse
Awesome thanks for your work! I would gladly test it when it's finished. I came from the Skyrocket a week and a half ago so I am still getting used to the Galaxy S5, but I helped the OP there for SlimKat by testing and providing logs, so just let me know if there is anything I can help with.
Well, every time I get close to getting another build done something gets in the way. I lost my system and had to set it up again. Now whenever I sync the repo it keeps not finding some of the repo saying it can't connect. Lol
lunerceli said:
Well, every time I get close to getting another build done something gets in the way. I lost my system and had to set it up again. Now whenever I sync the repo it keeps not finding some of the repo saying it can't connect. Lol
Click to expand...
Click to collapse
We appreciate that you keep on keeping on and that you keep us updated with this. Developing isn't easy, if it were we would all be making our own ROMs. Whenever you get this build out there will be testers around waiting to flash it to their devices. Me included
Sorry I haven´t posted anything in a couple of days, but I lost my system again and had to start from scratch. Some times I really have VM´s, but on my laptop I take everywhere It is too much of a pain in the ass to install Linux on the side or even straight up.
Just to update though, I am compiling the 2nd build right now and everything is going smoothly. I had to replace some of the Slim files with those from CM just to get past some build problems. I do believe that I have corrected most if not all of the not working. I am waiting for it to finish compiling and test it out before I release it to you guys. I will put up the download link regardless so that you fine ladies and gentlemen can test what and see what is going on in the development. The reason that I like to do this is so that the community can see active development and to compile the lists of what is and is not working with the ROM. I know it is a different approach to other developers, but this is just how I do it. Without you guys we as developers cannot do our jobs correctly and get a working daily driven ROM. Thank you for your support.
Mods please delete this thread. I am merging with another thread of the same topic. Thank you.
Will this rom work on G900FD as it has a qualcom chipset?