Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a preview build of Android JellyBean 4.2 from AOSP source code based on the CyaogenMod device tree for Acer A700. I have made this build to gauge how difficult it would be to port JellyBean 4.2 to current devices.
Kernel Source Code: https://github.com/pawitp/android_kernel_acer_t30/tree/jellybean-next
Device Tree: None yet available (Only notable part: patch for TinyHAL: https://gist.github.com/4104332)
Downloads
ROM: http://goo.im/devs/pawitp/a700/a700_aosp_jb42_20121116.zip
Google Apps: Currently integrated due to lack of gapps package for 4.2
SuperSU: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip (Currently, only SuperSU is compatible with 4.2)
Installation
Note: due to new /data/media layout in 4.2 for multiple user support, your data in /data/media (/sdcard) will be moved to /data/media/0. This may cause problems in restoring backups in recovery, you may fix it by moving data /data/media/0 back to /data/media via adb in recover prior to restoring data.
Install CWM recovery from http://forum.xda-developers.com/showthread.php?t=1791165
Do a Nandroid Backup!
Install the ROM using ClockworkMod Recovery
Optionally install the Google Addon
Wipe data if coming from stock
Known Issues
Camera does not work
Bluetooth sometimes freezes bringing down Wi-Fi with it
Reporting Bugs
You are allowed to report bugs only in this thread. Note that this is a preview release and non-device specific bugs will not be accepted. The development of this preview will also cease once enough progress has been made in CyanogenMod.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
gonna grab this later
Wow! This ROM is awesome. Please make it more stable. And the Performance is not so good as other ROMs.
Webitu
Webitu said:
Wow! This ROM is awesome. Please make it more stable. And the Performance is not so good as other ROMs.
Webitu
Click to expand...
Click to collapse
For stability: Please report crashes as mentioned in the OP, without logs, there'd be no way to know what broke.
For performance: Please report where and how performance differs.
Note that generic "please make this better" report do not help, please be more specific.
Runs so far, unfortunately I can not get a wifi connection. 'm Back to 4.1 back.
Fooox1 said:
Runs so far, unfortunately I can not get a wifi connection. 'm Back to 4.1 back.
Click to expand...
Click to collapse
Next time, please get a logcat.
pawitp said:
For stability: Please report crashes as mentioned in the OP, without logs, there'd be no way to know what broke.
For performance: Please report where and how performance differs.
Note that generic "please make this better" report do not help, please be more specific.
Click to expand...
Click to collapse
Okay sorry. The launcher laggs sometimes and the Antutu benchmark results are not really good.
The GPU test results are 967 points. (3D = 674, 2D = 293)
The fps are 31. In the stock ROM i had 42 fps i think.
And i havn´t any crashes but it seems like its a little bit unstable but it can be also the apps who are not official for 4.2
But very good work! :good:
Sorry for my bad English.
Webitu
The graphic issue can't really be helped, Android 4.2 requires new graphic drivers and the current binaries used are optimized for the Nexus 7. As there are closed-source binaries, there is no way to modify them. The situation may change in the future as compatibility layers are introduced or new drivers are released.
pawitp said:
The graphic issue can't really be helped, Android 4.2 requires new graphic drivers and the current binaries used are optimized for the Nexus 7. As there are closed-source binaries, there is no way to modify them. The situation may change in the future as compatibility layers are introduced or new drivers are released.
Click to expand...
Click to collapse
Okay thank you. I already thought so. Hopely Acer brings a new Update with 4.2
Webitu
Nvidia is the same xxx as samsung (
Is A701 supported?
It will work on A701, but 3G will not work.
BTW, CM10.1 preview. Nearly everything working (including Camera, etc.). Nightlies should start soon and I'll make a new thread then.
http://goo.im/devs/pawitp/a700/cm-10.1-20121216-UNOFFICIAL-a700.zip
pawitp said:
It will work on A701, but 3G will not work.
BTW, CM10.1 preview. Nearly everything working (including Camera, etc.). Nightlies should start soon and I'll make a new thread then.
http://goo.im/devs/pawitp/a700/cm-10.1-20121216-UNOFFICIAL-a700.zip
Click to expand...
Click to collapse
Yeah. Big thanks for your work! I will try it out now. Did you recognized that when you set a wallpaper on CM10 only half of the wallpaper is used on the homescreen? Don`t know how to log this issue.
OCmylife said:
Yeah. Big thanks for your work! I will try it out now. Did you recognized that when you set a wallpaper on CM10 only half of the wallpaper is used on the homescreen? Don`t know how to log this issue.
Click to expand...
Click to collapse
It's due to our screen size and peculiar wallpaper handling, so the default wallpapers don't scale too well.
pawitp said:
It's due to our screen size and peculiar wallpaper handling, so the default wallpapers don't scale too well.
Click to expand...
Click to collapse
Yeah I`ve tried logcat in the terminal, before I read your command. It shows no error-message when I changed the wallpaper. But I think I could live with this one.
I`ve encountered one minor Issue. You could change the default page size in the trebutchet settings, but it doesn`t take effect on your pages on the homescreen. Yeah really minor issue, but otherwise I haven`t found a bug so far. But I will search further.
Again. CM 10.1 looks absolutely awesome on the Acer A700 and I would recommend everybody who has CWM on his A700 to try this one out. :highfive:
Has anyone tried twrp recovery on the A700? I`m frightened every time to flash on my A700, cause I experienced the freeze issue also(one time so far, after I switched from CM10 to Iconian 2.2).
Trying to install CM10.1 but until now only bootscreen for 20 mins :/
Edit: hmm almost 40 minutes -.-
Tried Wiping Data/System/Cache now, but still Bootscreen loading and loading..
Chris0706 said:
Trying to install CM10.1 but until now only bootscreen for 20 mins :/
Edit: hmm almost 40 minutes -.-
Tried Wiping Data/System/Cache now, but still Bootscreen loading and loading..
Click to expand...
Click to collapse
Use adb to get a logcat, it'll tell you what's wrong. Normally, it's caused by not wiping data when coming from a stock ROM, but since you've said that you've wiped data, maybe there's some other cause.
pawitp said:
Use adb to get a logcat, it'll tell you what's wrong. Normally, it's caused by not wiping data when coming from a stock ROM, but since you've said that you've wiped data, maybe there's some other cause.
Click to expand...
Click to collapse
Which command parameters should i use ? Its a load of text.
If i want to save the log in a file with the -f parameter i always get the error, that the output file couldnt be openend and that my filesystem is read-only ..
Chris0706 said:
Which command parameters should i use ? Its a load of text.
If i want to save the log in a file with the -f parameter i always get the error, that the output file couldnt be openend and that my filesystem is read-only ..
Click to expand...
Click to collapse
adb logcat > log.txt
Sent from my GT-I9000 using xda app-developers app
So now i got the logcat attached, hopefully you find the error..
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the HTC Aria, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0-Liberty
Download: link
Mirror: link
MD5sum: 006197debecd916dc8ce3feadea1e74a
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
hey, just want to say… GREAT JOB GUYS. YES, THANK YOU SO MUCH FOR THIS AWESOME ROM!!!
Looking good so far. Will post if I run into any issues. Glad I can finally have a stable build and not need to flash for a little while!
Thanks for all the effort.
Having issues with data. It worked fine for a while on the first boot but once I rebooted the phone, I can't get the phone to connect on data. Anyone having this issue, and most importantly how do I resolve it?
Other than that, amazing. Thanks for this great rom.
Edit: I looked into the access point name under the mobile network section and noticed a bunch of info was wrong. Notably the password was missing. I added the password and rebooted the phone and now everything is working fine. FYI the password is CINGULAR1.
android market wont let me download aanything!!! Please help!
_jfo_ said:
Having issues with data. It worked fine for a while on the first boot but once I rebooted the phone, I can't get the phone to connect on data. Anyone having this issue, and most importantly how do I resolve it?
Other than that, amazing. Thanks for this great rom.
Click to expand...
Click to collapse
No issues here.
supetawesomedude said:
android market wont let me download aanything!!! Please help!
Click to expand...
Click to collapse
Again, not any issues here.
supetawesomedude said:
android market wont let me download aanything!!! Please help!
Click to expand...
Click to collapse
clear data and reboot?
Installed over an old nightly fine, no problems whatsoever after a full day of use.
Nice work guys.
brswattt said:
clear data and reboot?
Click to expand...
Click to collapse
What the heck? It's workking first fine now!
thnxz. looking good
Hmm...i wanted to try using this "juwe" script but it won't boot...i'm assuming some sort of conflict with darktremor. I also wanted to go to S2E but the last time i tried to go from DT to S2E, everything went haywire and i had to restore an old back up because i rookishly forgot to make one before i started fuxing with S2E...hmph guess i'm stuck with 8-9-1 & DT...life goes on though...
zervic said:
Hmm...i wanted to try using this "juwe" script but it won't boot...i'm assuming some sort of conflict with darktremor. I also wanted to go to S2E but the last time i tried to go from DT to S2E, everything went haywire and i had to restore an old back up because i rookishly forgot to make one before i started fuxing with S2E...hmph guess i'm stuck with 8-9-1 & DT...life goes on though...
Click to expand...
Click to collapse
Your best bet would be to do a Titanium Backup of all user apps, install the ROM fresh, then install S2E, reboot, then restore the backups of user apps and your S2E transition is complete.
Sent from my Liberty using XDA Premium App
^^^ titanium is godly! S2E is worth it, imo. do a fix permission in ROM manager afterwards and a couple re-boots and bam! Butter smoothness
Anybody with the vibration mode not working when receiving calls? I turned vibrate on pretty much everywhere and yet when receiving call, the phone does not vibrate. However, it does vibrate when I receive a text message. Help!
Sent from my Liberty using XDA App
EDIT: I just toggled from the "Default" profile to "Work" and then back to "Default" and now it works. Strange...
Very legit! My girl loves Cynogen!
Almost did a battery pull on first boot. Coming from an older Nightly. Right as I was pulling off the backplate though, the screen went dim and the keys lit up, and everything loaded. So be patient guys on first boot.
My you guys have been busy. Very polished, so many new features.
Just came back to CM7 after about 3 mo. on the Sense ROM. I use GPS constantly, so I have been testing it extensively today. Happy to say Maps, Nav, and this geotagging app I have all work really well.
Zero problems so far, congrats!
Ok guys (and girls), here's a problem I've been dealing with for over a week now. Any help would be appreciated. I have been keeping up with the nightly builds and on nightly 213 and forward (including this stable release), I have found that my phone will stop receiving data after around 8 hours after a reboot. The only way for the data to work again is to reboot. This occurs on both mobile data (3G) and wifi connections. I have rolled back to nightly 208 and the problem doesn't occur. I have uninstalled all new apps since this started occurring, so I know it is not an application problem. I installed 7.1.0 stable with a full wipe, so that's not the problem. I don't think it is similar to the problem reported in post #4 of this thread because my Access Point information under Mobile network settings are the same in my working N208 as they are in the non-working 7.1.0. Also, neither version had a password, so following the directions in post #4 I put in the password CINGUALR1 on the 7.1.0 stable version, and the problem still persisted.
I am running DC's 8.9.1 and Juwe's RAM script, though I have been told neither of those could be the culprit.
Any suggestions, please?
something with your setup - have been running since last night and have not rebooted since and have had no connectivity issues at all.
What's the earliest nightly build that has the problem for you?
Did you format your system partition before the clean install?
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2 (JB), which is designed to increase performance and reliability over stock Android for your device.
Your warranty is now void.
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you
.
Although many things work, there is still a lot of things we need to work out and fix.
After we get everything working, then I will no longer be maintaining this thread. I will turn it over to anyone who wants it. Since I have so many other projects going on.
This thread is specifically targeted in fixing the issues.
Please prune and post your logcats to pastebin.com.
Please include what you did to recreate the issue at hand.
If you figure out a fix, please update us with exactly what you did.
Instructions
- Read known issues ans FAQs
- Copy GApps and CM10.1 ZIPs to your SDCard
- Boot into Recovery
- Wipe /cache, /system, /data, /dalvik
- Flash CM10.1 zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Wipe data of clock app
- Reset everything under Settings -> Date & Time otherwise editing alarms might cause FCs
source code for the t769
I will update source code weekly with upstream. I will update fixed issues as they occur.
Special thanks to:
ktempleton
j3r3
The donators (Please PM so I can add your xda user name instead of your real names...lol)
jparnell8839
Download Links and Changelog/issue tracker
Gapps
For radio issues check post #31 (thanks jparnell8839 )
For now, the date will determine the build/version number (look at the date which are the numbers before "UNOFFICIAL")
Mostly Official cm-10.1-20130922-UNOFFICIAL-t769.zip
Camera fixed
userdebug added to build type
RC cm-10.1-20130903-UNOFFICIAL-t769.zip
Changelog:
With WiFi now working, we can move to a release candidate
RC build
Fixed WiFi
Fixed intermittent gallery crash
Initial WIP build (Release candidate)
cm-10.1-20130729-UNOFFICIAL-t769.zip
Fixed intermittent audio void
Fixed sdcard mounts
Fixed usb/otg connection (must go to system settings/storage, tap menu key, select usb computer connection and change it to mass storage)
Bug tracker:
WiFi signal intermittently low
Camera still not working
GPS doesn't seem to get a lock (someone please test)
Testers, please update me. I still need feedback on bluetooth, video, etc...
I am tracking that radio, data, calls, mms/sms are all working fine.
FIRST
Edit: YES AHAHHAHA.
xWolf13 said:
FIRST
Edit: YES AHAHHAHA.
Click to expand...
Click to collapse
Really? lol... Like little kids in a candy store...lmbo!
thomas.raines said:
Really? lol... Like little kids in a candy store...lmbo!
Click to expand...
Click to collapse
Yup ahaha. Been refreshing this whole dev section once you posted "lets move to this to the dev section".
Thanks Thomas (':
http://goo.im/gapps/gapps-jb-20130301-signed.zip
Link for gapps 4.2.2
Sent from my GT-N7100 using xda app-developers app
lol great, now I need to download the new build and get fresh logcats!
as always, if you need a mirror, my server is open not the fastest, my ISP wont let me go any higher than 5mb/s, but it's stable
I'll download and start testing the build
Sent from my GT-N7100 using xda app-developers app
Clean flash, ran Black Hole and FSC before flashing.
ok, so I'm still getting spotty connectivity for data, keeps dropping, same thing as before in my post >>>here<<<
Bluetooth worked until I enabled debug, then it did not. Gallery did NOT work, until I enabled debug, then it did. Camera still crashes gallery. Torch still crashes. I cant pull a logcat because adb keeps saying device is offline. I'll try a reboot, see if that helps once I get home
jparnell8839 said:
Clean flash, ran Black Hole and FSC before flashing.
ok, so I'm still getting spotty connectivity for data, keeps dropping, same thing as before in my post >>>here<<<
Bluetooth worked until I enabled debug, then it did not. Gallery did NOT work, until I enabled debug, then it did. Camera still crashes gallery. Torch still crashes. I cant pull a logcat because adb keeps saying device is offline. I'll try a reboot, see if that helps once I get home
Click to expand...
Click to collapse
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through your computer.. You confirm it and you can get the log.
jparnell8839 said:
Clean flash, ran Black Hole and FSC before flashing.
ok, so I'm still getting spotty connectivity for data, keeps dropping, same thing as before in my post >>>here<<<
Bluetooth worked until I enabled debug, then it did not. Gallery did NOT work, until I enabled debug, then it did. Camera still crashes gallery. Torch still crashes. I cant pull a logcat because adb keeps saying device is offline. I'll try a reboot, see if that helps once I get home
Click to expand...
Click to collapse
Thanks for the offer on the mirror... I have 2 sites I use, one main and one just in case...lol... But you are welcome to upload it and post the link... I'll include it in the dl section.
As for your issues, I'm tracking the camera/gallery issue and of course wifi. as for data, have you tried using a different radio? Torch is working fine for me. Try downloading/flashing again. Might have gotten a bad flash/download (doubtful, but let's try it). Also, has the log changed or is about the same?
for the logcat to work change the type of usb connection to camera. It worked for me.
theprogram1 said:
for the logcat to work change the type of usb connection to camera. It worked for me.
Click to expand...
Click to collapse
Go to System settings/About phone and tap Build number several times until it tells you that you are a developer. Then you will have developer options and can now enable adb debugging...
Hey Thomas there is a fix for the camera crash on gerrit
http://review.cyanogenmod.org/#/c/46310/
Its for 4.3 but should work with 4.2 same logic
Sent from my SAMSUNG-SGH-I577 using xda premium
For those still getting device offline in adb. my n4 does this every time I switch between mine and my wife's. First make sure SDK is up to date. Secondly if it still does it. Tap the USB debugging option in developer options on and off again several times and the dialog box asking to accept the computer should come up. . Its not a for sure way to get it to work but this usually works for me.
Sent from my Nexus 4 using xda app-developers app
ktempleton said:
Hey Thomas there is a fix for the camera crash on gerrit
http://review.cyanogenmod.org/#/c/46310/
Its for 4.3 but should work with 4.2 same logic
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
The patch is already present... but I'm going to add it to the boardconfig.mk and see if it works...
I'm not sure if all of it was there but there were changes in the kernel and common folders as well as v media and display caf
They discuss them in detail here
http://forum.xda-developers.com/showthread.php?t=1798056
Sent from my SAMSUNG-SGH-I577 using xda premium
ktempleton said:
I'm not sure if all of it was there but there were changes in the kernel and common folders as well as v media and display caf
They discuss them in detail here
http://forum.xda-developers.com/showthread.php?t=1798056
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
I got it in there... let's see if it works... tomorrow... I've screwed the phone up anyways, so I'm stuck trying to fix that for now...lol
10.1 comes out as soon as i switch to the Nexus 4! Haha, well great job raines, and all else who contributed. Proud of you guys.
aronianchici said:
10.1 comes out as soon as i switch to the Nexus 4! Haha, well great job raines, and all else who contributed. Proud of you guys.
Click to expand...
Click to collapse
Switched to a nexus 4 a few months back from the blaze. You will love the development section for it(;
Sent from my Nexus 4 using xda app-developers app
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Device-specific source code for the Acer A700 are available from https://github.com/CyanogenMod/android_device_acer_a700 and https://github.com/CyanogenMod/android_kernel_acer_t30
Do not submit bug on CyanogenMod issue tracker
Downloads
Latest Build: http://download.cyanogenmod.org/?device=a700
Google Apps: http://wiki.cyanogenmod.org/w/Gapps
Installation
Install CWM recovery from http://forum.xda-developers.com/showthread.php?t=1791165 (note that the old touch version will not work because of incorrect default.prop from CWM builder)
Do a Nandroid Backup!
Install the ROM using ClockworkMod Recovery
Optionally install the Google Addon
Wipe data if coming from stock
Changelog
A rough changelog will available here once nightlies have started:
http://www.cmxlog.com/11/a700/
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.
Code:
What is your--
Tablet model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Hi pawitp,
Works great and stable.. but i use pa gapps with enable ART.
Speed and Performance for this early Build is awesome.
Thanks that you work for our A700
Gesendet von meinem GT-I9505 mit Tapatalk 2
Hi all
I am really eager to upgrade my A700 to kitkat... Since acer won't provide upgrades, i am considering unofficial ROMs.
Can you guys comment on the downsides of this Rom?
Any functionality not working?
Many thanks
Installation aborted error status 7)
back to 10.2 adb push
s1r1 said:
Installation aborted error status 7)
back to 10.2 adb push
Click to expand...
Click to collapse
Try updating your recovery to the latest version.
Installed it over 10.2 stable version without a glitch (6.0.4.4 recovery). Seems to work fine, performance seems to be a little under 10.2 but it's early build. Thank you very much pawitp !
cwm 6.0.4.4 works fine thanks.
kit kat for a700
Hi pawitp
Thank you very much for this Rom ! I did a full wipe before flashing coming from Evil Alex Purgatory. Rom is fast and smooth but when i delete a widget on homescreen there is no "delete" button on the upper edge so i've got to keep the widget picked and "scan" the upper edge until it turns to red. Waiting for update or reflash ? But not a big thing for me.
G mac_o
mac_o said:
Hi pawitp
Thank you very much for this Rom ! I did a full wipe before flashing coming from Evil Alex Purgatory. Rom is fast and smooth but when i delete a widget on homescreen there is no "delete" button on the upper edge so i've got to keep the widget picked and "scan" the upper edge until it turns to red. Waiting for update or reflash ? But not a big thing for me.
G mac_o
Click to expand...
Click to collapse
It's currently a bug if you disable "show search bar" in launcher.
Cm11 works great on my a700 with pa-gapps and Art.
Gesendet von meinem A700 mit Tapatalk 4
Hi,
Loving it !
This is my first unofficial rom on a700 and I must recognize your fantastic work. It works great and is a major improvement compared to stock.
On top of jumping to a far more enjoyable version of Android, it brings an end to sluggish behavior AND to the below average responsiveness of the touch screen. It is like a new tab really. So THANK YOU.
One question though. I wiped everything, flashed the rom and the Gapps. At startup my memory available was only about 10Gigs...odd for a 32Gigs tab no?
The attached screenshot is where I am now. Feels like some space is missing.
What do you think?
benjieb said:
Hi,
Loving it !
This is my first unofficial rom on a700 and I must recognize your fantastic work. It works great and is a major improvement compared to stock.
On top of jumping to a far more enjoyable version of Android, it brings an end to sluggish behavior AND to the below average responsiveness of the touch screen. It is like a new tab really. So THANK YOU.
One question though. I wiped everything, flashed the rom and the Gapps. At startup my memory available was only about 10Gigs...odd for a 32Gigs tab no?
The attached screenshot is where I am now. Feels like some space is missing.
What do you think?
Click to expand...
Click to collapse
Either it's a miscalculation or some space is used where Android doesn't recognize (e.g. CWM backups).
If you run the following command from adb shell or terminal emulator, you'd be able to find out where all your storage went.
Code:
su
busybox du -d 2 -h /data
To check the actual free space, run
Code:
df /data
nice
continuous fc's of gapps and bootloop
i came from pawitps cm10.2 and installed cm11 plus the gapps given in the first post of this thread. i did a dirty upgrade (no full wipe) and everything worked well. then i decided to change from dalvik to art. the tablet rebooted and converted all the installed apps. since then i have continuous fc's of gapps which renders the tablet unuseable as the error messages pops up that fast and frequently that i have no chance to get access to the apps in the background. i then forced a shutdown by pressing the power button for several seconds and tried to restart the tablet. no success it hangs now showing the new cm-logo with the turning arrow around it.
a reflash of the rom did not help (as expected as the bad config telling it to use art instead of dalvik is still there). at the moment i am downloading an updated package of gapps from 12.12.2013 to flash it and see if that helps.
my next step would be downgrade to cm10.2 to get it back running.
any advice about how to change from art back to dalvik without the need of flashing an older rom is very appreciated. by the way, am i the only one who has tried out the new art vm? anyone having success to use it?
greetings
peter
peter_altherr said:
i came from pawitps cm10.2 and installed cm11 plus the gapps given in the first post of this thread. i did a dirty upgrade (no full wipe) and everything worked well. then i decided to change from dalvik to art. the tablet rebooted and converted all the installed apps. since then i have continuous fc's of gapps which renders the tablet unuseable as the error messages pops up that fast and frequently that i have no chance to get access to the apps in the background. i then forced a shutdown by pressing the power button for several seconds and tried to restart the tablet. no success it hangs now showing the new cm-logo with the turning arrow around it.
a reflash of the rom did not help (as expected as the bad config telling it to use art instead of dalvik is still there). at the moment i am downloading an updated package of gapps from 12.12.2013 to flash it and see if that helps.
my next step would be downgrade to cm10.2 to get it back running.
any advice about how to change from art back to dalvik without the need of flashing an older rom is very appreciated. by the way, am i the only one who has tried out the new art vm? anyone having success to use it?
greetings
peter
Click to expand...
Click to collapse
If you look at the linked page, you'd see that one of the gapps package is marked as not ART compatible
Boot into recovery and hope that you have adb shell access, then run
Code:
mount /data
rm /data/property/persist.sys.dalvik.vm.lib
Otherwise, you'd need to do a data wipe/factory reset.
peter_altherr said:
i came from pawitps cm10.2 and installed cm11 plus the gapps given in the first post of this thread. i did a dirty upgrade (no full wipe) and everything worked well. then i decided to change from dalvik to art. the tablet rebooted and converted all the installed apps. since then i have continuous fc's of gapps which renders the tablet unuseable as the error messages pops up that fast and frequently that i have no chance to get access to the apps in the background. i then forced a shutdown by pressing the power button for several seconds and tried to restart the tablet. no success it hangs now showing the new cm-logo with the turning arrow around it.
a reflash of the rom did not help (as expected as the bad config telling it to use art instead of dalvik is still there). at the moment i am downloading an updated package of gapps from 12.12.2013 to flash it and see if that helps.
my next step would be downgrade to cm10.2 to get it back running.
any advice about how to change from art back to dalvik without the need of flashing an older rom is very appreciated. by the way, am i the only one who has tried out the new art vm? anyone having success to use it?
greetings
peter
Click to expand...
Click to collapse
Hi, im using pa-gapps and they work perfectly with art. I had art on the a700 for a short time enabled but since xmbc doesnt work with art yet i had to go back :/ I believe on the top of the website where you can download the gapps suggest in first post is written that they dont support art yet. Dont know why pagapps work well with art and the official cm gapps dont. I recommend a full wipe, reflash cm11 and install pa-gapps.
http://forum.xda-developers.com/showthread.php?t=2397942
thank you pawitp for your excelent work on porting cm11 to our A700 and also for the hint regarding the gapps problem. i just did not notice that they are not art compatible. thanks also to BonzenPaule for the hint with pa-gapps. i have flashed this one: pa_gapps-stock-4.4.2-20131212-signed.zip and at the moment the tablet is rebuilding the apps-cache. so i will see if the boot process completes. i will report as soon as it finishes.
greetings
peter
pawitp said:
Either it's a miscalculation or some space is used where Android doesn't recognize (e.g. CWM backups).
If you run the following command from adb shell or terminal emulator, you'd be able to find out where all your storage went.
Code:
su
busybox du -d 2 -h /data
To check the actual free space, run
Code:
df /data
Click to expand...
Click to collapse
Hey, very helpful. I now see that I have huge amount of data in data/media... Very odd thing is that it contains every thing i had in "sdcard" in my previous stock setup... BUT it does not show in my current "sdcard". Despite wiping everything it seem to still be there. Have I missd something in the process?
benjieb said:
Hey, very helpful. I now see that I have huge amount of data in data/media... Very odd thing is that it contains every thing i had in "sdcard" in my previous stock setup... BUT it does not show in my current "sdcard". Despite wiping everything it seem to still be there. Have I missd something in the process?
Click to expand...
Click to collapse
CWM is designed not to wipe the "sdcard" when wiping data. However due to multiple users support, recent versions of Android do not recognize the content. You should use move the files into /data/media/0.
Sent from my Nexus 4 using xda app-developers app
the very simple way to upgrade lasted CMW is download ROM MANAGER from ggplay
thanks @scoobyjenkins
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kitkat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 11.0 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Experience issues?
* Nightlies: bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
* M-series: file a bug in Jira.
Download Links
CyanogenMod: download.cyanogenmod.org
Google apps addon:
Download: http://goo.im/gapps (use latest kk gapps)
Mirror: http://download.crpalmer.org/downloads/gapps/
Useful Links
Unofficial changelog
Picassowifi wiki
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 11.0 for Tab Pro 10.1 PicassoWiFi, ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
Version Information
Status: Stable
Created 2014-09-26
Last Updated 2014-09-25
Reserved
Reserved
@crpalmer, let me be the first to congratulate you on this! It's amazing how we have official CM support now!
Thank you very much!
Congrats again on your hard work paying off, and making it into AP. http://www.androidpolice.com/2014/0...-extended-to-the-samsung-galaxy-tab-pro-10-1/
Nice work. Think I'm about ready to do my first flash. . :good:
Congratulations on being official
It's with great interest I have followed the development of your T-520 version of the cm11, even though I don't have one myself. Why? Firstly, I'm amazed by the short time frame in which you actually accomplished this, and conquered the Exynos SoC. But, I'm also A proud owner of a T-900, and from what I can tell there is only the screen size that differs the T-520 from the T-900. In my mind, it should be feasible to port, though I might be wrong.... Maybe, you have some ideas of how to correct/evolve Shaheen's port of your ROM. Who knows, maybe at this point you're bored and need a new challenge, as the major obstacle is breached and, before the work with Android L begins... Besides, neither Shaheen, nor you own a T-900, why this should be a very simple task:laugh:
The current error report is as follows:
arcadia2uk said:
Thanks for reviving this one Shaheer,
After some problems in getting the full ROM onto the drive (all on my side), I finally got it up and working. The ROM is a lot snappier that prior versions, and is stable over all. Below is my summary of working/non-working functions. Additionally, with the all new TWRP 2.8.0.0, see post #55, the format of system and cache are instant, why ROM testing is a breeze.
I have noticed the following issues:
- WiFi connects, but loses password on reboot, same issue as earlier build
- Bluetooth: devices are seen, but do not connect - Error message: Can't connect
- External SD is not detected by device - see post #54, below, for more detailed info
- mtp - device does not mount on PC
- adb - device does not mount on PC
- Camera is broken - Error message
- Torch is broken - Error message
- Lid sensor - No reaction
- Capacitive lights - No reaction
- Sensors - No reaction
- IR blaster - No reaction
- Offmode charging - but it will not work on the picasso-wifi either, at least until tomorrow, 20140926
- Home button doesn't work correctly. It wakes up the device, but does not go to the home-screen
- Battery drain is significant - However, it might be my impression from heavy use of the screen while testing
Only two outstanding items (non-tested) from the list Shaheer posted below. I would appreciate if someone would test them and confirm if they are working, or not:
- Miracast displays - Most likely functional, given that the Chromecast dongle is working | Best Guess: yes
- Google Play Movies: downloading a video and then playing the downloaded copy. Apparently, crpalmer has received a CyanogenMod commit and the issue is fixed as of now, 20140925 | Best Guess: No
Click to expand...
Click to collapse
Anyhow, we (T-900 owners) would really appreciate your input, and I believe speaking for Shaheer as well, and to tap into your substantial knowledge and experience.
Once again, I'm really impressed by your accomplishments, and I sincerely congratulate you to the well deserved status as an officially recognized cm-developer.
Finally, if a tester is needed, I'll be around.
Thanks in advance.
Congrats! I appreciate your hard and nice work. Thanks :good:
I am so thrilled to see official CM support for Galaxy Tab PRO 10.1. Ordered mine couple of days.. and still in transit. They day I ordered.. I am thinking how will i live with touchwhiz..
I guess now i don't have to worry.. will root and flash right away once its here. Looks like everything is working. I don't care about small bugs if battery life is as good as stock
Thanks again
Good work !
I am on GraveD stock ROM, running very well for a month.
But I plan to try CM11 asap.
Sent from my SM-T520 using XDA Free mobile app
Subscribed in hopes this will trickle back to klimtwifi (Tab S with Exynos 5420)
Wow, thanks for the great news @crpalmer!
WiFi easy fix
sorry wrong thread
@crpalmer,
I followed the instructions "How To Build CyanogenMod Android for Samsung Galaxy Tab Pro 10.1 Wi-Fi ("picassowifi")" (http://wiki.cyanogenmod.org/w/Build_for_picassowifi).
I faced issues with drmserver and gpsd on extract-files.sh : "Permission Denied"
I managed this by copying them to internal memory and them adb pull to their destination locations.
It's compiling now...
Which ir app are you guys using? I can't find one that works.
If you want to disable the soft buttons and use the on-screen buttons (I use the tablet a lot in portrait mode and the soft buttons get in the way all the time).
1. Enable soft keys : edit the /system/build.prop file to include the following line qemu.hw.mainkeys=0
2. Disable the soft keys : edit the system/usr/keylayout/sec_touchscreen.kl file and add # in front of the two lines
3. Turn buttons light off : go to settings -> buttons and disable backlight
4. Reboot
I don't think it was posted all in one place before.
cviniciusm said:
@crpalmer,
I followed the instructions "How To Build CyanogenMod Android for Samsung Galaxy Tab Pro 10.1 Wi-Fi ("picassowifi")" (http://wiki.cyanogenmod.org/w/Build_for_picassowifi).
I faced issues with drmserver and gpsd on extract-files.sh : "Permission Denied"
I managed this by copying them to internal memory and them adb pull to their destination locations.
It's compiling now...
Click to expand...
Click to collapse
Hmmmm. That's a good one. Very few vendor blobs tend to have restricted read permissions but apparently we hit two of them. I assume that it was actually drmserver.samsung though right? That's important if your build is going to have working DRM.
I made myself a note to figure out how to make that work better and/or document it better.
FYI, you can also download an existing build, unzip that file somewhere, and then run
./extract-files.sh /path-that-you-unznipped-to/
and it will pull all the files from that unzipped directory.
burnski said:
Which ir app are you guys using? I can't find one that works.
Click to expand...
Click to collapse
I currently like Smart IR Remote. It's not free but they seem to be good people and I appreciate that.
crpalmer said:
Hmmmm. That's a good one. Very few vendor blobs tend to have restricted read permissions but apparently we hit two of them. I assume that it was actually drmserver.samsung though right? That's important if your build is going to have working DRM.
I made myself a note to figure out how to make that work better and/or document it better.
FYI, you can also download an existing build, unzip that file somewhere, and then run
./extract-files.sh /path-that-you-unznipped-to/
and it will pull all the files from that unzipped directory.
Click to expand...
Click to collapse
Hello,
Thanks.
Unfortunately, I need more RAM, only 2 GB RAM and 2 GB Swap don't fit the load.
crpalmer said:
I currently like Smart IR Remote. It's not free but they seem to be good people and I appreciate that.
Click to expand...
Click to collapse
Cool thanks I'll check it out
Did you get Infra Red ever to work? I use Touchsquid and it always worked with every ROM i tried.
But in CM11 it looks like it is broken. Maybe I am too impatient and i should wait a bit for CM to get IR working and go back to GraveD's ROM for a while.
Thanks for the hard work crpalmer!
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
Make sure you have a second partition on your SD card before flashing!!!! This can be created with minitool partition wizard on Windows or gparted on Linux.
If on a BML rom (stock-based GB)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. It will reboot a couple of times, don't be worried.
4. If you want root or Gapps, flash them now
If on an MTD rom (CM7 and all ICS+)(I tested CM9, CM10.1 and CM11)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Wipe data, and cache paritions (just in case). If updating to a newer build, you can probably skip this step
3. Install zip
4. If you want root or Gapps, install them now
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess and also provide T959P builds.
The USB connection is MTP and not mass storage as Omni has removed mass storage. In recovery there is still an option to mount as mass storage device.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps reportedly slow down the device significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
Video Recording
Automatic Brightness
Moving Apps to the SD Card
GPS
Encryption
Compass
SElinux in enforcing mode
What probably doesn't
Microphone mute option doesn't work during calls
What doesn't
720p recording is very laggy
What's been removed
TV-Out - It was removed upstream plus I think binary blobs are broken in Lollipop...
Live wallpapers - this is a low-ram device
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Galaxy S 4G (T959V) and Galaxy S Fascinate 4G (T959P), ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99, humberos
Source Code: http://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: All
Based On: OmniRom
Version Information
Status: No Longer Updated
Created 2015-06-30
Last Updated 2016-05-12
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Download folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch galaxys4gmtd"
Changelog
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
Notifications are sometimes wonky. To fix, in Settings, go to Performance, then Advanced. Select Force high-end graphics and reboot your phone.
Changelog for 2015/07/20 Build
The data partition is now the second partition of the SD Card as opposed to internal storage
Gapps now work. If you get error 461 when installing from Play Store, a full data wipe should fix it. You can try experimenting with clearing data for the Play Store and/or Play Services or removing and re-adding your Google account if you don't want to do a full data wipe.
HSPA vs UMTS settings in DeviceSettings has been fixed
High-End graphics are forced by default to fix notification issue
ART parameters have been tweaked
Miscellaneous other tweaks, see my Github for details
Changelog for 2015/07/24 Build
Stabilized bluetooth connection
Fixed typo in GPS initialization. Does it work?
Added ability to use f2fs file system on /data. Supposed to give better performance
Added force fast charge and touch wake to kernel. Touchwake is accessible through its sysfs path, fast charge through Performance Settings, BatterySelinux currently denies these requests...
Changelog for the 2015/07/29 Build
This is a maintenance build. Very little has changed
Some more RAM freed (disabled some debugging stuff, TV-Out driver, IR driver)
Sepolicy updated for fast charge and touch wake
GPS initialization tweaked - unsure if works. If it doesn't, a dmesg would be appreciated
Changelog for 2015/08/02 Build
SElinux changed to permissive - this build only
GPS sepolicy changed - unsure if all necessary things are implemented
Changelog for 2015/08/13 Build
Selinux back to enforcing. Thanks to @anoymonos for the dmesg and @DerPugNa for offering to send me one as well
Fixed encryption
Changelog for 2015/08/31 Build
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
Restoring /system in TWRP should now work
When installing from BML, a chance is given to install gapps and/or SuperSu before rebooting
zRam is now actually used...
Changelog for 15/10/2015 Build
Fixed typo in updater.sh (thanks @FBis251!)
Update Omni source code - plenty of little tweaks since last build
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-5.1-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Please let me know if the link doesn't work! There are also builds there for the T959P, in case there are any users of it left.
Gapps
Gapps do not work on builds prior to 2015/07/20. On more recent builds, they can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Thanks thanks ....
Awesome work @xc-racer99!
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
GFX.myst. said:
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
Click to expand...
Click to collapse
I hope I can keep this great little device going a little longer, however it will probably get tough. I did a repo sync earlier today and things are starting to break. The last few builds haven't even booted. With humberos no longer maintaining the i9000 and aries-common, I've had to fork the aries-common repository to try to keep going. The only upside of this is that I now have a little bit more freedom and can add things in if I want to.
Thanks for the offer of the graphics. If I can get a new build working, then I'll probably take you up on your offer. I think I've traced the problem but I'll have to wait and see...
For anyone that is trying/has tried this out, I'd be very curious on the status of the GPS on the T959V. I'm interested in creating the sepolicies for it so we can put selinux into enforcing mode but I don't want to go to the effort if it doesn't even work right now.
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
New Build Uploaded!
Download is still at the same link as before, just use the 2015-07-03 build
I managed to find out why my new builds hadn't been booting - it was because the syntax for using a custom kernel toolchain had changed.
Anyway...
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
On another note, I've had a look at re-implementing TV-Out support. It doesn't look promising as several of the functions in the android frameworks that it used have been tweaked.... Still working on it but don't hold your breath.
Also, if somebody could test dock audio that would be appreciated. I don't have any way of testing it. If it doesn't work, I do have an idea on how to fix it (for those interested, another almost-aries device, the Infuse 4G, had to modify things slightly to get it to work. I would try to emulate their solution).
Omg download nowwww....thanks my friend
Alright, I'm having some issues on the latest build with notifications and the lockscreen. I'm still working on tracing down the reason for the problem...
DickyG said:
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
Click to expand...
Click to collapse
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
billowusu47 said:
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
Click to expand...
Click to collapse
Good to hear that that's its (mostly) been working for you. I was hoping that the gapps problem was just me
Out of curiosity, which of the alternate gapps did you try?
A brief google of the error brings up a couple of possibilities...
Try an older gapps version. The ones from devloz on the i9000 thread devloz and the oldest revision for 5.1.1 are probably your best bet. Please be aware that Google Play store will automatically update!!! In order to prevent this, you will need to create a folder called "com.android.vending-1.apk" in /data/app (use a root explorer such as ES File Explorer or adb if you know how). If a file with that name already exists, delete it first.
Another thing to try would be to unmount your sdcard first before trying to install an app. I know, its a terrible work-around but it should work. This is because the error is that Google Play is trying to save some data on your sdcard but then for some reason it fails (I'm not sure why).
I'll hopefully get around to seeing if its a permissions problem after I find out what's been causing the issue with the notifications on the latest build.
P.S. Does the GPS work?
Early update...
...ROM flashed fine...a little slow to boot...about 3 minutes...but it booted.
...Gapps flashed fine...used 20150513_5.1.x package
...Installed Super SU (although I don't think that's necessary) and TB.
...So far only gave a quick test to camera and web browser...no problems.
...Am now in the process of re-installing user apps and data from TB...this will take a while.
When I'm done with that, I use Link2SD to link most of my user files to the SD card. After that is all set up, I'll test stuff like GPS, root access, etc. I'll post back later...maybe tomorrow.
But so far so good.
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
DickyG said:
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
Click to expand...
Click to collapse
Alright, thanks very much for the update. I'll do some more testing here and see if I can solve anything. For me, bluetooth file transfers to the phone work but not from the phone.
I've been looking at the notification "error" where the lockscreen notifications do not appear correctly. It appears to have been introduced upstream with a merge. I'm having difficulty finding out exactly what changed and since no errors are being thrown in the logcat, it could be a while...
For testing the GPS, there's an app from the Play Store called GPS Test which does a nice job of showing satellites and whether or not you have a lock on them.
you're the man!
nice one! its nice that this device are still alive.! and now were on 5.1
DerPuGNa said:
nice one! its nice that this device are still alive.! and now were on 5.1
Click to expand...
Click to collapse
No, it should be Humberos is the man! I basically re-hashed his code for the i9000 and used bits and pieces from people like Bhundven, noiphonehere, maxfierke, Dao, and FB to get things to work properly.
For a status update, I figured out the lockscreen notification problem. I have a new build being made that I hopefully will be able to upload in the next couple of days (internet dependent). TV-Out looks totally broken as the proprietary blobs no longer function. I don't have the know-how to make ugly hacks to get them to work. The new build will have SElinux in enforcing mode and have the different GPS initialization (like the last build) until someone tells me that it doesn't work
Uh-oh, looks like I jumped the gun.... Having problems once again
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
AgainstTheFlow said:
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
Click to expand...
Click to collapse
Darn, so its still not working. Not surprising. I've been struggling on the notification issue and am at my wit's end as to what the problem is. I don't think its only our phone as several i9000 users have been reporting it as well. Whether it is only the first-gen Galaxy S series that is having the problem or not is anyone's guess. My programming skills are insufficient to fix the issue!
I'll have another look at gapps over the next couple of days and see if I can figure out a combination that works 100% of the time.
I'm assuming the error message is still 963 or does it silently fail now? Its probably related to the fact that we have only an external sd card and no internal sd card like most devices...
All the problems with the notifications that I've found are:
Only one notification will show up at a time
Large notifications such as the music player do not render properly. They are cut off at the normal notification size and occasionally it seems as if there are two layers there (one for the small version, one for the bigger version) (see attached picture, taken with VLC as the media player, but also appears with Apollo)
Notifications don't always show up. A little icon appears in the top left corner of the status bar but no notification is present. Seems hit or miss
The words No notifications appears in the lockscreen just above the clock when there are no notifications. Otherwise, a notification (and only one) which can't be clicked covers part of the clock