CyanogeMod 10.1 for HTC ChaCha [a810e / Status]
DISCLAIMER :
Click to expand...
Click to collapse
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. 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 point that finger back at you and laugh.
* make sure you do a nandroid backup in case your phone blows up in
* your face because your phone cant handle the speed :).
*/
* CREDITS
Click to expand...
Click to collapse
Code:
Google
Android
CyanogenMod
androidarmv6
OWLProject
Andreas Schneider
Special thank to winsuk
Special thank to JDevs (kernel,Device & Vendor,bug fixed,guide,support)
alquez
Droste
pabloPL
WFS: crossfire77 rallapag
ChaCha: adumont (patches Lucas Arran
everyone who's been working on CM10.1
And you!
WORKING
Click to expand...
Click to collapse
Code:
- GSM
- Data (2G/3G)
- SMS / MMS
- GPS ???
- USB
- Bluetooth
- WI-FI
- LED
- Camera
- Photocamera [fully]
- Camcoder (low FPS)
- Panorama mode [figured screen sometimes,It can be fixed easily]
- Video playback [not fully, with the 90º rotation playback,It can be fixed easily]
- YouTube [LQ/HQ/Browser] ???
- FM ???
??? I have not tested them
BUG:
Code:
- Battery drain fast
- Front camera
- USB Tethering
- Wi-Fi-Modem
- A2DP lag
- FM Radio
- in-call screen - caller picture is not in the right place with the right dimensions.It can be fixed easily
KERNEL FEATURES
Click to expand...
Click to collapse
https://github.com/OWLProject/OWL-Predator-KERNEL/blob/master/README.md
NO NEXT
BUT I'll upload my source files and step-by-step guide on my github(https://github.com/luzifer1984). a few days later.
I'm Chinese,so I would not compile next ROM for WWE.
My next build is only support for HTC CN CHS.
You can build a rom from source. plz add zh_CN (Chinese Simplified) support. THX!
cm-10.1-20130528-EXPERIMENTAL-chacha-A1.zip
https://docs.google.com/file/d/0B2l4GSuwT6TKMExrRXpmXzZyb3M/edit
CronMod-INT2EXT
http://forum.xda-developers.com/showthread.php?t=1716124
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I havent tested this yet - I will this evening. but. if this works.. THANK YOU. I LOVE YOU SO MUCH FOR FIXING THE DIALPAD.
although I still think the "end call" onscreen button is not necessary.
We need to figure out how to map the End Call button(the red physical button) to end the call(if you havent already) and the number keys(physical keys) need to also input on the dialpad just as they do in CM9(again, havent tested yet. if they do, you're amazing. )
The "Call" or Green physical button should call the number onscreen, or from the home screen it should open the recently called list.
If you can fix all this stuff(or have already) I'll give you money. lol
Am I dreaming? This is amazing news! WOW. WOW. Great. Need to test this asap! Hopefully someone build one for us using your source. To who that would make a build for us: do not forget TURKISH language please!
---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------
By the way, why not you make builds for EU, too? I mean, It shouldn't take some time for you to add a couple of more languages whenever you make a new build.
MD5sum: 5b7ccba99f8b63087696568c85070808
I didn't fix the screen layout of the dialpad. that have been fixed by CM10.1
I want to ask, are you working on front cam? All the problems other than front cam seems solvable to me.
So you have made to first custom kernel for the ChaCha?
Do you intend to work on the kernel? Because even if you don't update the ROM, but you keep the kernel source updated I can build it and make a flashable zip.
The battery life is probably a kernel issue right?
Edit: running it now. The slow wakeup bug from CM10 is fixed. Everything is great, except for battery. I hope there is a breakthrough with that. Thanks for the ROM!
kernel,Device & Vendor
Updated
luzifer1984 said:
kernel,Device & Vendor
Updated
Click to expand...
Click to collapse
So these updates include the fixes that OWLProject offers for Wildfire S? In this build of yours there is lag and now I see it is fixed in wildfire s.
Flashed this rom yesterday, looks some of the issues with CM 10 is fixed with 10.1.
If you are looking for gapps for 10.1, the slim version can be found in http://forum.xda-developers.com/showthread.php?t=2265564
I don’t see major issue with battery drain, it got discharged 25% after 12 hours of usage without wifi or data.
a) Lock screen is completely fixed with CM10.1 and fits wells within the screen
b) In call screen is neatly tailored for landscape
c) Apollo player works in landscape
Some of the things which needs fix
a) Caller id screen is overlapped, and it is very difficult see the caller info
b) Many of the popular application in playstore says ‘This item is not compatible with your device’ example ‘gmail’, ‘apex launcher ‘ etc
c) The proximity sensor is not working.
overall its superb rom, and it alomost complete rom. Thanks bro
ajeevlal said:
b) Many of the popular application in playstore says ‘This item is not compatible with your device’ example ‘gmail’, ‘apex launcher ‘ etc
Click to expand...
Click to collapse
Use any file manager, navigate to /system, look for the build.prop
Thanks to
Furkan DEĞER :
Turns out lcd density is set to 150, which should be 160. I changed it back to 160 and it solved my problem.
Click to expand...
Click to collapse
luzifer1984 said:
Use any file manager, navigate to /system, look for the build.prop
Thanks to
Click to expand...
Click to collapse
i figured that out few min back, i just changed the lcd density in build.prop and cleared the data/cache in playstore and it worked.
Thank you
furkandeger said:
By the way, why not you make builds for EU, too? I mean, It shouldn't take some time for you to add a couple of more languages whenever you make a new build.
Click to expand...
Click to collapse
Because chinese need "Lunar support"
" phoneloc (Chinese phone location) display support "
"Chinese keyboard input support by different kernel"
sorry for my english
luzifer1984 said:
Because chinese need "Lunar support"
" phoneloc (Chinese phone location) display support "
"Chinese keyboard input support by different kernel"
sorry for my english
Click to expand...
Click to collapse
Oh, I see so you have to work on a different kernel. I see. I want to ask something else. There are some lags, especially occuring in lockscreen and also on the system generally. I see in the wildfire s forums, this was a problem with the kernel and it was fixed a couple of days ago. You said you updated, kernel, device and vendor. Does that mean you applied this fix? Because, I'm setting up environment to build from your gits so, when I pulled the repo from you, will this fix be applied on the kernel?
furkandeger said:
Oh, I see so you have to work on a different kernel. I see. I want to ask something else. There are some lags, especially occuring in lockscreen and also on the system generally. I see in the wildfire s forums, this was a problem with the kernel and it was fixed a couple of days ago. You said you updated, kernel, device and vendor. Does that mean you applied this fix? Because, I'm setting up environment to build from your gits so, when I pulled the repo from you, will this fix be applied on the kernel?
Click to expand...
Click to collapse
No. I didn't merge OWL-Predator-KERNEL‘s update.
But you can check https://github.com/Luzifer1984/OWL-Predator-KERNEL/commit/b83a499dcbc60b2a18f917de5845d024d905f3f8
and you will kown how to .
just initial import from chacha-gb-crc-2.6.35-1643b58 (HTCDev.com)
luzifer1984 said:
No. I didn't merge OWL-Predator-KERNEL‘s update.
But you can check https://github.com/Luzifer1984/OWL-Predator-KERNEL/commit/b83a499dcbc60b2a18f917de5845d024d905f3f8
and you will kown how to .
just initial import from chacha-gb-crc-2.6.35-1643b58 (HTCDev.com)
Click to expand...
Click to collapse
OWL-Predator-KERNEL updating too often to catch
I wonder, can we use the kernel from the other CM10 rom? would that fix any performance issues? it would likely result in some of the things fixed to be broken again(camera? I dunno) but in terms of battery life and whatnot, I wonder if it would work
That having been said - I tried out the rom, it's very fast, smooth, it does drain the battery faster, but its not -too- bad. I think this has to do with there being no options for governor(or at least, none that I could find)
The rom has fixed most of the layout issues with the ChaCha. The dial screen is very nice, and the physical keys input once again. The lock screen fits properly now too.
I'll definitely have to do some more testing, but theres a few things that need to be fixed still. One is the LCD density in the build.prop - it causes some issues with certain apps.
EDIT: I also just noticed that while the phone is locked, the cpu must get set to a lower clock speed or something. The phone is very slow to respond when you go to unlock it.
kronflux said:
I wonder, can we use the kernel from the other CM10 rom? would that fix any performance issues? it would likely result in some of the things fixed to be broken again(camera? I dunno) but in terms of battery life and whatnot, I wonder if it would work
That having been said - I tried out the rom, it's very fast, smooth, it does drain the battery faster, but its not -too- bad. I think this has to do with there being no options for governor(or at least, none that I could find)
The rom has fixed most of the layout issues with the ChaCha. The dial screen is very nice, and the physical keys input once again. The lock screen fits properly now too.
I'll definitely have to do some more testing, but theres a few things that need to be fixed still. One is the LCD density in the build.prop - it causes some issues with certain apps.
EDIT: I also just noticed that while the phone is locked, the cpu must get set to a lower clock speed or something. The phone is very slow to respond when you go to unlock it.
Click to expand...
Click to collapse
Using kernel-kitchen you can extract the ramdisk from the CM10 boot.img and then extract the zImage from the CM10.1 boot.img and then combine the resulting zImage and ramdisk. I'm not sure if that makes sense. I'll try it sometime this weekend.
atrix4g18 said:
Using kernel-kitchen you can extract the ramdisk from the CM10 boot.img and then extract the zImage from the CM10.1 boot.img and then combine the resulting zImage and ramdisk. I'm not sure if that makes sense. I'll try it sometime this weekend.
Click to expand...
Click to collapse
well, I can't be positive as of yet, because I just installed it, but I just grabbed the CPU editor thing from here:
http://forum.xda-developers.com/showthread.php?t=1846967
I set it to On-Demand, changed the minimum frequency a tiny bit higher than the default, and set the max to 800. So far it seems like its better on the battery, but again, just installed it like 20 minutes ago, so I'll have to give it some time in testing.
kronflux said:
well, I can't be positive as of yet, because I just installed it, but I just grabbed the CPU editor thing from here:
http://forum.xda-developers.com/showthread.php?t=1846967
I set it to On-Demand, changed the minimum frequency a tiny bit higher than the default, and set the max to 800. So far it seems like its better on the battery, but again, just installed it like 20 minutes ago, so I'll have to give it some time in testing.
Click to expand...
Click to collapse
"Settings"--"About phone" AND press "Build number" 3times to enabled development settings .
then go back "Settings" ,there have show "Performance" .
AND in "Processor" you will see this rom default setting is On-Demand.
CONFIG_MSM_CPU_FREQ_ONDEMAND_MAX=800000
CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN=122880
Yes, you are correct completely.
I also just noticed that while the phone is locked, the cpu must get set to a lower clock speed or something. The phone is very slow to respond when you go to unlock it."
Click to expand...
Click to collapse
that can be save power, I guess
kronflux said:
I wonder, can we use the kernel from the other CM10 rom? would that fix any performance issues? it would likely result in some of the things fixed to be broken again(camera? I dunno) but in terms of battery life and whatnot, I wonder if it would work
That having been said - I tried out the rom, it's very fast, smooth, it does drain the battery faster, but its not -too- bad. I think this has to do with there being no options for governor(or at least, none that I could find)
The rom has fixed most of the layout issues with the ChaCha. The dial screen is very nice, and the physical keys input once again. The lock screen fits properly now too.
I'll definitely have to do some more testing, but theres a few things that need to be fixed still. One is the LCD density in the build.prop - it causes some issues with certain apps.
EDIT: I also just noticed that while the phone is locked, the cpu must get set to a lower clock speed or something. The phone is very slow to respond when you go to unlock it.
Click to expand...
Click to collapse
I don't understand the "very fast, smooth" part. It is not like that for me. Rom is occasionally lagging. When scrolling especially. Sometimes it freezes completely. I believe it's kernel related.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Katnerstone Hybrid Rom
JellyBean 4.2.2
MultiWindow Panels - EOS4 & Cornerstone based
KatKernel & KatBoost included
Hi everyone
Here's the first rom including my Cornerstone port to Jellybean 4.2.2
Quite a few have been impatient to get it, and as TeamEOS prefers not to have an official Cornerstone build at the moment,
I'm taking it into its dedicated thread, so that you can get a first taste, and it should help the traffic in the original EOS4 thread that way too.
Keep in mind that it's still a Work in progress, don't try it unless you're ready to play with a few bugs and workarounds for the moment.
Make sure you read post#2 to see the already known issues & workarounds
DOWNLOADS:
ROM: Katnerstone-4.2.2_V033.zip
FSYNC is off by default in the rom, if you prefer it on just flash this after the rom: fsync_on.zip
Latest Gapps Package: 4.2.2 Gapps for TF101
Older 4.2.1 Eos Gapps for TF101
If you prefer to have the Swipe feature in the default Keyboard you can use this version, but the Keyboard will crash on auto-correction
If you use this version, make sure you go the keyboard settings and change these settings:
+ Auto-correction off
+ Show correction suggestions:always hide
What's Cornerstone ?
Cornerstone is a code modification to the window manager & graphic layers that allows you to run 3 apps together on the same screen in different panels.
You can also run without the 3 panels (so that it is the same than running a regular rom), start or stop the multi panel interface at any time,
the side panels can also be collapsed or expanded at run time.
For more information see their website: http://www.onskreen.com/cornerstone/
Features:
Feature wise you get all the EOS4 features + Cornerstone on top.
See respective links for details.
Installation Notes:
As with any JB4.2.2 roms you need a recent recovery to flash it. The latest TWRP is advised.
Going to Katnerstone4.2.2 from a rom < 4.2.2:
Backup everything !
Go to recovery
Make a full wipe / factory reset
format /system
Flash the rom
Flash optional kernel
Flash gapps
Wipe cache/dalvik
Reboot
Updating from Katnerstone 4.2.2 #VXXX to #VYYY:
You can usually skip the full wipe step.
If ever you encounter an issue make sure you make a full wipe first before reporting though.
Main Goals:
Well of course the ultimate goal will be to eat all the bugs
I'll go by priorities:
- Fix the few bugs introduced when not running in 3 panels mode.
That way we can basically use it as a daily rom, and then decide to activate the panels or not as needed.
- Fix the cornerstone specific bugs.
- Improve the rom and cornerstone features.
Issues & Workarounds:
Keep in mind that it's still a work in progress, and I'll try to improve it as time permit.
Cornerstone is not released for Jellybean 4.2.2, so it required quite a few adjustments, and there are still bugs,
some introduced by the 4.2.2 version, and some that are still there since the 1st cornerstone version for ICS.
See post #2 for more details & how to report
Disclaimer: The usual
The rom is provided as is.
Use at your own risk, I won't be responsible for any damages caused to your Transformer or to yourself.
In most cases if something breaks, flashing a rom on top should fix it.
Changelog: -
Sources: https://github.com/timduru/
Credits:
- TeamEOS for the original EOS4 rom
- Onskreen for the original cornerstone code
Additional info & links
Known Issues & Tips:
Multi-panel interface specific:
When collapsing the small panels, part of the apps will stay on top of the cornerstone interface.
=> just ignore, you can still hit the collapse/expand button in between the apps
Collapsing and expanding might not position the cornerstone "vertical bar" correctly sometime
=> just hit the collapse/expand button a couple of times and it'll reposition correctly.
Without running the multi-panel interface:
The default browser's is displaying the first page even if you choose another page
=> Start the cornerstone panels and try again.
Launcher seems to get killed everytime you hit the home button.
=> It doesn't do it if you run the panels.
Recent apps window might rotate wrongly.
Top most dialogs will get crazy and flash (dialogs asking you for default apps and so on)
=> you can still click on the choices if you're fast
=> hitting the home button or another recent app will get you out of the "loop"
=> running with the multipanel interface is not having this issue, so you can start the multipanel temporarily the time you can pick the choice in the topmost dialog.
General:
The cornerstone code might stop services randomly, this bug is there since the first release of Cornerstone unfortunately, so it might not be easy to fix.
Annoying side effects: everything that relies on a service that has been killed might not work properly (clock will not update, some of the EOSCC changes won't work, and so on...)
The original code is made for TabletUI, so it's not aware of of the statusbar on top, because of that the apps and cornerstone interface is "layered under the status bar currently.
=> For the top cornerstone panel you can still reach the top right button to choose the app running in the panel, even if you can't see the icon just click there.
Not all apps are compatible with the cornerstone code
Desktop wallpaper might not display with default laucher
=> use another launcher
EOS4 & JB Specific:
GPS:
if it is taking a long time to get a lock or no lock, follow this:
http://forum.xda-developers.com/showpost.php?p=38368206&postcount=2452
Google search:
If the version you're using is crashing when you open Google Now,
go to Settings => Language & Input => Voice Search , then uncheck Hotword Detection.
Other Tips
How to report:
Things to check before reporting:
- If it's a general question or if it is not specific to this rom ask in the Q&A section
- make sure you have read all the tips and searched on the forum before reporting an issue.
- try to reproduce your issue right after flashing and before restoring anything
- wait that the cpu usage is down to close to 0% for a few seconds before proceeding with testing.
- Check that it is not already listed in the known issues.
Reports about performances issues:
Keep in mind that coming from a full wipe / factory reset, there are a few cpu and disk io tasks that are going to happen:
- Mediascanner service is going to rescan all your medias, which can take from a few minutes to a few hours or days if you have many
- Google will restore / sync things.
So make sure that it is finished and that some app is not eating the cpu or disk io before reporting.
What to send in your report::
- Make sure you describe exactly what happens before/during/after the issue.
- If you can reproduce it, write a step by step way of reproducing it.
- If your issue is a performance issue, explain in details what you define as such
(is it taking time when you click , is it that it seems to have a low fps ? ..)
Make also sure you indicate the following:
- which rom/version are you using ?
- which kernel are you using ?
- did you follow the exact procedure listed above for flashing ?
- did you restore any of your applications / settings ?
Run these commands in a terminal:
su -
busybox top -n1 > /sdcard/top
dmesg > /sdcard/dmesg
logcat -d > /sdcard/lc
include the resulting files: /sdcard/top & /sdcard/dmesg & /sdcard/lc in your post
Thanks that will help to debug and save me a lot of time if I get correct reports
reserved2
Ermagherd I haven't sat and stared at a download bar like this for quite some time.
This looks pretty cool and is definitely appreciated. But I have to admit I'm more interested in this from a developer point of view than downloading your ZIP
Is this something which is viable to build yourself or integrate into your own Android-build?
From what I can tell from the source, this is an additional overlay which you apply to your device-tree. Is that correct? Or is it just a hot-patched / copied over the Android-repo after it's synced?
Or am I completely missing the big picture? Any feedback appreciated
I managed to work around the trippy flashing screen and overlay system bar, but I'm not able to select the menu button in TiBu whether I'm using Cornerstone or not.
Also I appear to have the weird no desktop image bug from the recent EOS build.
josteink said:
This looks pretty cool and is definitely appreciated. But I have to admit I'm more interested in this from a developer point of view than downloading your ZIP
Is this something which is viable to build yourself or integrate into your own Android-build?
Click to expand...
Click to collapse
The thing with the cornerstone code is that it's heavily modifying the android framework / window manager.
So you get an extra spaghetti layer on top of the existing android window manager spaghetti code
So it's not the easiest to maintain as you'll need to update back & forth and merge the regular rom changes all the time.
From what I can tell from the source, this is an additional overlay which you apply to your device-tree. Is that correct? Or is it just a hot-patched / copied over the Android-repo after it's synced?
Click to expand...
Click to collapse
It's file replacements/patching mostly in frameworks/base
which is quite busy and where most roms modifications already are unfortunately
Then you have the multi panel interface that is in separate packages, so at least that last part is easy to add on top.
But yeah, I'm still pondering how to release the code currently, as it's merged into EOS4 framework/base basically.
Doing file overwriting replacements like posted originally on the cornerstone git won't work well for other roms, these had to be adapted for 4.2.2 & EOS specific code.
I think the less painful might be to just post the new forked framework/base for EOS4.
Have to see...
st0nedpenguin said:
I managed to work around the trippy flashing screen and overlay system bar, but I'm not able to select the menu button in TiBu whether I'm using Cornerstone or not.
Click to expand...
Click to collapse
What's Tibu ?
And do you mean you can't select the button because it's under the status bar at top ?
If it's too high that can definitely happen, until I've fixed that issue listed in post #2
Did you try hitting the menu button on the dock or with LMT ?
Also I appear to have the weird no desktop image bug from the recent EOS build.
Click to expand...
Click to collapse
Yeah the new code doesn't seem to like cornerstone.
It should be fine if you use another launcher.
timduru said:
What's Tibu?
Click to expand...
Click to collapse
I'm guessing Titanium Back Up
timduru said:
What's Tibu ?
And do you mean you can't select the button because it's under the status bar at top ?
If it's too high that can definitely happen, until I've fixed that issue listed in post #2
Did you try hitting the menu button on the dock or with LMT ?
Yeah the new code doesn't seem to like cornerstone.
It should be fine if you use another launcher.
Click to expand...
Click to collapse
Titanium Backup as guessed ^ up there.
It's weird, because I can see the button, I can click on the button, the button even highlights to show the click, but nothing happens.
The wallpaper thing isn't really an issue since as you said I can just use another launcher once I can get my backups working.
st0nedpenguin said:
Titanium Backup as guessed ^ up there.
It's weird, because I can see the button, I can click on the button, the button even highlights to show the click, but nothing happens.
The wallpaper thing isn't really an issue since as you said I can just use another launcher once I can get my backups working.
Click to expand...
Click to collapse
Hmm, yeah that's weird I can reproduce that too, not sure what Titanium backup menu doesn't like...
The other buttons seems to works fine, like the scenario one next to it.
For the moment if you need to change something that is reached with the menu button, I'd advise to flash the regular EOS4 back, change the setting there,
flash back this rom, and only wipe /cache + dalvik-cache without doing a full wipe as to keep the settings / apps
Overall you should be able to "dirty-flash" this rom on top of EOS4, that should save time too.
Well I moved my backups onto the internal sdcard as a lazy fix, but now when I try to restore them in the batch action menu, none of the buttons there work either.
Re: [ROM][JB 4.2.2] [WIP] Katnerstone Hybrid - MultiWindow Panels (Cornerstone)
Tim, you will always surprise me. I'm lucky to share the same device like yours...
If not your work, i would have already spend another 600$ to get another device...
But in my opinion, tf101 bas no challengers because of guys like you. Sincere
Envoyé depuis mon Transformer TF101 avec Tapatalk
Re: [ROM][JB 4.2.2] [WIP] Katnerstone Hybrid - MultiWindow Panels (Cornerstone)
Thanks so much for taking on this exciting project. So far, cornerstone doesn't minimize. It animates like its going to, but then doesn't. The screen cuts off the top of everything whether or not cornerstone is used. And I get flickering whenever I'm suppose to choose how to open a file. The dialog box flickers and its almost impossible to tap the box to make a selection. Also, hiding system bars doesn't work.
Sent from my Transformer TF101 using XDA Premium HD app
bloodge1 said:
Thanks so much for taking on this exciting project. So far, cornerstone doesn't minimize. It animates like its going to, but then doesn't. The screen cut off the top of everything whether or not cornerstone is used. I attached a screenshot of this. And I get flickering whenever I'm suppose to choose how to open a file. The dialog box flickers and its almost impossible to tap the box to make a selection.
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
What do you call minimize, Collapsing the 2 small panels to the right ?
It works for me, but just not all the time, When it doesn't you just need to hit the collapse / expand button again and it should work.
Read post #2 first, as it's indicated there already along with the other stuff you report.
dirty flashing.....
timduru said:
Overall you should be able to "dirty-flash" this rom on top of EOS4, that should save time too.
Click to expand...
Click to collapse
Go on.....tell me more
On your latest B175 from the other day - are you saying that should be able to flash this straight over it? (after backing up of course)
(if any issues do you think I can dirty flash back)
gav2fc said:
Go on.....tell me more
On your latest B175 from the other day - are you saying that should be able to flash this straight over it? (after backing up of course)
(if any issues do you think I can dirty flash back)
Click to expand...
Click to collapse
Yeah should work fine.
Just flash on top and wipe /cache + dalvik-cache should be enough for these versions.
What to do ... I was just thinking yesterday about how beautifully stable and useful my TF101 was and now this comes out. I must resist, must use my system for a while first.
Ahh, to heck with it. nandroid backup & flash this to try it is
[edit so I don't spam the thread]
Wow, just wow. I had wondered if it would be a novelty running windows on a small screen, but no - it took me no time flat to see how useful this could be.
Tim, you have definitely outdone yourself - I'll do my best to run it as a day-to-day build to report anything I can see. So far I see nothing that would prevent me from doing that!
timduru said:
Yeah should work fine.
Just flash on top and wipe /cache + dalvik-cache should be enough for these versions.
Click to expand...
Click to collapse
May I use KatKernel96 for this build or I should use native kernel (built-in your cornerstone by default)?
garryveda said:
May I use KatKernel96 for this build or I should use native kernel (built-in your cornerstone by default)?
Click to expand...
Click to collapse
If I read correctly from the top post, KatKernel is the native included kernel, so it's already there!
CyanogenMod 10.1 (based on Android 4.2.2 "Jelly Bean") for the HTC Liberty/Aria/Gratia/etc
NOTE: Just to make this clear, this is UNOFFICIAL, and NOT supported by CyanogenMod.
Hboot 1.02 or higher is required! (Revolutionary or HTCdev unlock)
Bugs etc:
Gesture typing, Photosphere & voice recognition won't work (see notes below)
Built-in live wallpapers don't work
USB debugging verify (the popup when you plug into a new PC) doesn't work, so it has been disabled
WiFi & USB tethering don't work
Minor graphical glitches that don't happen every time
Camcorder doesn't work
Camera will force close if you have bad videos from the camcorder. Delete (or move) them to fix it
Camera app has graphical glitches (LegacyCamera won't build right now, and I would rather just fix the normal Camera)
Notes:
Android seems to now default to timer mode for button light(s), so they should turn on every time now, but will turn off after a few seconds of no input.
However the screen sometimes being at lowest brightness when turning it on still exists..
Gesture typing, Photosphere, and voice recognition: all require closed-source libraries from Google built for ARMv6, which don't exist.
I can't make any of these work unless Google does.
Links!
Newest build (October 20th, 2013) - http://goo.gl/xBu4Xo
239c552e3725725936df60eda1aa2184
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MediaFire mirror: http://www.mediafire.com/?9p4whmt34zopxtp
Manifest with full ROM & kernel source: https://github.com/WinSuk/android/tree/cm-10.1
Kernel source only: http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227.git/tree/?h=cm-10.1
I may or may not put together a gapps package this time.. If I do it'll be later.
If you want to use rootzwiki's gapps packages (available on goo.im/gapps) and have a standard/close to standard system size, the lib, usr, and probably tts folders are useless for our device and can be removed
Changelog of builds:
Previous builds can be found here or here
20131020 (October 20th, 2013):
Keyboard replaced with 4.1 version to fix crash
CM:
Add lockscreen rotation as an optional rotation setting
Add option for setting device phone number
Calculator: Digit grouping (and other things)
CM Account (includes CM setup screen) - not sure all of its features work on liberty though
Fix QuickMessage mdpi/hdpi layouts
Make notification-shade-collapse-after-dismiss behaviour configurable
Voice Plus app (untested on liberty)
Reduced memory usage on low memory devices
Restore old CyanAlarm as "Nuclear Launch"
Show advanced reboot if using an insecure lock screen
Storage Settings: Allow user to trigger a volume rescan
Trebuchet: Fix MDPI layout
etc
20130705 (July 5th, 2013):
Enabled more input sampling rates - Skype(etc?) fixed
Enabled volume rocker wake (didn't know this was now hidden by default)
Fixed bluetooth tethering
Increased dalvik heap size - editor in Gallery needs it
Trackball will always wake now, no more unreliable script
CM:
Lockscreen widget settings (disable music controls, disable camera, disable multiple widgets)
Option to allow a (subtle) notification vibration during calls
Option to change auto-brightness responsitivity
Option to enable/disable Electron Beam (screen-off animation)
Privacy Guard (link and link)
Quick settings Camera tile - preview doesn't display correctly on liberty
Show application's package name in the "App info" screen
Updated sounds (CyanAlarm, CyanMail, CyanMessage), added new ones (Highscore, Lyon, Rockin, Laser)
etc
20130526 (May 26th, 2013):
Baseline build
Thanks for your hard work!!!
Well it seems the WiFi module didn't get packaged in the zip correctly again, so WiFi doesn't turn on.
New zip uploaded at http://goo.gl/1SS2k with MD5: 15efb5b21dffd2c5a45845e102f8c71d
thnx alot for the hard work im downloading it right now
RIP my HTC Intruder.
The old bud finally gave up on me last night,
Fell from my hand for the tenth time or so, and no more sim card detection/network,
Also seems to be boot-looping/rebooting randomly every now and then.
Definitely hardware.
Its nothing but an mp3 player now.
Loved the tiny thingy.Nothing as cute as it exists as of now.
Rest in piece o old phone, you served well.
:crying:
Click to expand...
Click to collapse
Still, going to flash this CM10.1 even in this terminal condition,
Thanks for keeping this old device alive.
Lets see how it works out.
Thanks for your hard work, WinSuk!!!
Where I can get gapps for this rom?
here goo.im/gapps
but read the end of the description of the rom because there are a couple of folders you can delete
thnx alot for this amazing rom :laugh: its perfect for me cause i don't need tethering of any kind nor the camcorder :laugh: thnx alot man
So it's time to port Ubuntu now, right? Even my new phone (Desire X) doesn't get CM 10.1 or even CM 10, cause we are waiting for kernel sources... I shouldn't have lost this phone...
dansou901 said:
So it's time to port Ubuntu now, right? Even my new phone (Desire X) doesn't get CM 10.1 or even CM 10, cause we are waiting for kernel sources... I shouldn't have lost this phone...
Click to expand...
Click to collapse
That depends on if it has ARMv6 support... It runs on top of CM10.1 sources, but the Ubuntu-specific parts may not support it (like when I tried Boot2Gecko/FirefoxOS, the Android parts were fine, but Gecko didn't seem to have ARMv6 support)
I'll probably try and find out
Edit: Well all of Ubuntu doesn't support ARMv6, so that won't work.
But, Firefox OS hardware requirements say ARMv6 & Adreno 200 or better, so that's a good possibility (not sure if it wasn't supported back when I tried to get it working or if I did something wrong)
WinSuk said:
That depends on if it has ARMv6 support... It runs on top of CM10.1 sources, but the Ubuntu-specific parts may not support it (like when I tried Boot2Gecko/FirefoxOS, the Android parts were fine, but Gecko didn't seem to have ARMv6 support)
I'll probably try and find out
Edit: Well all of Ubuntu doesn't support ARMv6, so that won't work.
But, Firefox OS hardware requirements say ARMv6 & Adreno 200 or better, so that's a good possibility (not sure if it wasn't supported back when I tried to get it working or if I did something wrong)
Click to expand...
Click to collapse
Firefox OS sounds promising! Thanks for all your hard work WinSuk, my mom is loving my old little Aria
how can i let my aria stay awake when charging on this rom ??
rami.ejle said:
how can i let my aria stay awake when charging on this rom ??
Click to expand...
Click to collapse
In developer options, or enable Daydream while charging
Hello!
Many thanx to WinSuk! :good:
I have a question, how to enable screen unlock with trackball? THe powerbutton gets worth day by day
WinSuk said:
In developer options, or enable Daydream while charging
Click to expand...
Click to collapse
srry if im wrong but i can't find the developer options on this rom , but the daydream worked
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
elnone said:
Hello!
Many thanx to WinSuk! :good:
I have a question, how to enable screen unlock with trackball? THe powerbutton gets worth day by day
Click to expand...
Click to collapse
open the terminal emulator app and type "trackballwake" without the "" and done
rami.ejle said:
open the terminal emulator app and type "trackballwake" without the "" and done
Click to expand...
Click to collapse
Now I see pointer, but nothing happens when screen locked. Maybe something else missing in parameters should be set additionally?
that happened to me the first , i don't know what the problem is but i did a full wipe and flashed the rom and tried again before anything else and worked fine
rami.ejle said:
that happened to me the first , i don't know what the problem is but i did a full wipe and flashed the rom and tried again before anything else and worked fine
Click to expand...
Click to collapse
I got it working, until gapps install. ThnX
hey winsuk can we add this to the rom by any way possible i really need it http://forum.xda-developers.com/showthread.php?t=2018146 ??
elnone said:
I got it working, until gapps install. ThnX
Click to expand...
Click to collapse
The GApps you flashed probably filled up the system partition, the Trackball wake script needs at least 1MB free space in the /system partition to work I guess.
Try a lighter/trimmed gapps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INFAMOUS OPEN ANDROID PROJECT
AN INFAMOUS PRODUCTION
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.
*/
By using the rom you agree with the above terms!
ABOUT THE ROM:
You may be asking yourself, "What the hell is IOAP". Well, its simple really so I will keep it short and sweet. IOAP is built from source. Almost similar to AOSP with lots of added features.
FEATURES:
BT Car Fix
Dark UI
Active Display
Halo
MulitWindow
Gesture Anywhere
Appbar
LCD Density
Animation Control: System, listview, Scrolling, Keyboard, and Toast
Custom Progress Bar
Lockscreen Notifications
OmniSwitch
Recent RAM bar
Screen Record
System App Remover
Init.d
Build.prop Mods
GPS Optimizer
Navigation Bar
Expanded Desktop
Slim Recents
MORE!!!
Source:
Rom-https://github.com/IOAP
Kernel-https://github.com/CyanogenMod/android_kernel_htc_msm8960
Screenshots:
Changelog:
Code:
3/17/14 * intitial release for ville
3/18/14 * Added On-The-Go (Turn on from settings/IOAP settings/buttons/Power menu
*v3. 59
Removed GPSOptimizer
Added PACPreformance (open from settings)
Remove QuickSearchBox from build
releasetools: don't create prebuilt_dir path if it exits
av: added missing profiles
rebased: Launcher3
Added ONTHGO, powermenu and tiles (nameless)
Fixed naming convention for jflte bootlogo
Fixed some dependencies
removed paddingLeft broke build after slim card update
CM updates
Removed Bubble option in mms caused fc
Extend installd to support SELinux restorecon function
Add support for ECDSA P-256 with SHA256
libc: Fix memchr inclusion (older devices)
more fixes and tweaks than I can remember...
Downloads:
IOAP FOR VILLE
IOAP GAPPS
PA GAPPS
INSTRUCTIONS:
FULL WIPE, FLASH ROM THEN GApps
BUGS:
Code:
* You tell me
USE THIS RECOVERY
Dont forget the THANKS button
XDA:DevDB Information
INFAMOUS IOAP, a ROM for the HTC One S
Contributors
WhiTeRhiNo, mr impossible, Jamison904, mr impossible, Jamison904
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod, AOSP
Version Information
Status: Stable
Current Stable Version: 3.55
Stable Release Date: 2014-03-17
Created 2014-03-17
Last Updated 2014-03-31
Reserved
Reserved
WhiTeRhiNo said:
...
FEATURES:
BT Car Fix...
Click to expand...
Click to collapse
You got me with this one :laugh: I'll download it and try.
Also I saw that the GAPPS packages from OP are a little bit old (2013). Is there an issue if I use Slim GAPPS that are more recent? Why Slim? Because they have better compatibility with the "dark" switch
NOTE: There's a new official TWRP recovery version 2.7.0 HERE and I can confirm it is full SELinux compatible and you can flash KK ROMs with it. There's no need to use a modded TWRP recovery anymore. I am using it for some days and works great, flashed Twisted and Beanstalk with it (and now I'll try IOAP)
What you might consider adding to the ROM (if it's not already there)...Sound Packs. These are implemented in Beanstalk and provide different sound "sets" that are used for the different ROM sounds (screen lock, camera, tap and so on)
Rapier said:
You got me with this one :laugh: I'll download it and try.
Also I saw that the GAPPS packages from OP are a little bit old (2013). Is there an issue if I use Slim GAPPS that are more recent? Why Slim? Because they have better compatibility with the "dark" switch
NOTE: There's a new official TWRP recovery version 2.7.0 HERE and I can confirm it is full SELinux compatible and you can flash KK ROMs with it. There's no need to use a modded TWRP recovery anymore. I am using it for some days and works great, flashed Twisted and Beanstalk with it (and now I'll try IOAP)
Click to expand...
Click to collapse
Lol yea I remembered u. And thanks for the info I'll update op with recovery when I wake up lol
And u can use whichever GAPPS u prefer I just linked our teams GAPPS they will get updated eventually but feel free to use any they should all work fine
Edit: and I will definitely look into the sound packs and see what we can do
WhiTeRhiNo said:
...Edit: and I will definitely look into the sound packs and see what we can do
Click to expand...
Click to collapse
LOL..No need to look into it. It is ALREADY included :laugh:
What I've noticed so far:
- there are no color options for status bar items: battery, signal, clock
- there are no color options for the tiles
- there are no clock options at all: show date/AM/PM, clock color, clock position (center, right)
- even if in build.prop default screen DPI are set to 240, the look of the interface is like it is set to 200 (or something like this). Everything is smaller including status bar. I'll try to change DPI from the settings and reboot to see what's happening
- Messaging app is FC when entering in it and tapping on a message or sending a new message (this is annoying as hell for those texting a lot). Workaround: use Hangouts for SMS, that is working
- "selector notification" (also known as IME notification) ON/Off checkbox is doubled: once is present in Languages & Input and once is in Advanced Settings under Language & Input
- this is the only ROM for which Thyrus's HoloDark KK Theme (which in my opinion is the most good looking and complete dark theme out there) is theming the dialer completely including the incoming call screen. That means that the dialer is based on Carbon or Slim cause for any other dialers from any ROM I've tried, it is not properly themed (the incoming call screen has a semitransparent band on the bottom, text in the non-intrusive call is readable...and so on)
I'll add more as I test more... So far very good job :good:
---------- Post added at 12:03 PM ---------- Previous post was at 11:47 AM ----------
Rapier said:
...
- there are no color options for status bar items: battery, signal, clock
..
- there are no clock options at all: show date/AM/PM, clock color, clock position (center, right)
Click to expand...
Click to collapse
EDIT on that. Clock options (both color and position, etc) are present in Settings - Clock & Date. Not the usual place for them compared to other ROMs but they're present. Still looking for battery color
OK. Got sorted out the Messaging app FC as well. There's an option in Messaging settings to use "Speech Bubble theme". If that option is enabled (it is by default), Messaging app is FCing. Disable it and it'll work but you'll have the background white that's not so nice looking on dark theme...but that will be sorted out later
I just installed your new Rom as I was curious. All in all nice job, but I haven't tested to much. One issue is, that I get FC's, when I try to open the Dev settings.
Hi, which version of Hboot for this rom? thanks
kalel77 said:
Hi, which version of Hboot for this rom? thanks
Click to expand...
Click to collapse
2.15
Thanks for the feedback guys. All things will be improved and fixed in time. Keep the feedback coming so I know what u like and what doesn't work
derkleinebroicher said:
I just installed your new Rom as I was curious. All in all nice job, but I haven't tested to much. One issue is, that I get FC's, when I try to open the Dev settings.
Click to expand...
Click to collapse
Dont have that problem. You are talking about developer options in settings correct?
Nice rom and all i need... nice font nice design...
CRT animation in Display does not work properly. Regardless of the setting, there's only the colapse horizontal that is working
Sent from nowhere over the air..
WhiTeRhiNo said:
Dont have that problem. You are talking about developer options in settings correct?
Click to expand...
Click to collapse
Exactly! And I just made a new clean install, but with same result. Furthermore, when I tab the build number in settings and dev options are enabled, there should come something like "You are arlready a Dev." But nothing happens in this case, so for me, there is something wrong. BTW, I'm running ART, which normally should be no problem, I guess. Going to make some more inquiries and keep you informed.
derkleinebroicher said:
Exactly! And I just made a new clean install, but with same result. Furthermore, when I tab the build number in settings and dev options are enabled, there should come something like "You are arlready a Dev." But nothing happens in this case, so for me, there is something wrong. BTW, I'm running ART, which normally should be no problem, I guess. Going to make some more inquiries and keep you informed.
Click to expand...
Click to collapse
Not quite, if you're using ART it could very well be the problem. ART is experimental and it has issues sometimes. Doesn't mean that if you used ART on other ROMs without issues, you won't have issues at all with any ROM.
First, you don't need to tap several times on build number. This is needed only if Dev Options are not visible in settings but this is not the case, they are. Second, Dev Options works perfectly so you could switch to Dalvik and check again
@WhiTeRhiNo: there's another issue I found and that's related to audio libs somewhat. ONLY if using headset (wired ones not BT), if I'm in a call, the other party report that I can be barely heard, distorted and with frequent interruptions. It is not happening on normal call through handset, speaker or BT car kit. If for examplke I start the call through headset, after unplugging them all things go to normal if I continue to talk via handset. This is something I got also on TwistedKat but was not present in Beanstalk. I don't think it's kernel related because on all three ROMs I've used the same kernel with the same settings. Check with phoenixita what audio libs he's using, I'm not even sure which are used when headset is plugged in. Practically I cannot use a headset during a call because of this. I can hear perfectly, also music coming through OK, just that when I speak the other party cannot hear me well.
Rapier said:
Not quite, if you're using ART it could very well be the problem. ART is experimental and it has issues sometimes. Doesn't mean that if you used ART on other ROMs without issues, you won't have issues at all with any ROM.
First, you don't need to tap several times on build number. This is needed only if Dev Options are not visible in settings but this is not the case, they are. Second, Dev Options works perfectly so you could switch to Dalvik and check again
@WhiTeRhiNo: there's another issue I found and that's related to audio libs somewhat. ONLY if using headset (wired ones not BT), if I'm in a call, the other party report that I can be barely heard, distorted and with frequent interruptions. It is not happening on normal call through handset, speaker or BT car kit. If for examplke I start the call through headset, after unplugging them all things go to normal if I continue to talk via handset. This is something I got also on TwistedKat but was not present in Beanstalk. I don't think it's kernel related because on all three ROMs I've used the same kernel with the same settings. Check with phoenixita what audio libs he's using, I'm not even sure which are used when headset is plugged in. Practically I cannot use a headset during a call because of this. I can hear perfectly, also music coming through OK, just that when I speak the other party cannot hear me well.
Click to expand...
Click to collapse
I second the audio libs issue. I found the same problem actually. Any fix? Only work around I see is not to use my headphones in a call. My voice apparently drops in and out periodically, but I hear everything perfectly.
Sent from my One S using Tapatalk
Maybe something will be found in Beanstalk, that ROM does not have this issue. So far I found it in TwistedKat and on this one but to be honest I didn't test the headset with all the ROMs I've flashed
You asked also for suggestions what to add to the ROM. Well there are some, I'll make a list with what just crossed my mind:
- color option for battery
- lockscreen theming capabilities (lockring, colors, etc)
- tiles color settings
- add custom tile and contact tile
Rapier said:
Not quite, if you're using ART it could very well be the problem. ART is experimental and it has issues sometimes. Doesn't mean that if you used ART on other ROMs without issues, you won't have issues at all with any ROM.
First, you don't need to tap several times on build number. This is needed only if Dev Options are not visible in settings but this is not the case, they are. Second, Dev Options works perfectly so you could switch to Dalvik and check again.
Click to expand...
Click to collapse
Tapping the build number was simply to see, what happens. I know, I don't have to do this, if dev options is already enabled. And sadly, I can't switch the runtime on this Rom as long, as I can't open dev options. This will get a bigger operation. But maybe I will return to dalvik anyway as I can't see a really convincing advantage in using ART.
derkleinebroicher said:
Tapping the build number was simply to see, what happens. I know, I don't have to do this, if dev options is already enabled. And sadly, I can't switch the runtime on this Rom as long, as I can't open dev options. This will get a bigger operation. But maybe I will return to dalvik anyway as I can't see a really convincing advantage in using ART.
Click to expand...
Click to collapse
It just crossed my mind that the theory that ART broke dev options is correct. You COULD.enter dev options initially because you couldn't switch to ART in the first place. And after switching dev options didn't work.... Right? There is no ROM that has ART enabled by default.
Ok, if you don't want to full wipe and start over, here's a quick workaround to get you back to Dalvik. Install Xposed framework and reboot after activating it. Xposed is not ART compatible and has a safety measure built in...whenever try to install it, it switches to Dalvik automatically
Sent from nowhere over the air..
EDIT: It's a little bit unclear for me how the "multi window" feature work. There's a note in the Halo settings screen that if Halo is enabled, multi window is disabled. OK, I've disabled Halo completely, now what? There's no option I can see to make the apps show in multi window. Is there something that should be done?
Found a strange "bug" if I may call it like this but it's annoying as hell. I text alot. Mostly on whatsapp and I am using SwiftKey keyboard that's one of the best. Well, I am used to type fast, I swipe alot and I can say I am pretty good at it. What I've noticed though since I used this ROM, is that I have a lot of cases in which I don't insert "space" between words even if I was sure I've pressed space. Then I start to pay attention to this detail and I've noticed that there a small bottom area, several millimeters tall that's unresponsive some times. Not all the times, just sometimes. If I press any keyboard button on the bottom row like space, punctuation and so on, nothing happens. On a second tap it start to react but if I send the message and start another one it happens again. The area is almost half the height of the space bar and therefore it's happening not to insert a space. I've tested this alot till I figured it out. Don't know why is happening but it's present only on this ROM. I type the same every time and I am not talking about just few words. I've flashed and used this ROM since it was released so I was texting alot whole day. Now I've switched to Beanstalk and it's not happening. Don't know how to isolate the issue or if it was only for me but I thought it worth to be mentioned
Multi window is on as long as halo isn't activated there are no options for multi window just turn halo off then in your recent apps just long press an app and choose multi window
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOSP is a open source project based on Slim,AOSP and Cyanogen-Mod founded by jenkins-84, my aim is to bring a fast and smooth lightweight base with optimized performance, This Rom started out on the HTC One (m7) but now starting to make its way to other devices. Maintainers and Support is always welcome as this Rom is pretty much a one man show atm. I'm not responsible for anything that happens to your device so do recommend you do make a backup before flashing!
Feature's
Code:
* Advanced reboot set to default
* Development options unlocked
* Status bar Battery/Clock customization
* Configurable 0, 90, 180 and 270 degree rotation
* Quick tile customization
* Recent clear all
* Ambient display (only certain devices)
* Expandable desktop
* Partition size info
* Brightness control on status bar
* Double tap status bar to sleep
* Network traffic in status bar
* Disable/enable search bar in recent menu
* LCD density control
* SuperSU in settings
* Optimization boot-up message with random colours
* Eleven Music app
* AudioFX
* Viper4Android
* Kernel Adiutor
* Cyanogen STK
* Layers
* Slim Pie
* Slim Heads Up Customizations
* Hide Network Arrows
* Navbar Customizations
* Hardware Key Rebinding
* Slim Actions
* Slim Recents
* Live Display
* Advanced Volume Controls
* Chamber of Secrets
* Slim Global Menu
* Expanding Volume Panel
* Silent mode now available
* Blacklist
* Double tap lockscreen shortcuts
* Slim recents
* CMHW features
* App2sd
* More quick setting tiles
* Extra dashboard switches
* Expanding volume panel
* Silent mode now available
How To Install :
* Make sure your on FOTAWRP RECOVERY https://www.androidfilehost.com/?fid=95916177934529111
* Download ROM & GAPPS to ext sdcard
* Enter Recovery and do a FULL wipe
* Flash ROM, Flash Gapps
* Reboot device after finishing installation
* Enjoy
Downloads :
ROM:https://www.androidfilehost.com/?fid=24052804347771745
GAPPS:http://forum.xda-developers.com/slim...imkat-t2792842
**For V4A To Work Please change SELINUX To PERMISSIVE in Dev options**
XDA:DevDB Information
[ROM] Official NOSP , ROM for the Sony Xperia Z3 Compact
Contributors
AnGrY sCoTsMaN, jenkins-84
Source Code: https://github.com/NOSP-LP
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: UNLOCKED BOOTLOADER
Based On: AOSP,SLIM, CM12.1
Version Information
Status: Alpha
Created 2015-06-28
Last Updated 2015-07-12
Changelog:-
JULY 10TH
* Android release 6
* Ad blocker
* Unknown sources enabled by default
* Appops accessible from security
* Selinux switcher in dev settings
* Restart System UI in dev settings
* Live volume steps in advanced volume settings
* Battery bug in settings fixed
Screenshots (I have a custom layers theme applied, but you get the idea of what's include)
Nice to see your thread up bud [emoji106] thanks testing the ROM out and maintaining it too [emoji12] hope z3c users will enjoy NOSP too....
Sent from my One using Tapatalk
Thanks for the new ROM for our brilliant little Z3c's. Is the Ambient Display working on Z3c under this ROM?
Thanks.
Cr1ms0n said:
Thanks for the new ROM for our brilliant little Z3c's. Is the Ambient Display working on Z3c under this ROM?
Thanks.
Click to expand...
Click to collapse
Not at the moment but this is the first build for your device hopefully fixes like that will come in up coming updates too
Sounds awesome, just curious about the camera (hate to be that guy), is it still distorted? And can it be launched/lock focus+exposure using the camera button?
@mtsfilms yeah, still have camera issues but only noticeable on square/rectangular objects from a distance. Fine fore portrait and selfies imo. Camera can be launched with dedicated camera button but cannot be used to capture pic.
Cheers
Sent from my Xperia Z3C using Tapatalk
AnGrY sCoTsMaN said:
@mtsfilms yeah, still have camera issues but only noticeable on square/rectangular objects from a distance. Fine fore portrait and selfies imo. Camera can be launched with dedicated camera button but cannot be used to capture pic.
Cheers
Sent from my Xperia Z3C using Tapatalk
Click to expand...
Click to collapse
Okay thanks mate
AnGrY sCoTsMaN said:
@mtsfilms yeah, still have camera issues but only noticeable on square/rectangular objects from a distance. Fine fore portrait and selfies imo. Camera can be launched with dedicated camera button but cannot be used to capture pic.
Cheers
Sent from my Xperia Z3C using Tapatalk
Click to expand...
Click to collapse
mtsfilms said:
Okay thanks mate
Click to expand...
Click to collapse
I flashed it anyway....and it's awesome. Nice work I'm a photographer and shoot films for a living though, so that distortion is noticeable in every instance, no matter what hehe...is it a thing that Sony need to address? Or something that just needs time and dedication to fix...or a bit of both? Sorry if my question seems nooby, it's because beyond flashing, I have no idea what I'm talking about here on XDA. Great forum though
tried this rom very nice one question, it seems long press volume buttons when screen is off to switch tracks feature is not present.. possible??
moly82 said:
tried this rom very nice one question, it seems long press volume buttons when screen is off to switch tracks feature is not present.. possible??
Click to expand...
Click to collapse
Cheers, I will look into it on a update thank you
Sent from my One using Tapatalk
AnGrY sCoTsMaN said:
* Make sure your on FOTAWRP RECOVERY https://www.androidfilehost.com/?fid=95916177934529111
Click to expand...
Click to collapse
What is this and how is it different from regular twrp?
I noticed there wasn't an official twrp listing for the Z3c anywhere, yet I have 2.8.7.0 installed through dual recovery.
But trying to flash this and another rom gave me the aries error
Flashes fine after getting the fota version, albeit the recovery messes up after the first boot into the rom where everything's diagonally distorted (unusable, but still responses to touch in the correct locations).
(why isn't there just a working and official twrp for the Z3c )
Sorry if this is commonish problems/questions, just got the Z3c yesterday, been outta this world for a few years haha.
mtsfilms said:
I flashed it anyway....and it's awesome. Nice work I'm a photographer and shoot films for a living though, so that distortion is noticeable in every instance, no matter what hehe...is it a thing that Sony need to address? Or something that just needs time and dedication to fix...or a bit of both? Sorry if my question seems nooby, it's because beyond flashing, I have no idea what I'm talking about here on XDA. Great forum though
Click to expand...
Click to collapse
Sory for late reply, been really busy. i feel @Myself5 explains the answer to your question better than i could here http://forum.xda-developers.com/z3-compact/orig-development/cm12-kernel12-22-2-2015-t3037663/page8
House3272 said:
What is this and how is it different from regular twrp?
I noticed there wasn't an official twrp listing for the Z3c anywhere, yet I have 2.8.7.0 installed through dual recovery.
But trying to flash this and another rom gave me the aries error
Flashes fine after getting the fota version, albeit the recovery messes up after the first boot into the rom where everything's diagonally distorted (unusable, but still responses to touch in the correct locations).
(why isn't there just a working and official twrp for the Z3c )
Sorry if this is commonish problems/questions, just got the Z3c yesterday, been outta this world for a few years haha.
Click to expand...
Click to collapse
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader this partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery!
twrp included in dual recovery wont work with cm based roms thats why its suggested to flash the fotatwrp, which works fine so i dont understand how you can say its unusable?
AnGrY sCoTsMaN said:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader this partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery!
twrp included in dual recovery wont work with cm based roms thats why its suggested to flash the fotatwrp, which works fine so i dont understand how you can say its unusable?
Click to expand...
Click to collapse
Thanks for the info! Looks like I got a bit of catching up to do~
In regards to Fota-TWRP not working, I most likely did something wrong.
Using the file linked through the 1st post, I was able to flash cm roms just fine, including this one. But after the initial flash, going back to the recovery looks like the attached pic.
No idea there.
Also, using this one: http://forum.xda-developers.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573 just bricks it, and then I have to use flashtool to reflash the one you included in fastboot mode, otherwise, I just get vibration, no sony logo or anything.
Is there a sensitive order/flash methodology that is essential to get things to work?
I can get back to a rooted and unlocked/locked stock 5.0 state with dual recovery.
From then on, I'm probably working off of more assumptions than I should.
AnGrY sCoTsMaN said:
Sory for late reply, been really busy. i feel @Myself5 explains the answer to your question better than i could here http://forum.xda-developers.com/z3-compact/orig-development/cm12-kernel12-22-2-2015-t3037663/page8
Click to expand...
Click to collapse
thanks. that's a real pity because in such conditions camera can't be used at all, and I need it daily so I can't stay with custom, have to keep stock because of this problem :crying:
so the only hope is a fix from sony?
pardon my ignorance, but it is not possible maybe to use cam drivers from other phones with wideangle sensors running cm? all wideangle phones have this problem in custom rom? can't believe that?! :crying::silly:
Thank's for a nice rom! Here's my feedback after using it for a few days.
Bugs:
Navbar in homescreen randomly turns opaque. It happens seldom and I can't find a pettern to reproduce it either. Going to launcher settings and back will make it transparent again
ADB over network isn't working
If there's a notification, swiping it in lockscreen (to enlarge) will allow Quick Settings to be pulled down in a secure lockscreen
Usb connection options: charging only doesn't work (and there's no option to mount sdcard as a mass storage device)
Cellular networks > Carrier settings causes com.android.phone to stop and connection is lost. Hado to reboot to get connection back
APM can't be disabled from power menu and the indicator falsely stays active after disabling it in settings
Feature requests:
Additional dictionaries (Using Finnish)
Option to disable alarm icon in statusbar
Option to edit default lockscreen shortcuts
Quick pulldown width
Unlock pattern options (hiding dots, error..)
Editing power menu items
Other:
When using expanded desktop mode, swiping to activate nav-/statusbar swipes the active app also. In CM only the bar is shown while the active app stays untouched
It would be better to have Kernel Adiutor as a separate app. Now I can't have it running in the background if I want to edit other settings and also there's currently no way to have a shortcut for the app itself
A minor thing, but when a sim pin is required, it would be nice to boot directly to the numberpad. Currently I first have to swipe to unlock, enter sim pin, swipe again to unlock and then enter lock pattern
If you need a logcat or other more detailed info, pelase ask and I'll try to provide them! Cheers.
Edit: Couldn't get M5 kernel to work with this rom. Any plain reason for it (as this one uses cm kernel?). Hope I can get the info forwarded to Myself5 if it's something trivial as I would like to have a bit more control over the things going on
OK mate, I'm trying to reproduce some of your issues but am currently at work so limited to what I can try.
What launcher you using, do you have xposed installed and have you applied a layers theme?
Sent from my Xperia Z3C using Tapatalk
AnGrY sCoTsMaN said:
OK mate, I'm trying to reproduce some of your issues but am currently at work so limited to what I can try.
What launcher you using, do you have xposed installed and have you applied a layers theme?
Sent from my Xperia Z3C using Tapatalk
Click to expand...
Click to collapse
I'm using the default launcher and actually now that I think about it, after installing a theme I've not seen it happen again. So, default launcher, default theme, navbar resized. That's all I did I guess..
Edit: it could also be that something i did required a reboot, I haven't had the navbar problem today?
OK, I've reflashed rom and been running it for last 5hrs trying to replicate your issues . messed about with navbar height, APM, network services, settings etc etc...... I'm not getting any issues, it's all fine my end Bro. Adb over network, I never tested as I don't use it. The USB charging only issue I confirm is there but it still charges. With regards to your extended desktop issue, I can only assume that you've reduced the height of your softkeys/statusbar (navbar) too small and that's what's causing the issue (too small for touch interface to determine what your trying to do) anyways as for request: I'll pass it on to the creator of NOSP and see if he wants to add them to his rom.
Cheers
Sent from my Xperia Z3C using Tapatalk
ANNOUNCEMENTS
This kernel is already included in AICP, and it will not work on ROMs which use Nougat bootloader(RR by AndropaX, LAOS 14.1 by HnT).
KERNEL DEVELOPMENT
After the problems the entire community encountered using kernels based on Xiaomi's release, like the battery problems and various other issues, I decided to ask for help from the community in developing a stable kernel from the ground-up.
I've been working on this by myself for a while, but i can't test it alone.
This operation will most likely benefit all custom ROMs.
#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.
*/
Click to expand...
Click to collapse
SOURCE
https://github.com/Demon000/kernel_xiaomi_libra
DOWNLOAD
https://drive.google.com/open?id=0B4gtFsm9Zjb5eFJHLWJIQlFGUEE
Works on any rom except MIUI.
BUGS
vibration slider
FIXED
inaccurate battery percentage after restart
touchscreen not working on the edges
shutdown at low percentage
random reboots
improved camera
TASK
test the kernel
report bugs and get logs if you can
provide suggestions and improvements
be patient
test for user experience, battery life and stability, we are not doing a "who gets the highest Antutu score" race
Please only report bugs if you can't find an issue already opened here, https://github.com/Demon000/kernel_xiaomi_libra/issues .
Thanks!
I've been waiting for something like this. Flashing right away
Edit 1:
First report:
Double tap to wake is not working
solis_f said:
I've been waiting for something like this. Flashing right away
Edit 1:
First report:
Double tap to wake is not working
Click to expand...
Click to collapse
It's related to kumajaya's device tree modifications, and I'm waiting for someone to report not working touchscreen before adding his changes.
Cozzmy13 said:
It's related to kumajaya's device tree modifications, and I'm waiting for someone to report not working touchscreen before adding his changes.
Click to expand...
Click to collapse
If there is anything you want me to check (brute-force, crash test etc.) or anything in particular, it's easier for us to make a check-list in the first post so that we know what are we looking for !
solis_f said:
If there is anything you want me to check (brute-force, crash test etc.) or anything in particular, it's easier for us to make a check-list in the first post so that we know what are we looking for !
Click to expand...
Click to collapse
We're not looking for something particular, we're looking for general user experience, stability and battery life.
I updated the OP.
Well if we take Andropax's kernel as a baseline, this kernel must have somewhat near (of not the same) amount of features like sound controls, display controls and adreno idler
solis_f said:
Well if we take Andropax's kernel as a baseline, this kernel must have somewhat near (of not the same) amount of features like sound controls, display controls and adreno idler
Click to expand...
Click to collapse
We can focus on adding features after we get the kernel to work perfectly.
I'll add adreno_idler cause it might improve battery life.
@Cozzmy13 didn't realize you created this thread and was typing in cm14 one. Nice!. Let me know what device part needs to be changed to go inline with the kernel.
Officiak Aicp line compatibility with this kernel since next Thursday.
Just a question -- which ROM can I use to test the kernel?
Update:
When left at screen off for a small period of time, I can not unlock the phone and I have to screen off/screen on again. The reason this is happening seems to be some kind of problem with sliding gesture only registering first and last touch location and some random ghost touches. Just confirmed this with "show taps" option
Installed, I'd be delighted if it solves my battery issues. Will test and report back
solis_f said:
Update:
When left at screen off for a small period of time, I can not unlock the phone and I have to screen off/screen on again. The reason this is happening seems to be some kind of problem with sliding gesture only registering first and last touch location and some random ghost touches. Just confirmed this with "show taps" option
Click to expand...
Click to collapse
I have seen a commit that fixes this somewhere, I just don't remember where, will look for it and make a new build tomorrow.
Phlogistol said:
Just a question -- which ROM can I use to test the kernel?
Click to expand...
Click to collapse
Any ROM, it only patches the kernel and keeps the existing ramdisk.
Remember to backup your boot partition before installing.
helmat said:
Installed, I'd be delighted if it solves my battery issues. Will test and report back
Click to expand...
Click to collapse
One user reported that battery percentage doesn't decrease drastically after restart anymore.
I also think that the phone won't shutdown randomly anymore.
csolanol said:
@Cozzmy13 didn't realize you created this thread and was typing in cm14 one. Nice!. Let me know what device part needs to be changed to go inline with the kernel.
Officiak Aicp line compatibility with this kernel since next Thursday.
Click to expand...
Click to collapse
Find any instance of this inside the device repo
/proc/touchscreen/double_tap_enable
and replace it with
/sys/class/input/input1/wake_gesture
Also find any instance of
/proc/touchscreen/nav_button_enable
and replace it with
/sys/class/input/input1/0dbutton
Make a test build and check if double tap to wake works and if the hardware buttons can be disabled.
I'll have to add edge tap to the kernel then I'll rewrite the edge tap package inside the device tree and send it back to you.
If you don't have time to change those I'll fork your repo and change them myself tomorrow so you can merge it. I can't build the ROM because of bad internet connection so you'll have to test changes for me.
Thanks for the support, buddy!
Thanks a lot for your work, Cozzmy13.
From your fixes all roms can profit.
Cozzmy13 said:
One user reported that battery percentage doesn't decrease drastically after restart anymore.
I also think that the phone won't shutdown randomly anymore.
Click to expand...
Click to collapse
that would be amazing
First impression is good, not as smooth as before but very useable
Just one major issue - out of the three hardware buttons only the back button is working, no response from Home or Menu. I'm using the software buttons for the time.
helmat said:
that would be amazing
First impression is good, not as smooth as before but very useable
Just one major issue - out of the three hardware buttons only the back button is working, no response from Home or Menu. I'm using the software buttons for the time.
Click to expand...
Click to collapse
I am trying to find what's the source of the bug, it's harder to track this one.
Cozzmy13 said:
Find any instance of this inside the device repo
/proc/touchscreen/double_tap_enable
and replace it with
/sys/class/input/input1/wake_gesture
Also find any instance of
/proc/touchscreen/nav_button_enable
and replace it with
/sys/class/input/input1/0dbutton
Make a test build and check if double tap to wake works and if the hardware buttons can be disabled.
I'll have to add edge tap to the kernel then I'll rewrite the edge tap package inside the device tree and send it back to you.
If you don't have time to change those I'll fork your repo and change them myself tomorrow so you can merge it. I can't build the ROM because of bad internet connection so you'll have to test changes for me.
Thanks for the support, buddy!
Click to expand...
Click to collapse
Thanks, will do it tomorrow morning. Night of work today, have to patch some systems [emoji53]
Edit: changes done but can't build tonight.
FYI: For edge touch we are using /proc/touchscreen/edge_touch_mode now.
csolanol said:
Thanks, will do it tomorrow morning. Night of work today, have to patch some systems [emoji53]
Edit: changes done but can't build tonight.
FYI: For edge touch we are using /proc/touchscreen/edge_touch_mode now.
Click to expand...
Click to collapse
https://github.com/reposte/android_...src/com/cyanogenmod/settings/extra/Utils.java
In getInputControlPath
Replace /proc/touchscreen with /sys/class/input/input1/
In setActiveEdgeMode
Replace edge_touch_mode with edge_tap
And writeLine(path, (state ? "2" : "0")); with writeLine(path, state);
I will see if I can implement those changes in the kernel too.
If anyone reports not working touchscreen we will have to revert back to the original implementation.