Ill organize this and make it look good later...but for now lets get to the point:
This is an Android 4.1.1 Jellybean (JB) ROM, it is an unofficial version of a popular after market firmware known as CyanogenMod. it is essentially AOSP with some cool added features by the CyanogMod team -this has no sense, and it is not based off a sense stock rom
Befor i even begin stating what works and doesnt i would like to thank Synergy, he is the one who got this started, he is the one who got the first version of this to boot...unfortunately he quit due to frustrations with HTC and how hard they have made things, i am just picking up where he left off...
What works:
WiFi
Audio
Calls? **check out not working***
SMS...aka texting
home button -I know it sounds funny, but for a while the home button didnt work on CM10
Not working:
Data
Bluetooth
GPS
MMS...aka picture messaging and othe multimedia messaging (will work as soon as data works)
Camera
Video-likely a driver issue...mx player allows for videos to be played but they are extremely laggy...only tested with mp4's of videos i filmed while on ICS
Calls? i need people to test calls...i believe if you have ATT in call mic wont work...so the other end wont be able to hear you work...i cant verify it...but if you use any other carrier (even if you have an ATT vivid but are unlocked and using a differnt carrier) then i believe in call mic does work...i need people to verify...so make some calls and let me know if they work and if the other line can hear you, and also let me know what carrier you have
Instructions
1) Wipe data/factory reset
2) Wipe cache
3) wipe dalvic cache
4) flash CM10
5) flash GAPPS
S-ON?
just fastboot flash the boot.img located in the zip then follow the instructions above
Download
CM10
http://goo.im/gapps/gapps-jb-20120726-signed.zip
All versions of GAPPS: http://goo.im/gapps/
what are GAPPS? GAPPS are just google applications...like Play store, GMail...ETC, its not necessary...but if you wanna get any apps your gonna need it
Other stuff...
Featuring Synergys Kangbang-rebirth kernel...supports OC up to 2052 MHz...or about 2 GHz (you can change clock speed under settings/performancee
Features a built in file explorer...not included in most cm builds
Thanks/Credits
once again...synergy...cant thank him enough
kevstheblast, he also worked on cm10 for a little bit
TeamCodefireAOSP - most of my device trees are from you...some with slight modifications
DragunKorr - i am using your msm8660-common device tree
...ill add to this list later, but its late and i need to finish my homework and go to bed
-Its time to bring the vivid back to life...CM10 opens the door to numerous AOSP based JB ROM ports...lets get this stabilized!
Screenshots...coming soon
How to build:
1) First you need to sync CM10 source:
A)
Code:
mkdir cm10
-this creates a folder for where the source will be downloaded
B)
Code:
cd cm10
-this navigates you to the folder the source will be downloaded in
C)
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
-this initializes the repo...gets it ready/prepares for the sync
D)
Code:
repo sync
-this downloads the source...depending on the rom can range from 8-15+ GBs!
E)
Code:
./vendor/cm/get-prebuilts
-downloads necessary prebuilts for CM10
2) Now you need to clone my local manifest:
A)
Code:
cd ~/cm10/.repo
-this navigates to where the local manifest will be cloned
B)
Code:
git clone git://github.com/mg2195/local_manifest.git
-this makes a copy of the local manifest in your .repo folder
C)
Code:
repo sync
-downloads the sources that were added by my local manifest
3) Now you can build:
A)
Code:
. build/envsetup.sh
-prepares the system to build
B)
Code:
lunch
-opens the device menu for you to choose your device
c)
Code:
6
***or whatever number the holiday pops up as*** -the item number of the device
D)
Code:
mka bacon
-begins the build...can take a few hours depending on your computers CPU
4) relax, eat some pizza, go for a walk...do something, this can take a while...your finished product will be located in /cm10/out/target/product/holiday
How to build other roms from source:
1) First you need to sync there source:
A)
Code:
mkdir workingdirectory
you can name "workingdirectory" whatever you want...i suggest the name of the rom for organization purposes...so for AOKP i would do "mkdir AOKP"
B)
Code:
cd workingdirectory
C) repo init there manifest...for AOKP:
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b jb
found from here: AOKP...so basically find the roms source, then find there manifest, type "repo init -u gitreadlinkhere -b branchnamehere"
D)
Code:
repo sync
2) Now you need to clone my local manifest: (this gets you all the device specific stuff...device tree, common device tree, kernel...ETC)
A)
Code:
cd ~/workingdirectory/.repo
B)
Code:
git clone git://github.com/mg2195/local_manifest.git
C)
Code:
repo sync
3) Now you can build:
A)
Code:
. build/envsetup.sh
B)
Code:
lunch
c)
Code:
6
***or whatever number the holiday pops up as***
D)
Code:
mka bacon
***please note, this may or may not work for every roms source...some require a little extra work...but this should get you the core files needed...look at how other official devices are set up, try and match them...specifically in the workingfolder/vendor***
4) relax, eat some pizza, go for a walk...do something, this can take a while...your finished product will be located in /cm10/out/target/product/holiday
SOURCE
https://github.com/mg2195
https://github.com/KangBangKreations/KangBanged-Kernel/tree/kb-rebirth
CHANGELOG
10-08-2012
-First real release/started thread...
Post any bugs...and if possible get me some LOGCATS
To save a log to a file:
Code:
adb logcat > logcat.txt
Press
Code:
ctrl+c
once you are done collecting information
Then upload the logcat.txt as an attachment so I can look at it with ease...DO NOT JUST COPY AND PASTE THE LOGCATS HERE! that just hogs space and is a pain for those on mobile devices...if you really want to copy and paste there is this great site called pastebin paste it there, hit submit and post the link here
Absolutely awesome man! I love the persistence . Picking up where others left due to frustration, so x10 thumbs up for the dedication!
Will definitely be testing this out and posting back as much bug info I can get you (I will edit this, not just a thank you post). I can't agree more, hopefully you can bring the Vivid back to life . I have faith!
LOG/BUG UPDATE:
Ok so whooo again, great build! Very smooth and speedy, just love this phone without sense (sense works good, but this JB is so refreshing - 0 lag).
Cant wait for the bugs to be worked out, it will be very worth it. Anyway, onto the my report:
_______________________
First boot, it restarted after the white and green HTC screen, so anyone testing no worries when it reboots.
Everything loaded up pretty quickly, and no FCs or bugs besides the known ones. I did notice I think its new probably because of the work you did to get audio to work (messing with the display), when rotating it sometimes makes the screen go all funky (part of the current image is displayed like 4 times in a horizontal line for about .5 seconds) then its fine. So not a big deal.
Bugs:
I tested the calls using my VM, sound works . Now if I try to change the volume of the headset speaker it changes ringer volume I believe, as I didnt notice a difference in volume when the VM automation was talking to me. It also showed a telephone, not w.e it supposed to be (shows same image as not in a call - like its not realizing its 'in' a call). I tried to record a new greeting message, but mic does not work still (tmo).
Data is still the same [as your test builds], blinks E real quick (.5 seconds) then goes away. Under phone status it shows Mobile network type as EDGE:2. Then DCed for network state (changes to connected for the .5 secs when E pops up). Changing bearer to LTE or unspecified doesnt change anything. Also forcing LTE/GSM/WCDMA or GSM/WCDMA Preferred doesnt change anything either.
Camera I tried but FCs with gallery. So also with a few other apps that wouldnt be linked to gallery (though gallery works), no go. They all FC for some reason.
Now no worries, I got you logcats of everything here. I tried to slim them to just the problem although I dont know exactly where the problems end in these huge scripts lol. So I apologize for the length of some, rather you get more than less and I miss the problem line.
Making Calls while changing Volume: http://pastebin.com/gXmiHrCc
Changing bearer to LTE: http://pastebin.com/9hXBiNmS
Clicking Enable Data: http://pastebin.com/xH3AWUp4
Stock Camera: http://pastebin.com/xRsyUTmj (Sorry for lengthy, couldnt tell if it was looping or just straight erroring out million times x( )
Camera Illusion: http://pastebin.com/NFxf2nxd (Again sorry for lenthy, same ^^)
Camera 360: http://pastebin.com/YmRfXBxJ
Maybe hopefully you can get some matching errors on the camera, narrow the problem on that. And hopefully you can figure out the data, thats really big. Same with mic of course. But, again, very good job first actual alpha build.
Unless you wanna damage your hearing....I don't suggest using DSP manager while wearing headphones...went to change the bass and as soon as I changed it my volume went to like full blast lol...definitely some work needs to be done there
Anyways its bed time for me
Sent from my Holiday using Tapatalk 2
Lied about going to bed...found a work around for video...
Go to settings/developer options
Make sure its on
Then disable hw overlays
-my mp4s now play...but they are really laggy...YouTube app now playa video s flawlessly now... maybe its the resolution/quality?
Now I go to bed...
Sent from my Holiday using Tapatalk 2
Would love to try this now, but as this phone is my only phone, I'll have to wait. But once calls and data are working, I'd be more than happy to test out the rest for you. Thank you for your efforts!
Sent from my De-Sensed HTC Vivid using xda app-developers app
finally some JB love for Vivid. as soon as most of the features work, ill test it out.
Dear Santa.....
Can confirm in-call mic doesn't work with AT&T. Everything else is exactly as you described. Let me know if you need a reliable, thorough, tester on AT&T. Will be following this project very closely. Thanks for picking up the project. Keep it up and good luck sir
This thing is wicked fast, and buttery smooth. If in-call mic worked this could be my daily driver. Don't give a damn about data ATM
Internal/External storage works as well, but they arent auto-mounted you need to go into storage settings and manually mount. no usb mount either. but it does recognize the cord.
MisterSchnapps said:
Can confirm in-call mic doesn't work with AT&T. Everything else is exactly as you described. Let me know if you need a reliable, thorough, tester on AT&T. Will be following this project very closely. Thanks for picking up the project. Keep it up and good luck sir
This thing is wicked fast, and buttery smooth. If in-call mic worked this could be my daily driver. Don't give a damn about data ATM
Internal/External storage works as well, but they arent auto-mounted you need to go into storage settings and manually mount. no usb mount either. but it does recognize the cord.
Click to expand...
Click to collapse
Didn't think to test USB as it was working on previous builds...since it was previously working it shouldn't be to hard to fix
Sent from my Holiday using Tapatalk 2
It may be because data doesn't work lol, but I'm getting great battery life!
Anyways...doing some research...trying to figure out how to fix what's currently broken...
Also, it appears that many different devices have graphics/video problems caused by hw overlays....no real fix has been discovered except the work around I mentioned earlier about disabling hw overlays under developer options in settings
As far as USB...I think I might've deleted a line in accident that "defines" its function...
Once I get this stabilized I'll do a tutorial on how to build from source using my existing device sources and plug them into other source ROMs like aokp...
Sent from my Holiday using Tapatalk 2
:fingers-crossed:
Do both mics not work? Could we maybe use the camera mic instead?
Brand New said:
Do both mics not work? Could we maybe use the camera mic instead?
Click to expand...
Click to collapse
The mic works for everything except calls...ive tested it using the voice search app...i searched pizza lol, but it recognized what i said and BAM...all the local pizzerias
Apparntly ATT payed HTC extra to add some extra "security" features...the result is broken in-call mic for ATT users...still waiting for confirmation but if you are a non ATT user then in-call mic SHOULD work...
i stopped my research for a little bit and got my github set up...if you understand how it works you can track my progress there whenever i upload changes...also i edited the third post with instructions on how to build CM10 using my sources, you must already have a build environment set up though...ill add that part later https://github.com/mg2195 ***ill only push changes to github if something is fixed...or improved, so my sources should always produce a working build of the most stable CM10 available***
mg2195 said:
The mic works for everything except calls...ive tested it using the voice search app...i searched pizza lol, but it recognized what i said and BAM...all the local pizzerias
Apparntly ATT payed HTC extra to add some extra "security" features...the result is broken in-call mic for ATT users...still waiting for confirmation but if you are a non ATT user then in-call mic SHOULD work...
i stopped my research for a little bit and got my github set up...if you understand how it works you can track my progress there whenever i upload changes...also i edited the third post with instructions on how to build CM10 using my sources, you must already have a build environment set up though...ill add that part later https://github.com/mg2195 ***ill only push changes to github if something is fixed...or improved, so my sources should always produce a working build of the most stable CM10 available***
Click to expand...
Click to collapse
Please take a look at my updated post (a few up).
Mic for calls do not work for T-Mobile either. Logcats for all of that in that post, which should help you pinpoint some [hopefully].
theslam08 said:
Please take a look at my updated post (a few up).
Mic for calls do not work for T-Mobile either. Logcats for all of that in that post, which should help you pinpoint some [hopefully].
Click to expand...
Click to collapse
Thanks! I'll take a look later...and you have an Att vivid unlocked for T-Mobile?
Maybe in call mic will work for the velocity/raider...me having Att with a vivid...I don't really know, i just remember when syn was working on this he stated in call mic didn't work on Att...but he said it worked for other carriers...
I was able to use mic for voice search...so the problem isn't with the mic its self...has to be with the way the vivid handles calls...
Sent from my Holiday using Tapatalk 2
What about including as littlemount of HTC framework as possible for phone calls?
Just throwing ideas out hahah
Related
I wrote this program because I was unable to find a good app capable of recording the other side of the call properly.
Except for AirVoice, all such apps record the speaker rather than the line, and you barely hear the other side in the recordings.
The guy who wrote AirVoice knew the trick but seemed to be very annoyed by the negative feedback from Android Market, where the users of various devices (with the list of supported ones clearly stated!) tried to install that program. Because it wasn't open source, I had to disassemble it in order to write what I wanted exactly.
So the app uses an esoteric HTC driver, and NEEDS THE ROOT ACCESS just to open the device. If you do "adb shell chmod 666 '/dev/voc*' ", it'll never ask you for root access (but you have to be ROOT to execute that command).
It writes the calls in either WAV (recommended) or MP3 format (not tested much; needs some time to encode the file after the call, but the size is about 4 times smaller), stereo (left ear is your voice, right is that of the other party), to "/sdcard/voix" directory.
The kernel driver itself is kinda buggy. Actually, the auto-answer mode is non-functional for kendon's & ninpo's kernels (others not tested). Do NOT select it in Settings unless you've got such ROM and particularly need to reboot your phone on each incoming call . It'd be nice if somebody try to fix that.
If you select "Ask each time" for any incoming calls, be sure to wait half a mo until the confirmation dialog appears. The "Foreground service" (default) setting is also recommended because Android may otherwise kill it if memory is low.
Any comments are welcome. I'm not sure that I'll ever add something to this program because I'm too lazy for that, but any bugs will reasonably be fixed. The code is open source, PM me if you're a programmer and have any ideas how to improve it.
=======================
NOV 24 UPDATE
Numerous improvements/corrections/bugfixes (I'm not removing the previous version as this one haven't been much tested).
Enjoy!
Thanks dude. Great job
avs333 said:
I wrote this program because I was unable to find a good app capable of recording the other side of the call properly.
Except for AirVoice, all such apps record the speaker rather than the line, and you barely hear the other side in the recordings.
The guy who wrote AirVoice knew the trick but seemed to be very annoyed by the negative feedback from Android Market, where the users of various devices (with the list of supported ones clearly stated!) tried to install that program. Because it wasn't open source, I had to disassemble it in order to write what I wanted exactly.
So the app uses an esoteric HTC driver, and NEEDS THE ROOT ACCESS just to open the device. If you do "adb shell chmod 666 '/dev/voc*' ", it'll never ask you for root access (but you have to be ROOT to execute that command).
It writes the calls in either WAV (recommended) or MP3 format (not tested much; needs some time to encode the file after the call, but the size is about 4 times smaller), stereo (left ear is your voice, right is that of the other party), to "/sdcard/voix" directory.
The kernel driver itself is kinda buggy. Actually, the auto-answer mode is non-functional for kendon's & ninpo's kernels (others not tested). Do NOT select it in Settings unless you've got such ROM and particularly need to reboot your phone on each incoming call . It'd be nice if somebody try to fix that.
If you select "Ask each time" for any incoming calls, be sure to wait half a mo until the confirmation dialog appears. The "Foreground service" (default) setting is also recommended because Android may otherwise kill it if memory is low.
Any comments are welcome. I'm not sure that I'll ever add something to this program because I'm too lazy for that, but any bugs will reasonably be fixed. The code is open source, PM me if you're a programmer and have any ideas how to improve it.
Click to expand...
Click to collapse
thanks, good job
but recorded sound a lit low, any chance to make it loud
Aha Thats Great Now i can prove my prank calls
no auto start, please add (i mean after re-boot)
Hi-Fi said:
but recorded sound a lit low, any chance to make it loud
Click to expand...
Click to collapse
No problems with sound volume here, but I'll see if I can add some basic volume normalisation...
Hi-Fi said:
no auto start, please add (i mean after re-boot)
Click to expand...
Click to collapse
Added as an option in Settings. Also fixed a triffle UI bug (forgetting to set proper dialog attributes).
Just tried this, works great on my Hero (Vanilla Eclair 4.0). Thank you very much for this one!
Interesting software. Could you possibly add a new feature: The app saves all calls, but deletes them, if you don't move them to another folder/to your PC.
This because I could record all of my calls, without the risk of making a huge 1Gt folder to fill up my memory. So if the user could choose how many recent calls (2,5,10) the app saves before deleting them I'd be great!
What about battery draining?
This great app is also tiny enough not to reduce drastically battery duration?
TIA
I'd love to see this generalized to not require the HTC driver. Do you think that would be possible?
cool app. anyone know if it would be possible to play an audio file directly to the caller? would come in handy rickrolling damn telemarketers
Very good work. Handy app, for sure.
Can you enable recording mid call?
Works in all Androis Devices? I have a Milestone.
Awesome idea, I've been looking for exactly this sort of software.
I'm having a bug I hope someone can help me with. When I start the program I get a prompt that says "Device does not exist, or its permissions cannot be changed." When I click "OK" it takes me to the screen to uninstall the program.
I'm running an Evo, fully rooted, NAND unlocked, running Virus Airbourne ROM and King #11 kernel.
I never get the prompt from the SuperUser app to give the app root access.
I tried the adb command but it gave me the error:
Unable to chmod dev/voc*: No such file or directory
Having same issue on rooted G2.
Sent from my T-Mobile G2 using XDA App
MercuryTangent said:
Awesome idea, I've been looking for exactly this sort of software.
I'm having a bug I hope someone can help me with. When I start the program I get a prompt that says "Device does not exist, or its permissions cannot be changed." When I click "OK" it takes me to the screen to uninstall the program.
I'm running an Evo, fully rooted, NAND unlocked, running Virus Airbourne ROM and King #11 kernel.
I never get the prompt from the SuperUser app to give the app root access.
I tried the adb command but it gave me the error:
Unable to chmod dev/voc*: No such file or directory
Click to expand...
Click to collapse
I experience the same problems on my rooted DINC. ROM and kernel are in sig.
Am I right to assume that this is a HTC Hero exclusive?
bemymonkey said:
Am I right to assume that this is a HTC Hero exclusive?
Click to expand...
Click to collapse
Likely so, but I'm hoping the dev will extend it or I can find a way to make it work
This is amazing app. The only thing I would beg the author to consider a white status bar icon for normal running service as colored icons there usually break the aestetics of Android UI. The icon can change or become colored while recording, but when only running in the background it should remain white.
I have the same problem (link to uninstall) on my Nexus One. Everything works fine on Hero
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).
I've began to write up a guide for getting Arch usable on the Nexus 7. I just threw it up on google docs because I'm too lazy to try to do the wiki thing until it's more complete. Hopefully it is far enough along to get things rolling for people who are looking to experiment with arch.
Anyway, it's a work in progress, if anyone has suggestions, correction, completions, criticisms, etc then holler.
Linkies
Changelog
========
2013-07-20
--Added instructions for installing the platform tools on an arch host pc
--Added references to wicd and network manager as alternatives to netctl
2013-10-20
--Updated instructions to reflect new *-grouper.zip naming scheme for MultiROM files
--Added instructions for updating the kernel to include kexec
--Got bluetooth 90% working. Interface comes up and can find devices with scan. Can’t get it to pair yet though.
2013-10-24
--Got the bluetooth device to power up on boot by adding a udev rule. Unfortunately the bluetooth daemon seems to be failing as it starts.
2013-10-28
--My keyboard is pairing on boot now. Ugly ugly things to get it working, but it works.
2013-11-03
--Updated the guide to get X working.
2013-11-04
--Tweaked xorg.conf files to get kde and e17 working.
--Added instructions to get Touchégg working to provide more tablety experience
Todo/Bugs
Problems/Bugs/Todo
The following is a list of things that need to be addressed or that I want to address. These things will be tackled in no particular order but hopefully over time the number bugs and problems will go down relative to the number of features I want to add.
Feel free to comment with your own ideas or bug reports.
Fix slow shutdowns after enabling networking with netctl
Fix whatever extremely verbose crash shows up on shutdown after setting up bluetooth
Get bluetooth working without hacks and under bluez5
Get a graphical login working
On screen keyboard (especially at login screen)
Set up an aur and/or googlecode project to automate some of the scripting required to get things working
Automate the process with some kind of setup tool
Replace the google doc with a wiki page in a relevant place
Make a custom spin that works more out of the box
Sound
GPS
Accelerometer
Magnetometer
Hardware buttons
Any other sensors that I forgot or am unaware of
Auto screen rotation
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
joeG78 said:
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
Click to expand...
Click to collapse
Thanks for the feedback
I don't have arch on my pc at the moment, so it's not a given, but i think you are right that people are probably more likely to have arch if they are looking at this guide. I updated the guide with info on how to install the tools from AUR. Also added links to wicd and Network Manager in the arch wiki so people are aware of some options if they don't like netctl, and mentioned that e17 works.
Xorg with alarm on nexus 7
Okay, got ALarm installed on my nexus 7 8GB.
For Xorg, I used files from "plasma active" nexus 7 distribution.
Just take them from the plasma active and put them into your /etc/X11 and X should work.
(I can't post a link, must wait 10 posts, I'll link the files later or you can PM me)
My only problem now is to put a cross-compile toolchain on my computer to be able to compile e17 with illume modules. Tried to compile on my tablet but it's too slow and I've not enough disk free to finish. If anybody can help on this point…
What distribution are you using on your PC? Also you can pm me the link for the xorg configuration and I'll post it for you
OK so I have come as far as installing multirom and I installed the archlinux rom and got this error when I tried to boot it
"kexec-hardboot support required to boot this kernel"
How do I resolve this?
thecrimsonfukr said:
OK so I have come as far as installing multirom and I installed the archlinux rom and got this error when I tried to boot it
"kexec-hardboot support required to boot this kernel"
How do I resolve this?
Click to expand...
Click to collapse
Go back and reread the multirom thread, then install a kexec-hardboot patched kernel in your internal rom.
Sent from my SGH-T679 using xda premium
joeG78 said:
Go back and reread the multirom thread, then install a kexec-hardboot patched kernel in your internal rom.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Thank you! I didnt realize it was that simple... for some reason i find the original multirom post difficult to follow.
thecrimsonfukr said:
Thank you! I didnt realize it was that simple... for some reason i find the original multirom post difficult to follow.
Click to expand...
Click to collapse
Hello
i want install arch linux on nexus 7 , but i confuse about it . is arch linux on nexus 7 fast and stable ?
can i watch hd video in arch linux withot lag ? before days i install ubuntu desktop on N7 but when i open video HD ( not full) with vlc , it somtimes play withot sound and it have lag . unity is heavy for nexus 7 , i want install arch + lxde . is it fater ?
sorry for english .
For me Arch works without any problems but when I type startx xserver freezes after the first image of xfce or e17.
Has anybody a solution?
? How to install e17 ?
joeG78 said:
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
Click to expand...
Click to collapse
e17 is the fast
so , i want to installing to my nexus 7
thanks .
Why ? my bluetooth not work?
not find the device ????
ylixir said:
I've began to write up a guide for getting Arch usable on the Nexus 7. I just threw it up on google docs because I'm too lazy to try to do the wiki thing until it's more complete. Hopefully it is far enough along to get things rolling for people who are looking to experiment with arch.
Anyway, it's a work in progress, if anyone has suggestions, correction, completions, criticisms, etc then holler.
My bluetooth not working
cannot find the device ??
Nexus 7 32GB Wifi
Click to expand...
Click to collapse
bluetooth
I have bluetooth (almost) working. I've put instructions in the guide. They aren't really a final solution, but maybe people who are running gui's can tell me if they work. I know I have the hardware working because I can see my keyboard when I scan for it, but I can't figure out how to get bluez5 to pair from the command line. Hopefully someone has better luck with a gui?
bluetooth
I've got Bluetooth working. I even have it pairing automatically on boot with a keyboard. Its an ugly solution but it works. The guide has been updated. I'll tackle X next
My Arch Install
Hey just wanted to add my install experience to the thread hopefully to help others. First of all I want say thanks for all documentation from the previous posters. I tried to follow the instructions as close as possible for a kde install, but I ran into some trouble with lightdm, so I tried kdm instead. And I can happily report it has worked swimmingly. Instructions on how to setup kdm, navigate to /usr/share/config/kdm. First edit the kdmrc to turn off the themed greeter. Then add the xvkbd to the XSetup file as in the lightdm setup. Another thing I did was utilize the plasmaboard widget on my main kde panel for my on screen keyboard once I log in. It seems to work much better than xvkbd for me. I can also confirm flash is working great.
So this really close to totally replacing my linux laptop, especially when I am on the go, in fact I am writing this post on the device in arch. However one key piece is still missing for me is sound. I can't seem to coax any sound out the device with my arch install, and amarok crashes on startup, even though both these items were working perfectly in ubuntu. If any one has any ideas how to make audio and amarok work I would be immensely grateful. Also thanks again, I am so happy to be rid of the X11 touch race condition. I have added a screenshot of me editing this post for those interested as well.
Figured out sound!
I think i found a solution to all of my troubles from my previous post. Amarok started working after a pacman update. My general audio problems seem to be caused by the linux for tegra audio drivers lack of head phone jack detection, I found a workaround the ubuntu nexus 7 launchpad bug tracker: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1068804/comments/24. For the tldr crowd basically you have to use alsamixer manually mute and unmute the int_spkr channel for speaker audio and the int_mic channel to enable headphones. Then you can use the output and and hp to channels adjust volume for speaker and headphones respectively. It also might help to do a suspend resume cycle i sound still isn't working. Thanks to everyone else, hopefully others will find this useful as well.
Many thanks for your work!!! I'm using it on a nexus 7 with glass and touch broken (unuseless) but now it lives!!! and is a very responsive lxde desktop with xrdp starting on boot which I use with amule or bittorrent all night long...
two questions:
1) for me it does not work shutdown -r now or reboot... it close immediately all network connections but I have to keep power button 10 sec to restart system...
2) using it with an hub usb I'm trying to connect a big hard disk: pcmanfm (lxde file manager) refuse to mount it saying than it is not authorized... (I've followed archlinux wiki: it work on my archlinux desktop but not in nexus 7).
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?
Alright everyone, I'm Trailblazer101, an Android Developer who likes to take advantage of, and make better, the unique features of the phones I purchase. I started off with the Samsung Continuum back in 2010, which had a ticker ahead of its time, and went from there. I work 2 jobs, so time is tight sometimes, but I still manage to work on these things, a fun passion/hobby.
Status Updates
Code:
5/12
--- I got my patch working, and tested it out with a simple demo that takes advantage of the new capabilities. I've posted a Guide below!
5/10
--- Now that Verizon users have root, I will begin testing this myself :) Thanks to those who helped me figure out what we'd have to do, so I can get started right off the bat! I'll keep you posted.
What is this?!!
Okay, so by default the Feeds that you can make are restricted to the capabilities of a RemoteView. This severely limits what you can do with the Feed. Take a look here to see what exactly is supported, by default: http://stackoverflow.com/a/16089389
However, any Samsung App (which includes a few signed by Samsung on the Galaxy Apps Exclusives page) has the ability to put whatever it wants on the screen, just like a regular App. I've now extended that invitation on over to you/us!
Guide
The steps to take advantage of this is a little convoluted, so let me break it down for you easy!
STEP 1:
You have to flash my patch to allow this development to actually work. You can download it here: View attachment Trailblazer101_S6Edge_Advanced_Feeds_Patch.zip. Then flash it using FlashFire, or extract the zip and put everything where it needs to go, making sure to set the permissions appropriately!
STEP 2:
Now you can start developing your new Custom Feed! I would suggest using my simple demo project as your base, and going from there! You can find that here: View attachment EdgeScreen-BACKUP.zip. Extract it and take a look at the source!
STEP 3:
From here on out is where things get tricky... Without changing a thing, if you build from source and try to debug, it won't work. Why? Because the API that Samsung gives developers, like us, is different than the one they use for themselves. So Here's what you gotta do-- without changing a thing, build the Project. The best way to do that without debugging within Android Studio is to go to Gradle Projects -> :app -> Tasks -> build -> assembleDebug. This'll make the built apk and put it within "..\.EdgeScreen-BACKUP\app\build\outputs\apk\app-debug.apk".
STEP 4:
I'm assuming you have the latest Java Development Kit, and Android SDK, installed and configured properly, with their paths in the PATH variable, accordingly. You should also know how to use apktool for decompilation, at least a little I've compiled a toolkit folder based off of the test Project I shared above, which includes apktool, the NEW Samsung API files, the original built apk, and the already modified decompiled source/apk. You can download that here: View attachment Decompilation_Data.zip. Then, open a Command Prompt window and "cd" to the extracted folder.
STEP 5:
Decompile the built apk, which should be the same as the one in the extracted folder, using apktool like this:
Code:
.\apktool\apktool d -f TestFeed_orig.apk
STEP 6:
Compare the decompiled folder "TestFeed_orig" with my already modified "TestFeed_modded" one. I suggest using WinMerge! You'll see that the 'TestFeed_orig\smali\com\samsung\android\sdk' folder is very different. That's what I was talking about before, how Samsung Feeds have more options in their API. So delete the 'TestFeed_orig\smali\com\samsung' folder, and replace with the one in the '---SAMSUNG API---' folder.
STEP 7:
Continue comparing the two folders. Basically the rest of the changes are just getting our application to call the new Samsung API properly, instead of the stubs I was using in the Project. There aren't many changes you have to make, but they're all important!
STEP 8:
Once the two folders are the same, recompile it using apktool, like so:
Code:
.\apktool\apktool b TestFeed_orig
STEP 9:
Sign the new compiled apk stored in 'TestFeed_orig\dist' using your signing key. You can make your own, then use it to sign the app, following the instructions here: Official Instructions for Manual Signing.
STEP 10:
Install the newly signed apk, and enable the Feed by going to: Settings-> Edge screen -> Information stream -> Manage Feeds -> *ENABLE* FeedsCocktailExample! You may have to restart, or just hit 'reorder' in the top left. That sometimes fast-triggers it. Now turn off the screen, do the Feed Gesture to get it to turn on, and you should see our Custom Feed! It doesn't look like much, but it's using a custom view, HorizontalTextView, that would not work otherwise.
From here the options are endless. You can follow these steps and my Sample Project to play a video for a feed, if you wanted! Whatever strikes your fancy!
If you followed these steps and appreciate the help, show this thread some love, and maybe. Well i'd say buy me a beer, but it'll probably go to textbooks instead
Developer/Advanced Information!
We can make our own Feeds no problem, without root, they are just forced to use a RemoteView directly, which for all intents and purposes, is a pain in the kiester. Instead, it would be a lot nicer/convenient, without even mentioning the more advanced functionality we could bring, to use our own Views. However the version of SlookCocktailManager.UpdateCocktail that allows this is only found within a more advanced API, one I/no typical user don't have access to directly. BUT, I can still access it by decompiling for example the Edge RSS app from the Samsung AppStore, and putting/replacing the "sdk" folder from that into my own decompiled app, and recompiling. Easy enough, with apktool! (Of course with the headache of adding in my own temporary shell classes, in the project, so that I can actually write the calls, and just change the reference within the smali code once that sdk is replaced) The problem is, even when you do this, and it builds fine, installs great, and even begins initializing properly, we get an error from within CocktailBarService, the file I'm having you replace. More specifically, I tracked down the actual problem, and it comes back to "CocktailWhiteList", a class within CocktailBarServices, then checks the signature of the calling application, our Custom Feed, and sees if it comes from Samsung. This none of my expertise can fix, without being rooted, but trust me I tried. Now that we are rooted I was able to patch said apk, and get my own apps to work! Hurray!
cocktailbar service crashes when going into 'edge screen' option in settings menu.
logcat attached
Edit: sorry didn't rename cocktail bar (cocktailbarservice_signed to cocktailbarservice)
now it doesn't visibly crash, it just wont let me go into 'edge screen' option in settings menu
new log cat uploaded
This man looks promising! You have my S6 edge as soon as I have an official TWRP with working backup and restore
ktetreault14 said:
This man looks promising! You have my S6 edge as soon as I have an official TWRP with working backup and restore
Click to expand...
Click to collapse
I will help as well, when these tools are out for us..
Thanks for bringing cool stuff like this to the phone at this early date!
ktetreault14 said:
This man looks promising! You have my S6 edge as soon as I have an official TWRP with working backup and restore
Click to expand...
Click to collapse
How deep are you willing to go? Because it would be awesome if you could clear dalvik-cache, since I see this, right off the bat:
Code:
: Failed to find OatDexFile for DexFile /system/priv-app/CocktailBarService/CocktailBarService.apk ( canonical path /system/priv-app/CocktailBarService/CocktailBarService.apk) with checksum 0xfbfcb9f7 in OatFile /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex
EDIT: could you also make sure that you set the right permissions for the apk? I'm getting the impression that they might be off with:
Code:
msg=audit(1429397519.049:355): auid=4294967295 uid=10001 gid=10001 ses=4294967295 subj=u:r:untrusted_app:s0 pid=12605 comm="ktailbarservice" reason="memory violation" sig=11
EDIT2: We might have to disable SELinux... That's rather unfortunate/puts a rather large damper on things, until custom kernels come out at least... After starting a root shell, can you try:
Code:
setenforce 0
I don't know if it'll work, but if that goes through successfully try and launch the Edge Settings Screen again!
EDIT3: Do'h. It may have been something really simple *crosses fingers* Could you please re-download the CocktailBarService, and try doing the same thing you did last time, with right permissions, and maybe a dalvik-cache wipe if it doesn't work!?
Tried the new apk you uploaded. Getting a force close still when trying to open. I changed SELINUX to permissive, wiped dalvik, even tried deleting arm64 folder as well. No luck.
04-19 00:25:09.907 E/AndroidRuntime(15867): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.samsung.android.app.cocktailbarservice/com.samsung.android.app.cocktailbarservice.settings.EdgeScreenSettingsMain}: java.lang.SecurityException: Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
Was searching through logcat and found this. May this have something to do with the issue?
wase4711 said:
I will help as well, when these tools are out for us..
Thanks for bringing cool stuff like this to the phone at this early date!
Click to expand...
Click to collapse
Don't mean to hijack thread, but "Tool" is already available here:
NB: Chrome and IE don't translate into "Save file" - Use Mozilla which does > copy to phone and flash.
https://blck.io/twrp-2.8.6.0-zeroltetmo.img
Perfectly working on T-Mobile S6 Edge
Will
RoM_Addict said:
Don't mean to hijack thread, but "Tool" is already available here:
NB: Chrome and IE don't translate into "Save file" - Use Mozilla which does > copy to phone and flash.
https://blck.io/twrp-2.8.6.0-zeroltetmo.img
Perfectly working on T-Mobile S6 Edge
Will
Click to expand...
Click to collapse
that version doesn't work properly for me and many others; waiting for an "official" version from the TWRP folks..
trailblazer101 said:
How deep are you willing to go? Because it would be awesome if you could clear dalvik-cache, since I see this, right off the bat:
Code:
: Failed to find OatDexFile for DexFile /system/priv-app/CocktailBarService/CocktailBarService.apk ( canonical path /system/priv-app/CocktailBarService/CocktailBarService.apk) with checksum 0xfbfcb9f7 in OatFile /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex
EDIT: could you also make sure that you set the right permissions for the apk? I'm getting the impression that they might be off with:
Code:
msg=audit(1429397519.049:355): auid=4294967295 uid=10001 gid=10001 ses=4294967295 subj=u:r:untrusted_app:s0 pid=12605 comm="ktailbarservice" reason="memory violation" sig=11
EDIT2: We might have to disable SELinux... That's rather unfortunate/puts a rather large damper on things, until custom kernels come out at least... After starting a root shell, can you try:
Code:
setenforce 0
I don't know if it'll work, but if that goes through successfully try and launch the Edge Settings Screen again!
EDIT3: Do'h. It may have been something really simple *crosses fingers* Could you please re-download the CocktailBarService, and try doing the same thing you did last time, with right permissions, and maybe a dalvik-cache wipe if it doesn't work!?
Click to expand...
Click to collapse
Hi trailblazer, I set the permissions the same as the original apk ,
right lets try again: I've downloaded the new version and set permissions, wiped dalvik-cache but when trying to disable SELinux i get
tmp-mksh: 0 : not found.
and when going into 'edge screen' settings i get unfortunsatly cocktailbar service has stopped.
Catlog attached:
I used this to modify SELINUX. For anyone else who is helping out, try this.
[4/19] QuickLaunch Demo And Advanced Feed Development Request For Rooted Users
b-reezy said:
I used this to modify SELINUX. For anyone else who is helping out, try this.
Click to expand...
Click to collapse
I sent you a PM! I explicitly declared that permission for each activity, so let's see how it goes now! I put the same apk I sent you now on the OP, so the other testers can try it! In the mean-time, I do have something real for you guys to play with! It's the QuickLaunch window, customizable and all (from hitting the Feeds Settings Icon). I'll put that in the OP with the tag "WORKS(Kinda)"!
One thing, which is a big reason why I'm trying to do it this way-- clicking the icons launches the app, it just doesn't turn the screen back on! I've tracked it down, and it seems as if when the Feed Screen is on, it has the SCover flag set to on, manually, but when a user clicks a button from another Feed, it turns that flag back off, thus turning the screen back on. The easiest/cleanest way for us to do that too would be our Custom Feed Panel implementing the same OnClickHandler that the others do, just can't without doingwhat we're trying to do!
EDIT: Please still use the QuickLaunch apk with the tag "Signed" though for testing the replacement of CocktailBarService! My new one just does it the bad way, and had to get rid of the code for trying the good.
(There's other ways to turn the screen on, but the way I'm trying to do it does it easily, and allows for more advanced functionality!)
FOR DEVELOPERS:
If you are interested in taking what I have and running with it/collaborating, I am more than willing to send all sources of what I have so far, my resources that I've been using, along with all information gathered so far. Just ask!
Hopefully this will become available for non-rooted. I am DIEING to get more functionality out of the Edge API for this phone. The feed is an awesome option, but having to swiping finger is a pain in the @$$. A double tap on the edge or an automatic turn on would be AWESOME when Texts or missed calls are there.
b-reezy said:
I used this to modify SELINUX. For anyone else who is helping out, try this.
Click to expand...
Click to collapse
BTW.. can be disabled in the kernel source also.. I did that in m8 times
trailblazer101 said:
I sent you a PM! I explicitly declared that permission for each activity, so let's see how it goes now! I put the same apk I sent you now on the OP, so the other testers can try it! In the mean-time, I do have something real for you guys to play with! It's the QuickLaunch window, customizable and all (from hitting the Feeds Settings Icon). I'll put that in the OP with the tag "WORKS(Kinda)"!
One thing, which is a big reason why I'm trying to do it this way-- clicking the icons launches the app, it just doesn't turn the screen back on! I've tracked it down, and it seems as if when the Feed Screen is on, it has the SCover flag set to on, manually, but when a user clicks a button from another Feed, it turns that flag back off, thus turning the screen back on. The easiest/cleanest way for us to do that too would be our Custom Feed Panel implementing the same OnClickHandler that the others do, just can't without doingwhat we're trying to do!
EDIT: Please still use the QuickLaunch apk with the tag "Signed" though for testing the replacement of CocktailBarService! My new one just does it the bad way, and had to get rid of the code for trying the good.
(There's other ways to turn the screen on, but the way I'm trying to do it does it easily, and allows for more advanced functionality!)
FOR DEVELOPERS:
If you are interested in taking what I have and running with it/collaborating, I am more than willing to send all sources of what I have so far, my resources that I've been using, along with all information gathered so far. Just ask!
Click to expand...
Click to collapse
Liking the Quicklaunch app , are you still needing testers? or have you got all the info you need?
Alex-V said:
BTW.. can be disabled in the kernel source also.. I did that in m8 times
Click to expand...
Click to collapse
Exactly and imo its better if its done this way..
for anyone interested
you need to edit the security/selinux/selinuxfs.c file from source
FIND:
Code:
selinux_status_update_setenforce(new_value);
#else
ADD RIGHT BELOW "#else":
Code:
new_value = 0;
So it becomes:
Code:
selinux_status_update_setenforce(new_value);
#else
new_value = 0;
or use this one (from the G925F source)
friedrich420 said:
Exactly and imo its better if its done this way..
for anyone interested
you need to edit the security/selinux/selinuxfs.c file from source
FIND:
Code:
selinux_status_update_setenforce(new_value);
#else
ADD RIGHT BELOW "#else":
Code:
new_value = 0;
So it becomes:
Code:
selinux_status_update_setenforce(new_value);
#else
new_value = 0;
or use this one (from the G925F source)
Click to expand...
Click to collapse
yeah.. that's the one I used.. I'm still for and back to root or not..means for me.. develop roms and kernels ..or use it as it is.. lol..
friedrich420 said:
Exactly and imo its better if its done this way..
for anyone interested
you need to edit the security/selinux/selinuxfs.c file from source
FIND:
Code:
selinux_status_update_setenforce(new_value);
#else
ADD RIGHT BELOW "#else":
Code:
new_value = 0;
So it becomes:
Code:
selinux_status_update_setenforce(new_value);
#else
new_value = 0;
or use this one (from the G925F source)
Click to expand...
Click to collapse
Hii my friend, i also still , have a non rooted S6 Edge :thumbup:
Hey guys, I finished the QuickLaunch Feed and posted it in the Apps Folder here:
Click Me!
I did manage to get it to turn the screen on, then, with the clicking of the shortcuts, and it still launches it once unlocked (if you have a lockscreen). I am going to begin work on a music player Feed, now
I will continue development on more advanced Feeds, and also delve into enhancing the edge in other ways, once we Verizon users get root (or until I win the lottery and get a Sprint version ). I see all these great opportunities to make it better, I just can't do anything with it until I'm rooted, since this didn't go as well as I planned. Where we are stuck at now is this, and where it would be too much of a pain for me to do without a phone of my own to test one:
We need to re-sign the system with a signature key we have access to. This includes framework, apps, and the priv-apps signed with the samsung key. Then I can go about doing what I wanted to do, but otherwise, it's a no go.
A developer who does have a Sprint or T-Mobile version with root, I can tell you the information I gathered so far. I have seen where the 'turn screen on gesture' is stored, and all these other great things, I just can't right now
trailblazer101 said:
Hey guys, I finished the QuickLaunch Feed and posted it in the Apps Folder here:
Click Me!
I did manage to get it to turn the screen on, then, with the clicking of the shortcuts, and it still launches it once unlocked (if you have a lockscreen). I am going to begin work on a music player Feed, now
I will continue development on more advanced Feeds, and also delve into enhancing the edge in other ways, once we Verizon users get root (or until I win the lottery and get a Sprint version ). I see all these great opportunities to make it better, I just can't do anything with it until I'm rooted, since this didn't go as well as I planned. Where we are stuck at now is this, and where it would be too much of a pain for me to do without a phone of my own to test one:
We need to re-sign the system with a signature key we have access to. This includes framework, apps, and the priv-apps signed with the samsung key. Then I can go about doing what I wanted to do, but otherwise, it's a no go.
A developer who does have a Sprint or T-Mobile version with root, I can tell you the information I gathered so far. I have seen where the 'turn screen on gesture' is stored, and all these other great things, I just can't right now
Click to expand...
Click to collapse
very nice.. thanks my friend ?
This is just sounding AWESOME! I am on AT&T so will have to wait as well for Root. I was wondering if there is a possability for the edge to just turn on, on its own without the need to swipe the screen? Like when a new notification comes in it will just scroll across the edge (or maybe the icon will blink on and off until you see it and swipe).
I still feel the swipe is to hard to do consistantly and would rather use a double tap or something if the auto on isn't possible.