http://www.androidpolice.com/2012/11/13/breaking-android-4-2-being-released-to-aosp/
I know, it's just out so we can't be sure of anything. But I was wondering if CM11 was planned for the 10.1v if it doesn't ask for too much efforts. It's a 4.x update so I would guess it won't break a lot of things. But who knows. The CM10 are still considered experimental after all although they are quite stable, so it might not happen officially ?
So many questions, so much patience to have that I don't...:laugh:
DannyBiker said:
http://www.androidpolice.com/2012/11/13/breaking-android-4-2-being-released-to-aosp/
I know, it's just out so we can't be sure of anything. But I was wondering if CM11 was planned for the 10.1v if it doesn't ask for too much efforts. It's a 4.x update so I would guess it won't break a lot of things. But who knows. The CM10 are still considered experimental after all although they are quite stable, so it might not happen officially ?
So many questions, so much patience to have that I don't...:laugh:
Click to expand...
Click to collapse
I dont think that 4.2 is going to be CM11. Its still Jelly bean after all. I think that our only hope is that its as simple as updating the sources used to compile CM10. Then theoretically it should just slot right in there, the way that 4.1.2 did (although I dont know the actual required work in getting our device from 4.1.1 to 4.1.2), and then hopefully Pershoot could just run a new experimental build for us. Im loving his last CM10 experimental by the way. I dont seem to be having any of the previously mentioned issues.
However, with the age of our device getting closer to two years, Pershoot has been a godsend (along with isimobile and also Seo's coding work previously), but I couldnt ask him to move onto the hassles of a whole new version for us, especially if its not a simple change.
Yeah, if updating to 4.2 would ask too much work, at least to get a stable release, I wouldn't mind that all the effort are focused on bringing a final 4.1 rom for the tab and end development for it. If 4.2 is possible, that'd be great but I guess it would be the last version for us.
All in all, we won't ever be grateful enough for what you do for us pershoot. I know you don't want donations, so I'll just donate to CM instead...
4.2 has changes in Surface Flinger to support multiple screens. I made quick build for P3 and out of the box 4.2 is not compatible with current Nvidia binaries, surface flinger hangs at "create window surface". So unless we can mend 4.2 surface flinger to work with ICS nvidia binaries, this could be end of the road for Tegra 2 devices. Since Google ditched Xoom, hope is even smaller... Other option would be port 4.1.2 Surface Flinger to 4.2....could be useful for other devices though...
Well I just hope then we'll be able to implement some content of 4.2 like the lockscreen, the timer app or the multi-account feature...:good:
with some hacks in Surface Flinger, I actually managed to get surfaces flinger initialized, and now boot animation is working so there might be still chance .... it crashed later on in multimedia though, so still plenty of work.
But yeah, would be nice to back port some 4.2 things, though it might be easier to move 4.1 surface flinger to 4.2, at least if graphic drivers proof to be main issue for upgrade...
Any idea on how simple users like me can help beside beta-testing when the time will come ? Are there devices that we might need to check out as they may help us with this port ?
Thanks !
EDIT : also, I imagine that after some point, you'll share your work with pershoot.
OndraOrg said:
with some hacks in Surface Flinger, I actually managed to get surfaces flinger initialized, and now boot animation is working so there might be still chance
Click to expand...
Click to collapse
Can you tell me what you've changed?
But yeah, would be nice to back port some 4.2 things, though it might be easier to move 4.1 surface flinger to 4.2, at least if graphic drivers proof to be main issue for upgrade...
Click to expand...
Click to collapse
I don't think that this will be easy. There are so much changes in surfaceflinger 4.2, especially the interface has changed. You would have to port the hwcomposer interface from 4.1, but leave the rest of the interface unchanged. Otherwise the rest frameworks/native breaks.
C-o-M said:
Can you tell me what you've changed?
New surface flinger was not loading grallock component at all. So I added in display device call to load grallock, then attempt to create main window surface succeeds. I also tweak api version bit, to accept current version, though I don't think that was the issue, grallock was the main problem. But I can't really confirm if this is enough, since there are more crashes along the line in other components, so all I can see is android boot animation. But surface flinger composition must be working to some degree. And there are no more obvious errors from Surface Flinger.
Now problem is in Audio flinger, which is another component quite modified, it makes some calls to audio_policy.tegra.so with ilegal parameters. So similar issue as with graphics. I commented out this call, but then Dalvik VM crashed with some weird error. Let's see when I have more time.
I don't think that this will be easy. There are so much changes in surfaceflinger 4.2, especially the interface has changed. You would have to port the hwcomposer interface from 4.1, but leave the rest of the interface unchanged. Otherwise the rest frameworks/native breaks.
Click to expand...
Click to collapse
Agree here. My motivation for surface flinger port was a) this effort could be useful also for other devices which were left behind for 4.2 upgrade. b) while new Surface Flinger has many changes, lot of them are related to new multi screen functionality. That could be stubbed on api level (binder interface doesn't actually have that many changes). I bet many ppl would prefer to have 4.2 functionality, and loose HDMI functionality.
Problem I can see is that we don't know how many components we would need to port like this. Seeing now crashes in Audio Flinger, this can be lot bigger issues. There is new bluetooth stack in 4.2, replacing Bluez. If those close code binaries are using Bluez and same api does not exist in 4.2, we're in trouble.
OndraOrg said:
New surface flinger was not loading grallock component at all. So I added in display device call to load grallock, then attempt to create main window surface succeeds. I also tweak api version bit, to accept current version, though I don't think that was the issue, grallock was the main problem. But I can't really confirm if this is enough, since there are more crashes along the line in other components, so all I can see is android boot animation. But surface flinger composition must be working to some degree. And there are no more obvious errors from Surface Flinger.
Click to expand...
Click to collapse
Thanks. I'll try do redo that.
C-o-M said:
Thanks. I'll try do redo that.
Click to expand...
Click to collapse
Let me know if it works for you, or I can share code...
C-o-M said:
Thanks. I'll try do redo that.
Click to expand...
Click to collapse
Actually it is working! Sorry I have just hour a day to play with this, that's why sporadic progress. Anyway after stubbing audio flinger and one call in dalvik, I managed to boot it. It's not usable since, since phone app crash report is all the time in the front. But UI is there. So that hack from surface flinger seems to be work after all
OndraOrg said:
Actually it is working! Sorry I have just hour a day to play with this, that's why sporadic progress. Anyway after stubbing audio flinger and one call in dalvik, I managed to boot it. It's not usable since, since phone app crash report is all the time in the front. But UI is there. So that hack from surface flinger seems to be work after all
Click to expand...
Click to collapse
That's awesome. Do you have a diff for me? Or even a git?
Slightly edited the title as you started messing around with it, although we all know it's just "to see where's it going" for now...
C-o-M said:
That's awesome. Do you have a diff for me? Or even a git?
Click to expand...
Click to collapse
Need to still sort one thing about status bar, whole UI is in phone mode (status bar with soft keys in the middle, and notification bar at the top) and then I can share install package. Ui and wifi works fine, bluetooth and audio does not work. And I still have some issue with storage mapping. This has now new layout thanks to multiuser support.
OndraOrg, I think you need to read a bit about 4.2 : Tablet UI is gone, Phone UI has been pushed to all Android devices.
See this : http://www.androidpolice.com/2012/1...just-like-a-giant-phones-and-thats-fantastic/
OndraOrg said:
Need to still sort one thing about status bar, whole UI is in phone mode (status bar with soft keys in the middle, and notification bar at the top) and then I can share install package. Ui and wifi works fine, bluetooth and audio does not work. And I still have some issue with storage mapping. This has now new layout thanks to multiuser support.
Click to expand...
Click to collapse
I'm not interested in the install package. I'd like to get the source code to experiment on my tab 8.9.
C-o-M said:
I'm not interested in the install package. I'd like to get the source code to experiment on my tab 8.9.
Click to expand...
Click to collapse
OK I will clean code and get you diffs.
C-o-M said:
I'm not interested in the install package. I'd like to get the source code to experiment on my tab 8.9.
Click to expand...
Click to collapse
Here are my patches.
Dalvik patch will get you around storage issue in vm. You can remove it once you fix your boot image
framework-av will patch you crash with audio, though it will make audio not to work. Not sure if you will need this for your 8.9 tab
framework-native will patch you surface flinger, so it works with old binaries
OndraOrg said:
Here are my patches.
Dalvik patch will get you around storage issue in vm. You can remove it once you fix your boot image
framework-av will patch you crash with audio, though it will make audio not to work. Not sure if you will need this for your 8.9 tab
framework-native will patch you surface flinger, so it works with old binaries
Click to expand...
Click to collapse
Nice. Thought it was more to change.
Related
I need a straight answer as it's possibly the one thing I can't figure out.
For eclair, NCommander fixed camera, but camcorder and video were broken from a straight build from AOSP.
CM later fixed these, but I never quite figured out how. Then everybody else started getting the camera fixed on their roms (by pulling a couple libs, I assume), but I myself couldn't figure out how the heck it was done, where an alternate source was available, or even an explanation of exactly what was broken/how it was fixed, etc. Same went for video playback/hw acceleration.
Now, on froyo, camera is broken again and NCommander's camera won't work either. It's been fixed by other people, but when I ask around, there seems to get a reluctance and I never really get an answer (and don't give me the "you're not asking the right question" line, I'm being pretty straightforward).
I need somebody here who has some knowledge as to why/how camera/hw is not working and how to fix it. I don't need libs. I need to know how to get the thing built from AOSP, why it breaks, and what I should look out for in the future, should it break again.
As far as I can tell, the problem is that the qcomm proprietary parts are outdated (for dream, last were 1.6 and eclair/froyo break compatibility with those libraries). Those libraries have to be linked-to at compile time of other hardware-libs and without the correct library, it won't build right.
What I don't get is: 1. which parts are missing, 2. where are people getting them from, 3. how do you add them to AOSP (other than PRODUCT_COPY_FILES) to get camera and all hw working right (including 3d acceleration).
Or maybe the project aurora community is better able/willing to help...
Bump. Totally interested. If OP already got an answer, please share.
Jubeh sorry I can't help you out I'm not a dev or a chef so I can't really give you any help. But I am interested in how your progress is going with this rom?
I found two sources for hardware files for the msm7k on our phones, including the camera and hw3d driver for dream. Also, building camera for AOSP seems to be fixed now. I'm just waiting from my battery to get here so that I can test. ebay parts from hong kong take forever.
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).
Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:
karlis1989 said:
Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:
Click to expand...
Click to collapse
The reason why it is that way is because there are 4G models of the DS7
giveen said:
The reason why it is that way is because there are 4G models of the DS7
Click to expand...
Click to collapse
Understandable, but since I have a Wi-Fi only version I wanted to know if It's possible to change this in form of a setting or a few lines inside a configuration file without involving compiling. I even faintly remember stumbling upon something like this on a CM9 version I had on my old Xperia MT15i Neo ... if only I could remember or find where or how (currently strolling through the developer and CM10 related menus) - deleted my Xperia related bookmarks when I sold it.
p.s. - people mentioned some problems with the on-screen keyboard disappearing as described in one of the posts on the main CM10.1 thread, I've noticed them myself too and they tend to be application specific ... it feels like the keyboard crashes or force-closes due to not enough memory, like in lighter applications the keyboard works fine, but when trying to use the keyboard for writing for example a post in the comments section in a website will most likely result in keyboard disappearing after first input character.
So I am still trying to figure out why you started a new thread about this and what your question is.
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.
I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out:
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.
Click to expand...
Click to collapse
... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.
karlis1989 said:
I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out: ... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.
Click to expand...
Click to collapse
I make it my special concern to answer questions, even if it with sarcasm
I'm not sure what more you can do besides deleting the phone. Comment out in build.prop the rild stuff
I wonder if he is referring to TabUI? Which I as well am trying to relocate the flash able .zip which enabled this display difference. I have been running cm10.1 2/12 because of the sensors not working on the 2/14 build.
Sorry to piggyback the thread, but is there an answer for where the tab ui .zip is for the 2/12 build?
Sent from my Galaxy Nexus using xda premium
Hi guys,
anyone got an idea why it itsn't possible AT ALL with Android 4.4 to post a picture on Facebook or other sites that allow uploading content?
The maximum reaction i get out of it is "failure opening file",it just doesn't work with any browser (tried Dolphin,Chrome,Firefox,Stock)
This happens on every 4.4 based ROM somehow,can't thank you enough for any input about this matter
edit: 85 views and not a single "yeah,i face the same problem" or "no problem on my side at all",whats up with that
edit2: it tested every 4.4 ROM now,not only CM11&CyanFox.Nowhere is the upload working trough Browser
Tlailaxu said:
Hi guys,
anyone got an idea why it itsn't possible AT ALL with Android 4.4 to post a picture on Facebook or other sites that allow uploading content?
The maximum reaction i get out of it is "failure opening file",it just doesn't work with any browser (tried Dolphin,Chrome,Firefox,Stock)
This happens on every 4.4 based ROM somehow,can't thank you enough for any input about this matter
edit: 85 views and not a single "yeah,i face the same problem" or "no problem on my side at all",whats up with that
edit2: it tested every 4.4 ROM now,not only CM11&CyanFox.Nowhere is the upload working trough Browser
Click to expand...
Click to collapse
Google made changes in KitKat replacing webkit with chromium webview and broke file upload, text reflow, etc. Basically web browsing is awful in KitKat, Google is aware but won't revert the changes. The only workaround at present is to use Opera Beta, or Firefox nightlies, there are other browsers with file upload but I would not recommend them at all if you don't want spyware. CM just implemented some changes on last night's nightly to fix file upload, but it's done nothing for me so far, still broken. At least the CM team is aware and willing to fix things.
http://review.cyanogenmod.org/#/c/58210/
http://review.cyanogenmod.org/#/c/58211/
Thank you for passing that info,this problem was/is driving me nuts and not reading anything about it other than my ramblings was the icing on the cake.
Maybe they can make it work again on CM
Tlailaxu said:
Thank you for passing that info,this problem was/is driving me nuts and not reading anything about it other than my ramblings was the icing on the cake.
Maybe they can make it work again on CM
Click to expand...
Click to collapse
I'd blame developers just as much as Google though. I understand it makes sense for them to use a web engine that Android provides for free and save time and money, but this is what happens when Google breaks something, suddenly 90% of browsers are broken. Firefox uses its own gecko engine and thus is unaffected, Opera shows a bit of spirit and patches chromium to fix these things, on the other hand. And then most people use apps instead of a browser to do things, so if some of us protest, it's not relevant.
Anyway, know that there are lots of complaints over at AOSP, but Google's reply is that these changes are intended and won't be reverted, so that's that.
Edit : "From what I understand the following is what is broken in KitKat webview :"
• text wrap no longer works
• cannot upload files
• cannot save passwords
• cannot force enable zoom
• no inverted rendering
• cannot play Flash videos (broken in 4.3 too)
Woa,the rabbithole goes deeper & deeper.I thought this was a weird bug that just happens with custom ROMS of not officially supported devices but reading that it comes from Google (and they saying "deal with it") pushes this to a whole new level.
Tlailaxu said:
... reading that it comes from Google (and they saying "deal with it")...
Click to expand...
Click to collapse
KitKat is such a kick in the ... for anyone developing on Android or just using it. Here's another jewel.
It looks like they're trying to restrict more and more things. The very reason many of us choose android over ios....
Sent from my GT-I9305 using xda app-developers app
Ultramanoid said:
KitKat is such a kick in the ... for anyone developing on Android or just using it. Here's another jewel.
Click to expand...
Click to collapse
This whole KitKat issue transforms to a scandal of some sort.If Google doesn`t change its current course,we will be on full lockdown like iOS in 2 or 3 revisions (Android 6 for example).This roadmap doesn`t make me happy at all
Hello there,
Since Android 10 is finally out in final version for our beloved Note 9 Exynos, how many of you are upgrading, and why? Also, for whom will choose to stick with Pie, again, why? And last, for those who are still on Oreo, what are you waiting for?
Personally, I didn't see that much new features that I really want to use right now. Mostly some tweakings here and there in some interfaces, but nothing really new, looks more like a modded version of Pie . I'm not a fan of the new gestures either, I think I'd keep the navbar anyway so... I'm gonna wait a moment before upgrading. And I'm mostly waiting for Swift Installer/substratum/Goodlock compatibility too, can't live without those
The thing I'd like to try out is DeX on PC, but again I don't really have a need for it. I'm more sad to lose Linux On Dex when I'll upgrade.
What are your opinions?
Mwyann said:
Hello there,
Since Android 10 is finally out in final version for our beloved Note 9 Exynos, how many of you are upgrading, and why? Also, for whom will choose to stick with Pie, again, why? And last, for those who are still on Oreo, what are you waiting for?
Personally, I didn't see that much new features that I really want to use right now. Mostly some tweakings here and there in some interfaces, but nothing really new, looks more like a modded version of Pie . I'm not a fan of the new gestures either, I think I'd keep the navbar anyway so... I'm gonna wait a moment before upgrading. And I'm mostly waiting for Swift Installer/substratum/Goodlock compatibility too, can't live without those
The thing I'd like to try out is DeX on PC, but again I don't really have a need for it. I'm more sad to lose Linux On Dex when I'll upgrade.
What are your opinions?
Click to expand...
Click to collapse
Still no upgrade here ? middle east user N960F/DS
There is no question about should you upgrade or not. Unless you want to keep vulnerabilities, you have to update to the newer OS (if any) to get the latest security fixes.
fabienpascal said:
There is no question about should you upgrade or not. Unless you want to keep vulnerabilities, you have to update to the newer OS (if any) to get the latest security fixes.
Click to expand...
Click to collapse
True. Or to get newer vulnerabilities ?
Will upgrade the second the official OTA drops. I'm a non-root user and have been waiting for the battery limiter feature that's finally present in One UI 2.0.
Edit: No toggleable charging cap in One UI 2.0. It seems the battery limiter means preventing draining your battery too low when using wireless power sharing in the S10 and up.
Waiting for a decent rom like The Galaxy Project to offer it. Only one so far is Dr Ketan's which won't even boot for me despite 3 clean download and install attempts.
FerretallicA said:
Waiting for a decent rom like The Galaxy Project to offer it. Only one so far is Dr Ketan's which won't even boot for me despite 3 clean download and install attempts.
Click to expand...
Click to collapse
Have you updated your bootloaders and modem files to the latest version?
It usually works with the bootloops.
all the best
Except dex on windows and say good bye to linux on dex, nothing really new.
Only one big problem, as samsung block you to revert back to a stable pie os version. Latest pie is a no with bootloader 4.
Its all marketing I see
I received it yesterday in Morocco, I was using VPN (Germany) but I can't confirm, it is a bless, smooth and new features, I tried dex on pc : amazing, I still need to Check the battery
Just a quick update, to tell that I've finally upgraded because the "new update" notification kept showing up and I got bored of it. It went pretty well, and I'm trying to get used to the new gestures after all, I'll see if I can use them nicely. I'm only afraid to be confused when using my older S7E which doesn't have those. I'm using Hexed+ as a replacement for Swift Installer, waiting for the latter to be updated. Also waiting for Goodlock apps to be updated (for example, to put the clock on the right side again).
No upgrade yet i m from The Balkans. Still waiting for the update OneUI 2
No upgrade. i am afraid of battery life. On pie april patch, my phone battery last longer than pie july patch. I am living with it. but i do not want to lose more juice of battery. will upgrade if battery life improves.
Mwyann said:
Just a quick update, to tell that I've finally upgraded because the "new update" notification kept showing up and I got bored of it. It went pretty well, and I'm trying to get used to the new gestures after all, I'll see if I can use them nicely. I'm only afraid to be confused when using my older S7E which doesn't have those. I'm using Hexed+ as a replacement for Swift Installer, waiting for the latter to be updated. Also waiting for Goodlock apps to be updated (for example, to put the clock on the right side again).
Click to expand...
Click to collapse
Can you confirm what else was working in pie and not working in Q ?
Also give a try with linux on dex.
For clock on right you can use systemui tuner.
Software update notification can be disabled too.
LucianGL30 said:
Can you confirm what else was working in pie and not working in Q ?
Also give a try with linux on dex.
For clock on right you can use systemui tuner.
Software update notification can be disabled too.
Click to expand...
Click to collapse
What's not working:
- Linux On Dex (displays an error like "you must be on latest firmware", so I guess it doesn't recognize the phone as compatible anymore, which is the case as I've read - it's a kernel issue)
- Substratum and other overlay systems like Swift Installer (you could still install unsigned overlays on Pie on the Note9 but that's a thing of the past now. Hopefully there's Synergy (https://play.google.com/store/apps/details?id=projekt.samsung.theme.compiler) which allows using some overlays by using themes - the Android 10/OneUI 2.0 compatibility is in progress).
- Some SystemUI controls, like the clock position (I've tested it all, even the tips involving right_clock_position)
- Good Lock, which isn't updated yet (and it should solve the clock position problem)
So fat that's the only things I miss on my Pie install. Most of them will simply become available again soon, or can be replaced by other means, so that's not so bad. About the new gestures though, I miss my browser shortcut I had setup with NavStar, and also I kinda don't like the wasted space it introduces to allow for gestures. Well, I'll see when NavStar is updated it I simply go back to the navigation bar (I'll be able to use some gestures with OneHand Operation +).
About Linux On Dex problem, on my rooted S7E I'm using Linux Deploy (https://play.google.com/store/apps/details?id=ru.meefik.linuxdeploy) but on my unrooted Note9 I'm currently trying a combo of Termux (https://play.google.com/store/apps/details?id=com.termux) and AnLinux (https://play.google.com/store/apps/details?id=exa.lnx.a).
And I couldn't disable the notification, didn't find a way to do it at the time. I guess now it's too late
Mwyann said:
What's not working:
- Linux On Dex (displays an error like "you must be on latest firmware", so I guess it doesn't recognize the phone as compatible anymore, which is the case as I've read - it's a kernel issue)
- Substratum and other overlay systems like Swift Installer (you could still install unsigned overlays on Pie on the Note9 but that's a thing of the past now. Hopefully there's Synergy (https://play.google.com/store/apps/details?id=projekt.samsung.theme.compiler) which allows using some overlays by using themes - the Android 10/OneUI 2.0 compatibility is in progress).
- Some SystemUI controls, like the clock position (I've tested it all, even the tips involving right_clock_position)
- Good Lock, which isn't updated yet (and it should solve the clock position problem)
So fat that's the only things I miss on my Pie install. Most of them will simply become available again soon, or can be replaced by other means, so that's not so bad. About the new gestures though, I miss my browser shortcut I had setup with NavStar, and also I kinda don't like the wasted space it introduces to allow for gestures. Well, I'll see when NavStar is updated it I simply go back to the navigation bar (I'll be able to use some gestures with OneHand Operation +).
About Linux On Dex problem, on my rooted S7E I'm using Linux Deploy (https://play.google.com/store/apps/details?id=ru.meefik.linuxdeploy) but on my unrooted Note9 I'm currently trying a combo of Termux (https://play.google.com/store/apps/details?id=com.termux) and AnLinux (https://play.google.com/store/apps/details?id=exa.lnx.a).
And I couldn't disable the notification, didn't find a way to do it at the time. I guess now it's too late
Click to expand...
Click to collapse
What about SystemUI Tuner , doesn't let you to move the clock? It's on play store.
For linux like ubuntu kali debian arch parrot fedora manjaro give a try with AndroNix ,same is on playstore.
For navbar, you can get back as in pie from settings.
LucianGL30 said:
What about SystemUI Tuner , doesn't let you to move the clock? It's on play store.
For linux like ubuntu kali debian arch parrot fedora manjaro give a try with AndroNix ,same is on playstore.
For navbar, you can get back as in pie from settings.
Click to expand...
Click to collapse
As I said in my reply, I did try SystemUI Tuner (I used it on Pie too), and it just doesn't work, the clock doesn't move anymore.
I indeed tried AndroNix and one of their optimized OS, it's good stuff
There was a adb command to move clock too
LucianGL30 said:
There was a adb command to move clock too
Click to expand...
Click to collapse
Looked for this too, but I always find commands that gives permissions to SystemUI, which doesn't really help If you have something to try out, I'd be happy (but if it involves the keyword right_clock_position I can already tell that it doesn't work)
Do not like an iOS like software experience thanks to Google wanting to copy Apple.
Mwyann said:
Just a quick update, to tell that I've finally upgraded because the "new update" notification kept showing up and I got bored of it. It went pretty well, and I'm trying to get used to the new gestures after all, I'll see if I can use them nicely. I'm only afraid to be confused when using my older S7E which doesn't have those. I'm using Hexed+ as a replacement for Swift Installer, waiting for the latter to be updated. Also waiting for Goodlock apps to be updated (for example, to put the clock on the right side again).
Click to expand...
Click to collapse
Updated and so far so good except that annoying white/ black bar at the bottom of Gboard . Any ideas on how to get rid of it ?